Telemetry Health Check

# How much of your telemetry is noise?

Answer ten quick questions about your backend, your bill and your stack. See the OpenTelemetry® problems teams like yours usually have, and roughly what they cost.

Question 4 of 10

How does that bill split between logs, metrics and traces?

- Logs **60%**
- Metrics **20%**
- Traces **20%**

Traces

Traces with only one span

In most teams we checked, traces with only one span usually made up 38% to 60% of all spans.

## The quick check

It takes about two minutes, and you see your results without giving us an email. The numbers come from real production telemetry we analyzed in October 2026.

Start the quick check

- 01 Which observability backends do you pay for?
- 02 Roughly what do you pay per year?
- 03 Is anything forcing a decision on that spend?
- 04 How does that bill split between logs, metrics and traces?
- 05 Where do your workloads run?
- 06 Which languages run most services?
- 07 How are services instrumented?
- 08 What do your services talk to?
- 09 Which of these sound familiar?
- 10 Do you know whether personal data (emails, IDs, tokens) reaches your telemetry?

## How the health check works

- 01We analyzed real production telemetry from teams that send data to OllyGarden, usually an hour per team, in October 2026.

- 02For each problem, we measured how much of its signal it took up: the share of spans, metric datapoints or log records. The ranges you see are typical values. They leave out the best and worst cases we found.

- 03Your answers decide which problems apply and how much each signal counts. If most of your bill is traces, trace problems count most.

- 04Then we account for how your backend charges. On some backends, dropping spans or sending metrics less often doesn't lower the bill, so those changes count for less, or not at all.

- 05The dollar figure uses the middle of your spend range. It's an estimate: your contract, discounts and allowances decide the real number.

- 06Numbers that say what a fix removed come from applying our advice to real customer bills.

## About the health check

Where the numbers come from and what happens to your answers.

### Is this a savings calculator?

No. It shows which problems are common in setups like yours and what they might cost. Only your own data can tell you what you'd save, and that's what the assessment is for.

### Where do the numbers come from?

From real production telemetry we analyzed in October 2026, and from applying our advice to real bills. We never show numbers for a single company.

### Do you store my answers?

Only if you send us a request. Until then, your answers stay in your browser. If you allow analytics, we count which options people pick, but never what you type.

### What's in a telemetry quality report?

We run our checks on a sample of your telemetry. The report lists each problem we find, how much of your data it accounts for, and what fixing it is worth. [Explore OllyGarden Insights →](/products/insights)

Canonical URL: https://ollygarden.com/telemetry-health-check