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

Jump to bottom

Observability Research - Define devops measurement scenarios #360

Open
1 task
erikschlegel opened this issue Oct 8, 2019 · 0 comments
Open
1 task

Observability Research - Define devops measurement scenarios #360

erikschlegel opened this issue Oct 8, 2019 · 0 comments
Assignees
@erikschlegel @ianphil
Projects
Current Iteration

Comments

@erikschlegel
Copy link
Contributor

erikschlegel commented Oct 8, 2019 •
edited by ianphil

Description

As an operations engineer, I'd like to understand how to quantify and measure the statistical trends and health across my automated build and release pipeline(s).

Acceptance Criteria

  • Should define key metric questions and scenarios that would be of interest to an operations engineer. This should comprise a list of baseline questions that an devops dashboard should answer at an project level.

Notes

Builds
How many
How long
How many failed
How many completed
Check-in in to release complete metric
Someone makes a change and pipeline breaks, where did it break?
What is the break-fix time?

Per JOE:
my 4 KPIs to meause: 1. cost 2. dev velocity (how long to update) 3. function 4. errors

  • 3: does it deliver the business value that it is supposed to do?
@erikschlegel erikschlegel added this to Sprint Backlog in Current Iteration via automation Oct 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@erikschlegel erikschlegel

@ianphil ianphil

Labels
None yet
Projects
Current Iteration
  
Sprint Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@erikschlegel @ianphil