Operations | Monitoring | ITSM | DevOps | Cloud

In our previous post in our series on observability for the agent era, we looked at how Honeycomb provides unique visibility into LLMs operating in your production environment. Now, let’s flip it around and explore how Honeycomb provides observability insights uniquely suited to helping your AI agents rapidly diagnose and fix production issues, and build production feedback into the next round of development.

The agent era is here. Engineering teams are shipping AI-powered products, deploying multi-agent systems, and trying to figure out what observability even means for non-deterministic systems.

DNS Check now supports two features for Enterprise accounts that make it easier to work as a team: Team Members and Additional Email Recipients. Team Members lets multiple people log in and work with your DNS records using their own credentials. Additional Email Recipients sends notification emails to people who need to stay informed but don't need to log in.

Welcome to the March release roundup of VictoriaMetrics Stack, covering key enhancements in VictoriaMetrics and VictoriaLogs. These updates deliver improved UI scalability, enhanced authentication flexibility, improved query performance, and logging tools that streamline observability workflows in production environments. This roundup covers releases for.

Dozens of SaaS services you depend on, starting from Google Workspace and Slack to Shopify, may experience downtime, partial outages, or degraded performance. And most have their own status pages, APIs, or RSS feeds. Juggling all these sources is exhausting, and many teams suffer from alert fatigue, missed early warnings, and fragmented visibility.

Observability has evolved dramatically in the past decade. The industry has moved from basic uptime checks to full-stack observability (FSO), including metrics, logs, traces, and real user monitoring. Observability tools like ManageEngine FSO can detect anomalies in little time. And yet, outages still last longer than they should. Observability has matured. Response hasn’t. Most IT teams today have the tools to know when something breaks. But knowing is not the same as resolving.

Coroot already does eBPF-based CPU profiling for Java. It catches CPU hotspots well, but that's all it can do. Every time we looked at a GC pressure issue or a latency spike caused by lock contention, we could see something was wrong but not what. We wanted memory allocation and lock contention profiling. So we decided to add async-profiler support to coroot-node-agent. The goal: memory allocation and lock contention profiles for any HotSpot JVM, with zero code changes. Here's how we got there.