Operations | Monitoring | ITSM | DevOps | Cloud

AI agents fail differently from the software we spent the last two decades learning to monitor. We hear some version of the same story from teams shipping agents to production: an agent starts producing wrong answers. Not obviously broken: confident, well-formatted, plausible wrong. The logs are clean, latency looks healthy, and error rates sit at zero. Nothing flags a problem. A user eventually does.

---‍Key Takeaway: Today, we're launching the public beta of the Harness CLI: the single, officially supported command-line tool for the entire Harness platform. It replaces the older per-module CLIs with one binary, one grammar, and one auth flow across pipelines, CD, code, artifacts, IaCM, feature flags, governance, and audit. Designed for secure DevSecOps and enables terminal workflows for developers and deterministic execution for AI agents. ---

The Advanced Pipeline Editor is now live for all paid Bindplane plans. It's a rebuilt configuration editing experience that puts your whole config in a single interactive graph: every source, processor, router, and destination, across logs, metrics, and traces, in one view you can search, pan, zoom, and edit directly. If you've ever bounced between pipeline tabs trying to figure out where a processor sits in a config with a dozen sources and three destinations, this release is for you.

Cardinality problems usually begin with a small change that looks harmless: you add a label, and suddenly one metric turns into thousands of unique series. Cardinality explosions are often caught only after performance degrades. And at that point, your observability stack may be degraded and painful to troubleshoot. vmestimator is a new project specifically designed to follow cardinality trends in real time and send you alerts before they turn into a real problem.

An API latency spike hits your checkout service, and within ninety seconds your on-call phone won't stop buzzing. A CPU threshold breaches. A database connection pool exhausts. A pod restarts. An error rate crosses 5% on a downstream service. Six engineers get paged inside four minutes. Forty alerts. Seven services. One incident. Every monitoring tool in the stack is doing exactly what it was configured to do, telling you that something is wrong.

We are releasing Icinga TOTP Web v1.0.0, which adds Time-based One-Time Password (TOTP) two-factor authentication to Icinga Web.

Today, we are pleased to announce the release of CFEngine 3.28.0! The code word for this release is introspection. This is a non-LTS, not supported, feature release, with features which will become part of the next LTS scheduled for summer 2027.

Today, we’re excited to announce that Boost is moving out of beta and into public preview. After months of building, breaking, and rebuilding inside JFrog’s own R&D organization, Boost is ready for the world. If you are currently running into token limits, unpredictable costs, or runaway usage from AI agents, Boost was built for you. It has already helped our teams reduce token spend while maintaining performance.

Merge conflicts rarely make it into a sprint retrospective, but they should. They’re one of the most reliable ways to lose an hour of flow without anyone noticing it’s gone. Every developer expects them eventually, but almost nobody questions the workflow around resolving them.

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.