signoz-modifying-dashboards
Modify an existing SigNoz dashboard — add or remove panels, edit a panel's query, threshold, or unit, rename the dashboard, change a panel type (graph ↔ table ↔ value), rearrange the layout, add or edit variables, or update tags. Make sure to use this skill whenever the user says "add a panel to my dashboard", "change the query on this panel", "remove the latency widget", "rename my dashboard", "update the filters", "rearrange the layout", "add a variable", "change panel type from graph to table", or otherwise asks to change something on a dashboard that already exists — even if they don't say "modify" or "edit" explicitly.
SigNoz · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add SigNoz/agent-skills --skill signoz-modifying-dashboards技能说明
name: signoz-modifying-dashboards description: > Modify an existing SigNoz dashboard — add or remove panels, edit a panel's query, threshold, or unit, rename the dashboard, change a panel type (graph ↔ table ↔ value), rearrange the layout, add or edit variables, or update tags. Make sure to use this skill whenever the user says "add a panel to my dashboard", "change the query on this panel", "remove the latency widget", "rename my dashboard", "update the filters", "rearrange the layout", "add a variable", "change panel type from graph to table", or otherwise asks to change something on a dashboard that already exists — even if they don't say "modify" or "edit" explicitly.
Dashboard Modify
Prerequisites
This skill calls SigNoz MCP server tools (signoz_get_dashboard,
signoz_patch_dashboard, signoz_update_dashboard, signoz_list_dashboards,
signoz_list_metrics, signoz_get_field_keys, signoz_get_field_values,
signoz_execute_builder_query).
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 hand-edit dashboard JSON without the MCP tools.
When to use
Use this skill when the user asks to:
- Add, remove, or edit panels/widgets on an existing dashboard
- Change a panel's query, title, type, or display settings
- Add, remove, or edit dashboard variables
- Rename or re-describe a dashboard
- Rearrange panel layout or resize panels
- Change a panel type (e.g., graph to table, value to graph)
- Add or modify thresholds on a panel
- Update tags on a dashboard
Do NOT use when:
- User wants to understand what a dashboard shows →
signoz-explaining-dashboards - User wants to create a new dashboard →
signoz-creating-dashboards
Instructions
Step 1: Identify the target dashboard
Use an id supplied directly or by dashboard resource context. A name is not an
ID: resolve every name-only request with signoz_list_dashboards, narrowing with
the filter argument (see signoz://dashboard/list-filter-guide) and paging by
offset until you have covered total. Match on spec.display.name. If multiple
dashboards match, present them and ask which one to modify; if one matches, use
its id.
Step 2: Fetch the current dashboard state
Call signoz_get_dashboard with the dashboard id to retrieve its full
configuration. This is mandatory — signoz_update_dashboard requires the
complete post-update state, and a patch still needs the real panel ids and grid
item indices. Never skip this step.
Examine the response to understand:
- Current panels and their ids (
spec.panelsis a map keyed by panel id) - Current grid item positions (x, y, width, height in the 12-column grid)
- Current variables
- Current query on each panel (exactly one per panel)
- The
spec.layoutsstructure — one Grid per section, each with its own items
Step 3: Plan the modification
Based on the user's request, plan the changes.
Confirm with the user before applying if:
- The modification is destructive — removing panels, deleting variables,
replacing an entire query with a different one, changing a query's
signal(e.g., traces → logs), or fundamentally altering what data is shown (changing aggregation from p99 to avg, removing groupBy dimensions) - The request is ambiguous — multiple panels could match "the latency panel"
- The change is large — restructuring sections, adding many panels at once
Destructive means data loss or silent behavior change. Even if the user says "just do it quickly," a brief confirmation ("I'll remove 'Memory Fragmentation' permanently — OK?") takes seconds and prevents irreversible mistakes. User urgency does not override this guardrail.
Non-destructive changes need no destructive confirmation: renaming, adding a panel or variable, changing a unit or panel type, adjusting layout, and adding thresholds. Variable additions still require the panel-applicability prompt below.
Compound modifications: When a request involves multiple changes (e.g., remove a panel + add a panel + rename), plan all changes against the fetched state and apply them as a single write — one patch array may carry many ops. Do not apply and re-fetch between changes.
Step 4: Apply the modification
Pick the write tool first. Default to signoz_patch_dashboard (RFC 6902):
it sends only the changed ops, so it cannot drop a panel that was never in
question. Read signoz://dashboard/patch-instructions for the JSON Pointer
paths. Reach for signoz_update_dashboard — a full replacement merged into the
Step 2 state — only when most of the dashboard changes. The rules below apply to
both; each names its patch path.
Ops apply in sequence, against the document as the previous ops left it. When one patch removes several entries from the same array — grid items, layouts, variables, tags, or a composite's member queries — order those removals by descending index. Otherwise each removal reindexes the entries after it, and a stale index quietly drops the wrong entry or no-ops (remove on a missing path is not an error). Indices planned against the Step 2 state are only valid for the first removal from each array.
Modification rules:
-
Time range and refresh are viewer controls. Dashboard payloads do not persist a default time range or refresh interval. If asked to change one, explain that panels follow the viewer-selected global range; do not invent
timeRange,defaultTimeRange, orrefreshfields. -
Preserve supported mutable state. Copy the fetched dashboard, change only what the user requested, and compare semantics after MCP normalization. Do not drop unrelated panels, variables, grid items, or sections.
-
Preserve panel/grid-item identity. Every panel id in
spec.panelsneeds exact