Dynatrace Expert Skill

Core Competencies

• DQL async query lifecycle — submit via POST, poll for results, parse JSON response
• Entity inventory — hosts, services, process groups via fetch dt.entity.*
• Infrastructure metrics — CPU, memory, disk timeseries with timeseries command
• Davis problem triage — query active/recent problems, correlate with entities
• Log analysis — search and filter log records by level, content, entity
• Settings API — read/write metric events, alerting profiles, maintenance windows
• Dashboard management — list, read, create, update via Documents API
• SLO monitoring — query SLO status and burn rates

Code Style & Conventions

• Always use python3 for JSON encoding/parsing (not jq)
• Use strict=False for all JSON parsing of DQL responses (json.loads(data, strict=False))
• URL-encode request tokens before polling
• Use Bearer auth (not Api-Token)
• Present results as markdown tables

Common Patterns

DQL Submit / Poll

# Submit
RESPONSE=$(curl -s -X POST "${DT_PLATFORM_URL}/platform/storage/query/v1/query:execute" \
  -H "Authorization: Bearer ${DT_API_TOKEN}" \
  -H "Content-Type: application/json" \
  -d "{\"query\": \"${DQL}\", \"maxResultRecords\": 1000}")

STATE=$(echo "$RESPONSE" | python3 -c "import sys,json; d=json.loads(sys.stdin.read(),strict=False); print(d.get('state',''))")
TOKEN=$(echo "$RESPONSE" | python3 -c "import sys,json; d=json.loads(sys.stdin.read(),strict=False); print(d.get('requestToken',''))")

# Poll (URL-encode the token)
ENCODED=$(python3 -c "import urllib.parse; print(urllib.parse.quote('${TOKEN}', safe=''))")
RESULT=$(curl -s "${DT_PLATFORM_URL}/platform/storage/query/v1/query:poll?request-token=${ENCODED}" \
  -H "Authorization: Bearer ${DT_API_TOKEN}")

MZ-Filtered Timeseries Lookup

timeseries avg(dt.host.cpu.usage), by:{dt.entity.host}
| lookup [fetch dt.entity.host | filter in(managementZones, "MY_MZ")],
    sourceField:dt.entity.host, lookupField:id
| filter isNotNull(lookup.id)

Settings API Read

curl -s "${DT_PLATFORM_URL}/platform/classic/environment-api/v2/settings/objects?schemaIds=builtin:anomaly-detection.metric-events" \
  -H "Authorization: Bearer ${DT_API_TOKEN}"

Documents API (Dashboard) — Multipart Parsing

Dashboard responses are multipart; parse with python3 to extract the JSON body from the multipart envelope.

Security Best Practices

• Never expose DT_API_TOKEN in output or logs
• Validate token prefix (dt0s16. for Platform, dt0c01. for classic)
• Read-only by default; write operations require explicit approval
• No hardcoded entity IDs, MZ names, or AIDE IDs in scripts

When to Apply This Skill

• When working with Dynatrace monitoring data
• When querying infrastructure metrics or entity inventory
• When triaging Davis problems or reviewing logs
• When managing dashboards or alerting configuration
• When creating or modifying metric event rules or maintenance windows

Resources

• Dynatrace DQL Reference
• Dynatrace Settings API
• Dynatrace Platform Tokens