Alerting
Notifications
Notifiers
Webhook

Create a webhook notifier

To configure a webhook notifier, enter a URL that specifies the endpoint to send HTTP POST requests to.

To create a webhook notifier:

  1. In the navigation menu select Alerts> Notifiers.

  2. Click Create Notifier.

  3. Enter a descriptive name for the notifier.

  4. Select Webhook as the type of notifier you want to create.

  5. In the URL field, enter a URL, which is called as a POST request. For example:

    https://webhook.site/3723e8cb-b1b4-4399-86b0-e37f36a2acc5

  6. Click Save.

Webhook notifier request body

The following example outlines the body for a POST request to a webhook. The request consists of one triggered alert called "test alert" that has several associated labels, such as component, instance, and job.

This example contains several notable sections:

  • commonLabels: contains labels that are common across all alerts in a notification display. Each alerting series includes the full list of labels. Any static labels that you define also display under commonLabels.

  • groupLabels: contains label values for the related signal display, in addition to a "severity" for the label.

  • fingerprint: a representation of an alerting series, expressed as a deterministic value based on the hash of the labels.

{
  "notifier": "test webhook",
  "status": "firing",
  "alerts": [
    {
      "status": "firing",
      "labels": {
        "alertname": "test alert",
        "component": "remote_write",
        "instance": "localhost:3030",
        "job": "collector_binary",
        "severity": "critical",
        "pod_name": "prom-74cbfb46c9-2ftk9"
      },
      "annotations": {
        "ruleid": "32bb3fbe-c10b-44bb-a4c0-3d053f4a08cd",
        "monitor_slug": "test-monitor",
        "notification_policy_slug": "test-policy"
      },
      "startsAt": "2020-05-19T13:57:21.68227886Z",
      "endsAt": "0001-01-01T00:00:00Z",
      "fingerprint": "7424223989b20025"
    }
  ],
  "groupLabels": {
    "alertname": "test alert",
    "severity": "critical"
  },
  "commonLabels": {
    "alertname": "test alert",
    "component": "remote_write",
    "instance": "localhost:3030",
    "job": "collector_binary",
    "severity": "critical",
    "pod_name": "prom-74cbfb46c9-2ftk9"
  },
  "commonAnnotations": {
    "ruleid": "32bb3fbe-c10b-44bb-a4c0-3d053f4a08cd",
    "monitor_slug": "test-monitor",
    "notification_policy_slug": "test-policy"
  },
  "version": "4"
}

Webhook IP addresses

Chronosphere has established a list of static IP addresses which serve outbound webhook notification traffic. Use these addresses in your company's allowlist to restrict traffic and maintain security.

Chronosphere also provides a full list of IP addresses (opens in a new tab).

Chronosphere Observability Platform serves outbound webhook traffic from the following IP addresses:

  • 104.198.2.151
  • 34.122.142.108
  • 34.122.149.117
  • 34.122.224.78
  • 34.127.109.43
  • 34.135.53.117
  • 34.145.80.163
  • 34.16.24.232
  • 34.168.147.207
  • 34.168.150.81
  • 34.171.52.135
  • 34.173.251.109
  • 34.28.62.245
  • 34.29.130.124
  • 34.29.185.167
  • 34.41.168.213
  • 34.70.121.15
  • 34.82.119.158
  • 34.82.143.37
  • 34.82.179.176
  • 34.82.243.234
  • 34.83.169.174
  • 34.83.7.178
  • 34.83.75.236
  • 35.188.223.136
  • 35.188.42.84
  • 35.197.55.241
  • 35.225.28.124
  • 35.227.141.247
  • 35.230.72.253
  • 35.233.215.68
  • 35.239.112.38

Last updated: 2024.06.18

VictorOpsNotification policies