Integrations on Grafana Labs

Grafana Alerting

Tue, 07 Apr 2026 10:28:26 +0000

Grafana Alerting integration for Grafana OnCall

⚠️ A note about (Legacy) integrations: Integrations that were created before version 1.3.21 were marked as (Legacy) and recently migrated. These integrations are receiving and escalating alerts, but some manual adjustments might be required. Here you can read more about changes.

Grafana Alerting for Grafana OnCall can be set up using two methods:

Grafana OnCall is connected to the same Grafana instance being used to manage Grafana OnCall.
Grafana OnCall is connected to one or more Grafana instances, separate from the one being used to manage Grafana OnCall.

Configure Grafana Alerting in same Grafana instance

Use the following method if you are connecting Grafana OnCall with alerts coming from the same Grafana instance from which Grafana OnCall is being managed.

In Grafana OnCall, navigate to the Integrations tab and select New Integration to receive alerts.
Click Quick connect in the Grafana Alerting tile. This will open a New Grafana Alerting integration configuration window.
In the opened window, enter a name and description for the integration and choose existing or create a new contact point. This contact point will send alerts to the created integration.

Note: You must connect the contact point with a notification policy in Grafana Alerting to receive alerts in Grafana OnCall. For more information, see Contact points in Grafana Alerting
Determine the escalation chain for the new integration by either selecting an existing one or by creating a new escalation chain.
In Grafana Cloud Alerting, navigate to Alerting > Contact Points and find a contact point with a name matching the integration you created in Grafana OnCall.
Click the Edit (pencil) icon, then click Test. This will send a test alert to Grafana OnCall.

Configure external Grafana Alerting from other Grafana Instance

Connect Grafana OnCall with alerts coming from a Grafana instance that is different from the instance that Grafana OnCall is being managed:

In Grafana OnCall, navigate to the Integrations tab and select New Integration to receive alerts.
Select the Alertmanager tile.
Enter a name and description for the integration, click Create
A new page will open with the integration details. Copy the OnCall Integration URL from HTTP Endpoint section.
Go to the other Grafana instance to connect to Grafana OnCall and navigate to Alerting > Contact Points.
Select New Contact Point.
Choose the contact point type webhook, then paste the URL generated in step 3 into the URL field.

Note: You must connect the contact point with a notification policy in Grafana Alerting to receive alerts in Grafana OnCall. For more information, see Contact points in Grafana Alerting
Click the Edit (pencil) icon, then click Test. This will send a test alert to Grafana OnCall.

Note about grouping and autoresolution

Grafana OnCall relies on the Grafana Alerting grouping and autoresolution mechanism to ensure consistency between alert state in OnCall and AlertManager. It’s recommended to configure grouping on the Grafana Alerting side and use default grouping and autoresolution templates on the OnCall side. Changing this templates might lead to incorrect grouping and autoresolution behavior.

Note about legacy integration

Before we were using each alert from Grafana Alerting group as a separate payload:

{
  "labels": {
    "severity": "critical",
    "alertname": "InstanceDown"
  },
  "annotations": {
    "title": "Instance localhost:8081 down",
    "description": "Node has been down for more than 1 minute"
  },
  ...
}

This behaviour was leading to mismatch in alert state between OnCall and Grafana Alerting and draining of rate-limits, since each Grafana Alerting alert was counted separately.

We decided to change this behaviour to respect Grafana Alerting grouping by using AlertManager group as one payload.

{
  "alerts": [...],
  "groupLabels": {
    "alertname": "InstanceDown"
  },
  "commonLabels": {
    "job": "node", 
    "alertname": "InstanceDown"
  },
  "commonAnnotations": {
    "description": "Node has been down for more than 1 minute"
  },
  "groupKey": "{}:{alertname=\"InstanceDown\"}",
  ...
}

You can read more about AlertManager Data model here.

After-migration checklist

Integration URL will stay the same, so no need to change AlertManager or Grafana Alerting configuration. Integration templates will be reset to suit new payload. It is needed to adjust routes and outgoing webhooks manually to new payload.

Send a new demo alert to the migrated integration.
Adjust routes to the new shape of payload. You can use payload of the demo alert from previous step as an example.
If outgoing webhooks utilized the alerts payload from the migrated integration in the [trigger][trigger_webhook_template] or [data][data_webhook_template] template it’s needed to adjust them as well.

Alertmanager

Tue, 07 Apr 2026 10:28:26 +0000

Alertmanager integration for Grafana OnCall

⚠️ A note about (Legacy) integrations: Integrations that were created before version 1.3.21 (1 August 2023) were marked as (Legacy) and recently migrated. These integrations are receiving and escalating alerts, but some manual adjustments might be required. Here you can read more about changes.

The Alertmanager integration handles alerts from Prometheus Alertmanager. This integration is the recommended way to send alerts from Prometheus deployed in your infrastructure, to Grafana OnCall.

Pro tip: Create one integration per team, and configure alertmanager labels selector to send alerts only related to that team

Configuring Grafana OnCall to Receive Alerts from Prometheus Alertmanager

In the Integrations tab, click + New integration.
Select Alertmanager Prometheus from the list of available integrations.
Enter a name and description for the integration, click Create
A new page will open with the integration details. Copy the OnCall Integration URL from HTTP Endpoint section. You will need it when configuring Alertmanager.

Configuring Alertmanager to Send Alerts to Grafana OnCall

Add a new Webhook receiver to receivers section of your Alertmanager configuration
Set url to the OnCall Integration URL from previous section
- Note: The url has a trailing slash that is required for it to work properly.
Set send_resolved to true, so Grafana OnCall can autoresolve alert groups when they are resolved in Alertmanager
It is recommended to set max_alerts to less than 100 to avoid requests that are too large.
Use this receiver in your route configuration

Here is the example of final configuration:

route:
  receiver: "oncall"
  group_by: [alertname, datacenter, app]

receivers:
  - name: "oncall"
    webhook_configs:
      - url: <integration-url>
        send_resolved: true
        max_alerts: 100

Complete the Integration Configuration

Complete configuration by setting routes, templates, maintenances, etc. Read more in this section

Note about grouping and autoresolution

Grafana OnCall relies on the Alertmanager grouping and autoresolution mechanism to ensure consistency between alert state in OnCall and AlertManager. It’s recommended to configure grouping on the Alertmanager side and use default grouping and autoresolution templates on the OnCall side. Changing this templates might lead to incorrect grouping and autoresolution behavior. This is unlikely to be what you want, unless you have disabled grouping on the AlertManager side.

Configuring OnCall Heartbeats (optional)

An OnCall heartbeat acts as a monitoring for monitoring systems. If your monitoring is down and stop sending alerts, Grafana OnCall will notify you about that.

Configuring Grafana OnCall Heartbeat

Go to Integration Page, click on three dots on top right, click Heartbeat settings
Copy OnCall Heartbeat URL, you will need it when configuring Alertmanager
Set up Heartbeat Interval, time period after which Grafana OnCall will start a new alert group if it doesn’t receive a heartbeat request

