User Story

As an OpenShift engineer and/or Project Manager
I want to see measures of build success and failure by strategy
So that I can analyze if customers are successfully using builds.

Acceptance Criteria

• Create a recording rule which aggregates the counter metric in BUILD-94.
• Build success and failure metrics appear in OpenShift telemetry.

Launch Checklist

Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated

Notes

Need to determine in BUILD-94 which metric(s) are useful for telemetry first.
Once this is established, we need to do the following:

1. Create a recording rule to reduce the cardinality of said metrics
2. Add the build metrics to Telemeter's allowlist.

See the following doc on how to add metrics to Telemeter: https://docs.google.com/document/d/1a6n5iBGM2QaIQRg9Lw4-Npj6QY9--Hpx3XYut-BrUSY/edit?usp=sharing

Add pertinent notes here:

• Enhancement proposal link
• Previous product docs
• Best practices
• Known issues

Guiding Questions

User Story

• Is this intended for an administrator, application developer, or other type of OpenShift user?
• What experience level is this intended for? New, experienced, etc.?
• Why is this story important? What problems does this solve? What benefit(s) will the customer experience?
• Is this part of a larger epic or initiative? If so, ensure that the story is linked to the appropriate epic and/or initiative.

Acceptance Criteria

• How should a customer use and/or configure the feature?
• Are there any prerequisites for using/enabling the feature?

Notes

• Is this a new feature, or an enhancement of an existing feature? If the latter, list the feature and docs reference.
• Are there any new terms, abbreviations, or commands introduced with this story? Ex: a new command line argument, a new custom resource.
• Are there any recommended best practices when using this feature?
• On feature completion, are there any known issues that customers should be aware of?