Skip to main content

​
Background

Many organizations use Datadog as an alert source to trigger incident creation and/or escalations. If you are migrating from another paging provider to incident.io On-call, you’ll need your Datadog monitors to point from your old provider to incident.io. This can be done using either:
  1. Terraform
  2. Our migration tool (currently in beta)

​
Terraform

All you will need to do is update your monitor descriptions. Anywhere there is a tag referencing a paging provider (ie. @pagerduty-SERVICENAME), you can replace with @webhook-incident-io. If you are tagging your monitors with services, you can send all your monitors to one alert source and then parse the Datadog payload to get the service as an alert attribute. See more details on setting up your alert sources here .

​
Migration tool (currently in beta)

If you do not use Terraform, you can use our migration tool which automatically updates your Datadog configuration to point to incident.io . This is a tool you can download plug in your Datadog API keys. The tool itself will:
  • Analyze all your monitors and creating a file for them to fill out that maps PagerDuty or Opsgenie services, for example, to incident.io teams
  • Talk you through the options for one webhook in Datadog or multiple webhooks
  • Automatically create the webhook configurations in Datadog
  • Automatically update their monitors to point to incident.io
  • Automatically remove PagerDuty or Opsgenie when we are successful
This can be accessed via Github here . Also, see a complementary Loom for help here .