From the audit · FinOps

Consumption is configuration, one step removed

Under a consumption model the invoice is a report on your own settings. Host units follow monitoring mode. Ingest follows what the pipelines let through. Storage follows retention. Queries follow dashboards, workflows and whatever your teams run by hand.

Each of those is set by somebody who was solving a different problem, usually months earlier, and none of them is presented as a purchase at the moment it is made. The invoice is where all of it finally arrives at once, in aggregate, in a form that is very hard to argue with.

The four questions that explain most of a bill

How many hosts are in Full-Stack mode, and how many of those run a monitored service? On one audited tenant, 140 did not — $91,576 a year.

What retention does each bucket carry, and did anyone choose it? On the same tenant, one default bucket at 462 days, worth $22,455–$86,115 a year depending on the applicable rate.

What is being ingested that is never queried? Log sources that arrive in volume and are read by nobody are the most common ingest finding, and the easiest to fix at the pipeline.

And which consumption can be attributed to a team? On that tenant 384 hosts carried no cost-allocation tag, which makes chargeback arithmetically impossible rather than merely difficult.

Why the answers are hard to get

Not because the data is hidden — it is all in the tenant — but because each answer needs a join that no built-in view performs. Consumption is reported by dimension; configuration is stored by entity; the interesting question is the intersection, and the intersection has to be assembled.

That is the entire reason an audit exists as a product rather than as advice. The value is not knowing that idle hosts cost money. It is having the list, priced, with the source behind it.

Read the invoice backwards

Take the largest line, ask which setting produces it, and ask who set that setting and when. If nobody can answer the second question, you have found something. If they can — "that retention is our regulatory obligation", "those hosts run the batch estate" — you have documented a decision, which is worth almost as much and takes five minutes.

Do that once a quarter for the top three lines and the invoice stops being a bill that arrives and becomes a report on choices you made. That is the only durable form of cost control in a consumption model; everything else is a one-off clean-up that drifts back.

The takeaway

Nothing on a consumption invoice is arbitrary. Every line traces back to a setting, and most of those settings were never a decision anyone remembers making.

More from the series

The $91,576 question: Full-Stack hosts with nothing monitored on them From the audit · FinOps The Grail bucket nobody chose: 462 days of retention From the audit · Grail 1,617 maintenance windows: how alerting goes quiet without anyone deciding From the audit · Alerting Personal data in logs: 50 sources, about 30.7 million records a day From the audit · Pipelines

An audit takes one run. The findings take one meeting. What you do with them is up to you.

Certified Dynatrace experts

Send

Obzervability

Privacy Terms of use Accessibility