CtrlK
BlogDocsLog inGet started
Tessl Logo

create-dashboard

Create observability dashboards from OTEL metrics, logs, and traces using Kopai. Use when building metric visualizations, monitoring views, KPI panels, or when the user wants to see their telemetry data in a dashboard — even if they don't say "dashboard" explicitly. Also use when other skills or workflows need to present telemetry data visually (e.g. after root cause analysis).

100

Quality

100%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Create Dashboard with Kopai

Component Schema (auto-generated)

!npx @kopai/cli dashboards schema 2>/dev/null || echo "ERROR: Cannot connect to Kopai backend. If running locally, start it with: npx @kopai/app start — If using a remote backend, check the url in your .kopairc file."

Available Metrics

!npx @kopai/cli metrics discover --json 2>/dev/null || echo "ERROR: Cannot connect to Kopai backend. If running locally, start it with: npx @kopai/app start — If using a remote backend, check the url in your .kopairc file."

Workflow

  1. Discover metricsnpx @kopai/cli metrics discover --json
  2. Design tree — build a uiTree using components from the schema above
  3. Create dashboard — pipe JSON to npx @kopai/cli dashboards create --name "<name>" --tree-version "0.7.0" --json
  4. Verify — response contains id (success) or error (failure). On error: re-run metrics discover to check metric names and types match the component compatibility table below, fix the tree, and retry

Quick Example

A single-card dashboard showing CPU usage:

echo '{"uiTree":{"root":"stack-1","elements":{"stack-1":{"key":"stack-1","type":"Stack","props":{"direction":"vertical","gap":"md"},"children":["card-1"],"parentKey":""},"card-1":{"key":"card-1","type":"Card","props":{"title":"CPU Usage"},"children":["ts-1"],"parentKey":"stack-1"},"ts-1":{"key":"ts-1","type":"MetricTimeSeries","props":{"height":300,"unit":"1"},"children":[],"parentKey":"card-1","dataSource":{"method":"searchMetricsPage","params":{"metricType":"Gauge","metricName":"system.cpu.utilization"}}}}},"metadata":{}}' | npx @kopai/cli dashboards create --name "CPU Dashboard" --tree-version "0.7.0" --json

Common Components

ComponentUse forCompatible metric types
MetricStatKPI numbersSum, Gauge
MetricTimeSeriesTrend chartsSum, Gauge, Histogram
MetricHistogramDistributionsHistogram, ExponentialHistogram
LogTimelineLog streamn/a (uses searchLogsPage)

Rules

  • workflow - Dashboard creation workflow (detailed rules, tree structure, error handling)

Read rules/<rule-name>.md for details.

Repository
kopai-app/kopai-mono
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.