Configuring Alertmanager to send heartbeats to Grafana OnCall Heartbeat

You can configure Alertmanager to regularly send alerts to the heartbeat endpoint. Add vector(1) as a heartbeat generator to prometheus.yaml. It will always return true and act like always firing alert, which will be sent to Grafana OnCall once in a given period of time:

groups:
  - name: meta
    rules:
      - alert: heartbeat
        expr: vector(1)
        labels:
          severity: none
        annotations:
          description: This is a heartbeat alert for Grafana OnCall
          summary: Heartbeat for Grafana OnCall

Add receiver configuration to prometheus.yaml with the OnCall Heartbeat URL:

  ...
  route:
  ...
      routes:
      - match:
          alertname: heartbeat
        receiver: 'grafana-oncall-heartbeat'
        group_wait: 0s
        group_interval: 1m
        repeat_interval: 50s
  receivers:
  - name: 'grafana-oncall-heartbeat'
    webhook_configs:
  - url: https://oncall-dev-us-central-0.grafana.net/oncall/integrations/v1/alertmanager/1234567890/heartbeat/
    send_resolved: false

Note about legacy integration

Legacy integration was using each alert from AlertManager group as a separate payload:

{
  "labels": {
    "severity": "critical",
    "alertname": "InstanceDown"
  },
  "annotations": {
    "title": "Instance localhost:8081 down",
    "description": "Node has been down for more than 1 minute"
  },
  ...
}

This behaviour was leading to mismatch in alert state between OnCall and AlertManager and draining of rate-limits, since each AlertManager alert was counted separately.

We decided to change this behaviour to respect AlertManager grouping by using AlertManager group as one payload.

{
  "alerts": [...],
  "groupLabels": {
    "alertname": "InstanceDown"
  },
  "commonLabels": {
    "job": "node", 
    "alertname": "InstanceDown"
  },
  "commonAnnotations": {
    "description": "Node has been down for more than 1 minute"
  },
  "groupKey": "{}:{alertname=\"InstanceDown\"}",
  ...
}

You can read more about AlertManager Data model here.

After-migration checklist

Integration URL will stay the same, so no need to change AlertManager or Grafana Alerting configuration. Integration templates will be reset to suit new payload. It is needed to adjust routes and outgoing webhooks manually to new payload.

Send a new demo alert to the migrated integration.
Adjust routes to the new shape of payload. You can use payload of the demo alert from previous step as an example.
If outgoing webhooks utilized the alerts payload from the migrated integration in the trigger or data template it’s needed to adjust them as well.

Page people manually

Tue, 07 Apr 2026 10:28:26 +0000

Page people manually

Grafana OnCall relies on automated and pre-configured workflows, such as integrations, routes, and escalation chains to handle most of the incident response process. However, sometimes you might need to page a team or request assistance from specific people that are not part of these pre-defined rules.

For such ad-hoc scenarios, Grafana OnCall allows you to create an alert group, input necessary information, and decide who will be alerted – a team, or a set of users.

Page a team

Click on + Escalation on the Alert groups page to start creating a new alert group. From there, you can configure the alert group to notify a particular team and optionally include additional users. Here are the inputs you need to fill in:

Message: Write a message to provide more details or instructions to those whom you are paging.
Team: Select the team you want to page. The team’s direct paging integration will be used for notification. Note that you will only see teams that have a “contactable” direct paging integration (ie. it has an escalation chain assigned to it, or has at least one Chatops integration connected to send notifications to).
Users: Include more users to the alert group. For each additional user, you can select a notification policy: default or important.

The same feature is also available as /escalate Slack command.

Add users to an existing alert group

If you want to page more people for an existing alert group, you can do so using the + Add button, within the “Participants” section on the specific alert group’s page. The same functionality is available in Slack using the Responders button in the alert group’s message.

Notifying additional users doesn’t disrupt or interfere with the escalation chain configured for the alert group; it simply adds more responders and notifies them immediately. Note that adding users for an existing alert group will page them even if the alert group is silenced or acknowledged, but not if the alert group is resolved.

It’s not possible to page a team for an existing alert group. To page a specific team, you need to create a new alert group.

Learn the flow and handle warnings

When you pick a team to page, Grafana OnCall will automatically use the right direct paging integration for the team. “Direct paging” is a special kind of integration in Grafana OnCall that is unique per team and is used to send alerts to the team’s ChatOps channels and start an appropriate escalation chain.

Set up direct paging for a team

By default all teams will have a direct paging integration created for them. However, these are not configured by default. If a team does not have their direct paging integration configured, such that it is “contactable” (ie. it has an escalation chain assigned to it, or has at least one Chatops integration connected to send notifications to), you will not be able to direct page this team. If this happens, consider following the following steps for the team (or reach out to the relevant team and suggest doing so).

Navigate to the Integrations page and find the “Direct paging” integration for the team in question. From the integration’s detail page, you can customize its settings, link it to an escalation chain, and configure associated ChatOps channels. To confirm that the integration is functioning as intended, create a new alert group and select the same team for a test run.

Amazon SNS

Tue, 07 Apr 2026 10:28:26 +0000

This integration is not available in OSS version

The Amazon SNS integration for Grafana OnCall handles ticket events sent from Amazon SNS webhooks. The integration provides grouping, auto-acknowledge and auto-resolve logic via customizable alert templates.

You must have the role of Admin to be able to create integrations in Grafana OnCall.

Configuring Grafana OnCall to Receive Alerts from Amazon SNS

In the Integrations tab, click + New integration.
Select Amazon SNS from the list of available integrations.
Enter a name and description for the integration, click Create
A new page will open with the integration details. Copy the OnCall Integration URL from HTTP Endpoint section.

Create a new Topic in https://console.aws.amazon.com/sns
Open this topic, then create a new subscription
Choose the protocol HTTPS
Add the OnCall Integration URL to the Amazon SNS Endpoint

AppDynamics

Tue, 07 Apr 2026 10:28:26 +0000

AppDynamics integration for Grafana OnCall

This integration is not available in OSS version

The AppDynamics integration for Grafana OnCall handles health rule violation events sent from AppDynamics actions. The integration provides grouping and auto-resolve logic via customizable alert templates.

You must have the role of Admin to be able to create integrations in Grafana OnCall.

Configuring Grafana OnCall to Receive Alerts from AppDynamics

In the Integrations tab, click + New integration.
Select AppDynamics from the list of available integrations.
Enter a name and description for the integration, click Create
A new page will open with the integration details. Copy the OnCall Integration URL from HTTP Endpoint section. You will need it when configuring AppDynamics.

Configuring AppDynamics to Send Alerts to Grafana OnCall

Create a new HTTP Request Template in AppDynamics to send events to Grafana OnCall using the integration URL above.

