SigNoz

How's your relationship with YAML? Good enough to win a t-shirt? 😉

We made a YAML game!

The top 5 scorers who share their results will win exclusive SigNoz swag (t-shirt + stickers!)

Show us what you've got! Play at www.ohyaml.wtf and tweet your score tagging us!

Making LLMs Observable · Luma Note: You can register on LinkedIn directly. As LLM agents and AI-powered pipelines grow more complex, observability has to evolve too. In this session, we'll…

🤖 Making LLMs Observable - Live Session on 12th Aug, 9 AM PT

We'll be discussing:

1/ MCP Semantic Convention
2/ OpenTelemetry for AI
3/ Live demo - Shinzo + SigNoz

lu.ma/z79nttep

23,000+ GitHub Stars and counting! ⭐

We just crossed another major milestone!

OpenTelemetry-native metrics, traces & logs in a single pane - that's what developers want, and that's what we deliver.

The momentum is incredible. Eyes on 25K next 👀

Want observability in your Next.js app?

We published a guide to instrumenting Next.js with OpenTelemetry and sending data to SigNoz.

1/ Set up OpenTelemetry
2/ Track API and client spans
3/ Export traces to SigNoz
4/ Code examples in TypeScript

Read → signoz.io/opentelemetr...

Integrating Vercel AI SDK Telemetry with SigNoz Enable telemetry in your Vercel AI application with OpenTelemetry and send traces, logs, and metrics to SigNoz

Using Vercel AI SDK for your LLM app?

You can now monitor it with SigNoz.

1/ Prompt-level metrics
2/ Input-output traces
3/ Token usage and cost tracking

No extra infra. Works with experimental_tools.

Guide: signoz.io/docs/llm/ver...

We got 30% more log processing performance without adding hardware.

Problem: Sequential processing = idle CPU cores
Solution: Concurrent worker pools = full utilization

35.7k → 66k logs/second peaks
67% → 108% CPU usage

Technical breakdown: signoz.io/blog/optimiz...

MCP servers for observability: sophisticated co-pilots, not automated SREs.

Problem: Root cause analysis is an NP problem. Verifying AI hypotheses often takes as much effort as manual investigation.

Research shows the limitations: signoz.io/blog/unhyped...

OpenTelemetry K8s observability:

2 collectors for full coverage:

- DaemonSet (per-node telemetry)
- Deployment (cluster-wide metrics)

Helm presets handle configuration automatically.

Complete setup guide: signoz.io/blog/kuberne...

We made log queries 99.5% faster by fixing how we store data.

Before: 41,498/41,676 blocks scanned (99.5%)
After: 222/26,135 blocks scanned (0.85%)

The fix: Resource fingerprinting + ClickHouse primary key optimization.

signoz.io/blog/query-p...

SigNoz SigNoz is an open-source observability tool powered by OpenTelemetry. Get APM, logs, traces, metrics, exceptions, & alerts in a single tool.

Full changelog: signoz.io/changelog/

The release also includes:
1/ New datasource docs in onboarding (ELK migration, WordPress, Cloudflare, OpenAI)
2/ Ingestion keys restored for self-hosted users
3/ Light mode fixes for alert channels
4/ Layout shift fixes in logs explorer
5/ AWS ElastiCache dashboard corrections

Changelog v0.90.0 - JSON Flattening in Log Pipelines

You can now flatten complex nested JSON logs into simple, queryable structures with configurable depth and custom field mapping.

Think log parsing, but for your deeply nested JSON nightmares.

5-part Next.js observability tutorial series: signoz.io/opentelemetr...

1/ Server-side tracing & API monitoring
2/ Error tracking & external API monitoring
3/ Web Vitals & component performance
4/ Structured logging
5/ Production deployment & scaling

YC-backed Shaped AI Swapped a Siloed Toolset for SigNoz, achieving One-Stop Observability YC-backed Shaped AI Swapped a Siloed Toolset for SigNoz, achieving One-Stop Observability

