Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add reference to DORA metrics in the primer.md #82

Merged
merged 1 commit into from
Oct 20, 2022
Merged

Add reference to DORA metrics in the primer.md #82

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions primer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -403,10 +403,11 @@ There are two root use cases that we are considering:
to correlate them with each other and build an end to end view. With the same
events, we want to measure DevOps performance as well. The same events can be
used to track different metrics over time, to be visualized through a
dashboard.
dashboard. The current events provide enough data to calculate two of the four
[DORA DevOps metrics][dora]:

The use cases are work in progress - the list is being drafted in a [separate
document](https://hackmd.io/ZCS2KYKZTpKBqhU9PMuCew).
- Lead time for changes: the amount of time it takes a commit to get into production
- Deployment frequency: how often an organization successfully releases to production

## Design Decisions

Expand Down Expand Up @@ -463,3 +464,4 @@ created and its mission.
https://github.com/package-url/purl-spec/blob/master/PURL-SPECIFICATION.rst
[sig-interop-vocabulary]:
https://github.com/cdfoundation/sig-interoperability/blob/main/docs/vocabulary.md
[dora]: https://cloud.google.com/blog/products/devops-sre/using-the-four-keys-to-measure-your-devops-performance