Operations | Monitoring | ITSM | DevOps | Cloud

An interview series with the people building Mezmo’s open-source agentic harness for production operations. Builder in the loop is a Mezmo interview series focused on the engineers, product leaders, and operators shaping AURA, our open-source, MCP-native agentic harness for production operations. The goal is to get past the polished product layer and talk through the decisions that matter when AI starts interacting with real systems. What should agents be allowed to do?

Every persistent message in ActiveMQ must survive a broker restart. That guarantee is the contract behind DeliveryMode.PERSISTENT is what separates a messaging system from a memory buffer. It is also what makes message persistence configuration the most consequential decision in ActiveMQ architecture.

AI coding tools turned every engineer into a 10x developer. Now your CI/CD pipeline is the bottleneck. Learn how to handle 10x more deploys per engineer with Qovery's dual deployment model. Romaric founded Qovery to make Kubernetes accessible to every engineering team. He writes about platform strategy, developer experience, and the future of cloud infrastructure.

Non-technical teams are building apps on Lovable, Bolt.new, and Replit with company data and zero governance. Here's why that's a compliance nightmare - and what enterprise platform teams should deploy instead. Romaric founded Qovery to make Kubernetes accessible to every engineering team. He writes about platform strategy, developer experience, and the future of cloud infrastructure.

Are you spending more time figuring out whose problem it is than actually fixing it? If that feels familiar, you are not alone. Many IT teams start their day with multiple dashboards and tools, yet still struggle to understand what is wrong when something breaks. Everything may look fine in one view, and fine in another, but the customer impact tells a different story. Incidents end up taking longer to resolve than they should. This is not about effort or capability.

Effective disaster recovery testing follows a clear three-phase lifecycle: plan, execute, and review. Most DR programs fail not because of missing tools, but because of untested runbooks and unclear ownership. Platforms like Harness Resilience Testing bring chaos, load, and DR testing into one pipeline so teams can catch risks before they become incidents. Most organizations don't fail at disaster recovery because they lack technology.

For the past year, I've been hearing a version of the same thing from engineering leaders: AI tools are working, productivity is up, the business case is there. And yet, something about the picture still feels incomplete. So we decided to go find out how widespread that feeling actually is. We surveyed 700 engineers and managers across five countries, and published the results in the State of Engineering Excellence 2026.

In 2024, Mark Boost, CEO at Civo, introduced the concept of ‘cloud parity’, a cloud computing approach that ensures a consistent, identical experience, feature set, and operational model across public, private, hybrid, and edge environments. “Cloud parity gives teams the freedom the cloud was supposed to deliver in the first place. It gives enterprises the sovereignty they need. It gives public sector bodies the clarity they require.

Today, we are going to look at a few things related to handling secrets. While Icinga 2 has no dedicated mechanisms for secret handling, there are a few tricks you can do with standard features. This is not meant as a step-by-step tutorial, but rather as an inspiration where you can adopt the ideas that make sense in your setup.