Skip to content

From the author

Core DQL syntax, pitfalls, query patterns, and query optimization. Load to write, build, fix, or OPTIMIZE a DQL query — prevents syntax errors and makes queries faster, more efficient, and cheaper (less data scanned = lower query consumption/cost per run). Covers fetch commands, data models, field namespaces, time alignment, entity/smartscape patterns, metric discovery, and performance/cost optimization (filter early, bucket filters, short time ranges, field selection, sampling, cardinality). Trigger: "write/build/fix a DQL query", "DQL syntax", "query logs/spans/metrics", "create a timeseries", "optimize my DQL", "make my query faster/cheaper", "reduce DQL cost/consumption/scanned data", "keep DQL cost under control". Do NOT use to explain an existing query or answer product questions. For MONITORING a tenant's ACTUAL query consumption/billing (how much queries cost, who scanned most, cost trends) use dt-platform-costs — this tunes the query text, not billing data.

Install

npx skills add Dynatrace/dynatrace-for-ai --skill dt-dql-essentials -a claude-code

Installs to .claude/skills/dt-dql-essentials/ · Each command fetches the skill straight from GitHub with the open skills CLI.

Download .zip

Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.

Want your agent to suggest skills while you type? See how to use skills from your IDE.

Safety checks on SKILL.md

No warnings.

Why 84

Security100
Provenance67
Maintenance100
Licence100
Adoption38

aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.

Similar skills

Closest to this one by what they do and when they are used.

Ratings & reviews

—

no reviews

Tried this skill? Rate it to help others. Sign in

    Discussion

    Join the discussion. Sign in