Integrating with Datadog
Datadog provides observability monitoring for your cloud infrastructure. Use alerts from Datadog to power incidents and notifications in FireHydrant.
Configuration steps
-
First, you need to authorize the Datadog integration on FireHydrant's integrations page.
-
Once you click Authorize Application, you'll see a webhook URL provided.
-
In your Datadog account, head to the Integrations page from the navigation sidebar. Search for the Webhooks integration and install/configure it or, if already installed, just click Configure to open its configuration form in a modal.
-
Click the + New button to add a new webhook. Give it a unique name, and paste the URL that was given to you in FireHydrant. For the Payload, use the following:
{
"event": {
"id": "$ALERT_CYCLE_KEY",
"title": "$EVENT_TITLE",
"description": "$EVENT_MSG",
"priority": "$ALERT_PRIORITY",
"status": "$ALERT_TRANSITION",
"date": "$DATE",
"url": "$LINK"
}
} -
Save your new webhook. Then, navigate to Monitors in the navigation sidebar, and find the monitor for which you'd like to forward triggered alerts to FireHydrant.
-
On the monitor's page, click the gear icon in the upper right corner, and then Edit to open the monitor's form.
-
In the Notify your team section, select your new webhook from the Notify your services and your team members dropdown below the message template. Selecting the webhook should insert the proper template fragment to route alerts to your webhook in FireHydrant.
-
At the very bottom of the page, click the Save button, or alternatively, the Test Notifications button to send a test alert to FireHydrant. You should then see the alert logged on the FireHydrant Datadog configuration page (where you originally got the URL) under Alert Routing.
Using Alert Routes with Datadog
Once your Datadog instance is configured, you can setup Alert Routes to take action on your alerts based on the data included in the alert. You can automatically open new incidents, send alerts to any Slack channel, log an alert in FireHydrant, or simply ignore it. To learn more, read about Alert Routes.