Operations | Monitoring | ITSM | DevOps | Cloud

Many “LLM observability with OpenTelemetry” tutorials stop at a single chat.completions span. That works for a demo, but it leaves gaps once an agent fans out into 30 tool calls, two vector-DB queries, three handoffs, and a 90-second tail latency you need to attribute. This post wires the OpenLIT SDK (50+ instrumentations, OTel GenAI semantic conventions, one line of code) into the full VictoriaMetrics observability stack and shows query examples that turn agent telemetry into decisions.

We are shipping a new batch of Icinga Web ecosystem releases today. Icinga Web 2.14 is the headline, bringing the baseline for two-factor authentication support, configurable password policies, a configurable Content Security Policy, and a round of developer tooling improvements that have been in the works for a while. Icinga Certificate Monitoring 1.4, Icinga Reporting 1.1, and Icinga PDF Export 0.13 join it with PHP 8.5 support across the board and a set of focused improvements for each module.

Let’s take a look at everything we launched in June. From new Chrome and Firefox browser extensions and API enhancements to powerful new integrations and our latest Early Warning Signals report, here’s what’s new in StatusGator.

June 2026 saw major outages across ecommerce, AI, developer tools, and business applications. StatusGator’s Early Warning Signals surfaced many of these incidents before providers updated their official status pages. Of the 1,067 incidents detected by StatusGator in June, only 191 (17.9%) were eventually acknowledged by providers.

Understanding a service outage is easier when you can see what it’s connected to. That’s why we’re introducing Relationships for Service Monitors, one of the most requested features from StatusGator’s hundreds of enterprise IT teams. You can now explore related services directly from the Service Details page by opening the Relationships dropdown.

Network performance metrics are real-time measurements of how data moves across your network, from speed and capacity to delay, loss, and reliability. Network performance metrics are the diagnostic layer between your infrastructure and your users. They explain why things are slow, dropped, or unreachable by capturing everything from how fast packets travel and how much bandwidth is in use to how often data gets dropped or delayed.

Monitoring load is not always steady. A team might add a new batch of checks or run several ad hoc tests during a rollout. When that happens, your Private Location agents need to pick up more work at once. If there aren’t enough agents available during a burst, checks start piling up in the queue, which can delay or disrupt check execution. But solving this by running a high number of agents around the clock has the opposite problem: most of that capacity sits idle until the next busy period.

A lesson we’ve learned in experimentation at Datadog is how easy it is to fall into interpretative pitfalls even when following rigorous conventions. For example, consider an experimentation program that appears to do everything right on the surface.

This is a guest post by Dan Mindru, a Frontend Developer and Designer who is also the co-host of the Morning Maker Show. Dan is currently developing a number of applications including PageUI, Clobbr, and CronTool. It feels like with every release, we are walking a tightrope. We need to keep our app lightweight, stable, and performant, all the while depending on APIs that can shift at any moment (without warning, too!).