Send Events from Edge Delta Monitors to an API

Send events to an API.

  2 minute read  

Overview

You can create a webhook or API integration, which can be triggered by a monitor in the backend, and which does not need to be deployed in a particular pipeline like a webhook node.

Pagerduty

In this example, a PagerDuty integration is triggered to send an event to a PagerDuty API.

To create an integration:

  1. Click Admin.
  2. Click Legacy Integrations.
  3. Select Available.
  4. Search for and select the PagerDuty destination.

To receive events from Edge Delta you need to create an Events API v2 integration in PagerDuty for your specific PagerDuty service. During this process you are provided with the endpoint (probably https://events.pagerduty.com/v2/enqueue) and an integration key.

The key must be included as a routing_key in the event payload, and a custom header Content-Type with the value application/json must be configured:

The payload in this example:

{
  "payload": {
    "summary": "Example alert",
    "id": "$EVENT_ID",
    "eventType": "$EVENT_TYPE",
    "eventURL": "$EVENT_URL",
    "eventTime": "$EVENT_DATE",
    "eventQuery": "$EVENT_QUERY",
    "eventMetric": "$EVENT_METRIC",
    "eventMessage": "$EVENT_MSG",
    "eventStatus": "$EVENT_STATUS",
    "OrgID": "$EVENT_ORG_ID",
    "eventGroupALL": "$EVENT_GROUP_ALL",
    "eventSpecificGroup": "$EVENT_GROUP.k8s.namespace.name",
    "eventTitle": "$EVENT_TITLE",
    "eventValue": "$EVENT_EVALUATED_VALUE",
    "source": "Edge Delta Monitor"
  },
  "routing_key": "<routing_key>",
  "dedup_key": "samplekeyhere",
  "images": [
    {
      "src": "https://www.pagerduty.com/wp-content/uploads/2016/05/pagerduty-logo-green.png",
      "href": "https://example.com/",
      "alt": "Example text"
    }
  ],
  "links": [
    {
      "href": "$EVENT_URL",
      "text": "Link text"
    }
  ],
  "event_action": "trigger",
  "client": "Edge Delta",
  "client_url": "https://edgedelta.com"
}

Replace <routing_key> with the integration key provided by PagerDuty.

Event Variables

This configuration will attempt to populate the payload with available event variables from the incoming signal’s metadata. You reference event variables using the $ character:

    "id": "$EVENT_ID",
    "eventType": "$EVENT_TYPE",
    "eventURL": "$EVENT_URL",
    "eventTime": "$EVENT_DATE",
    "eventQuery": "$EVENT_QUERY",
    "eventMetric": "$EVENT_METRIC",
    "eventMessage": "$EVENT_MSG",
    "eventStatus": "$EVENT_STATUS",
    "OrgID": "$EVENT_ORG_ID",
    "eventGroupALL": "$EVENT_GROUP_ALL",
    "eventSpecificGroup": "$EVENT_GROUP.k8s.namespace.name",
    "eventTitle": "$EVENT_TITLE",
    "eventValue": "$EVENT_EVALUATED_VALUE"

Monitor Integration

This integration can now be triggered by a monitor by including it in the monitor Notification configuration with the @ character and its name:

{{#is_alert}}
@pagerduty
{{/is_alert}}