Operations | Monitoring | ITSM | DevOps | Cloud

Last month, we launched a new way to use our MCP server, released the Live Outage Map, brought Early Warning Signals to status page subscribers, passed 10,000 monitored services, added more ways to manage monitors in bulk, and much more. Here’s everything new in StatusGator this August.

Learn how MTTD, MTTA, and MTTR measure different stages of incident response, how to calculate Mean Time to Repair, and why measuring the complete incident lifecycle provides a clearer view of operational performance.

Every page view, click, and session your RUM SDK captures lands in Coralogix as a log event under the cx_rum subsystem — the raw data behind how people actually use your product. You can turn it into a shareable report without writing a single query. Just ask your coding agent. Your agent queries that data through the CX CLI and writes the report for you: describe what you want in plain English, get a formatted report back — without leaving the terminal.

Authored by Greg Janco, Engineering Manager at Mezmo I've always thought there was something backwards about incident response. An alert fires at 3 a.m. PagerDuty does its job. Somebody wakes up, grabs a laptop, connects to the VPN, opens the alert, and then starts answering the same basic questions we ask at the beginning of almost every incident. What changed? What else is broken? Have we seen this before? Some of those need a human eventually. A lot of the first pass doesn't.

Your uptime tool reports the site as available all month. Support reports something else, because customers in one region spent the morning unable to complete a checkout. Both records are accurate, and that is the problem. An external check confirms the page answered. It cannot tell you that the answer took nine seconds for everyone routed through one CDN edge, or what caused the delay.

Every number on your dashboards has a life story. It is born somewhere inside a running process, lives for a while as a few bytes in memory, travels across the network, settles down on a disk in some compressed shape, gets queried thousands of times, slowly loses its resolution as it ages, and is eventually deleted and forgotten forever.

Teams use AI coding agents and Bits Chat to troubleshoot systems and handle complex tasks, often uncovering repetitive work worth automating. But turning those routines into workflows can still require switching tools and recreating context manually. Through the Datadog MCP Server, Workflow Automation now lets you build workflows from Bits Chat or AI coding agents like Claude Code, Cursor, and Codex.