Skip to main content

Notifiers

Notifiers are endpoints that receive alert notifications when monitor conditions are triggered. This guide explains each supported notifier type and provides step-by-step configuration instructions.

Supported Notifiers​

Slack​

To send notifications to Slack, you'll need an incoming webhook URL. There are two methods to create one:

  1. Slack Apps
  2. Incoming Webhooks (Legacy)

Slack Apps​

Follow these steps to create an incoming webhook using Slack Apps. For more details, see the official Slack documentation on incoming webhooks.

  1. Create a Slack App:

  2. Enable incoming webhooks:

  3. Create a webhook:

    • Click Add New Webhook to Workspace
    • Select the channel for receiving messages
    • Click Authorize

You'll receive a webhook URL that looks like this:

https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX
note

Webhooks created through Slack Apps can only post to their designated channel. You'll need separate webhooks for different channels.

Incoming WebHooks App (Legacy)​

The legacy Incoming WebHooks app allows you to create webhooks that can send messages to any channel in your workspace.

  1. Install the Incoming WebHooks app to your workspace

  2. Click Add to Slack, select a default channel, then click Add Incoming WebHooks Integration

note

Legacy webhooks can send messages to any channel in your workspace, unlike Slack Apps webhooks which are channel-specific.

Configuration​

To set up a Slack notifier in Oodle:

  1. Navigate to Alerts (Bell icon in sidebar) → click the ellipsis (...) → select Notifiers

  2. Click the + icon and choose Slack from the dropdown

  3. Fill in the following:

    • Name: A descriptive name for your notifier
    • API URL: The URL from Slack
    • Channel (optional): Override the default channel. Note: This only works with legacy webhooks
    note

    For Slack Apps webhooks, messages will always go to the channel specified during webhook creation, regardless of the channel setting in Oodle.

  4. Click Save to create the notifier

    Slack Notifier

Pagerduty​

To send notifications to Pagerduty, you'll need an API Key. Oodle supports following Pagerduty Integrations:

  1. Events API V2 (Recommended)
  2. Prometheus

Events API V2 is rich Events API in comparison to Prometheus integration. For example, it allows to set Pagerduty Alert's Severity, attach images etc. which are not possible in Prometheus integration type.

To get an Events API v2 API Key, follow:

  1. Log in to PagerDuty and navigate to Services in the top menu bar.
  2. Click on the service you are currently using, or create a new service.
  3. Click Integrations and then Add another integration.
  4. Select Events API V2 from the list of integrations.
  5. After creating the integration, you will be able to see the API Key for this integration.
Prometheus​

Prometheus Integration is less richer in comparison to Events API V2 Integration. To get a Prometheus Integration API Key, follow:

  1. Log in to PagerDuty and navigate to Services in the top menu bar.
  2. Click on the service you are currently using, or create a new service.
  3. Click Integrations and then Add another integration.
  4. Select Prometheus from the list of integrations.
  5. After creating the integration, you will be able to see the API Key for this integration.

Configuration​

To set up a Pagerduty notifier in Oodle:

  1. Navigate to Alerts (Bell icon in sidebar) → click the ellipsis (...) → select Notifiers

  2. Click the + icon and choose Pagerduty from the dropdown

  3. Fill in:

    • Name: A descriptive name for your notifier
    • Integration: Choose Events API V2 or Prometheus based on the Integration you have configured on Pagerduty.
    • API Key: Your Pagerduty integration API key

  4. Click Save to create the notifier

When using Events API V2, Oodle sets Pagerduty Alert's Severity based on the Condition Severity defined within the monitor:

  • Critical condition in Oodle is mapped to critical severity in Pagerduty.
  • Warning condition in Oodle is mapped to warning severity in Pagerduty.

Follow Configure Dynamic notifications in Pagerduty to govern alert notifications based on Severity.

PagerDuty Notifier

Opsgenie​

To send notifications to Opsgenie, you'll need an API key. Here's how to get one:

  1. Log in to Opsgenie and navigate to Integrations

  2. Click Add Integration and select Prometheus

  3. Configure the integration:

    • Enter a name
    • Select the team to receive alerts
    • Click Continue

  4. Click Turn on Integration to activate it

  5. [Optional] In Incoming | Rules for creating and processing alerts section, Click on Create Alert and update Message field from [Prometheus]: {{message}} to {{message}}.

Configuration​

To set up an Opsgenie notifier in Oodle:

  1. Navigate to Alerts (Bell icon in sidebar) → click the ellipsis (...) → select Notifiers

  2. Click the + icon and choose Opsgenie from the dropdown

  3. Fill in:

    • Name: A descriptive name for your notifier
    • API Key: Your Opsgenie integration API key

  4. Click Save to create the notifier

Oodle sets Opsgenie's Priority based on the Condition Severity defined within the monitor:

  • Critical condition in Oodle is mapped to P1 priority in Opsgenie.
  • Warning condition in Oodle is mapped to P2 priority in Opsgenie.
Opsgenie Notifier

Rootly​

