Operations | Monitoring | ITSM | DevOps | Cloud

Give one agent every tool and every incident is a question of trust. This one hands each job to a worker that can only reach what that job needs. One AURA configuration defines a coordinator and three specialist workers. Qdrant stores the runbooks, Prometheus measures workload health, and Kubernetes provides inspection and remediation, and each of the three is wired to one worker.

"Hey, I built this over the weekend. I want to get it in front of customers." And it always hits architecture, security, and infrastructure. Ross Hendrickson, CTO at Inspectiv, calls that gap the chasm. His team crosses it on Control Plane: AI-written code secured, reviewed, and released in a day. Control Plane combines AWS, GCP, Azure and your own hardware into one virtual cloud shaped to your workloads.

When should you reach for Grafana MCP? It’s one of the two “hands” in Grafana’s AI toolkit — and the easy one at that. MCP lets you bring Grafana into the tools you already use, like ChatGPT, Claude, or Cursor, without changing your workflow. No terminal? MCP. Want to stick with your favorite AI tool? MCP. Want easy tool discovery out of the box? MCP. Here’s where it fits, and when to use it — explained by Nicole van der Hoeven.

AI agents are moving fast. For enterprises, the bigger question is how to make them useful, trusted, and safe enough to take action. In this episode of Agents of IT, Zach Austin and Ian Coppock unpack what it takes to move from experimenting with AI to operationalizing agentic AI across the enterprise. They explore why organizations are racing to deploy AI before defining the problems they want to solve, why governance and scoped responsibilities are critical, and why the real value of AI comes from fixing and orchestrating the workflows underneath it.

Join Terry Chevalier, Founder and Managing Director, Sunstone Associates to explore why rural markets are emerging as AI hotspots, what Neocloud developers need, and how broadband providers can capitalize on this growing opportunity.

Six engineers, two QA, a product owner and a Scrum Master used to be a normal squad. With today's tooling, that's bloat. Teams are being rebuilt around three people. Not because the work got smaller — because agentic tooling absorbed the parts that needed all those hands. The engineer's job shifts from writing the code to directing the agents that write it, and owning the outcome that comes out the other end.