Let's talk about building observability tools, open source, or whatever's on your mind.

See you there 🧡

Second: We designed merch we'd actually want to wear, pondering over the most philosophical question of an SRE/DevOps engineer - "Who will monitor the monitor?" - with our tees, mugs hoodies and stickers.

Come say hi at Booth 1372.

Repo: github.com/signoz/signo...
Full changelog: signoz.io/changelog/

Watching teams actually choose SigNoz has been incredibly humbling. Thank you to every team that's given us a shot.

Shoutout to the team that keeps shipping, and to everyone who's contributed code, filed issues, or given us honest feedback along the way.

Here's to the next 100 releases!

When we started SigNoz, we wanted to build an "open" observability platform :
- Open Source
- Based on open standards (OpenTelemetry)
- Gives you flexibility to host in your infra if needed

and didn't surprise you with unpredictable bills at the end of the month

Complete blog - medium.com/@ShiveeGupta...

→ Why they chose push-based OTEL over Prometheus pull model
→ Practical configs that go beyond the docs

Huge shoutout to Shivee and the entire Dream11 team for not just building this, but taking the time to document and share it with the community.

Some gems from the post:
→ How they built a Kafka-backed metric collection layer for self-observability → Custom OTEL instrumentation for legacy systems (Vert.x 3.9!)
→ Tail-based sampling strategies for traces

Most tutorials stop at "here's how to install it." Shivee goes into the real stuff — the 2 AM debugging sessions, the ClickHouse merge tuning, the Kafka buffer optimizations, the memory pressure battles. The things that only show up when you're actually running observability at production scale.

The scale they're running: → 100M+ unique metrics at peak → 1M rows/sec into ClickHouse → 357TB of spans ingested per month → >10K EC2 instances monitored → ~200Mbps continuous ingestion

But what makes this post special isn't just the numbers.

Shivee from Dream11 just published one of the most detailed production observability case studies I've seen — and it's honestly humbling to see what the team has built.

Now he's packing for KubeCon. He's bringing 15 mystery boxes. One has a $5000 discount voucher, all have limited edition Olly merch you won't find anywhere else.

Booth 1372. Come say hi.

We've been so consumed by the excitement of meeting our most important team member ever in person at KubeCon Atlanta that we didn't communicate as clearly as we should have.

We've been working with Olly for about 2 months now.

We'll be ready to share more about Olly very soon.

Seats are limited; approval required. See you there!

👉 Register here: luma.com/2w9p5qzn

Mixer with builders, maintainers, and founders

When & where
🗓 Wed, Oct 22, 5:00–7:30 PM PT
📍 98 Battery St, San Francisco

🤓 Who should join

AI/ML engineers, infra/platform teams, OSS maintainers, and founders who care about reliability & open standards

If you’re building AI in production, come hang with the folks shipping the tooling behind it.

💡 What to expect

Candid panel: Open Source in the Age of AI (Hatchet × Medplum × SigNoz)
Lightning talks on agentic AI reliability, healthcare agents, and orchestration at scale

If you’re building Agentic AI, check out what’s possible with SigNoz + OpenTelemetry. Check out our docs or DM me.

signoz.io/docs/llm-obs...

- LLMs are non-deterministic → you need end-to-end traces to see what actually happened.

- Trace agent loops, tool calls, vector store lookups, and external API hops—along with latency, errors, retries, and token costs.

- Use OpenTelemetry for a standard, portable instrumentation model.