Operations | Monitoring | ITSM | DevOps | Cloud

Where did all my Claude Code tokens go?

Most teams judge their AI coding agent on two things: the monthly bill and a feeling. The bill tells you what you spent and the feeling tells you whether it seems to be helping, but neither one tells you what the agent actually did. As these tools move into the critical path of how software ships, that gap is starting to matter. I wanted to replace the feeling with something I could measure and understand what shapes of work affects this bill, so I decided to run an experiment on myself.

Designing the Operational Architecture for Continuous SLA Exposure Governance

Organizations seeking to reduce SLA volatility often attempt incremental enhancements to existing monitoring stacks. While additional analytics layers may improve telemetry visibility, exposure governance cannot function effectively when data, service context, and execution capabilities remain fragmented. Treating exposure management as an add-on capability limits its ability to protect across interdependent systems in real time.

Cortex catalog data now flows into Rootly

Incident response is a context problem. The first minutes of any incident are spent reconstructing what the affected service is, what it depends on, and who owns it. That reconstruction happens during the worst possible window. The Cortex catalog already holds this data: services, teams, domains, and the relationships between them, maintained by the engineers who run those systems.

The debugging crisis nobody's talking about: AI, abstraction, and the skills gap

Here's a scenario that's playing out in engineering teams across the industry right now. A developer uses AI to rapidly prototype a microservice. The code works. They deploy it to production. Six months later, something breaks. The system is under load, a database connection pools, and the service starts failing in subtle ways. The engineer pulls up the code, but here's the problem, they didn't write it. An AI assistant did. They don't understand the flow deeply. They don't know where to look first.

What's New in Network Observability for Summer 2026

As a network engineer, you likely face two persistent operational challenges every day: When you have to manually track device lifecycles on spreadsheets or spend your scheduled maintenance periods troubleshooting software upgrades, you lose the time you need to proactively ensure network performance. Over the past six months, we have continued to enhance Network Observability by Broadcom. These latest enhancements directly address the operational challenges outlined above.

Chart Your Team's Analytics Journey with Customizable Dashboards in DX NetOps

DX NetOps now features customizable dashboards that give all users some important new features and capabilities. In addition, with the solution’s new integration capabilities, DX NetOps enables users of current analytics and reporting tools to add standardized dashboards over time.

High Cardinality in ClickHouse at Scale: What Actually Breaks

ClickHouse swallows high-cardinality telemetry at ingest, then breaks at query time weeks later. Here is what fails, and how we keep it fast in production. Prathamesh works as an evangelist at Last9, runs SRE stories - where SRE and DevOps folks share their stories, and maintains o11y.wiki - a glossary of all terms related to observability.

How AI-First Operations Unlocks Compounding Engineering Productivity

Engineering teams have plenty of ideas, but they’re often short on time to act on them. As software systems grow more complex, an increasing share of engineering capacity is consumed by non-building activities: investigating alerts, coordinating fixes, and managing operational incidents. Every hour spent diagnosing failures is an hour not spent shipping features or experimenting with new product ideas. Over time, that lost capacity compounds.

Should you self-host your Git repos? We are, and here's why.

Git is decentralized by design, yet most organizations have funneled their entire source of truth (repositories, CI triggers, access control, release tooling) onto one third-party platform that nobody on the team operates or can inspect. That concentration was a fair trade when self-hosting meant adding massive capex overhead, but with modern architectures and platforms, that's no longer the case.

The 5 Best Custom Headwear Companies in Australia for Businesses and Events (Ranked & Reviewed)

Custom hats, caps, and beanies have become an essential marketing tool for businesses, sports clubs, charities, schools, and event organizers. A well-designed piece of branded headwear can increase brand visibility, create team unity, and leave a lasting impression on customers. As great as these can be, actually having them made can seem like a bit of an issue. Your business mightn't have the tools or expertise to create these, especially at scale. That's why finding the best custom headwear companies in Australia can be recommended.