SigNoz Integration
Overview
SigNoz is an open-source observability platform built on OpenTelemetry. It provides unified APM, logs, traces, metrics, and alerting in a single tool — a self-hostable alternative to Datadog and New Relic. SigNoz includes a built-in Alertmanager, so no external Alertmanager deployment is required. When alert thresholds are breached, SigNoz delivers a structured webhook payload directly to the platform. Resolved events are sent automatically when the condition clears.
This integration supports automatic alert creation on firing events and automatic resolution when SigNoz sends a resolved notification.
Integration Flow
You define alert rules in SigNoz based on metrics, logs, or traces.
SigNoz evaluates these rules continuously against incoming telemetry data.
When a rule condition is met, the built-in Alertmanager routes the alert to configured notification channels.
The platform receives a webhook POST request and creates an alert.
When the condition clears, SigNoz automatically sends a
resolvednotification and the platform closes the alert.
Webhook Payload Schema
The payload follows the standard Prometheus Alertmanager webhook format (version 4). SigNoz adds a message field inside annotations alongside the standard summary and description.
{
"receiver": "string",
"status": "firing | resolved",
"alerts": [
{
"status": "firing | resolved",
"labels": {
"alertname": "string",
"severity": "string"
},
"annotations": {
"summary": "string",
"description": "string",
"message": "string"
},
"startsAt": "ISO8601 timestamp",
"endsAt": "ISO8601 timestamp",
"generatorURL": "string",
"fingerprint": "string"
}
],
"groupLabels": {
"alertname": "string",
"severity": "string"
},
"commonLabels": {
"alertname": "string",
"severity": "string"
},
"commonAnnotations": {
"summary": "string",
"description": "string",
"message": "string"
},
"externalURL": "string",
"version": "4",
"groupKey": "string",
"truncatedAlerts": 0
}Setup
Step 1 — Create an Alert Source on the Platform
Navigate to Sources → Add Source.
Search for SigNoz and select it.
Give the source a name and click Save.
Copy the https://api.itoc360.app/functions/v1/events URL.
Step 2 — Navigate to Notification Channels in SigNoz
In your SigNoz instance, click Settings at the bottom of the left sidebar, then select Notification Channels.
SigNoz sidebar with Settings menu highlighted at the bottom left
On the Notification Channels page, click New Alert Channel.
Notification Channels page (empty state) with the "New Alert Channel" button in the top right corner
Step 3 — Configure the Webhook Channel
Fill in the New Notification Channel form as follows:
Name: Give the channel a descriptive name (e.g.
ITOC360)Send resolved alerts: Toggle ON — this is required for automatic alert resolution on the platform
Type: Select
WebhookWebhook URL: Paste the https://api.itoc360.app/functions/v1/events URL
User Name: Leave empty
Password: Paste your Token from the platform (SigNoz uses this as a bearer token)
Click Test to verify connectivity, then click Save.
New Notification Channel form filled with ITOC360 name, Webhook type, and the platform webhook URL
Step 4 — Verify the Channel Was Saved
After saving, the channel appears in the Notification Channels list with type webhook.
Notification Channels list showing the ITOC360 webhook channel with Edit and Delete actions
Step 5 — Assign the Channel to an Alert Rule
When creating or editing an alert rule in SigNoz (Alerts → New Alert), select the notification channel you created under Notification Channels. The alert will be routed to the platform when it fires.
Step 6 — Verify the Integration
Use the Test button on the notification channel to send a test payload. Confirm the alert appears on the platform under the source you created.
Sample Payload
The following is a real payload captured during integration testing.
ALERT (firing):
RESOLVE (resolved):
Field Mapping Reference
status
Top-level event type: firing → ALERT, resolved → RESOLVE
alerts[0].fingerprint
Unique identifier per alert label set — used for fingerprint matching
alerts[0].labels.alertname
Name of the alert rule that fired
alerts[0].labels.severity
Severity label from the rule definition — used for priority mapping
alerts[0].annotations.summary
Short human-readable alert title
alerts[0].annotations.description
Detailed description of the alert condition
alerts[0].annotations.message
Additional message field specific to SigNoz (same value as summary in test alerts)
alerts[0].startsAt
ISO 8601 timestamp when the alert started firing
alerts[0].endsAt
ISO 8601 timestamp when resolved (0001-... means still active)
commonLabels
Labels shared across all alerts in this group
commonAnnotations
Annotations shared across all alerts in this group
externalURL
URL of the SigNoz instance that sent the alert
groupKey
SigNoz-specific group key used for alert deduplication
Priority Mapping
The platform maps the severity label from the alert rule to an internal priority level.
SigNoz severity Label
Platform Priority
critical
CRITICAL
error
HIGH
warning
MEDIUM
info
LOW
(not set)
MEDIUM (default)
The
severitylabel is set in your SigNoz alert rule definition. It is a required field when creating alerts in SigNoz.
RESOLVE Detection
The platform automatically resolves an alert when SigNoz sends a payload with "status": "resolved". This requires the Send resolved alerts toggle to be enabled on the notification channel (set in Step 3).
The resolved event is matched to the original alert using the fingerprint field, which SigNoz generates deterministically from the alert's label set. As long as the labels do not change between firing and resolution, the fingerprint will match and the alert will be closed automatically.
Last updated
Was this helpful?