Datadog
Send monitoring events from Datadog to BigPanda.
Supported Versions | Type | Authentication Type |
---|---|---|
SaaS Deployments | Webhook | Org 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.
Open Integration Manager
The Open Integration Manager is available for use with Datadog. For more information, see the Open Integration Manager documentation.
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.
Tag | Description | Additional Info |
---|---|---|
host | Host that triggered the alert. This tag is relevant only when a specific host is selected in the Datadog monitor definition. | Primary Property |
monitor_name | Name of the monitor in Datadog. | Alternate Primary Property (if host does not exist) |
alert_metric | Metric that triggered the alert. This tag is relevant only when a specific metric is selected in the Datadog monitor definition. For example: • system.mem.total/free/used • system.disk.total/used/free • process.up • http.can_connect | Secondary Property |
event_type | Type of Datadog event. For example: • service_check • metric_alert_monitor • query_alert_monitor | Alternate Secondary Property (if alert_metric does not exist) |
alert_query | Query of the triggered monitor in Datadog. | |
description | Description of the alert. This is the Datadog event message with markdown removed. | |
link | Link to the Datadog event this alert represents. | |
last_trigger | Last trigger time for this Datadog alert. | Parsed from the Datadog event message. |
logs_link | Link to related logs in Datadog, if they exist. | Parsed from the Datadog event message. |
monitor_link | Link to the actual Datadog monitor that this alert is generated by. | Parsed from the Datadog event message. |
processes_link | Link to related processes in Datadog, if they exist. | Parsed from the Datadog event message. |
resource_link | Link to the related resource in Datadog, if it exists. | Parsed from the Datadog event message. |
tags | An 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 |
Statuses
BigPanda will automatically correlate a Datadog status into a BigPanda status that can be used to search and filter incidents.
Datadog Status | BigPanda Status |
---|---|
triggered , retriggered | Critical |
warn | Warning |
recovered | Ok |
no data , re-no data` | Unknown |
Install the Integration
Administrators can install the integration by following the on-screen instructions in BigPanda
Deactivate the Integration in BigPanda
If you want to stop sending data to BigPanda but don’t want to delete your integration, you can temporarily deactivate it.
To deactivate an integration:
- In BigPanda, navigate to the Integrations tab and select the desired integration from the list. This will open integration details on the right side of the window.
- At the top of the integration details, click the Active/Inactive toggle next to the application name to change the status of the integration.
Alert Resolution for Inactive Integrations
Any active alerts belonging to an inactive integration must be manually resolved or they will stay in the system until the auto-resolve window is reached.
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
- In Datadog, go to the BigPanda integration tile.
- 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 in BigPanda
- In BigPanda, navigate to the Integrations tab and select the desired integration from the list.
- In the integration details on the right of the page, click the trash icon, then confirm you want to delete the integration. The integration will then be removed immediately.
Alert Resolution for Deleted Integrations
All active alerts from the integration will be resolved after deletion.
️Data Removal
This procedure does not remove any data from the integrated system.
Updated about 1 month ago