Refer to [AppDynamics documentation] (https://docs.appdynamics.com/appd/23.x/latest/en/appdynamics-essentials/alert-and-respond/actions/http-request-actions-and-templates) for more information on how to create HTTP Request Templates:

Use the following values when configuring a new HTTP Request Template:

Request URL:
- Method: POST
- Raw URL: OnCall Integration URL from previous section
Authentication:
- Type: None

Payload:

MIME Type: application/json
Template:

{
  "event": {
    "eventType": "${latestEvent.eventType}",
    "id": "${latestEvent.id}",
    "guid": "${latestEvent.guid}",
    "eventTypeKey": "${latestEvent.eventTypeKey}",
    "eventTime": "${latestEvent.eventTime}",
    "displayName": "${latestEvent.displayName}",
    "summaryMessage": "${latestEvent.summaryMessage}",
    "eventMessage": "${latestEvent.eventMessage}",
    "application": {
      "name": "${latestEvent.application.name}"
    },
    "node": {
      "name": "${latestEvent.node.name}"
    },
    "severity": "${latestEvent.severity}",
    "deepLink": "${latestEvent.deepLink}"
  }
}

Response Handling Criteria:
- Success Criteria: Status Code 200
Settings:
- One Request Per Event: Enabled

After setting up a template, create a new action in AppDynamics and select the template you created earlier. Now you can configure policies to trigger the action when certain events occur in AppDynamics. When configuring a policy, select the following events to trigger the action:

Health Rule Violation Started - Warning
Health Rule Violation Started - Critical
Health Rule Violation Continues - Warning
Health Rule Violation Continues - Critical
Health Rule Violation Upgraded - Warning to Critical
Health Rule Violation Downgraded - Critical to Warning
Health Rule Violation Ended - Warning
Health Rule Violation Ended - Critical
Health Rule Violation Canceled - Warning
Health Rule Violation Canceled - Critical

After setting up the connection, you can test it by sending a test request from the AppDynamics UI.

Understanding How Alerts Grouped and Auto-resolved

Grafana OnCall provides grouping and auto-resolve logic for the AppDynamics integration:

Alerts created from health rule violation events are grouped by application and node name
Alert groups are auto-resolved when the health rule violation is ended or canceled

Complete the Integration Configuration

Complete configuration by setting routes, templates, maintenances, etc. Read more in this section

Datadog

Tue, 07 Apr 2026 10:28:26 +0000

Datadog integration for Grafana OnCall

This integration is not available in OSS version

The Datadog integration for Grafana OnCall handles ticket events sent from Datadog webhooks. The integration provides grouping, auto-acknowledge and auto-resolve logic via customizable alert templates.

You must have the role of Admin to be able to create integrations in Grafana OnCall.

Configuring Grafana OnCall to Receive Alerts from Datadog

In the Integrations tab, click + New integration.
Select Datadog from the list of available integrations.
Enter a name and description for the integration, click Create
A new page will open with the integration details. Copy the OnCall Integration URL from HTTP Endpoint section.

Configuring Datadog to Send Alerts to Grafana OnCall

Navigate to the Integrations page from the sidebar
Search for webhook in the search bar
Enter a name for the integration, for example: grafana-oncall-alerts
Paste the OnCall Integration URL, then save
Navigate to the Events page from the sidebar to send the test alert
Type @webhook-grafana-oncall-alerts test alert
Click the post button

ElastAlert

Tue, 07 Apr 2026 10:28:26 +0000

ElastAlert integration for Grafana OnCall

The ElastAlert integration for Grafana OnCall handles ticket events sent from ElastAlert webhooks. The integration provides grouping, auto-acknowledge and auto-resolve logic via customizable alert templates.

You must have the role of Admin to be able to create integrations in Grafana OnCall.

Configuring Grafana OnCall to Receive Alerts from ElastAlert

In the Integrations tab, click + New integration.
Select ElastAlert from the list of available integrations.
Enter a name and description for the integration, click Create
A new page will open with the integration details. Copy the OnCall Integration URL from HTTP Endpoint section.

Configuring ElastAlert to Send Alerts to Grafana OnCall

To send an alert from ElastAlert to a webhook, follow these steps:

Refer to ElastAlert http-post docs for more details

Open your ElastAlert configuration file (e.g., config.yaml).
Locate the alert section.
Add the following configuration for the webhook alert:

alert: post
http_post_url: "http://example.com/api"
http_post_static_payload:
  title: abc123

Replace "abc123" with a suitable name for your alert, and "http://example.com/api" with OnCall Integration URL. 4. Save the configuration file.

After configuring the webhook, ElastAlert will send alerts to the specified endpoint when triggered. Make sure your webhook endpoint is configured to receive and process the incoming alerts.

Grouping, auto-acknowledge and auto-resolve

Grafana OnCall provides grouping, auto-acknowledge and auto-resolve logic for the ElastAlert integration:

Alerts created from ticket events are grouped by ticket ID
Alert groups are auto-acknowledged when the ticket status is set to “Pending”
Alert groups are auto-resolved when the ticket status is set to “Solved”

To customize this behaviour, consider modifying alert templates in integration settings.

Configuring Elastalert to send heartbeats to Grafana OnCall Heartbeat

Add the following rule to ElastAlert

    index: elastalert_status
    type: any
    alert: post
    http_post_url: {{ heartbeat_url }}
    realert:
        minutes: 1
    alert_text: elastalert is still running
    alert_text_type: alert_text_only

Fabric

Tue, 07 Apr 2026 10:28:26 +0000

Fabric integration for Grafana OnCall

This integration is not available in OSS version

The Fabric integration for Grafana OnCall handles ticket events sent from Fabric webhooks. The integration provides grouping, auto-acknowledge and auto-resolve logic via customizable alert templates.

You must have the role of Admin to be able to create integrations in Grafana OnCall.

Configuring Grafana OnCall to Receive Alerts from Fabric

In the Integrations tab, click + New integration.
Select Fabric from the list of available integrations.
Enter a name and description for the integration, click Create
A new page will open with the integration details. Copy the OnCall Integration URL from HTTP Endpoint section.

Configuring Fabric to Send Alerts to Grafana OnCall

Go to https://www.fabric.io/settings/apps
Choose your application
Navigate to Service Hooks -> WebHook
Enter URL: OnCall Integration URL
Click Verify
Choose “SEND IMPACT CHANGE ALERTS” and “ALSO SEND NON-FATAL ALERTS”

Inbound Email

Tue, 07 Apr 2026 10:28:26 +0000

Inbound Email integration for Grafana OnCall

Inbound Email integration will consume emails from dedicated email address and make alert groups from them.

Configure required environment variables

Refer to Inbound Email Setup for details.

Configure Inbound Email integration for Grafana OnCall

You must have an Admin role to create integrations in Grafana OnCall.

In the Integrations tab, click + New integration to receive alerts.
Select Inbound Email from the list of available integrations.
Get your dedicated email address in the Integration email section and use it to send your emails.

Grouping and auto-resolve

Alert groups will be grouped by email subject and auto-resolved if the email message text equals “OK”. This behaviour can be modified via custom templates.

Alerts from Inbound Email integration have the following payload:

{
   "subject": "<your_email_subject>",
   "message": "<your_email_message>",
   "sender": "<your_email_sender_address>"
}

Jira

Tue, 07 Apr 2026 10:28:26 +0000

Jira integration for Grafana OnCall

This integration is not available in OSS version

The Jira integration for Grafana OnCall handles issue events sent from Jira webhooks. The integration provides grouping, auto-acknowledge and auto-resolve logic via customizable alert templates.

You must have the role of Admin to be able to create integrations in Grafana OnCall.

Configuring Grafana OnCall to Receive Alerts from Jira

In the Integrations tab, click + New integration.
Select Jira from the list of available integrations.
Enter a name and description for the integration, click Create
A new page will open with the integration details. Copy the OnCall Integration URL from HTTP Endpoint section. You will need it when configuring Jira.

Configuring Jira to Send Alerts to Grafana OnCall

Create a new webhook connection in Jira to send events to Grafana OnCall using the integration URL above.

Refer to Jira documentation for more information on how to create and manage webhooks

When creating a webhook in Jira, select the following events to be sent to Grafana OnCall:

Issue - created
Issue - updated
Issue - deleted

After setting up the connection, you can test it by creating a new issue in Jira. You should see a new alert group in Grafana OnCall.

Grouping, auto-acknowledge and auto-resolve

Grafana OnCall provides grouping, auto-acknowledge and auto-resolve logic for the Jira integration:

Alerts created from issue events are grouped by issue key
Alert groups are auto-acknowledged when the issue status is set to “work in progress”
Alert groups are auto-resolved when the issue is closed or deleted

To customize this behaviour, consider modifying alert templates in integration settings.

Configuring Grafana OnCall to send data to Jira

Grafana OnCall can automatically create and resolve issues in Jira via outgoing webhooks. This guide provides example webhook configurations for common use cases, as well as information on how to set up a user in Jira to be used by Grafana OnCall.

Prerequisites

Create a new user in Jira to be used by Grafana OnCall. Obtain an API token for the user, these credentials will be used to communicate with Jira REST API.
Make sure the user has appropriate permissions to create and update issues in Jira.

Create issues in Jira

The steps below describe how to create an outgoing webhook in Grafana OnCall that will allow to automatically create issues in Jira from Grafana OnCall alert groups.

Create a new Outgoing Webhook in Grafana OnCall, and configure it as follows:

Trigger type: Alert Group Created
Integrations: Select integrations that will trigger the webhook
HTTP method: POST
Webhook URL:

https://<INSTANCE>.atlassian.net/rest/api/2/issue

Replace <INSTANCE> with your Jira instance.

Username: Email of the Jira user
Password: API token of the Jira user

Use the following JSON template as webhook data:

{
  "fields": {
    "project": {
      "key": "<PROJECT_KEY>"
    },
    "issuetype": {
      "name": "[System] Incident"
    },
    "summary": "{{alert_group.title}}",
    "description": "This issue is created automatically by Grafana OnCall. Alert group {{alert_group.id}}: {{alert_group.permalinks.web}}"
  }
}

Replace <PROJECT_KEY> with the key of the project in Jira.

Note: You might want to use a different issuetype.name depending on your Jira instance configuration and use case.

Resolve issues in Jira

The steps below describe how to create an outgoing webhook in Grafana OnCall that will allow to automatically resolve issues in Jira when an alert group is resolved in Grafana OnCall.

Trigger type: Resolved
Integrations: Select integrations that will trigger the webhook
HTTP method: POST
Webhook URL:

https://<INSTANCE>.atlassian.net/rest/api/2/issue/{{responses.<WEBHOOK_ID>.key}}/transitions

Replace <INSTANCE> with your Jira instance, and <WEBHOOK_ID> with the ID of the webhook used for creating issues.

Username: Email of the Jira user
Password: API token of the Jira user

Use the following JSON template as webhook data:

{
  "transition": {
    "id": "<TRANSITION_ID>"
  },
  "fields": {
    "resolution": {
      "name": "Done"
    }
  },
  "update": {
    "comment": [
      {
        "add": {
          "body": "Resolved by Grafana OnCall.",
          "public": false
        }
      }
    ]
  }
}

Replace <TRANSITION_ID> with the ID of the transition specific to your Jira instance. See here for more info on how to find the transition ID in Jira UI, or use the REST API endpoint to get the list of available transitions.

Advanced usage

The examples above describe how to create outgoing webhooks in Grafana OnCall that will allow to automatically create and resolve issues in Jira.

Consider modifying example templates to fit your use case (e.g. to include more information on alert groups). Refer to outgoing webhooks documentation for more information on available template variables and webhook configuration.

For more information on Jira REST API, refer to Jira REST API documentation.

Kapacitor

Tue, 07 Apr 2026 10:28:26 +0000

Kapacitor integration for Grafana OnCall

The Kapacitor integration for Grafana OnCall handles ticket events sent from Kapacitor webhooks. The integration provides grouping, auto-acknowledge and auto-resolve logic via customizable alert templates.

You must have the role of Admin to be able to create integrations in Grafana OnCall.

Configuring Grafana OnCall to Receive Alerts from Kapacitor

In the Integrations tab, click + New integration.
Select Kapacitor from the list of available integrations.
Enter a name and description for the integration, click Create
A new page will open with the integration details. Copy the OnCall Integration URL from HTTP Endpoint section.

Configuring Kapacitor to Send Alerts to Grafana OnCall

To send an alert from Kapacitor, you can follow these steps:

Create a Kapacitor TICKscript or modify an existing one to define the conditions for triggering the alert. The TICKscript specifies the data source, data processing, and the alert rule. Here’s an example of a simple TICKscript:

stream
    |from()
        .measurement('measurement_name')
        .where(lambda: <condition>)
    |alert()
        .webhook('<webhook_url>')

Replace 'measurement_name' with the name of the measurement you want to monitor, <condition> with the condition that triggers the alert, and '<webhook_url>' with OnCall Integration URL 2. Save the TICKscript file with a .tick extension, for example, alert_script.tick. 3. Start the Kapacitor service using the TICKscript:

kapacitor define <alert_name> -tick /path/to/alert_script.tick
kapacitor enable <alert_name>
kapacitor reload

Replace <alert_name> with a suitable name for your alert. 4. Ensure that the Kapacitor service is running and actively monitoring the data. When the condition defined in the TICKscript is met, Kapacitor will trigger the alert and send a POST request to the specified webhook URL with the necessary information. Make sure your webhook endpoint is configured to receive and process the incoming alerts from Kapacitor.

New Relic

Tue, 07 Apr 2026 10:28:26 +0000

New Relic integration for Grafana OnCall

This integration is not available in OSS version

The New Relic integration for Grafana OnCall handles ticket events sent from New Relic webhooks. The integration provides grouping, auto-acknowledge and auto-resolve logic via customizable alert templates.

You must have the role of Admin to be able to create integrations in Grafana OnCall.

Configuring Grafana OnCall to Receive Alerts from New Relic

In the Integrations tab, click + New integration.
Select New Relic from the list of available integrations.
Enter a name and description for the integration, click Create
A new page will open with the integration details. Copy the OnCall Integration URL from HTTP Endpoint section.

Configuring New Relic to Send Alerts to Grafana OnCall

Go to “Alerts”.
Go to “Notification Channels”.
Create “Webhook” notification channel.
Set the following URL: OnCall Integration URL
Check “Payload type” is JSON.

Pingdom

Tue, 07 Apr 2026 10:28:26 +0000

Pingdom integration for Grafana OnCall

This integration is not available in OSS version

The Pingdom integration for Grafana OnCall handles ticket events sent from Pingdom webhooks. The integration provides grouping, auto-acknowledge and auto-resolve logic via customizable alert templates.

You must have the role of Admin to be able to create integrations in Grafana OnCall.

Configuring Grafana OnCall to Receive Alerts from Pingdom

In the Integrations tab, click + New integration.
Select Pingdom from the list of available integrations.
Enter a name and description for the integration, click Create
A new page will open with the integration details. Copy the OnCall Integration URL from HTTP Endpoint section.

Configuring Pingdom to Send Alerts to Grafana OnCall

Go to https://my.pingdom.com/integrations/settings
Click “Add Integration”.
Type: Webhook. Name: Grafana OnCall. URL: OnCall Integration URL
Go to “Reports” -> “Uptime” -> “Edit Check”.
Select Grafana OnCall integration in the bottom.
Click “Modify Check” to save.

PRTG

Tue, 07 Apr 2026 10:28:26 +0000

PRTG integration for Grafana OnCall

This integration is not available in OSS version

The PRTG integration for Grafana OnCall handles ticket events sent from PRTG webhooks. The integration provides grouping, auto-acknowledge and auto-resolve logic via customizable alert templates.

You must have the role of Admin to be able to create integrations in Grafana OnCall.

Configuring Grafana OnCall to Receive Alerts from PRTG

In the Integrations tab, click + New integration.
Select PRTG from the list of available integrations.
Enter a name and description for the integration, click Create
A new page will open with the integration details. Copy the OnCall Integration URL from HTTP Endpoint section.

Configuring PRTG to Send Alerts to Grafana OnCall

PRTG can use the script to send the alerts to Grafana OnCall. Please use the format below

Body Fields Format:

alert_uid [char][not required] - unique alert ID for grouping;
title [char][not required] - title;
image_url [char][not required] - url for image attached to alert;
state [char][not required] - could be "ok" or "alerting", helpful for auto-resolving;
link_to_upstream_details [char][not required] - link back to your monitoring system;
message [char][not required] - alert details;

ps1 script example:

# This script sends alerts from PRTG to Grafana OnCall
Param(
  [string]$sensorid,
  [string]$date,
  [string]$device,
  [string]$shortname,
  [string]$status,
  [string]$message,
  [string]$datetime,
  [string]$linksensor,
  [string]$url
)

# PRTG Server
$PRTGServer = "localhost:8080"
$PRTGUsername = "oncall"
$PRTGPasshash  = *****

#Directory for logging
$LogDirectory = "C:\temp\prtg-notifications-msteam.log"

#Acknowledgement Message for alerts ack'd via Teams
$ackmessage = "Problem has been acknowledged via OnCall."

# the acknowledgement URL
$ackURL = [string]::Format("{0}/api/acknowledgealarm.htm?id={1}&ackmsg={2}&username={3}&passhash={4}",
$PRTGServer,$sensorID,$ackmessage,$PRTGUsername,$PRTGPasshash);

# Autoresolve an alert in OnCall
if($status -eq "Up")
{ $state = "ok" }
ElseIf($status -match "now: Up")
{ $state = "ok" }
ElseIf($status -match "Up (was:")
{ $state = "ok" }
Else
{ $state = "alerting" }

$image_datetime = [datetime]::parse($datetime)
$sdate = $image_datetime.AddHours(-1).ToString("yyyy-MM-dd-HH-mm-ss")
$edate = $image_datetime.ToString("yyyy-MM-dd-HH-mm-ss")

$image_url = "$PRTGServer/chart.png?type=graph&graphid=-1&avg=0&width=1000&height=400
&username=$PRTGUsername&passhash=$PRTGPasshash&id=$sensorid&sdate=$sdate&edate=$edate"

$Body = @{
            "alert_uid"="$sensorid $date";
            "title"="$device $shortname $status at $datetime ";
            "image_url"=$image_url;
            "state"=$state;
            "link_to_upstream_details"="$linksensor";
            "message"="$message";
            "ack_url_get"="$ackURL"
} | ConvertTo-Json
$Body

try
{ Invoke-RestMethod -uri $url -Method Post -body $Body -ContentType 'application/json; charset=utf-8'; exit 0; }
Catch
{
    $ErrorMessage = $_.Exception.Message
    (Get-Date).ToString() +" - "+ $ErrorMessage | Out-File -FilePath $LogDirectory -Append
    exit 2;
}

Sentry

Tue, 07 Apr 2026 10:28:26 +0000

Sentry integration for Grafana OnCall

This integration is not available in OSS version

The Sentry integration for Grafana OnCall handles ticket events sent from Sentry webhooks. The integration provides grouping, auto-acknowledge and auto-resolve logic via customizable alert templates.

You must have the role of Admin to be able to create integrations in Grafana OnCall.

Configuring Grafana OnCall to Receive Alerts from Sentry

In the Integrations tab, click + New integration.
Select Sentry from the list of available integrations.
Enter a name and description for the integration, click Create
A new page will open with the integration details. Copy the OnCall Integration URL from HTTP Endpoint section.

Configuring Sentry to Send Alerts to Grafana OnCall

To send a webhook alert from Sentry, you can follow these steps:

Log in to your Sentry account.
Navigate to your project’s settings.
Click on “Alerts” in the sidebar menu.
Click on “New Alert Rule” to create a new alert rule.
Configure the conditions for the alert rule based on your requirements. For example, you can set conditions based on issue level, event frequency, or specific tags.
In the “Actions” section, select “Webhook” as the action type.
Provide the necessary details for the webhook:
- URL: OnCall Integration URL
- Method: POST
- Payload: Define the payload structure and content that you want to send to the webhook endpoint. You can use Sentry’s dynamic variables to include relevant information in the payload.
Save the alert rule.

Once the alert conditions are met, Sentry will trigger the webhook action and send a request to the Grafana OnCall.

ServiceNow integration for Grafana OnCall

Tue, 07 Apr 2026 10:28:26 +0000

ServiceNow integration for Grafana OnCall

Note
This integration is available exclusively on Grafana Cloud.

Integrate ServiceNow with Grafana OnCall for bidirectional functionality that automatically creates and updates incidents in ServiceNow based on Grafana OnCall alert groups, and vice versa. Whether your alerts originate from ServiceNow or another integration like Alertmanager or Grafana Alerting, you can manage updates and status changes directly from ServiceNow.

Use this integration to automate the following processes:

Create an incident in ServiceNow when an alert group is created in OnCall.
Update the incident state in ServiceNow when the alert group status changes in OnCall.
Create an alert group in OnCall when an incident is created in ServiceNow.
Update the alert group status in OnCall when the incident state changes in ServiceNow.

Before you begin

Before configuring the integration, ensure you or your ServiceNow Admin have created a Service account specifically for Grafana OnCall integration.

Follow these steps to create a ServiceNow user for Grafana OnCall:

In ServiceNow,navigate to User Administration > Users and click New.
Fill in the following details:
- Username: grafana-oncall
- First name: Grafana OnCall
- Active: ✔
- Web service access only: ✔
After creating the user, generate a password using the Set Password button. Securely store the password for later use.
Navigate to the Roles tab and grant the following roles to the user:
- itil (for incident creation and updates)
- personalize_choices (to fetch the list of available incident states)

Configure ServiceNow integration

Create integration

On the Integrations tab in Grafana OnCall, click + New integration.
Select ServiceNow from the list of available integrations.
Enter a name and description for the integration.
Enter ServiceNow credentials (instance URL, username, and password of the Grafana OnCall user) and verify the connection.
Ensure Create default outgoing webhooks is enabled to create necessary webhooks in Grafana OnCall for sending alerts to ServiceNow.
Click Create integration.

Map incident states

Map ServiceNow incident states to OnCall alert group statuses.

Example:

Firing -> New
Acknowledged -> In Progress
Resolved -> Resolved
Silenced -> Not Selected

Generate Business Rule script

Generate a ServiceNow Business Rule script to enable your ServiceNow instance to send updates to Grafana OnCall.

Note
You can’t view the script again after closing the dialog, but you can regenerate it at any time in integration settings.

Generate a new ServiceNow Business Rule script and copy it to your clipboard.
In ServiceNow, navigate to System Definition > Business Rules and click New.
Fill in the following details:
- Name: grafana-oncall
- Table: incident
- Active: ✔
- Advanced: ✔
- When to run > When: before
- When to run > Insert: ✔
- When to run > Update: ✔
- Advanced > Script: Paste the generated script
Click Submit to save the Business Rule.

In Grafana OnCall, click Proceed to complete the integration setup.

Test the integration

Create a new incident in ServiceNow.
Verify that a new alert group is created in Grafana OnCall.
Acknowledge the alert group in Grafana OnCall, and verify that the incident state is updated in ServiceNow.
Resolve the incident in ServiceNow, and verify that the alert group status is updated in Grafana OnCall.

Connect other integrations

You can connect other integrations such as Alertmanager, Grafana Alerting, and others to your ServiceNow integration for a consolidated workflow. When connected, Grafana OnCall sends alerts from the connected integrations to ServiceNow and update alert groups on the connected integrations based on incident state changes in ServiceNow. Connected integrations utilize the same ServiceNow credentials and outgoing webhooks as the ServiceNow integration they are connected to.

To connect other integrations:

Navigate to the Outgoing tab of an existing ServiceNow integration.
Use the Send data from other integrations section to connect other integrations.
Enable the backsync option if you want alert groups from connected integrations to be updated from ServiceNow. If disabled, Grafana OnCall will only send alerts to ServiceNow, but not receive updates back.
Test the connection by creating a demo alert for the connected integration.
- Verify that an incident is created in ServiceNow.
- Verify that incident state changes in ServiceNow are reflected in Grafana OnCall, and vice-versa.

Advanced usage

Customize the integration behavior according to your needs by editing the outgoing webhooks on the Outgoing tab of the integration.

Custom incident fields

You can set custom fields on ServiceNow incidents. To do so, edit the Alert group created webhook on the Outgoing tab of the integration.

Example: Set the “urgency” field based on alert group labels, add the provided JSON to Data template:

{
  ...,
  "urgency": "{{ alert_group.labels.urgency }}"
}

For more information, refer to Outgoing webhook templates and Alert group labels.

Stackdriver

Tue, 07 Apr 2026 10:28:26 +0000

Stackdriver integration for Grafana OnCall

This integration is not available in OSS version

The Stackdriver integration for Grafana OnCall handles ticket events sent from Stackdriver webhooks. The integration provides grouping, auto-acknowledge and auto-resolve logic via customizable alert templates.

You must have the role of Admin to be able to create integrations in Grafana OnCall.

Configuring Grafana OnCall to Receive Alerts from Stackdriver

In the Integrations tab, click + New integration.
Select Stackdriver from the list of available integrations.
Enter a name and description for the integration, click Create
A new page will open with the integration details. Copy the OnCall Integration URL from HTTP Endpoint section.

Configuring Stackdriver to Send Alerts to Grafana OnCall

Create a notification channel in Stackdriver by navigating to Workspace Settings -> WEBHOOKS -> Add Webhook OnCall Integration URL
Create and alert in Stackdriver by navigating to Alerting -> Policies -> Add Policy -> Choose Notification Channel using the channel set up in step 1

UptimeRobot

Tue, 07 Apr 2026 10:28:26 +0000

UptimeRobot integration for Grafana OnCall

This integration is not available in OSS version

The UptimeRobot integration for Grafana OnCall handles ticket events sent from UptimeRobot webhooks. The integration provides grouping, auto-acknowledge and auto-resolve logic via customizable alert templates.

You must have the role of Admin to be able to create integrations in Grafana OnCall.

Configuring Grafana OnCall to Receive Alerts from UptimeRobot

In the Integrations tab, click + New integration.
Select UptimeRobot from the list of available integrations.
Enter a name and description for the integration, click Create
A new page will open with the integration details. Copy the OnCall Integration URL from HTTP Endpoint section.

Configuring UptimeRobot to Send Alerts to Grafana OnCall

Open https://uptimerobot.com and log in
Go to My Settings > Add Alert Contact and set the following fields:
Alert Contact Type: Webhook
Friendly Name: Grafana OnCall
URL to Notify: OnCall Integration URL POST Value (JSON Format):

{
  "monitorURL": "monitorURL",
  "monitorFriendlyName": "monitorFriendlyName",
  "alertType": "alertType",
  "alertTypeFriendlyName": "alertTypeFriendlyName",
  "alertDetails": "alertDetails",
  "alertDuration": "alertDuration",
  "sslExpiryDate": "sslExpiryDate",
  "sslExpiryDaysLeft": "sslExpiryDaysLeft"
}

Flag Send as JSON
Click Save Changes and Close
Send Test Alert to Grafana OnCall
Click Add New Monitor
Monitor Type HTTP(s)
Friendly Name Test OnCall
Set URL to http://devnull.oncall.io or any other non-existent domain
Click Checkbox next to OnCall Alert Contact (created in the previous step)
Click Create Monitor

Zabbix

Tue, 07 Apr 2026 10:28:26 +0000

Zabbix integration for Grafana OnCall

Zabbix is an open-source monitoring software tool for diverse IT components, including networks, servers, virtual machines, and cloud services. Zabbix provides monitoring for metrics such as network utilization, CPU load, and disk space consumption.

Configure Zabbix integration for Grafana OnCall

This integration is available for Grafana Cloud OnCall. You must have an Admin role to create integrations in Grafana OnCall.

In the Integrations tab, click + New integration to receive alerts.
Select Zabbix from the list of available integrations
Follow the instructions in the How to connect window to get your unique integration URL and review next steps.

Configure the Zabbix server

Deploy a Zabbix playground if you don’t have one set up:

 docker run --name zabbix-appliance -t \
      -p 10051:10051 \
      -p 80:80 \
      -d zabbix/zabbix-appliance:latest

Establish an ssh connection to a Zabbix server.
Bash
```
docker exec -it zabbix-appliance bash
```
Place the grafana_oncall.sh script in the AlertScriptsPath directory specified within the Zabbix server configuration file (zabbix_server.conf).
Bash
```
grep AlertScriptsPath /etc/zabbix/zabbix_server.conf
```
Note: The script must be executable by the user running the zabbix_server binary (usually “zabbix”) on the Zabbix server. For example, chmod +x grafana_oncall.sh
Bash
```
ls -lh /usr/lib/zabbix/alertscripts/grafana_oncall.sh
-rw-r--r--    1 root     root        1.5K Jun  6 07:52 /usr/lib/zabbix/alertscripts/grafana_oncall.sh
```

Configure Zabbix alerts

Within Zabbix web interface, do the following:

In a browser, open localhost:80.
Navigate to Adminitstration > Media Types > Create Media Type.
Create a Media Type with the following fields.
- Name: Grafana OnCall
- Type: script
- Script parameters:
  - {ALERT.SENDTO}
  - {ALERT.SUBJECT}
  - {ALERT.MESSAGE}

Set the {ALERT.SEND_TO} value

To send alerts to Grafana OnCall, the {ALERT.SEND_TO} value must be set in the user media configuration.

In the web UI, navigate to Administration > Users and open the user properties form.
In the Media tab, click Add and copy the link from Grafana OnCall in the Send to field.
Click Test in the last column to send a test alert to Grafana OnCall.
Specify Send to OnCall using the unique integration URL from the above step in the testing window that opens.
Create a test message with a body and optional subject and click Test.

Grouping and auto-resolve of Zabbix notifications

Grafana OnCall provides grouping and auto-resolve of Zabbix notifications. Use the following procedure to configure grouping and auto-resolve.

Provide a parameter as an identifier for group differentiation to Grafana OnCall.
Append that variable to the subject of the action as ONCALL_GROUP: ID, where ID is any of the Zabbix macros. For example, {EVENT.ID}. The Grafana OnCall script grafana_oncall.sh extracts this event and passes the alert_uid to Grafana OnCall.
To enable auto-resolve within Grafana Oncall, the “Resolved” keyword is required in the Default subject field in Recovered operations.

grafana_oncall.sh script

#!/bin/bash
# This is the modification of original ericos's shell script.

# Get the url ($1), subject ($2), and message ($3)
url="$1"
subject="${2//$'\r\n'/'\n'}"
message="${3//$'\r\n'/'\n'}"

# Alert state depending on the subject indicating whether it is a trigger going in to problem state or recovering
recoversub='^RECOVER(Y|ED)?$|^OK$|^Resolved.*'

if [[ "$subject" =~ $recoversub ]]; then
    state='ok'
else
    state='alerting'
fi

payload='{
    "title": "'${subject}'",
    "state": "'${state}'",
    "message": "'${message}'"
}'

