--- title: DORA Metrics Data Collected description: >- Learn about DORA Metrics events, fields, tags, and change lead time stages for deployment frequency, change lead time, and failure analysis. breadcrumbs: Docs > DORA Metrics > DORA Metrics Data Collected --- # DORA Metrics Data Collected {% callout %} # Important note for users on the following Datadog sites: app.ddog-gov.com {% alert level="danger" %} This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site). (). {% /alert %} {% /callout %} ## Overview{% #overview %} DORA Metrics generates events that have associated fields and tags. | Event Type | Description | | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Deployment | A single code deployment uniquely identified by env, service, and version tags.Deployments can be [marked as failed](https://docs.datadoghq.com/dora_metrics/change_failure_detection/) and are used to compute deployment frequency, change failure rate, and failed deployment recovery time. | | Commit | An event generated for each individual commit included in a deployment. Contains metadata and is automatically linked to the corresponding deployment.Commits are used to compute change lead time. | | Incident | An incident declared in production.Tracking incidents provides a side-by-side view of how failed deployments translate into real-world incidents, including their severity and frequency. | **Note**: DORA Metrics events have a 2-year retention period. ### Default tags{% #default-tags %} All events contain the following tags if any are available: - `service` - `team` - `env` - `version` - `source` - `repository_id` **Note**: The `severity` tag is available for failure events when it is provided by the failure's data source. For more information about using tags, see [Getting Started with Tags](https://docs.datadoghq.com/getting_started/tagging/). ### Custom tags{% #custom-tags %} In addition to the tags above, deployment and failure events can be enriched with custom tags to filter DORA Metrics. There are three potential sources for these tags: - Software Catalog: If a deployment or failure event is associated with services in Software Catalog, it is automatically enriched with the `language` tag and the [custom tags defined in the Service Definitions](https://www.datadoghq.com/blog/service-catalog-setup/). - Incident Management: Failure events created from [Datadog Incident Management](https://app.datadoghq.com/incidents) are enriched with custom tags for any user-defined [Single Select or Multi Select property fields](https://docs.datadoghq.com/incident_response/incident_management/investigate/describe/). - DORA Metrics API: Up to 100 user-provided custom tags can be added to both deployment and failure events in the [API](https://docs.datadoghq.com/api/latest/dora-metrics/). For more information about using custom tags in DORA Metrics, see [DORA Metrics Overview](https://docs.datadoghq.com/dora_metrics/). ## Event-specific fields{% #event-specific-fields %} ### Deployment fields{% #deployment-fields %} | Field | Description | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Duration` | Duration of the deployment. | | `Avg Change Lead Time` | The average duration of change lead time of all commits. | | `Avg Time to PR Ready` | The average duration of time to PR ready of all commits. | | `Avg Review Time` | The average duration of review time of all commits. | | `Avg Merge Time` | The average duration of merge time of all commits. | | `Avg Time to Deploy` | The average duration of time to deploy of all commits. | | `Number of Commits` | Count of all commits included in a deployment. | | `Deployment Type` | Type of deployment (`standard`, `rollback`, or `rollforward`). | | `Change Failure` | Boolean indicating whether a deployment is marked as a change failure. | | `Recovery Time` | Duration in seconds between a failed deployment's `finished_at` and its remediation's `finished_at`. Only available for deployments marked as failures. | | `Remediation Type` | The type of remediation applied (`rollback` or `rollforward`). Only available for deployments marked as failures. | ### Commit fields{% #commit-fields %} | Field | Description | | ------------------ | --------------------------------------------------------------------------- | | `Change Lead Time` | Duration it takes for a commit to get into production. | | `Time to PR Ready` | Duration from commit creation to when the PR is marked as ready for review. | | `Review Time` | Duration from PR being marked ready for review to approval. | | `Merge Time` | Duration from PR approval to merging. | | `Time to Deploy` | Duration from merging to start of deployment. | | `Deploy Time` | Duration from start of deployment to end of deployment. | ### Incident fields{% #incident-fields %} | Field | Description | | ----------------- | -------------------------------------------------------------------------- | | `Time to Restore` | The time in between a failure's `started_at` and `finished_at` timestamps. | ## Further Reading{% #further-reading %} - [Learn about DORA Metrics](https://docs.datadoghq.com/dora_metrics/) - [Set up data sources for DORA Metrics](https://docs.datadoghq.com/dora_metrics/setup/) - [Learn about metrics](https://docs.datadoghq.com/metrics/) - [Getting started with Tags](https://docs.datadoghq.com/getting_started/tagging/)