Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on Monitoring for Websites, Applications, APIs, Infrastructure, and other technologies.

How We Do Support at Scout

Today, we are taking a break from your regularly scheduled technical programming to talk about support. Here at Scout, we consider support one of our differentiators, and even as we adopt AI as a human multiplier behind the scenes, we are committed to keeping it real on the human-interaction side. It will be a long time, if ever, that you reach out to us and get a response from an AI agent. Would it be cheaper? Sure, but it isn’t up to our standards, and we won’t compromise on that.

The Best SKILL.md Is the One You Never Update - Meet Checkly's CLI

Most agent skills are static — frozen documentation snapshots that go stale the moment APIs change or flags get deprecated. Checkly does it differently. Our SKILL.md is just 100 lines of CLI pointers. No baked-in docs. Your coding agent learns what it needs, when it needs it, straight from the Checkly CLI.

Alert Acknowledgement: Mark It as Seen, Keep Working

If you’ve ever opened the alerts tab during a busy period, you know the problem. There are alerts you’ve already looked at, alerts someone on your team is handling, and alerts that fired on a known issue that’s being worked on. They all sit together in the same list alongside the new ones you haven’t seen yet.

Tech Talk | AI Agents in O11y Cloud

Transform reactive incident response with Splunk’s troubleshooting agents, designed to drastically reduce mean time to identify and resolve issues. This session demonstrates how a multi-agent approach empowers teams of all skill levels to pinpoint root causes, prioritize issues by business impact, and prevent future outages. Tech Talk sessions offer insightful and valuable deep-dives for any technical practitioner.

The Runbook Problem: How AURA Documents What Teams Don't Have Time to Write

Runbooks are rarely missing because teams don't value them. They're usually missing because incident response, follow-up, and platform work compete for the same limited time. By the time an issue is resolved, the knowledge is fresh, but the window to document it is already closing. That gap creates familiar failure modes: over-reliance on senior engineers, slower handoffs, and less confidence for whoever is on call next.

The History of AI in IT Operations: How We Got to Autonomous IT

Autonomous IT is the result of a long operational evolution, from static monitoring and rule-based automation to AIOps and now to systems that can increasingly diagnose, prioritize, and act within defined guardrails. Autonomous IT gets talked about like it appeared out of nowhere. As if someone flipped a switch and suddenly systems started managing themselves. The reality is far less dramatic and far more instructive. What we’re seeing today is the result of decades of incremental progress.