# Alert group identifier from the subject of action. Grouping will not work without ONCALL_GROUP in the action subject
regex='ONCALL_GROUP: ([a-zA-Z0-9_\"]*)'
if [[ "$subject" =~ $regex ]]; then
    alert_uid=${BASH_REMATCH[1]}
    payload='{
        "alert_uid": "'${alert_uid}'",
        "title": "'${subject}'",
        "state": "'${state}'",
        "message": "'${message}'"
    }'
fi

return=$(curl $url -d "${payload}" -H "Content-Type: application/json" -X POST)

More Information

For more information on Zabbix scripts, see scripts for notifications.

Zendesk

Tue, 07 Apr 2026 10:28:26 +0000

Zendesk integration for Grafana OnCall

This integration is not available in OSS version

The Zendesk integration for Grafana OnCall handles ticket events sent from Zendesk webhooks. The integration provides grouping, auto-acknowledge and auto-resolve logic via customizable alert templates.

You must have the role of Admin to be able to create integrations in Grafana OnCall.

Configuring Grafana OnCall to Receive Alerts from Zendesk

In the Integrations tab, click + New integration.
Select Zendesk from the list of available integrations.
Enter a name and description for the integration, click Create
A new page will open with the integration details. Copy the OnCall Integration URL from HTTP Endpoint section.