To send notifications to Rootly, you'll need a Bearer Token Secret from a Rootly Alertmanager source.

  1. In Rootly, navigate to Alert Sources > New Alertmanager Source

  2. Give the source a name (e.g. "Oodle Alerts")

  3. Under Urgency, add a condition: $.alerts[0].labels._oodle_severity is warn sets urgency to Medium, otherwise High

    Rootly Urgency Configuration

  4. Save and copy the Bearer Token Secret

Configuration​

To set up a Rootly notifier in Oodle:

  1. Navigate to Alerts (Bell icon in sidebar) → click the ellipsis (...) → select Notifiers

  2. Click the + icon and choose Rootly from the dropdown

  3. Fill in:

    • Name: A descriptive name for your notifier
    • Bearer Token: The Bearer Token Secret from Rootly

  4. Click Save to create the notifier

Oodle delivers alerts in Alertmanager webhook format. Rootly uses the _oodle_severity label to map alert urgency based on the conditions you configured above.

A Rootly notifier is a webhook underneath, so it also accepts a Custom Payload, but with a difference. Rootly's alert source parses the standard Alertmanager body, and the urgency condition above reads $.alerts[0].labels._oodle_severity out of it, so Oodle keeps that body in place: anything you add is sent alongside the standard fields rather than replacing them. The editor names those fields below the box, and expands to show the full body that goes out.

Oodle adds the standard fields as it delivers the alert, thus you write only your own keys, and the API and the Terraform provider behave the same way. A payload that sets one of the standard keys itself is rejected, because the value would be lost.

Two of the standard fields cannot be carried on a custom payload: groupKey is dropped, and version is sent as the number 4 rather than the string "4".

For more details, see the Rootly Alertmanager docs.

Google Chat​

To send notifications to Google Chat, you'll need a webhook URL. Get the Webhook URL by following Create a webhook for the Google Space for the Google Space you want to send notification to.

When creating the webhook in Google Chat, we recommend:

  • Name: Oodle Alerts
  • Avatar URL: https://www.oodle.ai/img/logo_square.png

This gives alert messages a recognizable name and Oodle logo in Google Chat.

Configuration​

To set up a Google Chat notifier in Oodle:

  1. Navigate to Alerts (Bell icon in sidebar) → click the ellipsis (...) → select Notifiers

  2. Click the + icon and choose Google Chat from the dropdown

  3. Fill in:

    • Name: A descriptive name for your notifier
    • Webhook URL: The Webhook URL you created above.

  4. Click Save to create the notifier.

Microsoft Teams​

To send notifications to Microsoft Teams, you'll need a webhook URL. Get the Webhook URL by following Create an incoming Webhook with Workflows for the Teams Channel you want to send notifications to.

Configuration​

To set up a Microsoft Teams notifier in Oodle:

  1. Navigate to Alerts (Bell icon in sidebar) → click the ellipsis (...) → select Notifiers

  2. Click the + icon and choose Microsoft Teams from the dropdown

  3. Fill in:

    • Name: A descriptive name for your notifier
    • Webhook URL: The Webhook URL you created above.

  4. Click Save to create the notifier

Webhook​

A webhook notifier posts each alert to an HTTP endpoint you control. By default Oodle sends the standard Alertmanager webhook payload.

Configuration​

To set up a webhook notifier in Oodle:

  1. Navigate to Alerts (Bell icon in sidebar) → click the ellipsis (...) → select Notifiers

  2. Click the + icon and choose Webhook from the dropdown

  3. Fill in:

    • Name: A descriptive name for your notifier
    • API URL: The endpoint Oodle posts to
    • Authorization Credentials (optional): Sent as a Bearer token in the Authorization header
    • Custom Payload (optional): See below

  4. Click Save to create the notifier

Custom Payload​

If your endpoint expects a different request body, set Custom Payload to a JSON object. It replaces the default body entirely. Every string in the object (keys included, at any nesting depth) is a Go template rendered against the alert notification data, so you can shape the request to whatever the endpoint needs:

{
  "text": "{{ .CommonLabels.alertname }} is {{ .Status }}",
  "severity": "{{ .CommonLabels._oodle_severity }}",
  "labels": "{{ .CommonLabels | toJson }}",
  "sections": [{ "summary": "{{ .CommonAnnotations.summary }}" }]
}

A rendered string that itself parses as JSON is inlined as structured data rather than quoted, which is what makes toJson useful: labels above arrives at the endpoint as an object, not as a string containing JSON.

The payload is per notifier: each webhook notifier carries its own, and one left empty keeps the default body.

The template data is the same Alertmanager notification data available to the other notifier types. Expand Available Variables above the editor for the full list: .Status, .CommonLabels.alertname, .CommonLabels._oodle_severity, .CommonAnnotations._oodle_message, .Alerts.Firing and the rest.

warning

Oodle does not validate that the rendered payload is what your endpoint expects. If the template is malformed or the endpoint rejects the body, the notification fails to deliver. Use Test on the notifier after saving.

Use a Notifier​

Once you have a notifier created, you can use it in a notification policy to route alerts to the notifier. See the Notification Policies documentation for more details.

Support

If you need assistance or have any questions, please reach out to us through: