What problem does it solve? Dynatrace Platform Subscription (DPS) consumption data lives in dt.system.events as billing usage events with inconsistent units across capabilities, making it hard to answer questions like what is driving spend, how to allocate costs to teams, or whether included volume is being deducted correctly. ## Core Features & Use Cases - Cost Driver Ranking: Rank capabilities by relative spend using DQL-computed normalization weights, with included volume deduction for Metrics and Traces Ingest. - Chargeback & Showback: Attribute costs to cost centers and products, including billable Metrics/Traces volume per cost center with proportional redistribution. - Cost Investigation: Drill into query scan cost attribution by source, workflow total cost across three billing signals, and entity-level breakdowns for RUM, hosts, synthetic, and Kubernetes. - Use Case: A platform owner asks "What are my top cost drivers for the last 7 days?" and receives a ranked list of capabilities in native units, computed from deduplicated billing events with explicit UTC midnight boundaries. ## Quick Start Ask the assistant to show your top Dynatrace cost drivers for the last 7 days using DQL against dt.system.events.