DORA report docs #29993
Merged
DORA report docs #29993
+82
−18
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
Preview links (active after the
|
|
Created DOCS-11257 for docs review |
|
Hi @joepeeples - can I get your help to review and finalize this PR? Thanks! |
joepeeples
reviewed
Jun 25, 2025
| @@ -21,12 +21,10 @@ The Scorecards Performance report includes an organization-wide view of Scorecar | |||
| - Filter information based on team, scorecard, rule, application, tier, and lifecycle. | |||
| - Explore historical info for the last 12 months to identify trends over time. | |||
|
|
|||
| Access the Scorecards Performance report by clicking on the "Overview" tab in Internal Developer Portal (IDP) and selecting "Scorecards Performance" in the left-hand menu. | |||
| Access the Scorecards Performance report by searching for "Engineering Reports" (or clicking on the "Overview" tab in IDP) and selecting "Scorecards Performance" in the left-hand menu. | |||
There was a problem hiding this comment.
Suggested change
| Access the Scorecards Performance report by searching for "Engineering Reports" (or clicking on the "Overview" tab in IDP) and selecting "Scorecards Performance" in the left-hand menu. | |
| Access the Scorecards Performance report by searching for "Engineering Reports" (or clicking on the **Overview** tab in IDP) and selecting **Scorecards Performance** in the left-hand menu. |
| - Customize your SLO or Incident groupings to be based on service, team, or other tags or properties that have been added to your SLOs or Incidents. | ||
| - Use a summary score, based on the remaining error budget of the underlying SLOs, to understand SLO performance across different groups and identify areas of improvement. | ||
| - Explore daily, weekly, and monthly historical reliability trends over the last 12 months to understand performance over time. | ||
|
|
||
| Access the Reliability Overview report by clicking on the "Overview" tab in Internal Developer Portal (IDP) and selecting "Reliability Overview" in the left-hand menu. | ||
| Access the Reliability Overview report by searching for "Engineering Reports" (or clicking on the "Overview" tab in IDP) and selecting "Reliability Overview" in the left-hand menu. |
There was a problem hiding this comment.
Suggested change
| Access the Reliability Overview report by searching for "Engineering Reports" (or clicking on the "Overview" tab in IDP) and selecting "Reliability Overview" in the left-hand menu. | |
| Access the Reliability Overview report by searching for "Engineering Reports" (or clicking on the **Overview** tab in IDP) and selecting **Reliability Overview** in the left-hand menu. |
Comment on lines
20
to
22
| - View a breakdown of DORA metrics by service, team, or env. | ||
| - Explore historical info and understand which services and teams are performing best vs. underperforming. | ||
| - Filter information based on service, team, repository id, env, and other tags. |
There was a problem hiding this comment.
Suggested change
| - View a breakdown of DORA metrics by service, team, or env. | |
| - Explore historical info and understand which services and teams are performing best vs. underperforming. | |
| - Filter information based on service, team, repository id, env, and other tags. | |
| - View a breakdown of DORA metrics by service, team, or environment. | |
| - Explore historical info and understand which services and teams are performing best vs. underperforming. | |
| - Filter information based on service, team, repository id, environment, and other tags. |
| - Filter information based on service, team, repository id, env, and other tags. | ||
| - Leverage monthly Datadog recommendations to improve your organization's software delivery performance. | ||
|
|
||
| Access the DORA Metrics report by searching for "Engineering Reports" (or clicking on the "Overview" tab in IDP) and selecting "DORA Metrics" in the left-hand menu. |
There was a problem hiding this comment.
Suggested change
| Access the DORA Metrics report by searching for "Engineering Reports" (or clicking on the "Overview" tab in IDP) and selecting "DORA Metrics" in the left-hand menu. | |
| Access the DORA Metrics report by searching for "Engineering Reports" (or clicking on the **Overview** tab in IDP) and selecting **DORA Metrics** in the left-hand menu. |
|
|
||
| ### Adjust your view | ||
|
|
||
| By default, the Scorecards Performance report breaks down data by service, which allows you to quickly understand DORA metrics performance across all your services. |
There was a problem hiding this comment.
Suggested change
| By default, the Scorecards Performance report breaks down data by service, which allows you to quickly understand DORA metrics performance across all your services. | |
| By default, the Scorecards Performance report breaks down data by service, which allows you to understand DORA metrics performance across all your services. |
Comment on lines
37
to
38
| - **Switch the aggregation between "Service", "Team", or "Env"**: View your organization's DORA metrics by service/team/env groupings to identify top- and bottom-performing areas. | ||
| - **Add filters to scope the data**: Filter by service, team, repository id, env, and other tags. |
There was a problem hiding this comment.
Suggested change
| - **Switch the aggregation between "Service", "Team", or "Env"**: View your organization's DORA metrics by service/team/env groupings to identify top- and bottom-performing areas. | |
| - **Add filters to scope the data**: Filter by service, team, repository id, env, and other tags. | |
| - **Switch the aggregation grouping**: View your organization's DORA metrics grouped by **Service**, **Team**, or **Env** to identify top- and bottom-performing areas. | |
| - **Add filters to scope the data**: Filter by service, team, repository id, environment, and other tags. |
|
|
||
| ### Customize your report | ||
|
|
||
| On the upper right corner of the report, click the kebab menu and select **Clone as a Dashboard** to create a dashboard with content from the DORA Metrics report. The dashboard reflects the "service" aggregated view. |
There was a problem hiding this comment.
Suggested change
| On the upper right corner of the report, click the kebab menu and select **Clone as a Dashboard** to create a dashboard with content from the DORA Metrics report. The dashboard reflects the "service" aggregated view. | |
| On the upper right corner of the report, click the three-dot menu and select **Clone as a Dashboard** to create a dashboard with content from the DORA Metrics report. The dashboard reflects the "service" aggregated view. |
👋 Hey @roxanne-moslehi, see my review above about adding the new page to the side nav. Also I just noticed the PR has a merge conflict on the Engineering Reports page in the frontmatter. Happy to help with either issue if needed! Feel free to ping me once this is ready for a final review & approval. |
|
@joepeeples thanks for the review! addressed the feedback |
joepeeples
approved these changes
Jun 25, 2025
content/en/internal_developer_portal/eng_reports/dora_metrics.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Joe Peeples <joe.peeples@datadoghq.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes