You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Replaced incidents by failures
* v1
* v1.1
* Little update of some requirements (DORA settings)
* Upper case small changes
* Update content/en/dora_metrics/data_collected/_index.md
Co-authored-by: Jorge Calvar <[email protected]>
* Applied feedback from Jorge
Change deployment.merge_time to Merge Time (i.e. metric to field) to avoid any confusion with previous Metrics type
* Applied feedback from Guillaume
* Fix typos and improve consistency in DORA metrics documentation
Applied suggestions from Joe Peeples
* Applying Joe's feedback and fixing small tweak
* Added Incident Management as a DORA Failure data source
* Update content/en/dora_metrics/setup/failures.md
Co-authored-by: Alicia Scott <[email protected]>
* Update content/en/dora_metrics/setup/failures.md
Co-authored-by: Alicia Scott <[email protected]>
* Applied feedback from alicia
- Added consistency between data sources requirements.
- Remove /dora_metrics/failures/datadog_incidents alias as not needed.
* Applied feedback from Jorge
* Update content/en/dora_metrics/setup/failures.md
Co-authored-by: Alicia Scott <[email protected]>
* Update failures.md
---------
Co-authored-by: Jorge Calvar <[email protected]>
Co-authored-by: Alicia Scott <[email protected]>
Copy file name to clipboardExpand all lines: content/en/dora_metrics/setup/_index.md
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -36,8 +36,9 @@ The four DORA Metrics are calculated based on two types of events that support d
36
36
### Select a failure data source
37
37
38
38
{{< whatsnext desc="DORA Metrics supports the following data sources for failure events. See the respective documentation to set up one or more data sources for your failure events:" >}}
Copy file name to clipboardExpand all lines: content/en/dora_metrics/setup/failures.md
+24-2Lines changed: 24 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -39,12 +39,34 @@ Failed deployment events, currently interpreted through failure events, are used
39
39
## Selecting and configuring a failure data source
40
40
41
41
{{< tabs >}}
42
+
{{% tab "Datadog Incidents" %}}
43
+
DORA Metrics can automatically identify and track failures through [Datadog Incidents][201]. Once incidents are declared, DORA uses them to measure change failure rate and time to restore.
44
+
45
+
**Note**: Only incidents that are in a `stable` or `resolved` state are used to calculate time to restore.
46
+
47
+
### Requirements
48
+
49
+
-**Incidents** is enabled as a **Failures** event data source in [DORA settings][202].
50
+
51
+
For incidents to appear in filtered DORA metrics views, Incidents must be tagged with the following attributes:
52
+
-`Teams`
53
+
-`Services`
54
+
-`Envs`: The `Envs` attribute can be added in the [Incident Settings][203] if it doesn’t already exist.
55
+
56
+
If provided with Incidents, the `Severity` tag will be added to failure events.
[PagerDuty][104] is an incident management platform that equips IT teams with immediate incident visibility, enabling proactive and effective responses to maintain operational stability and resilience.
44
66
45
67
To integrate your PagerDuty account with DORA Metrics:
46
68
47
-
1. Enable PagerDuty as a failure data source in [DORA settings][111].
69
+
1. Enable **PagerDuty** as a **Failures** event data source in [DORA settings][111].
48
70
49
71
1. Navigate to **Integrations > Developer Tools** in PagerDuty and click **Generic Webhooks (v3)**.
50
72
@@ -132,7 +154,7 @@ Include the `finished_at` attribute in a failure event to mark that the failure
132
154
133
155
### Requirements
134
156
135
-
- datadog-ci CLI / API is enabled as a failure events data source in [DORA settings][15].
157
+
-**datadog-ci CLI / API** is enabled as a **Failures** event data source in [DORA settings][15].
136
158
- The following attributes are required:
137
159
-`services` or `team` (at least one must be present)
0 commit comments