From observability chaos to clarity in days.

Before: CloudWatch + Honeycomb = constant context switching
After: One platform for logs, metrics, traces

"Every single time we have an issue, SigNoz is always the first place to check." - Karl, Shaped AI

We shipped v0.89.0 completing the final step in our Dot Metrics Migration.

Also includes UI improvements:
1/ Text selection in log JSON fields
2/ Smooth auto-refresh updates

signoz.io/changelog/

Timelines00:00 Introduction to Observability in MCP Systems02:30 Understanding the MCP Architecture in context05:27 Implementing Distributed Tracing (tracing... Perform Distributed Tracing for your MCP system with OpenTelemetry

MCP servers are black boxes in your agentic AI stack.

When things break, how do you debug?

Our guide shows how OpenTelemetry brings transparency to MCP architectures: signoz.io/blog/mcp-obs...

SigNoz SigNoz is an open-source observability tool powered by OpenTelemetry. Get APM, logs, traces, metrics, exceptions, & alerts in a single tool.

signoz.io/changelog/

v0.88
Featuring Trace Funnel Analytics - Analyze user journeys between spans across distributed services, enhancing our industry 1st Trace Funnels.

Also shipping:
- In-app changelog notifications
- Sidebar revamp with pinning
- OpenTelemetry migration
- 12+ fixes

5/ Encryption Everywhere: All data in transit—inbound, outbound, and internal—must be encrypted using strong standards like TLS 1.2 or higher to protect data and enforce trust boundaries.

4/ Least Privilege Access: Every system and user operates with the minimum access required, for the shortest time necessary. IAM roles must be tightly scoped and tokens time-limited.

3/ Component-Level Zero Trust: Services within the BYOC deployment do not implicitly trust each other. All internal interactions require authentication and authorization using strong, signed identities (e.g., JWTs, IAM roles) to prevent lateral movement.

2/ Pull-Based Control Plane Communication: All communication must be initiated from the customer's environment. The vendor control plane should never initiate inbound connections, eliminating a common attack vector.

1/ Data Plane Isolation: Customer data and compute must remain entirely within their cloud account. No data leaves their environment, period. This is fundamental for data sovereignty and compliance (GDPR, HIPAA).

We’re proposing a solution: Zero Trust BYOC (ZTB), a framework rooted in the principle of "never trust, always verify."

A true ZTB deployment must adhere to five core principles:

The "Bring Your Own Cloud" (BYOC) model solves for data privacy and compliance, but it introduces a critical problem: the absence of a standardized security framework.

How do you guarantee security when your product runs in a customer's environment?

Observability doesn’t have to be all serious tech talk!

Our DevOps Wordle is a fun, daily brain teaser that makes learning DevOps and observability terms a blast.

Guess the word, uncover its meaning, and level up your skills in just 2 minutes ☕ signoz.io/todaysdevops...

3/ Finally, Exporters use the OTLP protocol to send this rich, correlated data to a backend.

An OTel-native tool like SigNoz can then visualize this data out-of-the-box, giving you a clear view of your system's health.

1/ Your app's code uses the OTel API to generate telemetry (spans, metrics, logs). The language-specific SDK then collects & batches this data.

2/ The Collector is the core processing hub. It enriches data, filters noise, & performs intelligent sampling before routing.

How does OpenTelemetry turn raw signals into correlated insights? It's all in the architecture.

A quick thread on the OTel pipeline.

Introducing ZTB - Defining Zero Trust for Bring Your Own Cloud (BYOC) Just like the Zero Trust Network (ZTN) became a standard way to reimagine network security, we believe BYOC needs a clear, opinionated model rooted in Zero Trust principles. We’re calling this, ZTB —…

Key tenants:
1/ Total data plane isolation.
2/ Pull-only control plane communication.
3/ Component-level mTLS.
4/ Least privilege access.
5/ Encryption everywhere.

Here's a framework to help engineers skip the trial-and-error: signoz.io/blog/zero-tr...