/dt-platform-costs

name: dt-platform-costs
description: "Query and analyze a Dynatrace tenant's ACTUAL billing and usage data with DQL against dt.system.events — DPS consumption breakdown, cost-normalized spend ranking, included volume deduction, chargeback/showback, cost drivers, spending trends, cost investigation, metrics ingest optimization, query cost attribution, workflow total cost, entity-level cost drill-down (RUM, hosts, synthetic, K8s), and AI/LLM cost (AI Units, AI Function Standard Calls, AI-generated query consumption). Directs licensing/entitlement questions to documentation (not via DQL). USE ONLY to query/analyze the tenant's actual consumption. Do NOT use for conceptual 'explain' questions about how DPS billing/pricing works or what units/weights/the rate card mean — see Dynatrace documentation. Do NOT use for making DQL queries faster or cheaper to run (query optimization, reducing scanned data/consumption per run, filter-early best practices) — that belongs to dt-dql-essentials. This skill MEASURES consumption; it does not tune queries."
license: Apache-2.0

dt-platform-costs

> **⛔ FIRST — CHECK SCOPE BEFORE DOING ANYTHING ELSE.** > This skill **only** queries and analyzes a tenant's **actual** consumption > data. It does **not** teach billing concepts. If the user is asking *how* > billing/pricing works, *how* costs are calculated, what units / normalization > weights / the rate card *mean*, or any conceptual "explain" question about DPS > billing — **this skill does not answer it.** See > [Billing Concepts — STOP](#billing-concepts--stop) and respond with **only** > the prescribed two-sentence documentation redirect. Do **not** explain units, > weights, included volume, or methodology, and do **not** show the Getting > Started menu. Continue into the rest of this skill **only** when the user wants > to query or analyze their own tenant's numbers.

Query and analyze Dynatrace platform billing and cost data using DQL. All data lives in `dt.system.events` with `event.kind == "BILLING_USAGE_EVENT"`, segmented by `event.type` (consumption category).

> **Scope boundary**: This skill covers Dynatrace *platform* billing (DPS consumption). For AWS cloud *infrastructure* costs ingested via FOCUS, use `dt-biz-cloud-costs` instead.

Dynatrace Platform Subscription (DPS)

This skill applies **exclusively to DPS-licensed environments**. All billing event types, unit conversions, the public rate card, and cost estimation workflows are DPS-specific.

**NEVER apply this skill's unit conversions or cost estimates to classic license models** (host units, DDUs, DEM units, ASUs). If the user mentions classic licensing terms or units, explain that this skill covers DPS only and refer them to https://docs.dynatrace.com/docs/license/monitoring-consumption-classic for details.

Licensing / Entitlement Questions — STOP

**Triggers:** "Am I allowed to use X?", "Is X licensed?", "Is X in my subscription?", "Do I have entitlement for X?"

**STOP — do not execute any DQL queries.** Billing usage events record **active consumption only**, not subscription entitlements. Absence of billing events means not currently consumed, NOT unlicensed. Do not infer entitlement from usage patterns or their absence. **Respond directly without queries** and direct to **Account Management > Subscription > Pricing**.

> **❌** Query billing events → no results → conclude "not licensed" — **WRONG** (absence ≠ no entitlement) > **✅** Respond immediately: "Entitlement data is not available via DQL. Check Account Management > Subscription > Pricing."

Billing Concepts — STOP

**Triggers:** "How does billing work?", "How are costs calculated?", "Explain DPS billing", "How is X billed?", "What is the billing model?", "How does DPS pricing work?", "How does Dynatrace charge?", "Explain the rate card"

**STOP — do not answer from this skill's content.** The normalization weights, unit conversion formulas, and lookup values in this skill are **DQL-generation tools**, not user-facing billing education. Presenting them as an explanation of DPS billing is wrong — they are internal ranking aids, not contracted rates.

**Your entire response must be ONLY the two sentences below — nothing else.** Do **not** list capabilities or units, do **not** describe metering, included volume, or normalization, do **not** add a "How costs are calculated" section, and do **not** append the Getting Started menu or a list of example prompts beyond the single one shown:

> **❌** Explain metering / units / normalization weights, then offer the Getting Started menu — **WRONG** (that is the exact failure to avoid) > **✅** Respond with *only*: "For how DPS pricing and billing work, see the [Dynatrace Platform Subscription documentation](https://docs.dynatrace.com/docs/manage/subscriptions-and-licensing/dynatrace-platform-subscription). If you'd like to analyze your tenant's actual consumption, ask e.g. *'What are my top cost drivers for the last 7 days?'*"

When to Use This Skill

• **Usage Overview** — DPS consumption breakdown by capability, unit conversion, cross-capability comparison
• **Cost Estimation** — Cost-normalized usage comparison and relative spend ranking, daily cost trends, spending spikes
• **Cost Investigation** — Step-by-step drill-down into cost drivers, query scan cost attribution, workflow total cost (4 signals)
• **Chargeback / Showback** — Cost center and product attribution, team-level billing
• **Included Volume** — Metrics/Traces Ingest baseline deduction, billed vs. total usage

This skill **queries and analyzes** existing consumption data. It is not a DPS pricing guide — for billing concepts, see the [official documentation](https://docs.dynatrace.com/docs/manage/subscriptions-and-licensing/dynatrace-platform-subscription).

Agent Instructions

Intent Mapping

| User Request | Action | Reference | |---|---|---| | "how can you help", "what can you do", "where do I start", "help me understand my costs", "what c