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. [Get Started](https://ollygarden.app) ## You’re Heading to the App Create your OllyGarden account over at ollygarden.app. You can get started for free, no credit card needed. Stay Here[Continue to the App](https://ollygarden.app) ## Instrumentation Score Hide details 89 Excellent ## Instrumentation Score89 Hide details - Suspicious PII Leakage -5 pts Critical Trace - Semantic Convention Attribute Level -3 pts Important Resource - Root Client Span -3 pts Important Trace 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 active Ingestion 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 Replay animationOllyGarden works alongside your existing telemetry flow to analyze quality and surface issues. ### Data Ingestion OllyGarden receives a sample of your OpenTelemetry data through the OTLP protocol. ### 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. ![OllyGarden Insights dashboard showing an Instrumentation Score of 97 rated Excellent, a volume metrics chart for spans, logs, and metrics, and a row of next recommended actions](/images/insights/dashboard.png) ### Service-Level Insights Drill down into individual services to review their score, version history, telemetry volume, and the issues affecting quality. ![Service view with an Instrumentation Score of 89, a version history table listing scores per release, and a semantic convention attribute level insight](/images/insights/service.png) ### Insight Details Explore each insight in depth, including the problem description, impact analysis, affected attributes, remediation guidance, and additional resources. ![Insight detail view for Suspicious PII Leakage on the Cart service, showing the problem description, critical impact level, scope, and attribute lists](/images/insights/detail.png) ## What Observability Leaders Are Saying - ![Portrait of Blake Irvin](/images/insights/blake.png)Blake Irvin Platform Engineering Leader Most teams don’t look at telemetry quality until there’s an incident. - ![Portrait of André Fiche](/images/insights/andre.png)André Fiche Head of Observability The 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 works→](/resources/instrumentation-score) Free **$0**/month For small projects and getting started. - [Instrumentation Score calculation](/resources/instrumentation-score) - 2 insights (incl. suspicious PII leaks) - Unlimited seats - Unlimited services - Community support - No credit card required[Start Free](https://ollygarden.app) ## You’re Heading to the App Create your OllyGarden account over at ollygarden.app. You can get started for free, no credit card needed. Stay Here[Continue to the App](https://ollygarden.app) RecommendedEssentials **$990**/month For teams shipping production telemetry. - [Instrumentation Score calculation](/resources/instrumentation-score) - All OllyGarden Insights - Unlimited seats - Unlimited services - Priority email support - API access[Get Started](https://ollygarden.app) ## You’re Heading to the App Create your OllyGarden account over at ollygarden.app. You can get started for free, no credit card needed. Stay Here[Continue to the App](https://ollygarden.app) Enterprise **Custom** For scale, security, and governance. - [Instrumentation Score calculation](/resources/instrumentation-score) - 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)[Contact Sales](/contact) ## See Insights at work - [Case study · Enterprise software An enterprise platform: nearly half the spans had no name One 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.](/resources/case-studies/enterprise-platform-half-the-spans-had-no-name) - [Case study · Digital health A digital-health platform: the PII leak was a logger setting Personal 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.](/resources/case-studies/digital-health-pii-leak-was-a-logger-setting) - [Case study · Enterprise software A 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.](/resources/case-studies/b2b-saas-cuts-logs-and-metrics-at-the-source) - [Blog Introducing the Instrumentation Score The Instrumentation Score is an open, standardized measure of OpenTelemetry instrumentation quality, scoring OTLP data against best-practice rules.](/resources/blog/instrumentation-score) - [Blog You 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.](/resources/blog/you-dont-have-too-much-telemetry-you-have-bad-telemetry) - [Blog Where Sensitive Data Hides in OpenTelemetry Pipelines, and How to Find It Trust 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.](/resources/blog/where-sensitive-data-hides-in-opentelemetry-pipelines)[What is telemetry quality?](/resources/telemetry-quality)[Compare Insights and Rose pricing](/pricing)[Read the FAQ](/resources/faq) ## Start with your Instrumentation Score Get your first score, review your findings, and start improving telemetry quality across your OpenTelemetry services. [Get Started](https://ollygarden.app) ## You’re Heading to the App Create your OllyGarden account over at ollygarden.app. You can get started for free, no credit card needed. Stay Here[Continue to the App](https://ollygarden.app) [Book a Demo](/contact) Canonical URL: https://ollygarden.com/products/insights