Perses Dashboard Create

Guided workflow for creating Perses dashboards from requirements through validation and deployment.

Overview

This workflow guides you through four phases: gathering requirements, generating a dashboard definition, validating it, and deploying to Perses. The skill applies sensible defaults at each phase to minimize configuration while remaining flexible for advanced scenarios.

Key workflow principle: Requirements → Definition → Validation → Deployment. Never skip validation, even for simple dashboards, because percli lint catches structural errors early.

Instructions

Phase 1: GATHER Requirements

Understand what the dashboard should display.

1. Identify metrics/data: What should the dashboard show? (CPU, memory, request rates, traces, logs)
2. Identify datasource: Which backend? (Prometheus, Tempo, Loki, Pyroscope, ClickHouse, VictoriaLogs). Defaults to Prometheus unless a datasource type is explicitly specified because Prometheus is the most common monitoring backend.
3. Identify project: Which Perses project does this belong to? Always ask — if the project does not exist, create it first before proceeding, because dashboards cannot exist without a project.