Skip to content

Commit ad52fa9

Browse files
Tecoddyjoepeeples
andauthored
DORA Metrics retention period and requirements update (#33265)
* Added retention + small edits Add retention period to 2 years and changed Change lead time requirement for better clarity. * Update content/en/dora_metrics/setup/deployments.md Co-authored-by: Joe Peeples <[email protected]> * Update content/en/dora_metrics/setup/deployments.md Co-authored-by: Joe Peeples <[email protected]> --------- Co-authored-by: Joe Peeples <[email protected]>
1 parent fd7690d commit ad52fa9

File tree

2 files changed

+7
-4
lines changed

2 files changed

+7
-4
lines changed

content/en/dora_metrics/data_collected/_index.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,9 @@ DORA Metrics generates events that have associated fields and tags.
2626
|Commit | A commit event is generated for each individual commit included in a deployment. These events contain metadata and are automatically linked to the corresponding deployment.
2727
|Failure | A failure in production, such as an incident, rollback, or alert.
2828

29-
#### Default tags
29+
**Note**: DORA Metrics events have a 2-year retention period.
30+
31+
### Default tags
3032

3133
All events contain the following tags if any are available:
3234

@@ -41,7 +43,7 @@ All events contain the following tags if any are available:
4143

4244
For more information about using tags, see [Getting Started with Tags][6].
4345

44-
#### Custom tags
46+
### Custom tags
4547

4648
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:
4749

content/en/dora_metrics/setup/deployments.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,8 @@ For service deployments tracked by APM to contribute to change lead time, ensure
160160

161161
### Requirements for calculating change lead time
162162
- Your application telemetry is tagged with Git information. You can enable this [in APM][101] or see the [Source Code Integration documentation][102].
163-
- Your repository metadata is synchronized to Datadog through the [GitHub integration][103] or by the `datadog-ci git-metadata upload` command.
163+
- Your repository metadata is [synchronized](#synchronize-repository-metadata-to-datadog) to Datadog.
164+
164165

165166
[101]: https://app.datadoghq.com/source-code/setup/apm
166167
[102]: /integrations/guide/source-code-integration/?tab=go#tag-your-telemetry-with-git-information
@@ -174,7 +175,7 @@ For service deployments tracked by the DORA Metrics API or the `datadog-ci dora
174175
### Requirements for calculating change lead time
175176

176177
- The attributes `repository_url` and `commit_sha` are included in the deployment events payload.
177-
- Your repository metadata is synchronized to Datadog through the [GitHub integration][101] or by the `datadog-ci git-metadata upload` command.
178+
- Your repository metadata is [synchronized](#synchronize-repository-metadata-to-datadog) to Datadog.
178179

179180
[101]: /integrations/github/
180181

0 commit comments

Comments
 (0)