SigNoz
Official@signoz · SF/Bengaluru
Open source Observability Platform
Agent Skills by SigNoz
Showing 8 vetted skills indexed across 1 GitHub repositories.
signoz-investigating-alerts
Correlate SigNoz alert signals with metrics, traces, and logs to diagnose root causes.
signoz-explaining-alerts
Translate SigNoz alert configurations and histories into plain-language summaries.
signoz-generating-queries
Generate and run ad-hoc SigNoz queries for metrics, logs, and traces.
signoz-searching-docs
Answer SigNoz documentation questions with cited canonical URLs.
signoz-modifying-dashboards
Modify SigNoz dashboards by applying structured panel, layout, and metadata changes via MCP server tools.
signoz-writing-clickhouse-queries
Generate raw ClickHouse SQL for SigNoz dashboard panels on logs and traces.
signoz-explaining-dashboards
Explain SigNoz dashboard panels, queries, and layout in plain language.
signoz-creating-alerts
Create SigNoz alert rules from natural-language intents with validation and dry-run preview.
Frequently Asked Questions About SigNoz
FAQPage SchemaWhat specific tasks can engineers perform using SigNoz?▼
Engineers can correlate metrics, traces, and logs to identify root causes of system failures. The platform enables the creation of custom dashboard panels, the generation of raw ClickHouse queries for deep data inspection, and the configuration of alert rules to monitor infrastructure health and performance thresholds.
What are the prerequisites for deploying this observability platform?▼
Deployment requires a host environment capable of running containerized services, typically managed via Docker or Kubernetes. Users must have access to a ClickHouse instance for data storage and ensure that telemetry data sources are configured to export spans and logs to the SigNoz collector endpoint.
Is this platform open-source and what are the associated costs?▼
SigNoz is released under the Apache License 2.0, allowing for free self-hosted deployment and modification. While the core software is open-source, users are responsible for the infrastructure costs associated with hosting the storage backend, compute resources, and data retention requirements for their specific telemetry volume.