Open specification · Apache 2.0

The Instrumentation Score

The Instrumentation Score is a 0–100 measure of how well a service's OpenTelemetry® telemetry follows best practices and semantic conventions. It checks the traces, metrics, logs, and resource attributes a service already sends against 25 open rules, and weighs each failed rule by its impact.

Get your score

You’re Heading to the App

Create your OllyGarden account over at ollygarden.app. You can get started for free, no credit card needed.

Read the specification
  • 25 open rules
  • 4 impact levels
  • 0–100 one comparable number

How it is calculated

Weighted rules, one number

The score is a meta-signal: a signal about the quality of your signals. Every rule passes or fails for a service, and failed rules cost points in proportion to their impact, so one Critical failure costs four times as much as one Low failure. Nothing is capped, and fixing the most severe problems first always moves the score the most.

  1. Analyze the telemetry

    An implementation reads the OTLP data a service already sends, grouped by service.name, over a sliding window that defaults to 30 days. The score follows the service as it changes: spans that helped during development can become noise once it is stable.

  2. Check every rule

    Each of the 25 rules is a pass or fail condition on resources, spans, metrics, logs, or the SDK. A rule with several conditions passes only when all of them hold.

  3. Weigh the results

    The score is the weighted share of passed rules: the sum of passed rules times their weight, divided by the sum of all rules times their weight, times 100.

Impact levels and weights

ImpactWeightRules
Critical405
Important3013
Normal206
Low101

All rules passing: 720 weighted points

What a score means

ScoreCategoryMeaning
90–100ExcellentA high standard of instrumentation quality.
75–89GoodSolid quality; minor improvements are possible.
50–74Needs ImprovementTangible issues that need attention.
0–49PoorSignificant problems that need urgent action.

The rules

All 25 rules

The rules come from OpenTelemetry semantic conventions and community practice. This table is generated from the specification repository, most severe first; each rule ID links to its full definition and criteria.

Synced from the specification on 2026-09-24 (commit 0ef3cc6).

Showing 25 of 25 rules

Worked example

Scoring a checkout service

A checkout service sends traces, metrics, and logs and fails 4 of the 25 rules. Here is how those findings become its score. Fix them one by one to see what each is worth.

service.name = checkout4 of 25 failing
  • SPA-006Critical

    url.full on password-reset spans carries the reset token in its query string.

  • RES-007Important

    No deployment.environment.name, so staging and production share dashboards.

  • MET-002Important

    Custom queue metrics are exported without a unit.

  • RES-001Normal

    No service.instance.id, so the three replicas cannot be told apart.

Instrumentation Score83.3Good

83.3: Good

Score 83.3, Good

With every rule passing, the service would hold all 720 weighted points. The 4 failures cost 120, which leaves 83.3: Good.

Fixing the Critical token leak alone raises the score to 88.9. Adding the two Important fixes reaches 97.2, which is Excellent.

That ordering is the point of the weights: the score tells a team which fix to make first.

Get your score

Compute it yourself, or let Insights do it

The specification is open, so anyone can implement it. OllyGarden Insights is a hosted implementation that keeps the score current for every service.

Open source · Apache 2.0

Use the open specification

Read the rules and the formula on GitHub, run them against your own OTLP data, and propose changes. Discussion happens in the #instrumentation-score channel on the CNCF Slack.

Free plan · No credit card

Get it continuously with Insights

Send a sample of your OTLP data to OllyGarden Insights and get a score for every service, the findings behind it, and remediation guidance. The Free plan includes the Instrumentation Score, with no credit card.

Get your score

You’re Heading to the App

Create your OllyGarden account over at ollygarden.app. You can get started for free, no credit card needed.

Learn more about Insights
An OllyGarden Insights service view: an Instrumentation Score of 89, its version history, and a semantic convention finding marked Important

In real fleets

What the rules catch

These findings come from our anonymized case studies. Each one is a rule that failed in production or staging telemetry, and a real cost behind it.

