PORT-11788 DORA Metrics - additional tracking ways #1851
Conversation
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
Refined the DORA metrics setup guide by reworking the structure and adding alternative tracking methods, including Jira-based deployment tracking, lead time tracking, CFR using high-priority bugs, and hotfix deployments. Improved section clarity and alignment to recommended practices for tracking incidents and metrics.
The link to the Jira integration guide was incorrect. Updated the path from "issue-tracking" to "project-management" to ensure accurate navigation for users.
…proaches using Jira. Enhanced incident tracking section with alternative methods, tabs for clarity, and improved formatting. These changes aim to improve usability and comprehension without altering functionality.
|
@kodjomiles @hadar-co I highly recommend to start split this guide into files for readability. it's way too long.
Its really hard to understand the guide (technically) in its current structure (the UI shouldnt' change, just files structure) |
|
|
||
| ::: | ||
|
|
||
| ### Tracking lead time with Jira tickets |
There was a problem hiding this comment.
This feels out of place. We discuss on tracking deployments and instead we're talking about lead tim
| @@ -886,25 +924,71 @@ By this method, individual services within a monorepo are mapped to Port bluepri | |||
| Custom integrations provide flexibility in mapping and tracking each service or microservice within a monorepo. With Port’s API, you can track deployments and updates for each component separately, giving you granular control over monitoring and managing services in a monorepo. | |||
| ::: | |||
|
|
|||
| ### Tracking deployment via Jira tickets (Alternative) | |||
There was a problem hiding this comment.
Why don't we put it with the other tracking strategis?
|
|
||
| Ensure that your **PagerDuty incident blueprint** is properly configured to map incidents to the correct services(gitHub). | ||
| <TabItem value="recommended" label="Recommended"> |
There was a problem hiding this comment.
Why not have tab items like "Incident management tools" ,"Jira", "Hotfix deployment"
| </TabItem> | ||
|
|
||
| </Tabs> | ||
|
|
||
|
|
||
| ## Metrics |
There was a problem hiding this comment.
Maybe I'm missing but no where we explain how the aggregation correlate with the alternative methods. e.g., if I use Jira to track lead time
Description
Added some additional ways to track deployment, calculate lead time for change and measure change failure rate for in the dora metrics guide leveraging on Jira.
Updated docs pages
Please also include the path for the updated docs
/guides/all/setup-dora-metrics)