Sending Incident Events for DORA Metrics

DORA Metrics is not available in the selected site () at this time.

The DORA Metrics private beta is closed. Fill out the form below to be added to the waitlist.

Request Access


Incident events are used in order to compute Change Failure Rate and Mean Time to Restore. To send incident events, use the DORA Metrics API. The following attributes are required:

  • services or team (at least one must be present)
  • started_at

You can optionally add the following attributes to the incident events:

  • finished_at for resolved incidents. This attribute is required for time to restore service.
  • id for identifying incidents when they are created and resolved. This attribute is user-generated; when not provided, the endpoint returns a Datadog-generated UUID.
  • name to describe the incident.
  • severity
  • env to accurately filter your DORA metrics by environment.
  • repository_url
  • commit_sha

See the DORA Metrics API reference documentation for the full spec and more examples with the API SDKs.


curl -X POST "https://api./api/v2/dora/incident" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -H "DD-API-KEY: ${DD_API_KEY}" \
  -d @- << EOF
    "data": {
      "attributes": {
        "services": ["shopist"],
        "team": "shopist-devs",
        "started_at": 1693491974000000000,
        "finished_at": 1693491984000000000,
        "git": {
          "commit_sha": "66adc9350f2cc9b250b69abddab733dd55e1a588",
          "repository_url": ""
        "env": "prod",
        "name": "Web server is down failing all requests",
        "severity": "High"

Change Failure Rate

The Change Failure Rate metric is calculated as the percentage of incident events out of the total number of deployments. Send both deployment events and incident events to correctly populate this metric.

Time to restore service

The Mean Time to Restore (MTTR) metric is calculated as the duration distribution for resolved incident events. Include the finished_at attribute in an incident event to mark that the incident is resolved.

Events can be sent both at the start of the incident and after incident resolution. Incident events are matched by the env, service, and started_at attributes.

Further Reading