signoz-creating-dashboards
Create a new SigNoz dashboard from a natural-language intent — import a curated template (PostgreSQL, Redis, JVM, k8s, hostmetrics, APM, LLM, etc.) when one fits, or build a custom dashboard from scratch with metric / trace / log panels. Make sure to use this skill whenever the user says "create a dashboard for…", "set up monitoring for…", "build me a dashboard…", "I need observability for…", "import a dashboard template", or asks to track / visualize a service, database, cluster, or AI/LLM platform — even if they don't explicitly say "dashboard". Also use it when someone wants to "monitor", "watch", or "see metrics for" a technology and the natural answer is a dashboard.
SigNoz · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add SigNoz/agent-skills --skill signoz-creating-dashboards技能说明
name: signoz-creating-dashboards description: > Create a new SigNoz dashboard from a natural-language intent: import a curated template (PostgreSQL, Redis, JVM, k8s, hostmetrics, APM, LLM, etc.) when one fits, or build a custom dashboard from scratch with metric / trace / log panels. Make sure to use this skill whenever the user says "create a dashboard for…", "set up monitoring for…", "build me a dashboard…", "I need observability for…", "import a dashboard template", or asks to track / visualize a service, database, cluster, or AI/LLM platform, even if they don't explicitly say "dashboard". Also use it when someone wants to "monitor", "watch", or "see metrics for" a technology and the natural answer is a dashboard. argument-hint:
Dashboard Create
Prerequisites
This skill calls SigNoz MCP server tools (signoz_create_dashboard,
signoz_list_dashboards, signoz_list_dashboard_templates,
signoz_import_dashboard, signoz_get_dashboard,
signoz_update_dashboard, signoz_list_metrics,
signoz_get_field_keys, signoz_get_field_values,
signoz_aggregate_logs, signoz_aggregate_traces, etc.).
Before running the workflow, confirm the signoz_* tools are
available. If they are not, the SigNoz MCP server is not installed or
configured; run signoz-mcp-setup first to initialize or repair the MCP
connection. Do not fall back to raw HTTP calls or fabricate dashboard JSON
without the MCP tools.
When to use
Use this skill when the user wants to:
- Create, set up, or build a new dashboard.
- "Monitor" or "set up observability" for a service, database, infrastructure component, or AI/LLM platform.
- Import a curated dashboard template.
- Visualize a set of metrics / traces / logs together on one screen.
Do NOT use when the user wants to:
- Modify an existing dashboard →
signoz-modifying-dashboards. - Understand what an existing dashboard shows →
signoz-explaining-dashboards. - Run a one-off query without persisting it →
signoz-generating-queries.
Required inputs (strict)
Dashboard creation is a write operation. Guessing here clutters the shared workspace with empty or wrongly-scoped dashboards someone else has to clean up. The skill enforces a soft input contract; most fields have sensible defaults, but a few cannot be guessed:
| Input | Required | Source if missing |
|---|---|---|
| Dashboard intent (NL goal) | yes | $ARGUMENTS or recent user turn |
| Technology / domain (e.g. PostgreSQL, Redis, "payment pipeline") | yes | parse from intent; otherwise ask |
| Confirmation to create (plus the modify-or-create choice when duplicates exist) | yes | ask the user (Step 2); still required with zero duplicates and under stated urgency |
| Resource scope for custom builds (service / namespace / cluster) | yes for custom builds | discover via signoz_get_field_keys + signoz_get_field_values; fall back to a dashboard variable |
| Specific metrics / signals for custom builds | inferred | derive from technology + MCP signoz://dashboard/* resources; surface in preview |
| Layout | inferred | apply defaults (see "Defaults" below) |
If a required input is missing and cannot be discovered, stop before
calling any write tool and ask the user. The host application decides
how the question is surfaced (a structured clarification tool, inline
<assistant_question> tags, an interactive prompt, etc.); follow the
host's UI rendering rules.
What to include in the question:
- What is missing: name the input concretely (e.g. "no service or cluster specified for the custom build").
- Candidate lists populated from your discovery calls: concrete
values per attribute the user can pick from. Example shape:
service.name→frontend,checkout,payments,inventory;k8s.cluster.name→prod-us-east-1,staging. - Allow free-form input so the user can name a value you didn't surface.
In autonomous mode (no human), escalate to the caller or fill the gap
from upstream context. Either way, do not proceed to
signoz_create_dashboard / signoz_import_dashboard with
a guessed value.
Workflow
The create path starts duplicate check → modify-or-create choice → template lookup. A matching template uses no-data probe → preview → import; a custom build uses no-data probe → build → per-panel dry-run → preview → create. Template lookup is internal; the user's only upfront choices are modify or create.
Step 1: Check for duplicates
Call signoz_list_dashboards. Most installs fit in the default
page (limit=50); narrow with the filter argument when the wording is
distinctive (see signoz://dashboard/list-filter-guide), and page by offset
until you have covered total; the schema accepts
integer or string limit / offset values.
Match by relevance Compare each existing
dashboard's lowercased spec.display.name, .description, and tags against the
user's technology/domain. Surface only matches a human would recognize
as the same thing: a "redis" dashboard does not match a "postgresql"
request just because both have a database tag. Collect each match's
spec.display.name, id, and createdAt for the next step.
Step 2: Ask the user (modify or create)
Present exactly two options (no template-import as a separate top-level choice; that's an internal decision in Step 3b):
- Duplicates found: "There are already these similar dashboards: [list with name, id, created-at]. Want me to (a) modify one of these, (b) create a new dashboard anyway, or (c) stop?"
- No duplicates: "I'll create a new dashboard for this. Proceed?" (No "modify" option when there's nothing to modify.)
Wait for the user's choice. "modify" → Step 3a. "create new" / confirm → Step 3b. "stop" → stop.
Step 3: Create or modify
Step 3a: Modify an existing dashboard
Hand off immediately to signoz-modifying-dashboards with the chosen
dashboard id and the user's in