Operations | Monitoring | ITSM | DevOps | Cloud

On May 27, the Apache ActiveMQ project shipped two releases on the same day: 5.19.7 and 6.2.6. Look at the changelogs side by side and the story is clear — this isn’t a feature drop. It’s a coordinated security-hardening pass applied to both maintained branches of ActiveMQ Classic at once, with the same fixes deliberately backported so that no supported line is left behind.

A single leaky application can crash your entire IBM MQ estate by consuming OS resources through unclosed connections. Traditional monitoring misses these silent killers. Learn how proactive observability detects OPPROCS anomalies before they trigger infrastructure failures.

If you manage endpoints for a living, you'll know the problem isn't a lack of data. It's that there's too much of it, scattered across too many places. A modern IT team or MSP might be looking after thousands of devices spread across dozens of customer organizations, each generating a constant stream of alerts, patch results, antivirus events and disk warnings. NinjaOne does a great job of collecting all of that.

Building automated workflows that adapt to real-world complexity can be a challenge. As systems scale and scenarios multiply, teams often end up hardcoding endless logic branches just to handle every potential outcome. That’s why we’re introducing Bits Agent Builder, a powerful new tool that lets you create custom AI agents that are fully hosted by Datadog.

You get an infrastructure alert. Something's off, so you task your agent to investigate, and it ends up grepping through the logs. You both wonder if there's customer impact. There’s a simple rule: AI agents in the incident loop are only as good as the signal you feed them. And logs alone aren't a great signal.

Enterprise IT was built for a more predictable workplace, where support began when an employee reported a problem and IT worked backward from the details they could provide. That model made sense when devices, applications, and ways of working were easier to control. Today, the digital workplace moves too quickly for IT to rely on reported issues alone. By the time a ticket appears, employees may have already lost time, worked around the problem, abandoned the tool, or turned to an unmanaged alternative.

For many operational time series workloads, machine learning can’t operate in the historical way, where data is compiled once and models are trained offline. Sensor readings, infrastructure metrics, application telemetry, energy data, industrial measurements, and financial ticks all share a basic property: the next datapoint is more useful when the system can respond to it immediately (or at least close to immediately).

Observability is how platform teams stop being the answer to every question and start building platforms that answer those questions themselves. This article explains specifically how observability enables platform engineers to support development teams better which reducing ticket volume, cutting MTTR, enabling SLO ownership, and making microservice debugging something devs can do without escalating to you.

Internet Performance Monitoring (IPM) provides end-to-end visibility into what happens between your infrastructure and your users, across networks and services you don’t own or control. The internet is your network now. Your apps live in the cloud, your users are everywhere, and the systems that deliver your applications and services to them use hundreds of providers, ISPs, and networks beyond your control. In practice, that means infrastructure monitoring is the foundation.

In the modern development landscape, we are seeing a shift in how work is managed. The rise of AI-assisted development and highly distributed teams means that work is moving faster than ever before. However, this increased velocity often comes with a hidden tax: complexity. We are seeing more parallel work streams, more intricate dependencies, and a constant stream of shifting priorities. In this environment, simply moving fast is not enough to guarantee success.