BusinessPractitioner3 min read
How do you cut the observability bill at the source?
Measure volumes and, with your prices, the observability bill before and after each Collector lever: unbounded criteria, aggregation, trace selection, log filtering and archiving.
For: architects · finance, risk and compliancePrerequisites: Basic notions of metrics, traces, logs and the OpenTelemetry Collector.
An illustrative scenario: the finance department asks the platform team to cut the observability bill significantly next year. The first reflex is to drop dashboards, shorten retention, negotiate with the provider. This simulator suggests another question: of all the data you send, which was really worth keeping?
Think of moving house. Paying the truck to carry boxes you will throw away on arrival means paying twice for nothing. Better to sort before loading. Observability data works the same way. Filtering once the data has reached the provider means paying to receive it before throwing it away. The same sorting done in the Collector, the software that receives data from applications before sending it to storage, removes it before transport, reception and storage.
The simulator uses the illustrative case of a mid-size Kubernetes platform: 6 million active series (the rows metrics store), 800 GB of traces and 1.2 TB of logs per day. It shows what each lever takes off the volumes, then off the bill if you enter your prices. Prices change fast and vary by contract: this guide gives none; use your provider’s dated price list. Without prices, the simulator shows volumes in series and in GB per month. With your volume prices, it shows the bill before and after, signal by signal.
Result
| Signal | Before | After | Change |
|---|
Months of 30 days. Levers chain in the order shown: a lever’s contribution depends on the ones before it on the same signal. The fixed base does not move with volumes, which is why a large volume cut does not divide the bill by as much.
Things to try
Section titled “Things to try”- Look at the default volumes. The 6 million active series become 1.8 million (-70%). The 24,000 GB of traces per month become 3,240 GB (-86.5%). The 36,000 GB of hot logs per month become 11,902 GB (-66.9%), plus 8,978 GB sent to cold storage.
- Turn off every lever except the first two. Both deal with cardinality, meaning the number of metric rows: removing criteria whose values have no limit (such as a user ID) and counting per service rather than per instance. On their own, they already remove 4.2 million of the 6 million active series, without touching application code.
- Raise the share of traces kept from 13.5% to 50%. Tail sampling, which picks the traces to keep once they are complete, still cuts volume. But an overly generous policy, with a latency threshold set too low, wipes out much of the saving: the lever now removes only 12,000 GB of traces per month instead of 20,760.
- Look at the routing row. It removes no GB: it moves 8,978 per month from hot storage, fast and expensive, to cold storage, slow and cheap, the way you carry boxes up to the attic. Enter your prices and give cold storage the same price as hot: the lever no longer saves anything. Its value lies in the price gap between the two, not in the routing itself.
- Enter your prices, then raise the fixed base of the subscription. The relative reduction flattens. Depending on your provider’s pricing model, the same volume cut does not yield the same saving.
For technical teams: where the 13.5% and the routing saving come from
The 13.5% comes from the default settings of the tail sampling simulator: 1% errors and 5% slow traces all kept, plus 8% of the rest (0.01 + 0.0495 + 0.9405 × 0.08 ≈ 0.135, shown rounded to 13%).
The monthly routing saving is 8,978 x (hot_gb_price - cold_gb_price).
The rule
Section titled “The rule”Cardinality first, sampling next, routing for the rest. The first two levers deliver most of the saving because they act on the largest volumes. Routing mainly serves to meet retention obligations without paying hot storage prices. The amount depends on your prices: enter those of your contract. Even without them, the volumes removed are enough to open the conversation with finance.
Further reading: the business dimension, the metrics bill simulator, the tail sampling simulator and the bridges.
Revised on 2 October 2026: prices removed; the simulator shows volumes and the bill only with your prices.