Read the case studies →

Frequently Asked Questions

What teams ask us about the Instrumentation Score, the specification, and how to use it.

What is the Instrumentation Score?

The Instrumentation Score is a 0–100 measure of how well a service's OpenTelemetry telemetry follows best practices and semantic conventions. It checks the traces, metrics, logs, and resource attributes a service already sends against 25 open rules, and weighs each failed rule by its impact.

How is the Instrumentation Score calculated?

Each rule has an impact level with a weight: Critical 40, Important 30, Normal 20, and Low 10. The score is the sum of the weights of the rules a service passes, divided by the sum of the weights of all rules, times 100. The current specification has 5 Critical, 13 Important, 6 Normal, and 1 Low rules.

What is a good Instrumentation Score?

The specification maps scores to four categories: 90 to 100 is Excellent, 75 to 89 is Good, 50 to 74 is Needs Improvement, and 0 to 49 is Poor. Do not chase 100; a score of 75 or more is a sound target for most services. Fix Critical failures first: one of them, such as personal data in spans, costs 40 of 720 points and leaves 94.4, and two leave 88.9, which is Good.

Is the Instrumentation Score vendor-neutral?

Yes. The specification is open source under the Apache 2.0 license, and its maintainers work at Splunk, New Relic, Dash0, and OllyGarden. Implementations may not add rules of their own, so the same telemetry gets the same score in any tool.

Who maintains the Instrumentation Score specification?

OllyGarden started the specification in 2025 and hosts it today under an open governance model. Maintainers from Splunk, New Relic, Dash0, and OllyGarden review changes, and the goal is to move it to a neutral foundation such as the CNCF or the OpenTelemetry project.

How is the Instrumentation Score different from SLOs?

An SLO measures how a service behaves for its users, such as latency or error rate. The Instrumentation Score measures the telemetry itself: whether the data your SLOs, dashboards, and alerts are built on is complete, consistent, and safe. A service can meet its SLOs while its telemetry hides problems.

How is the Instrumentation Score different from data quality checks?

Generic data quality checks validate schemas, freshness, or volumes. The Instrumentation Score checks telemetry against OpenTelemetry semantic conventions and instrumentation practice, such as service identity, units, cardinality, broken traces, and sensitive data, and summarizes the result in one number you can compare across services and tools.

Do I have to change application code to improve my score?

Not always. Many failed rules can be fixed in the OpenTelemetry Collector: the transform processor, written in the OpenTelemetry Transformation Language (OTTL), can add missing resource attributes, move attributes to the right level, or redact sensitive values, and the filter processor can drop debug logs and noisy spans. Fixing the instrumentation at the source is still the better long-term answer.

Has the scoring formula changed since the 2025 launch?

Yes. The first draft, published in June 2025, started every service at 80 and added or subtracted fixed points per rule. The community replaced it with the weighted share of passed rules described on this page, which keeps the score between 0 and 100 without clamping and makes every rule's effect proportional to its impact.

Which signals does the Instrumentation Score cover?

The rules cover resource attributes, spans, metrics, and logs, plus one rule on SDK support for the language and runtime. New rules are added through the specification repository.

How do I get an Instrumentation Score for my services?

Implement the open specification against your own OTLP data, or use OllyGarden Insights, which computes the score continuously for every service and shows the findings behind it. The Insights Free plan includes the Instrumentation Score, with no credit card.

Can I propose a new rule?

Yes. Open an issue or pull request in the instrumentation-score/spec repository on GitHub, or start a discussion in the #instrumentation-score channel on the CNCF Slack. Every rule needs a rationale, pass or fail criteria, a target, and an impact level.

Get yourInstrumentation Score

Send a sample of your OpenTelemetry data to Insights and see the score for every service, with the findings behind it.

Get Started

You’re Heading to the App

Create your OllyGarden account over at ollygarden.app. You can get started for free, no credit card needed.

Book a Demo