Operations | Monitoring | ITSM | DevOps | Cloud

Why Observability Systems Fail AI Code.

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.

We’re back with another roadmap stream! You might think to yourself, “Talking about 2027 already? Isn’t that a bit early? I’m still sweating and lying out by the pool!” But planning this far ahead will give you plenty of time to sort out priorities, talk to relevant parties, set your budget(s), and more. Having these discussions in August may feel extreme but the leaves will fall and the snow will pile up before you know it, so you might as well get started now!

Open source is the backbone of most software. But should developers trust OSS? npm, PyPI, and Maven don't vet packages before publication, so "publicly available" doesn't automatically mean "safe to pull right now." A secure OSS posture is to trust the ecosystem but verify at ingestion: route packages and dependencies through a controlled layer that runs scanning, age checks, and malware detection before anything reaches a build.

For every $1 you pay OpenAI or Anthropic, it's costing them about $1.60. AI is running at a loss — so is the whole business model broken? The full bill for AI hasn't landed yet. In this ShipTalk short, Field CTOs Adam and Martin break down the economics of generative AI: why the frontier labs lose money on every prompt, why they'd need to raise prices ~60% just to break even, and the bet the entire industry is making — that inference costs drop fast enough to catch up. Plus the Gartner forecast every CFO should see: by 2028, the AI bill could be bigger than the employment bill.

New enhancements to SRE Agent power faster triage, greater access controls, and more connectivity into existing systems. Watch this demo to learn more about them: SRE Agent on Escalation Policies (EA), Recommended Workflows (GA), Agent Connectors and Tools (GA) and PagerDuty Advance team-level permissions (GA).

We intentionally introduced a bug into our app to see what would happen. The agent used the CircleCI MCP Server to detect the failed pipeline, diagnose the issue from the build logs, implement a fix, and keep iterating until CI was green.

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.

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.