dt-platform-costs

Query and analyze Dynatrace DPS billing usage events with DQL for cost ranking and chargeback.

Updated Dec 12, 2025
One-click install
npx skills add https://github.com/ricardojjulia/ESACompanion --skill dt-platform-costs-ricardojjulia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dt-platform-costs
Source: https://github.com/ricardojjulia/ESACompanion/tree/main/.github/skills/dt-platform-costs
Command: npx skills add https://github.com/ricardojjulia/ESACompanion --skill dt-platform-costs-ricardojjulia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about dt-platform-costs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find my top Dynatrace cost drivers with DQL?▼

Query dt.system.events filtered to BILLING_USAGE_EVENT, deduplicate by event.id and event.type, then apply the full inline lookup to compute cost_weight in DQL and sort descending. Present only rank, capability name, and usage in native units, never the weight as a dollar figure.

How do I build a chargeback report by cost center in Dynatrace?▼

Run a coverage pre-flight query first to confirm dt.cost.costcenter tags are populated, then group billing events by cost center. String-typed fields group directly; record[] types like Metrics Ingest and Log Retain require expand to unnest before aggregation.

Does this skill work with classic Dynatrace licensing like host units or DDUs?▼

No, it applies exclusively to the Dynatrace Platform Subscription (DPS) license model. All event types, unit conversions, and normalization weights are DPS-specific; classic licensing questions should go to the monitoring consumption documentation.

Why do my Metrics Ingest billable numbers look inflated?▼

Metrics Ingest includes a baseline of data points from host monitoring that must be deducted before billing. Use the billable volume query with included volume deduction, and keep windows at 14 days or less to avoid silent timeseries interval coarsening that halves the deduction.

Can I check licensing entitlements or subscription eligibility with DQL?▼

No, billing usage events record active consumption only, not entitlements. Absence of billing events does not mean a capability is unlicensed; check Account Management > Subscription > Pricing for entitlement information.

Why do billing totals not match the Account Management portal?▼

Common causes are missing deduplication of refreshed billing events, rolling time ranges instead of explicit UTC midnight boundaries, and emission lag cutting off late-arriving events. Extend the fetch window for Metrics Ingest by 5 hours and guard on usage.start.