Operations | Monitoring | ITSM | DevOps | Cloud

OpenTelemetry instrumentation used to mean hours of manual work, wiring up metrics service by service. Now you can just ask for it. Tell an AI agent what you're trying to observe, something like "add OpenTelemetry so I can track this application's performance," and it turns that into an intent specification, then enriches your existing code with instrumentation to match. OpenTelemetry is open source and on GitHub. Pairing it with an AI agent that actually understands your codebase is what turns "add some metrics" into instrumentation that's useful.

Why Observability Systems Fail AI Code.

We spend thousands of dollars "token maxing" and running endless debugging cycles just to walk our LLMs through a problem. But is the AI actually failing, or are we just withholding the right environment? Giving your AI assistant its own sandbox to test hypotheses might just be the missing link in your development workflow.

We create AI. Give AI rules to follow. Then we get mad when it follows those rules. Sigh... New episode of Movies and Mainframes is out now.

Taylor Mattison explains how SigNoz MCP helped surface wasted work inside MSI's sales-order workflow. Warning checks were firing on user actions that had nothing to do with any warning they could raise. By comparing telemetry across the workflow, Taylor could point to unnecessary operations that were wasting API calls, database time, and server capacity. This clip is part of our MSI customer story on using SigNoz MCP with Claude to debug slow sales orders across the stack.