-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
False
-
None
-
False
-
-
No
-
-
Value Statement
As an SRE troubleshooting Hosted Control Plane installations times, I want to be able to trace back the time it took for the initial manifestworks to apply to a management cluster.
For this, I would need a metric representing the time it took for the first apply of manifestworks (not updates to an existing manifestwork) to take effect. Ideally, this metric should also contain the cluster_id to better correlate the data.
Definition of Done for Engineering Story Owner (Checklist)
- Create a metric representing intiial time for a manifestwork to apply
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the [Customer
Portal_doc_issue template](
https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
and ensure doc acceptance criteria is met. Link the development issue to
the doc issue. - [ ] Provide input to the QE team, and ensure QE acceptance criteria
(established between story owner and QE focal) are met.
Support Readiness
- [ ] The must-gather script has been updated.