Dt App Dashboards

If you're working with Dynatrace dashboards, this handles the JSON mechanics so you don't have to memorize the schema. It knows the 24-unit grid system, the difference between data and markdown tiles, which visualizations need timeseries versus categorical data, and how to wire up DQL query variables. The create/update workflow is opinionated about order: load domain skills first, validate queries, always download before modifying to avoid clobbering manual UI edits. Honestly most useful when you're building dashboards programmatically or need to bulk-update tiles without clicking through the UI.

skills.sh installs: 3K
GitHub stars: 177
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add dynatrace/dynatrace-for-ai --skill dt-app-dashboards --agent claude-code

Installs into .claude/skills of the current project.

Files

Dynatrace Dashboard Skill

Overview

Dynatrace dashboards are JSON documents stored in the Document Store containing tiles (content/visualizations), layouts (grid positioning), and variables (dynamic query parameters).

When to use: Creating, modifying, querying, or analyzing dashboards.

Dashboard JSON Structure

{
  "name": "My Dashboard",
  "type": "dashboard",
  "content": {
    "version": 21,
    "variables": [],
    "tiles": { "<id>": { "type": "data|markdown", ... } },
    "layouts": { "<id>": { "x": 0, "y": 0, "w": 24, "h": 8 } }
  }
}

Tile IDs in tiles must match IDs in layouts
Grid is 24 units wide. Common widths: 24 (full), 12 (half), 6 (quarter)
Two tile types: markdown (text content) and data (DQL query + visualization)

Optional content properties: settings, refreshRate, annotations

Reading & Analyzing

Fetch full content with dtctl get dashboard <id> -o json (describe returns metadata only), then inspect the JSON to discover its available properties. Carefully read references/analyzing.md before analyzing.