Configuring Zendesk to Send Alerts to Grafana OnCall

Create a new “Trigger or automation” webhook connection in Zendesk to send events to Grafana OnCall using the integration URL above.

Refer to Zendesk documentation for more information on how to create and manage webhooks.

After setting up a webhook in Zendesk, create a new trigger with the following condition: Meet ANY of the following conditions: "Ticket Is Created", "Ticket status Changed"

Set Notify webhook as the trigger action and select the webhook you created earlier. In the JSON body field, use the following JSON template:

{
  "ticket": {
    "id": "{{ticket.id}}",
    "url": "{{ticket.url}}",
    "status": "{{ticket.status}}",
    "title": "{{ticket.title}}",
    "description": "{{ticket.description}}"
  }
}

After setting up the connection, you can test it by creating a new ticket in Zendesk. You should see a new alert group in Grafana OnCall.

Grouping, auto-acknowledge and auto-resolve

Grafana OnCall provides grouping, auto-acknowledge and auto-resolve logic for the Zendesk integration:

Alerts created from ticket events are grouped by ticket ID
Alert groups are auto-acknowledged when the ticket status is set to “Pending”
Alert groups are auto-resolved when the ticket status is set to “Solved”

To customize this behaviour, consider modifying alert templates in integration settings.

Configuring Grafana OnCall to send data to Zendesk

