Operations | Monitoring | ITSM | DevOps | Cloud

Monitoring is built around the system a team understands at a point in time. Engineers add endpoints, move dependencies, and change user flows every day. Over time, that creates coverage drift as monitors keep reflecting the system as it used to behave, while changing paths introduce failure modes that teams didn’t yet know to watch for. Bits Detection automatically creates, tunes, and maintains monitors for your services.

Coding agents are good at reading a spec and producing code. But producing code is one step in a longer process. The real loop is Spec -> Code -> Deploy -> Test -> Verify -> Ship. Agents stop at step two. Romaric founded Qovery to make Kubernetes accessible to every engineering team. He writes about platform strategy, developer experience, and the future of cloud infrastructure.

There’s a lot happening across Asia Pacific right now. Enterprises are moving quickly to modernize operations, adopt AI, and manage growing complexity across increasingly distributed environments, and the opportunity ahead for LogicMonitor in the region continues to grow alongside it. That’s why I’m especially excited to welcome Dave Patnaik to LogicMonitor as our new Vice President of APAC.

Engineering teams lose hours in the gap between detecting a problem and getting a fix into review. An on-call engineer sees an error spike in Datadog, pivots to traces and logs to isolate the failure, opens the relevant repository, reproduces the issue, writes a fix, adds tests, waits on CI, and finally opens a pull request. Even when the problem is familiar, the workflow pulls engineers across several tools and stretches remediation from minutes into hours or days.

No matter how fast we build, we'll never integrate with every tool. There are too many, new ones appear constantly, and some are too niche to ever reach the top of our roadmap. So if the tool you care about isn't supported yet, your options have been to wait for us to get to it, or build it yourself with our Web API plugin — a powerful, flexible option, though one that asks you to map out the endpoints, authentication and paging yourself.

The Harness VS Code Extension is now on the Marketplace. Monitor pipelines, debug logs, approve deployments, and query failures with Claude Code, Copilot, or Cursor, without leaving VS Code. Your Harness pipelines, logs, and deployment approvals are now a sidebar panel away inside VS Code. The Harness VS Code Extension is live on the VS Code Marketplace today, no.vsix download, no manual install.

The promise of agentic AI is dead simple to understand. Instead of waiting for a human to draft every instruction, an AI agent can interpret a goal, take action, and work across systems until the task is done. For IT teams, that motion sounds like the next logical phase of automation. That promise is real... but it’s also where the risk starts. Traditional automation followed instructions. Agentic AI, by contrast, pursues outcomes. That difference turns the entire governance model on its head.

A few months ago, Steve Yegge published his 8 levels of AI-assisted development, and it clicked the moment I read it, because I had lived that exact progression myself, moving from autocomplete to running agents one step at a time. Framed as an AI trust gradient, it finally gave the industry a vocabulary for something most of us were already going through without a name for it. If you haven’t read it, save it for later.