Dash0 acquires Polar Signals
Dash0 integrates with webhooks to send notifications to any system. Gain visibility into your systems with this flexible integration.
Use this channel to send notifications to a generic webhook, allowing integration with various systems.
| Type | Description |
|---|---|
| Name | Specify the name for this webhook notification. |
| URL | Provide the webhook URL where notifications will be sent. |
| Additional HTTP Headers (Optional) | Add headers to authenticate the request or include extra information for downstream integration. |
{
"type": "alert.ongoing",
"data": {
"issue": {
"id": "a53b18cd-2f45-4896-90f5-2b6c3e9b0479",
"issueIdentifier": "742195867438912365",
"dataset": "production",
"start": "2024-10-31T11:23:05.123456789Z",
"status": "critical",
"summary": "High CPU Usage Detected",
"description": "CPU usage on server cluster 'prod-cluster-01' has exceeded the threshold, indicating potential resource bottleneck.",
"labels": [
{
"key": "environment",
"value": {
"stringValue": "production"
}
},
{
"key": "region",
"value": {
"stringValue": "us-west-2"
}
}
],
"annotations": [
{
"key": "impacted_service",
"value": {
"stringValue": "web-server"
}
}
],
"checkrules": [
{
"id": "d9e4a500-1cfc-4fa7-a84c-f7b2b2d97c42",
"version": 5,
"name": "High CPU Usage Check",
"expression": "avg({host_cpu_usage > $__threshold})",
"thresholds": {
"degraded": 0.75,
"failed": 0.9
},
"interval": "5m0s",
"for": "2m0s",
"keepFiringFor": "10m0s",
"summary": "Alert on high CPU usage across production servers",
"description": "Triggered when average CPU usage exceeds specified thresholds over 5 minutes.",
"labels": {
"severity": "critical"
},
"annotations": {
"team": "SRE"
},
"modes": [
"performance",
"threshold",
"alert"
],
"url": <LINK_TO_CHECK_RULE>
}
],
"url": <LINK_TO_FAILED_CECK>
}
}
}| Field Name | Description |
|---|---|
| type | Status of the alert, any of alert.ongoing / alert.resolved / alert.superseded / alert.closed |
| data.issue.id | Unique ID for this specific issue |
| data.issue.issueIdentifier | Identifier for the combination of CheckRule and Resource, should remain stable over different issue instances |
| data.issue.checkrule.id | Unique ID for the CheckRule that triggered the issue |
| data.issue.checkrule.version | Version of the CheckRule that triggered the issue, every configuration change leads to a new version |