Grafana OnCall can automatically create and resolve tickets in Zendesk via outgoing webhooks. This guide provides example webhook configurations for common use cases, as well as information on how to set up a user in Zendesk to be used by Grafana OnCall.

Prerequisites

Create a new user in Zendesk to be used by Grafana OnCall. Obtain an API token for the user, these credentials will be used to communicate with Zendesk API.
Make sure the user has appropriate permissions to create and update tickets in Zendesk.

Create tickets in Zendesk

The steps below describe how to create an outgoing webhook in Grafana OnCall that will allow to automatically create tickets in Zendesk from Grafana OnCall alert groups.

Create a new Outgoing Webhook in Grafana OnCall, and configure it as follows:

Trigger type: Alert Group Created
Integrations: Select integrations that will trigger the webhook
HTTP method: POST
Webhook URL:

https://<INSTANCE>.zendesk.com/api/v2/tickets

Replace <INSTANCE> with your Zendesk instance.

Username: Username of the Zendesk user, followed by /token (e.g. user@example.com/token)
Password: API token of the Zendesk user

Use the following JSON template as webhook data:

{
  "ticket": {
    "type": "incident",
    "subject": "{{alert_group.title}}",
    "comment": {
      "body": "This ticket is created automatically by Grafana OnCall. Alert group {{alert_group.id}}: {{alert_group.permalinks.web}}"
    }
  }
}

