Operations | Monitoring | ITSM | DevOps | Cloud

We’ve released a new set of updates to help you reduce noise, customize your experience, and get clearer insights into your services. Here’s what’s new this month.

Knowing something is broken is easy. Figuring out why is hard. Introducing three new, native AI diagnostic capabilities in the Kentik Network Intelligence Platform to accelerate root cause analysis and keep your network running better.

What if the next breach in your cloud is already in motion, and your team has no idea how to see it? Cloud workloads are growing fast. APIs, identities, and data are spread across AWS, Azure, GCP, and on-prem systems all at once. Every layer creates its own logs, its own alerts, and its own blind spots. Most security teams are short on visibility, context, and time. That is the gap cloud threat detection is built to close.

In October 2023, security researchers published CVE-2023-46604, a CVSS 10.0 remote code execution vulnerability in Apache ActiveMQ. Within days, it was being actively exploited in ransomware campaigns. The attack required nothing more than network access to port 61616. No authentication, no credentials, no social engineering. The attacker connected to the standard ActiveMQ port and executed arbitrary code on the server.

When I read about the Vercel breach tied to a Context AI compromise, I wasn’t surprised. I’ve been talking with customers for a while now about how AI was going to introduce a new kind of supply chain risk. This is exactly what that looks like. What stands out to me is how familiar the pattern is. We saw it with open source, then again with SaaS, and again with cloud.

Monitoring coverage, anomaly detection, and SLO-based alerting have significantly narrowed detection windows for most failure types, but MTTD remains stubbornly high for a specific silent failure. This blog covers why type mismatches, swallowed exceptions, and values that pass validation without occurring without triggering errors, and what changes when your monitoring stack can generate those signals without waiting for a failure to surface them.

The new interface into production telemetry is a tool call, made from whichever agent runtime the operator happens to be using at that moment. A finance lead in Claude Code, a product manager in Cursor, an engineer in Codex. Three different jobs, three different agents, three different reasoning loops. The thing they have in common is the data layer underneath.