20 Years of Dashboards. 20 Years of War Rooms.

I’ve spent the last two decades deep in network operations, application performance monitoring (APM), and observability. Across 18 years at HP and Cisco, and another 6 years at Dynatrace, I’ve worked with IT operations teams spanning NASDAQ, telecom, retail, and manufacturing.

Over that time, the industry was sold a persistent promise. First it was APM, then it was "Single Pane of Glass" dashboards, then it was AIOps. The pitch was always the same: this new tool will finally end the 3:00 AM war room.

But let’s be honest about what actually happened. The toil never stopped. The war rooms never ended.

Instead of unification, we got more fragmentation. We ended up with logs in Splunk or Elastic fighting for data ownership against observability platforms, cloud solutions, and GitOps pipelines. Everyone guards their own domain. Nobody has the full picture. And when a Sev-1 incident hits, teams are still manually scrambling to connect the dots across a dozen different screens.

I realized that traditional observability and ITSM had hit a wall. That is why I joined Ciroos.

The next generation of operations isn't about building another dashboard or fighting a political battle to force all your data into one massive, expensive lake. It’s about leveraging multi-agentic AI to cut through the noise and turn fragmented telemetry into actionable answers.

Ciroos is an AI SRE Teammate that acts exactly how a seasoned human expert would. It fetches data on demand from your existing observability tools, logging platforms, and Kubernetes environments—without copying or duplicating anything.

‍

‍

This zero-copy architecture means no data consolidation battles, no tool-to-tool migrations, and no domain ownership politics. Ciroos fetches what it needs, investigates the anomaly, correlates the signals across every domain, surfaces the true root cause, and then discards the data. Clean. Purposeful. Precise.

Your domain tools aren't going anywhere. Your engineers won't let go of Splunk, Grafana, or whatever they've built their workflows around—and they shouldn't have to. Ciroos doesn't ask you to rip and replace your stack. It asks you to finally connect the dots.

We need to stop normalizing late nights and reactive war rooms. It's time to put something in place that actually moves teams from chasing symptoms to resolving causation.

‍