Resolve tickets in Zendesk

The steps below describe how to create an outgoing webhook in Grafana OnCall that will allow to automatically resolve tickets in Zendesk when an alert group is resolved in Grafana OnCall.

Trigger type: Resolved
Integrations: Select integrations that will trigger the webhook
HTTP method: PUT
Webhook URL:

https://<INSTANCE>.zendesk.com/api/v2/tickets/{{responses.<WEBHOOK_ID>.ticket.id}}

Replace <INSTANCE> with your Zendesk instance, and <WEBHOOK_ID> with the ID of the webhook used for creating tickets.

Username: Username of the Zendesk user, followed by /token (e.g. user@example.com/token)
Password: API token of the Zendesk user

Use the following JSON template as webhook data:

{
  "ticket": {
    "status": "solved",
    "comment": {
      "body": "Resolved by Grafana OnCall.",
      "public": false
    }
  }
}

Advanced usage

The examples above describe how to create outgoing webhooks in Grafana OnCall that will allow to automatically create and resolve tickets in Zendesk.

For more information on Zendesk API, refer to Zendesk API documentation.

Inbound Webhook

Tue, 07 Apr 2026 10:28:26 +0000

Inbound Webhook integrations for Grafana OnCall

Grafana OnCall directly supports many integrations, those that aren’t currently listed in the Integrations menu can be connected using the webhook integration and configured alert templates.

