Cloud cost
Observability tax
The cost of the monitoring stack itself, such as hosts, custom metrics, traces, and logs. It grows on its own, apart from the infrastructure it watches.
Last updated
Definition
Every other line on a cloud bill follows a decision that someone made on purpose. More instances, more storage, and more traffic all start that way. Observability spend follows side effects of normal operation instead. A tag a developer added, a debug log left in, or an autoscale spike can raise it. Nobody provisions an observability increase the way they provision an instance. So the team that carefully reviews the infrastructure often leaves the monitoring bill unwatched.
The fix is not to monitor less. Treat the monitoring bill as its own line item to review. Give it its own metrics, such as cardinality, host peaks, and indexed log volume. Do not assume it moves in step with the infrastructure beneath it.
Where it shows up
Observability tax appears as its own line item on a monitoring vendor's invoice, apart from the infrastructure it watches. You track it through host count, custom metric cardinality, trace volume, and indexed log volume. The vendor's usage dashboard shows all of these next to the invoice total.
What makes it expensive
Do not assume the monitoring bill follows the infrastructure bill. A tag a developer added, or a debug log left in production, can move it alone. Give the monitoring invoice its own review slot. Use the same schedule as the infrastructure it watches. The two do not move together.
Related
More in Cloud cost
- Committed use discount (CUD)
- Reserved instance (RI)
- Savings plan (SP)
- On-demand vs. spot instances
- Data egress
- Amortized, blended, and unblended cost
- Billed vs. effective vs. list vs. contracted cost
- Rightsizing
- Idle and orphaned resources
- Storage class
- Lifecycle policy
- Incremental snapshot
- Allocatable capacity
- Requests vs. limits
- Cluster idle
- Workload idle
- Bin packing
- Cost allocation tags
- Tag coverage
- Unallocated spend
- Showback vs. chargeback
- Unit economics
- RI/SP coverage and utilization
- Metric cardinality
- High-water-mark billing
- Log ingest vs. index
- Snowflake credit
- Auto-suspend / resume minimum
- BigQuery slot
- Bytes scanned & partition pruning
- Time Travel & Fail-safe
The invoice is a lagging signal.
A monthly invoice tells you what already happened. CostMon builds a daily baseline, so a spike stands out while you can still act on it.