Operations | Monitoring | ITSM | DevOps | Cloud

Modern infrastructure is no longer a stack of routers, switches, and racks sitting in a single data center. Most teams now run a mix of Kubernetes clusters, virtual machines, managed cloud services, and SaaS dependencies spread across regions and providers. Knowing which device is up is not the same as knowing whether your application is healthy.

One of the most important realizations emerging across enterprise AI governance discussions is that most risky AI behavior is not malicious. Employees are typically trying to work faster. They are trying to summarize documents, accelerate research, draft communications, analyze spreadsheets, or automate repetitive tasks. In many cases, employees may not fully understand how AI providers handle uploaded information, what data policies apply, or where organizational compliance boundaries actually exist.

When you add a domain to a DNS monitor, the first question is simple: which records should it watch? Until now there were two answers, and both had a catch. Autodiscovery probes hundreds of common names — www, mail, _dmarc, the usual suspects — and it catches most of what real zones contain. But if you named a record something unusual, no wordlist in the world is going to guess it.

Every on-call engineer has lost an evening to some version of this. Something breaks; the fix is usually somewhere in the logs, and the logs are scattered everywhere: a dozen servers, a few containers, a couple of cloud services, none of them in one place. So, you SSH into one box, grep, get nothing, move to the next, and an hour later there are fifteen terminal tabs open and still no clear sequence of events. Log aggregation tools kill that scramble.

The new Advanced Pipeline Editor went live for all paid plans, we launched a public Blueprints library of ready-made pipeline patterns, we reworked plan pricing and raised the Free tier to 100 GB/day, and the source and processor catalog grew with an AWS Neuron source, an AWS CloudWatch metrics source, and a full set of XML processors. None of these are flashy on their own.

We’ve overhauled macOS monitoring in the latest Netdata release. Netdata already collects system metrics on Macs at per-second resolution; this release completes the picture with logs and hardware telemetry, areas that previously required users to run CLI tools like log show and powermetrics. The new collectors read this data through Apple’s own frameworks, allowing users to trace application and OS errors and catch hardware issues early.