With the webhook integration, you can connect to any alert source that isn’t listed in the Create Integration page.

There are two available formats, Webhook and Formatted Webhook.

Webhook will pull all of the raw JSON payload and display it in the manner that it’s received.
Formatted Webhook can be used if the alert payload sent by your monitoring service is formatted in a way that OnCall recognizes.

The following fields are recognized, but none are required:
- alert_uid: a unique alert ID for grouping.
- title: a title.
- image_url: a URL for an image attached to alert.
- state: either ok or alerting. Helpful for auto-resolving.
- link_to_upstream_details: link back to your monitoring system.
- message: alert details.

To configure a webhook integration:

In the Integrations tab, click + New integration to receive alerts.
Select either Webhook or Formatted Webhook integration.
Follow the configuration steps in the How to connect section of the integration settings.
Use the unique webhook URL to complete any configuration in your monitoring service to send POST requests. Use any http client, e.g. curl to send POST requests with any payload.

For example:

curl -X POST \
https://a-prod-us-central-0.grafana.net/integrations/v1/formatted_webhook/m12xmIjOcgwH74UF8CN4dk0Dh/ \
-H 'Content-Type: Application/json' \
-d '{
    "alert_uid": "08d6891a-835c-e661-39fa-96b6a9e26552",
    "title": "The whole system is down",
    "image_url": "https://upload.wikimedia.org/wikipedia/commons/e/ee/Grumpy_Cat_by_Gage_Skidmore.jpg",
    "state": "alerting",
    "link_to_upstream_details": "https://en.wikipedia.org/wiki/Downtime",
    "message": "Smth happened. Oh no!"
}'

To learn how to use custom alert templates for formatted webhooks, see Configure alerts templates.

Integrations on Grafana Labs

Grafana Alerting

Grafana Alerting integration for Grafana OnCall

Configure Grafana Alerting in same Grafana instance

Configure external Grafana Alerting from other Grafana Instance

Note about grouping and autoresolution

Note about legacy integration

After-migration checklist

Alertmanager

Alertmanager integration for Grafana OnCall

Configuring Grafana OnCall to Receive Alerts from Prometheus Alertmanager

Configuring Alertmanager to Send Alerts to Grafana OnCall

Complete the Integration Configuration

Note about grouping and autoresolution

Configuring OnCall Heartbeats (optional)

Configuring Grafana OnCall Heartbeat

Configuring Alertmanager to send heartbeats to Grafana OnCall Heartbeat

Note about legacy integration

After-migration checklist

Page people manually

Page people manually

Page a team

Add users to an existing alert group

Learn the flow and handle warnings

Set up direct paging for a team

Amazon SNS

Amazon SNS integration for Grafana OnCall

Configuring Grafana OnCall to Receive Alerts from Amazon SNS

Configuring Amazon SNS to Send Alerts to Grafana OnCall

AppDynamics

AppDynamics integration for Grafana OnCall

Configuring Grafana OnCall to Receive Alerts from AppDynamics

Configuring AppDynamics to Send Alerts to Grafana OnCall

Understanding How Alerts Grouped and Auto-resolved

Complete the Integration Configuration

Datadog

Datadog integration for Grafana OnCall

Configuring Grafana OnCall to Receive Alerts from Datadog

Configuring Datadog to Send Alerts to Grafana OnCall

ElastAlert

ElastAlert integration for Grafana OnCall

Configuring Grafana OnCall to Receive Alerts from ElastAlert

Configuring ElastAlert to Send Alerts to Grafana OnCall

Grouping, auto-acknowledge and auto-resolve

Configuring Elastalert to send heartbeats to Grafana OnCall Heartbeat

Fabric

Fabric integration for Grafana OnCall

Configuring Grafana OnCall to Receive Alerts from Fabric

Configuring Fabric to Send Alerts to Grafana OnCall

Inbound Email

Inbound Email integration for Grafana OnCall

Configure required environment variables

Configure Inbound Email integration for Grafana OnCall

Grouping and auto-resolve

Jira

Jira integration for Grafana OnCall

Configuring Grafana OnCall to Receive Alerts from Jira

Configuring Jira to Send Alerts to Grafana OnCall

Grouping, auto-acknowledge and auto-resolve

Configuring Grafana OnCall to send data to Jira

Prerequisites

Create issues in Jira

Resolve issues in Jira

Advanced usage

Kapacitor

Kapacitor integration for Grafana OnCall

Configuring Grafana OnCall to Receive Alerts from Kapacitor

Configuring Kapacitor to Send Alerts to Grafana OnCall

New Relic

New Relic integration for Grafana OnCall

Configuring Grafana OnCall to Receive Alerts from New Relic

Configuring New Relic to Send Alerts to Grafana OnCall

Pingdom

Pingdom integration for Grafana OnCall

Configuring Grafana OnCall to Receive Alerts from Pingdom

Configuring Pingdom to Send Alerts to Grafana OnCall

PRTG

PRTG integration for Grafana OnCall

Configuring Grafana OnCall to Receive Alerts from PRTG

Configuring PRTG to Send Alerts to Grafana OnCall