OpenSRE

OpenSRE just hit 5,000 stars on GitHub! ⭐ What started as an idea is now a community of thousands building, contributing, and shipping together. Thank you all! Lots more to come. 🚀 github.com/Tracer-Cloud/o…

Turns out the best product feedback doesn't come from surveys. It comes from an SRE sharing their screen on a Thursday community call saying "this is where it lost me." Last call we covered: live investigation demos, a walkthrough of the benchmark results, and maintainers digging into where the loop still gets stuck. Thanks to everyone who showed up. Next one's Thursday 23rd, the invite's in the Discord: discord.com/invite/opensre ✉️

@sahildarz Exactly that, the weird ones are always where the learning is. Nobody writes a postmortem about the failure that behaved exactly like the docs said it would.

@open_sre Seen it with Spine and Laravel, weird failures are where the real expertise lies, not just model size.

Unpopular opinion: the best AI infrastructure tools won't come from the big labs. They'll come from open source. 🛠️ Labs never see the weird failures, the vendor-specific ones, the ones that only happen at your company. A community does. The labs have the models. The community has the failures. The failures are the moat. 🏰

We recently ran a 7-day hackathon. 🛠️ → A pipeline rewrite shipped at 2:30am. → 10 PRs merged in a day. 23 total. → +36pts on the hardest Kubernetes failure category. +400 GitHub ⭐ in 7 days. This is what building in public looks like. See you at the next one! 🚀 github.com/Tracer-Cloud/o…

We benchmarked OpenSRE against 452 broken Kubernetes clusters. Same GPT-4o model. Same tools. Only difference: the investigation loop. 🔍 Hardest fault type in the benchmark: OpenSRE scored 56% vs GPT-4o at 20%. That's what thinking harder looks like. 🚀 github.com/Tracer-Cloud/o…

Big shoutout to Greptile, our newest sponsor 🦎 Less guesswork navigating a codebase, more time actually fixing things, that's the instinct behind their tool, and it's one we share. Proud to have them in our corner as we keep building OpenSRE fully in the open. → github.com/Tracer-Cloud/o… → greptile.com

big two weeks for opensre ↓ • GitHub Actions - investigate CI/CD failures directly from your pipeline • xAI Grok added as an LLM provider • 6 new integrations: Azure SQL, MongoDB Atlas, Snowflake, Supabase, OpenObserve, Trello • Hermes eval suite - measure RCA evidence quality, not vibes • CLI: session resume, cleaner commands, silent errors fixed github.com/Tracer-Cloud/o…

@okadikeluc81 100%! 🚀 The momentum is real and we're just getting started!

@open_sre Big milestone—5,000 stars shows real momentum for OpenSRE. Now it’s all about sustaining quality as it scales.

OpenSRE just hit 5,000 stars on GitHub! ⭐ What started as an idea is now a community of thousands building, contributing, and shipping together. Thank you all! Lots more to come. 🚀 github.com/Tracer-Cloud/o…

@ChigoziOkorie @vincent_hus Of course! Head over to our GitHub and jump into the community, everyone's super helpful. github.com/Tracer-Cloud/o…

@open_sre @vincent_hus Please can I join the community to be able to contribute

OpenSRE just hit 4.4k ⭐ on GitHub. really appreciate everyone building, contributing, and supporting. lot more to come → github.com/Tracer-Cloud/o…

@GG_Observatory Exactly why we’re building OpenSRE. The goal isn’t just smarter agents — it’s traceable ones. Every decision, every action, every outcome… tied together so debugging in prod actually works.

The observability angle is underrated. Most AI debugging tools fail in prod not because the model is wrong but because there's no trace between what the agent decided and what actually happened. You're right that audit trails change the failure mode from "silent wrong answer" to "explainable mistake" — which is the difference between a tool you trust and a tool you pray on.

Building AI for debugging production systems OpenSRE Contributors welcome → github.com/Tracer-Cloud/o…