signozlisted

SigNoz MCP tool reference for querying a live observability backend (OTel metrics, traces, logs) plus alerts, dashboards, saved views, and notification channels. Covers all ~41 signoz_* tools, the 4 built-in MCP prompts, the resource-attribute-first filtering rule, and the regen incident -> SigNoz correlation loop on the mini-axol/Riddler deployment. TRIGGER when: user asks to query SigNoz, inspect a service's errors/latency, search OTel logs or traces, read/aggregate metrics, triage an alert, or uses signoz_* MCP tools; or pivots from a regen incident into telemetry. DO NOT TRIGGER when: user wants to DESIGN SLOs/alerts/dashboards conceptually (use observability-designer skill), or READ/ack/resolve incidents in Regen itself (use the regen agent/skill -- signoz is the telemetry side of that loop).
DROOdotFOO/agent-skills · ★ 1 · AI & Automation · score 75

Install: claude install-skill DROOdotFOO/agent-skills

# SigNoz MCP Query a **live** SigNoz instance over MCP (server already configured). ~41 `signoz_*` tools across telemetry (metrics/traces/logs), alerts, dashboards, saved views, notification channels, and docs -- plus 4 built-in workflow prompts. This skill is for **reading and operating a running SigNoz**. For designing SLOs, alert thresholds, or dashboards from first principles use `observability-designer`. For reading/acking incidents use the `regen` agent -- SigNoz is where you land *after* extracting an incident's correlation keys. ## Two rules that make queries fast (and correct) **1. Filter by resource attributes first.** Resource attributes (`service.name`, `k8s.namespace.name`, `host.name`) are indexed and dramatically speed up backend queries. If you don't already have one: ``` signoz_get_field_keys(signal="logs", fieldContext="resource") # discover keys signoz_get_field_values(signal="logs", name="service.name") # discover values ``` Then always scope queries with a `service` (or `filter: service.name = '...'`). Do not run broad, unfiltered log/trace scans. **2. Pick the operator to match intent AND data type.** | Intent | Operator | Example | | --- | --- | --- | | Field exists | `EXISTS` | `trace_id EXISTS` | | Field absent | `NOT EXISTS` | `k8s.pod.name NOT EXISTS` | | Exact match | `=` | `service.name = 'frontend'` | | Exclude (field must exist) | `EXISTS AND !=` | `service.name EXISTS AND service.name != 'redis'` | | One of several | `IN` | `sever