Observability Research - Define devops measurement scenarios
erikschlegel opened this issue · comments
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?