1. Reminder: the rate card #
What consumes the budget.
Capabilities #
With the Dynatrace Platform Subscription (DPS), each capability consumes the budget according to a pricing grid (rate card). The article « Dynatrace licenses: classic model and DPS » details the units; here, we focus on how to manage them.
2. Measuring and attributing #
Who consumes what.
Tools #
- Account Management > Subscription: consumption per capability, per environment, and end-of-period forecast.
- Billing events in Grail, queryable in DQL for custom dashboards.
- Cost attribution with
dt.cost.costcenteranddt.cost.product, set on hosts, Kubernetes namespaces or via OpenPipeline.
fetch dt.system.events, from: -30d
| filter event.kind == "BILLING_USAGE_EVENT"
| summarize events = count(), by: { event.type, bin(timestamp, 1d) }3. Optimizing #
Concrete levers.
Levers #
| Item | Lever |
|---|---|
| Logs | Filter and route in OpenPipeline, retention per bucket, extracted metrics instead of retained logs |
| DQL queries | Short time windows, filters first, targeted segments and buckets |
| Full-Stack | Infrastructure Monitoring for hosts that do not need application traces |
| Traces | Adaptive sampling, excluding endpoints with no value (health checks) |
| Retention | Durations aligned with real needs (audit, security, debugging) |
Governance #
Good practice: Appoint an observability FinOps owner, publish a monthly consumption dashboard per team and attach a budget alert to each environment.
