Operations | Monitoring | ITSM | DevOps | Cloud

Enterprise AI isn't broken; your data is broken

A friend who runs data engineering at a mid-sized logistics company once showed me something that made me laugh, and then made me a little sad. Her team spent four months building a chatbot that was supposed to answer simple questions like "how many shipments are delayed in the Chennai warehouse right now." The bot worked beautifully in the demo. Then someone asked it a real question, and it confidently returned a number that was off by almost a factor of ten. Not because the model was dumb.

Where Historians Fall Short for Physical AI

Summary Physical AI—machines and industrial systems that sense conditions, reason, and act in the real world—needs two things from operational data: detailed history for training, and real-time telemetry for inference. Traditional data historians weren’t built for either at the speed Physical AI requires. Four gaps result: limited real-time access, compression that strips model-relevant signal, IT/OT fragmentation, and site-by-site architectures.

Building an AI Observability Agent: Lessons from the Trenches - Stripe at O11yCon 2026

Stripe shares lessons from building an incident investigation agent, from context-window blowups to why the final 5% still needs a human. In this O11yCon 2026 talk, they dig into what it takes to go from 'it works' to 'it works reliably,' including how pointing agents at like Honeycomb's speeds up on-call investigations.

How to automate artifact cleanup in Harness Artifact Registry without breaking production | Harness Blog

AI is changing artifact management in two ways at once. Every AI-generated pull request, dependency update, and automated build creates more container images, packages, and Helm charts than ever before. Registries are growing faster than engineering teams can manage them, driving up storage costs and leaving thousands of stale artifacts behind. At the same time, the cost of deleting the wrong artifact has never been higher.

The AI Hack Nobody Told You About

AI agents are now hacking on their own — and it already happened to two of the world's biggest AI labs. OpenAI's models broke out of a test sandbox, exploited a vulnerability, and hit Hugging Face's production systems. Days later, Anthropic reviewed over 141,000 evaluation runs and found three of its own Claude models had done the exact same thing to three different organizations.

Agent security starts with where the agent runs, not how it behaves

When engineering teams evaluate AI agents, the first questions are usually about capability. Which model performs best? How much faster can it write code? What's the return on investment? Security, if it enters the conversation at all, tends to come later. Patrick Dawkins, Principal Software Engineer at Upsun, thinks that's backward. Over the past year, he's been building the infrastructure that enables AI agents to operate safely within engineering teams.

Railway Mania, the birth of the S&P 500, and the lesson for the AI era

In 1846, Britain poured roughly 7% of its national income into railways, proportionally about three times what the U.S. spends on AI infrastructure today. The technology delivered everything it promised, and a generation of investors still lost their shirts. What sorted the winners from the wreckage wasn't conviction about the technology; it was whether ROI was measured or asserted. The man who fixed that problem gave his name to the S&P 500.

How SigNoz MCP Helped MSI Find 20 Unnecessary Operations

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.