Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on APIs, Mobile, AI, Machine Learning, IoT, Open Source and more!

Chaos Monkey Won't Find Your Bug

We shipped a chaos feature that never caused any chaos. Our mock server has had a fault-injection effect for years with a straightforward job: withhold the response entirely and see whether the caller copes. Last week I audited it against the actual code path. It had never withheld anything. The handler returned early without writing a response. Go’s net/http then did what it is designed to do, which is synthesize a 200 OK and flush the recorded body.

Virtana's Agentic AI

Anomaly Detection Isn’t Agentic AI. Detecting anomalies is table stakes. That’s pattern recognition. Agentic AI is different. It understands dependency chains, explains cause and recommends action. There’s a big gap between: “Something changed.” and “Here’s what broke and what to do next.” If your AI stops at anomaly scoring, you’re still doing the thinking.

Run an AI SRE Agent Entirely Inside AWS with Bedrock and S3: AURA

An on-call question returns the threshold and the escalation owner from your own runbooks, and the answer comes back without a call to anyone outside. AURA runs against Bedrock as its model provider, using Claude Sonnet 5 served by AWS in the same region. Authentication is the normal AWS credential chain: a profile on a laptop, an IAM role in EKS.

Debug AI agents wherever they run, from Slack bots to code review with Sentry's Agent Tracing

Agent Tracing shows the full execution path of an AI agent: the model call, every tool invocation and its arguments, token counts, cost, and the span where it broke. Same traces and spans you already use, with agent-specific attributes on top. Serge walks through three apps — a Next.js e-commerce agent using the AI SDK with a failing tool call, a Slack bot built with Eve that orders lunch, and a code review agent built with Flue over MCP.

Your Framework Doesn't Have to Be on Our List: How MCP Server Deployment Changes Everything

To deploy an application we haven't seen before, we need two things out of its repository. One is a Dockerfile that builds it. The other is a service definition saying what runs, which ports it listens on, which databases it needs, and what environment variables it expects. Customers arrive with a git URL, and we figure out the rest. We even do the tricky task of generating a Dockerfile if it doesn't already exist in the codebase. We've built a solution for this twice already.

Workspace now reads your tickets and automates the fix

IT teams don’t need another place to look for problems. They need a faster way to understand what is happening, decide what to do next, and act before disruption spreads. That has always been the promise of Workspace. It gives IT teams a conversational way to investigate issues, surface insights from Nexthink data, and understand what needs attention across the digital workplace. Now, Workspace is entering its next phase.

Advancing Semiconductor Manufacturing Through Intelligent Equipment Communication

In semiconductor manufacturing, reliable communication between production equipment and host systems is essential for maintaining efficiency, automation, and process consistency. As manufacturing environments become increasingly complex, standardised communication technologies have become critical in ensuring that equipment from different suppliers can operate together effectively. If you're looking to improve equipment connectivity and automation, explore solutions from SECS/GEM software providers to support reliable communication between manufacturing equipment and host systems.

12 Top SD-WAN Solutions for Growing Enterprises (2026)

Adding branches, cloud applications, contractors, and connected equipment changes the WAN problem. The network must steer traffic intelligently, preserve application quality during poor link conditions, and apply consistent controls without creating a separate operational stack at every location.