signoz-setting-up-observability
Run the full end-to-end observability setup for a service after its telemetry is already flowing into SigNoz — sequence SLI/SLO capture, data exploration (RED/USE), focused dashboards, saved Explorer views, burn-rate and absent-data alerts, and a tuning loop into one opinionated, SLO-aware workflow. Make sure to use this skill whenever the user says "set up observability after ingestion", "now that data is flowing, give me dashboards and alerts", "onboard this service to SigNoz end-to-end", "I want the full monitoring setup for X", or asks to go from raw telemetry to a complete dashboard + alerts + views package — even if they don't say "observability" explicitly. This is the orchestration layer: for a single artifact (just a dashboard, just one alert, just a saved view, or one static threshold alert, or a one-off query) use signoz-creating-dashboards, signoz-creating-alerts, signoz-managing-views, or signoz-generating-queries directly.
SigNoz · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add SigNoz/agent-skills --skill signoz-setting-up-observability技能说明
name: signoz-setting-up-observability description: > Run the full end-to-end observability setup for a service after its telemetry is already flowing into SigNoz — sequence SLI/SLO capture, data exploration (RED/USE), focused dashboards, saved Explorer views, burn-rate and absent-data alerts, and a tuning loop into one opinionated, SLO-aware workflow. Make sure to use this skill whenever the user says "set up observability after ingestion", "now that data is flowing, give me dashboards and alerts", "onboard this service to SigNoz end-to-end", "I want the full monitoring setup for X", or asks to go from raw telemetry to a complete dashboard + alerts + views package — even if they don't say "observability" explicitly. This is the orchestration layer: for a single artifact (just a dashboard, just one alert, just a saved view, or one static threshold alert, or a one-off query) use signoz-creating-dashboards, signoz-creating-alerts, signoz-managing-views, or signoz-generating-queries directly. argument-hint: <service name + what to set up (dashboard / alerts / views)>
Setting Up Observability After Ingestion
Take a service from "telemetry is flowing into SigNoz" to "I have a
dashboard, alerts, saved views, and a tuning loop." This skill is an
orchestration layer, not a standalone reference — the mechanical
work lives in the sibling SigNoz skills and the MCP tools/resources hold
the current payload schemas. This skill sequences them and supplies the
judgment calls (scope, SLOs, thresholds, what to skip) that no single
skill owns; it deliberately does not restate payload schemas or field
rules, so read the relevant signoz://… resource before composing any
payload.
Use this when traces, logs, or metrics are already landing in SigNoz and you want an opinionated, SLO-aware setup — not when you're still wiring up the SDK. Audience: two consumers — an autonomous AI SRE agent that runs without a human in the loop (e.g. an in-product SigNoz assistant), and an engineer at a Claude Code / Codex / Cursor prompt. Both follow the same flow; where a step needs a human decision (Phase 1 triage, Phase 5 sign-off), the host decides how to surface it, and an autonomous host fills the gap from upstream context instead of blocking.
Prerequisites
This skill calls SigNoz MCP server tools (signoz_list_services,
signoz_list_dashboards, signoz_get_field_keys,
signoz_execute_builder_query, signoz_create_dashboard,
signoz_create_alert, signoz_create_view, etc.) and
delegates to sibling skills. 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. Do
not fall back to raw HTTP calls or fabricate payloads.
When to use
Use this skill when the user wants the whole post-ingestion setup: SLI/SLO → exploration → dashboard → views → alerts → tuning, in any combination of those deliverables, sequenced as one workflow.
Do NOT use this skill when the user wants a single artifact — hand off directly:
- Just a dashboard →
signoz-creating-dashboards. - Just one static / threshold alert or notification rule →
signoz-creating-alerts. (But SLO / burn-rate / error-budget alerting — even with no dashboard — stays here: it needs the SLI/SLO capture and burn-rate judgment in the phases below.) - Just a saved Explorer view →
signoz-managing-views. - A one-off exploratory query →
signoz-generating-queries. - A concept/doc lookup (SRE methods, OTel conventions, burn-rate math)
→
signoz-searching-docs/signoz_search_docs.
Each phase below points to the skill that does the mechanical work; this skill owns the order and the decisions.
Phase 1 — Triage scope (don't skip)
Before touching any tools, get these answers. Each unblocks a downstream phase.
- What does this service do, and does it call external services? One or two sentences. This shapes the SLI (what "working" means) and flags downstream dependencies worth monitoring — if it calls a DB, cache, queue, or third-party API, plan to watch the client-span latency and error rate to each dependency, since a healthy service fronting a sick dependency still fails users.
- What deliverables? dashboard / alerts / saved views — any combination.
- Infra monitoring too? (optional — ask) If the service runs on infra you own (k8s pods, VMs, containers) shipping telemetry under the same resource attributes, you can add USE/infra panels (CPU, memory, restarts, network) with no extra instrumentation — see Phase 3. Skip if a platform team already owns the host/cluster dashboard.
- Which signals are emitted? traces / logs / metrics. Drives which
signoz_get_field_keyscalls you make. - What's the canonical resource filter? Usually
service.name. Confirm the exact value before querying — don't guess. - What does success look like for users of this service? (Sets up Phase 2.) Even a one-line answer ("requests under 1s with no 5xx") is enough — it becomes the SLI.
- Who owns it, and is there a runbook? Owning team, service tier, and the prod/staging scope — these become alert labels and annotations in Phase 8. Capture a real runbook URL if one exists; never invent one.
Offer "explore data first" as an explicit option.
Phase 1.5 — Inventory what already exists
Each create sub-skill runs its own rigorous duplicate-check when invoked
(signoz-creating-dashboards lists dashboards; signoz-creating-alerts
paginates alert rules) — don't re-implement that here. The orchestration
value is a single up-front sweep so you sequence around what exists
instead of hitting collisions mid-build:
- Is the service reporting, and under what exact name?
(
signoz_list_services.) This name is the resource filter every later phase reuses — pin it before anything else. - **Does a dashboard / alert / saved