Operations | Monitoring | ITSM | DevOps | Cloud

Until now, someone on your team had to start every root cause analysis in Rollbar. An alert fires, they open the item, read enough of the stack trace to decide it deserves an investigation, and start the analysis by hand, after dropping whatever they were doing. With Agent Automation, Resolve, Rollbar’s AI agent for root cause analysis and fixes, takes over that step. You write a rule once in Project Settings, and when an error matches it, Resolve starts the analysis on its own.

When profits miss plan, marketing is the budget line most likely to be cut. The CMO Survey found that marketing expenses are cut 45.4% of the time in that scenario, more often than any other expense category. Most marketing teams have more data than ever. Finance still discounts much of it, because few of those numbers connect spend to business outcomes. The pressure is structural. Gartner’s 2026 CMO Spend Survey shows marketing budgets flat at 7.8% of company revenue.

The first CRA deadline is behind us. Now comes the opportunity to solve the engineering problem underneath it. When I worked with connected appliances at Electrolux, I learned something that is obvious to customers but sometimes less obvious to product organizations: Release day is not the end of product development. In many ways, it is the beginning of the longest and most unpredictable part of the product lifecycle.

The model your team relies on today is unlikely to be the one you're relying on a year from now. If your team's process for shipping AI-assisted code is built around a specific model, coding assistant, or a vendor's take on an autonomous agent, you are not building infrastructure. You are building something you will tear out and rebuild the next time the leaderboard shifts.

If you’re running FastAPI, you’re running Starlette underneath it, whether you think about it or not. At Scout, we spend a lot of time thinking about what happens at that ASGI layer, since that’s exactly where our Python agent hooks in to give you request-level visibility. Starlette 1.7.0 just landed, and it’s a release worth reading closely if you care about tracing, routing, or just keeping your app running on a supported dependency chain.

A few months ago, we launched Agent Timeline to close the gap between knowing an agent failed and understanding why. It took the tangled reality of a multi-agent, multi-trace workflow and rendered it as a single, readable conversation: every LLM call, tool invocation, handoff, and downstream system span laid out in the order they happened.

Earlier this year, we introduced more capabilities to support agents in production, a more chaotic, complex environment that requires a tremendous amount of context to understand. Unlike tools that capture shallow, pre-aggregated metrics, or cannot join a metric, trace, and log in one query, Honeycomb retains the context and connective tissue from telemetry data to build a nuanced view of production.