Operations | Monitoring | ITSM | DevOps | Cloud

Shipped: Catch a broken regex before it breaks your rules

Let’s say you want a Matches condition that picks up “prod”, “PROD”, and “Prod”, so you write ‘Matches: (?i)prod’ and check it in an online regex tester before publishing. It looks fine. Python accepts it, and so does JavaScript. Dimension Studio used to accept it too, and the rule is published. Then your data stops updating. The new pattern is what’s keeping it from materializing, but nothing tells you that.

Our 3-month AI roadmap - the future of smart dashboards

AI is set to transform our technology landscape. For many of us working in software, it already has — developers are now writing more code, building more features, and deploying more applications, faster. For the teams supporting IT and software services that means more applications to support, across a greater breadth of technologies, and with more complexity (that is probably less well understood by the developers who created it). Your operational tooling needs to keep pace.

A practical guide to React error monitoring

When designing effective error handling for React apps, the troubleshooting information you collect and display is critical. React errors can stem from a variety of causes, including user misconfiguration, backend and network issues, and mismatches in browser environments. Instrumenting your code to log critical context, including feature names, user data, and session activity, enables you to quickly identify where these errors originate.

Reproducing split brain on CloudNativePG

We run Postgres under an operator for automatic failover. That is a promise about what happens during a failure, so the only way to know you have it is to cause the failure and watch. The docs tell you what should happen. A config review tells you which knobs are set. Neither tells you how long an isolated primary keeps accepting writes after its replacement has been promoted, and that number decides whether a failover is clean or leaves you with two versions of your data.

Your AI Agents Can Take Action Now. Can You Prove They Should Have?

Enterprise AI agents clear every demo and pilot, then hit a compliance wall. The gap isn't technology—it's architecture. Discover why governance must sit inside the execution flow across six control points, not bolt on afterward as an afterthought at input and output only.

Model Rightsizer: the agent that stops your other agents from defaulting to Fable

Model Rightsizer is an open-source Claude Code sub-agent from CloudZero that scores each task on capability need versus cost pressure, then routes it to the smallest model that can handle it. In its first week, it cut Opus spend 75% while shifting 234x more work to Sonnet. Every Claude Code agent you run has to answer a question it usually never gets asked: does this task need the smartest model available, or are you paying Fable prices to rename a variable across three files?

A default is not a decision: cut AI model costs with CloudZero's free, open-source Model Rightsizer

Only 22% of finance leaders can tie their AI spend to a business outcome, according to CloudZero’s 2026 finance survey. When AI ROI falls short, it usually isn’t because a company is doing too much AI. It’s that no one is watching which model runs which task, and that one choice accounts for a large part of the cost. Here’s why it happens.

Automate all the things: How to use Grafana Cloud's AI to relieve the operational burden

Continuous integration and continuous delivery (CI/CD) have dramatically changed how we ship software. But once code reaches production, the operational work is still surprisingly manual. Engineers continually monitor systems, investigate unexpected behavior, and decide which issues require action. And that is where the next opportunity for AI-driven automation lies. For example, in today's CI/CD workflows, someone refreshes the pipeline page to see whether the queue has moved.

Honeycomb Named a Visionary in the 2026 Gartner Magic Quadrant for Observability Platforms

For the third consecutive year, Honeycomb has been recognized for its Ability to Execute and Completeness of Vision, and we believe for its strong vision around fast, flexible, high-cardinality querying that helps engineers understand not just that something broke, but why. The software development lifecycle has collapsed. The neat sequence of plan, build, test, and ship that teams have relied on for 20 years is now happening in a single afternoon. AI writes a large share of the code.