Data Ingestion
OllyGarden receives a sample of your OpenTelemetry data through the OTLP protocol.
OllyGarden Insights
Find your bad telemetry
Insights analyzes your OpenTelemetry® data to pinpoint where telemetry quality breaks down and show your team what needs attention first. Identify sensitive data leaks, noisy signals, incomplete instrumentation, and telemetry without clear ownership.
Instrumentation Score
89
Excellent
Instrumentation Score89
- Suspicious PII Leakage-5 ptsCriticalTrace
- Semantic Convention Attribute Level-3 ptsImportantResource
- Root Client Span-3 ptsImportantTrace
How OllyGarden Insights Works
Analyze telemetry quality without
changing your observability stack
Your telemetry keeps flowing through your existing OpenTelemetry pipeline. OllyGarden analyzes a sample alongside that flow, so teams can surface quality issues without replacing their observability backend.
Your infrastructure
Applications
OTel Collector
Destinations
Backends
Auto-routed via OllyGarden
OllyGarden telemetry validation engine
Inline filter activeIngestion
Active quality rules (5)
Auto-repairing
- Suspicious PII Leakage
- Missing Service Name
- Client Root Span
- High Cardinality Metric
- Semantic Convention Level
- 12 More Rules Running
Insights
OllyGarden works alongside your existing telemetry flow to analyze quality and surface issues.
Insight Analyzers
Specialized analyzers inspect telemetry patterns such as suspicious PII leakage, missing service names, client root spans, high-cardinality metrics, and semantic convention issues.
OllyGarden Insights
The Insights dashboard turns those findings into scores, detailed reports, and recommendations your team can review and act on.
Insights in Action
See OllyGarden Insights in action
Watch how teams use the Insights dashboard to review organization health, inspect service-level findings, and share specific insights with the right people.
From Overview to Insight Details
Understand telemetry
quality at every level
Start with a high-level view of telemetry health, then drill into the services, findings, and details behind each score.
Dashboard Overview
Get a bird’s-eye view of your telemetry health with organization-level scores, telemetry volume across spans, logs, and metrics, and recommended actions prioritized by impact.
Service-Level Insights
Drill down into individual services to review their score, version history, telemetry volume, and the issues affecting quality.
Insight Details
Explore each insight in depth, including the problem description, impact analysis, affected attributes, remediation guidance, and additional resources.
What Observability Leaders Are Saying
Blake IrvinPlatform Engineering LeaderMost teams don’t look at telemetry quality until there’s an incident.
André FicheHead of ObservabilityThe insights you’re bringing are gold. No backend today brings this so digested.
Pricing
Start measuring telemetry quality today
Start with our Free Plan - Full access to the Instrumentation Score and critical insights including PII leakage detection. No credit card required.
How the Instrumentation Score worksFree
$0/month
For small projects and getting started.
- Instrumentation Score calculation
- 2 insights (incl. suspicious PII leaks)
- Unlimited seats
- Unlimited services
- Community support
- No credit card required
Essentials
$990/month
For teams shipping production telemetry.
- Instrumentation Score calculation
- All OllyGarden Insights
- Unlimited seats
- Unlimited services
- Priority email support
- API access
Enterprise
Custom
For scale, security, and governance.
- Instrumentation Score calculation
- All OllyGarden Insights
- Unlimited seats
- Unlimited services
- Slack/phone support
- API access
- Custom SLA agreements
- Real-time notifications
- Custom rules (coming soon)
- Telemetry sampling opt-out and custom retention
- Zero data retention with AI providers (add-on)
See Insights at work
- Case study · Enterprise softwareAn enterprise platform: nearly half the spans had no nameOne background worker named cli made 45% of all spans, a third of logs were exact duplicates, a third were access logs, and the Collector shipped its own logs again.
- Case study · Digital healthA digital-health platform: the PII leak was a logger settingPersonal data in 1 in 6 services traced to one ORM logging setting, logs with no severity at all, one worker writing most of the logs, and auth tokens Rose found in a day.
- Case study · Enterprise softwareA B2B SaaS platform cuts logs 24% and metrics 25%Repeated logs, metrics that never change, and a pipeline complaining about itself. How replay-verified Collector changes beat a six-week proof of value, and what happened after.
- BlogIntroducing the Instrumentation ScoreThe Instrumentation Score is an open, standardized measure of OpenTelemetry instrumentation quality, scoring OTLP data against best-practice rules.
- BlogYou don't have too much telemetry. You have bad telemetry.High observability costs are rarely a volume problem. Learn how to fix bad telemetry at the source before relying on sampling.
- BlogWhere Sensitive Data Hides in OpenTelemetry Pipelines, and How to Find ItTrust store passwords in resource attributes, OAuth tokens in query strings, tax IDs in metrics: what we found in real pipelines, why tools cause most of it, and what privacy laws allow.
What is telemetry quality?Compare Insights and Rose pricingRead the FAQ
Start with yourInstrumentation Score
Get your first score, review your findings, and start improving telemetry quality across your OpenTelemetry services.