Send monitoring events from Datadog to BigPanda.

Supported VersionsTypeAuthentication Type
SaaS DeploymentsWebhookOrg Bearer Token

To set up this integration, start by configuring the native BigPanda integration within Datadog. The Datadog alerting pipeline will send all alerts to BigPanda. BigPanda then processes and correlates the alert data from Datadog to create and maintain up-to-date incidents in BigPanda.

Key Features

  • Easily send all Datadog alerts to BigPanda with a native integration in Datadog.
  • Correlate alerts from Datadog Monitors to help you understand and respond faster to production issues.

Data Model

BigPanda normalizes alert data from Datadog into tags. You can use tag values to filter the incident feed and to define filter conditions for Environments. The primary and secondary properties are also used during the deduplication and correlation processes.

Data Normalization

All properties from the Datadog alert are mapped 1:1 to tags on the BigPanda alert. The below chart describes some special properties of specific Datadog alert tags.

TagDescriptionAdditional Info
hostHost that triggered the alert. This tag is relevant only when a specific host is selected in the Datadog monitor definition.Primary Property.
monitor_nameName of the monitor in Datadog.Alternate Primary Property (if host does not exist)
alert_metricMetric that triggered the alert. This tag is relevant only when a specific metric is selected in the Datadog monitor definition. For example:
Secondary Property.
event_typeType of Datadog event. For example:

Alternate Secondary Property (if alert_metric does not exist)
alert_queryQuery of the triggered monitor in Datadog.
descriptionDescription of the alert. This is the Datadog event message with markdown removed.
linkLink to the Datadog event this alert represents.
last_triggerLast trigger time for this Datadog alert.Parsed from the Datadog event message.
logs_linkLink to related logs in Datadog, if they exist.Parsed from the Datadog event message.
monitor_linkLink to the actual Datadog monitor that this alert is generated by.Parsed from the Datadog event message.
processes_linkLink to related processes in Datadog, if they exist.Parsed from the Datadog event message.
resource_linkLink to the related resource in Datadog, if it exists.Parsed from the Datadog event message.
tagsAn array of tags on the Datadog monitor without associated keys (values only).
XXX (Datadog tags)All tags on the Datadog monitor which are in key:value format are mapped directly to corresponding tags on the BigPanda alert.status and description tags are reserved keys on the BigPanda alert and any Datadog monitor tags with these keys will be renamed to tag.KEY


BigPanda will automatically correlate a Datadog status into a BigPanda status that can be used to search and filter incidents.

Datadog StatusBigPanda Status
triggered, retriggeredCritical
no data, re-no data`Unknown

Install the Integration

In BigPanda

Administrators can install the integration by following the on-screen instructions in BigPanda.

In Datadog

Once you've created the integration in BigPanda you can then finish setup via the BigPanda integration tile in the Datadog console.

If you do not wish to send all of your Datadog monitor alerts to BigPanda you can uncheck the Route All Monitor Events option of the BigPanda integration in Datadog and then manually add @bigpanda to the notifications for each monitor you wish to send.

Upgrade an Existing Datadog Integration

If you are using an existing Datadog integration the best approach is to replace it with a completely new integration using the steps above: Installing the Integration

However, if you have many monitoring notifications already configured you may wish to keep using your existing Webhook integration. In that case, you can follow the below steps:

  1. In Datadog, go to the Integrations Settings from the sidebar.
  2. Locate your existing Webhook integration sending to BigPanda and click Configure.
  3. Click Edit.
  4. Change the URL to the following, replacing BEARER_TOKEN and APP_KEY with your BigPanda account bearer token and Datadog integration's app key respectively:
  1. Change the payload to the following:
   "host": "$HOSTNAME",
   "title": "$EVENT_TITLE",
   "alert_metric": "$ALERT_METRIC",
   "alert_query": "$ALERT_QUERY",
   "body": "$EVENT_MSG",
   "body_clean": "$TEXT_ONLY_MSG",
   "link": "$LINK",
   "tags": "$TAGS",
   "event_type": "$EVENT_TYPE",
   "priority": "$PRIORITY",
   "alert_status": "$ALERT_STATUS",
   "alert_transition": "$ALERT_TRANSITION",
   "last_updated": "$LAST_UPDATED",
   "date": "$DATE",
   "email": "$EMAIL",
   "datadog_org_name": "$ORG_NAME",
   "datadog_org_id": "$ORG_ID",
   "aggreg_key": "$AGGREG_KEY"
  1. Click Save.

Uninstall the Integration

Deleting an integration requires changes to both the integrated system and BigPanda. You must uninstall the integration on the integrated system and then delete the integration from BigPanda.


When replacing an existing integration with a new tool or system, we recommend configuring the new integration first to ensure no data is lost.

Stop Sending Data to BigPanda

  1. In Datadog, go to the BigPanda integration tile.
  2. Under the Configuration tab click Uninstall Integration

Manually resolve any open alerts sent from the integration to remove the associated incidents from your incident feed. These incidents will not automatically resolve without an ok status from the original sending integration.

Delete the Integration from BigPanda

  1. In BigPanda, navigate to the Integrations tab and select the desired integration from the list.
  2. In the integration details on the right, click Delete Integration. A support message opens, pre-populated with a request to delete the selected integration.
  3. Press Enter to send the request.
  4. The BigPanda support team will remove the integration from the UI.

This procedure does not remove any data from BigPanda or the integrated system. As needed, remove data from each system before deleting the integration.