-
Epic
-
Resolution: Done
-
Major
-
None
Goal
Use existing telemetry data to trigger practical actions. This is rather to process the data we have right now, than to add additional metrics or alerts. Examples are included in the user stories below.
User Stories
- As an OpenShift Virtualization team member I'd like to see trends in the telemetry to get a feel on what 's going on in the field. One of the examples would be to group alerts by z and y streams, so with each released version we can see trends with telemetry data, can compare them with previous versions and take some actions.
- As an OpenShift Virtualization team member I'd like to be notified about any suspicious trends in alerts (by a section dedicated to it in weekly telemeter report)
- As an OpenShift Virtualization engineer/manager I'd like to have the bug open for suspiciously looking alerts so my team can investigate it.
Non-Requirements
- List of things not included in this epic, to alleviate any doubt raised during the grooming process.
Notes
- Any additional details or decisions made/needed
Done Checklist
| Who | What | Reference |
|---|---|---|
| DEV | Upstream roadmap issue (or individual upstream PRs) | <link to GitHub Issue> |
| DEV | Upstream documentation merged | <link to meaningful PR> |
| DEV | gap doc updated | <name sheet and cell> |
| DEV | Upgrade consideration | <link to upgrade-related test or design doc> |
| DEV | CEE/PX summary presentation | label epic with cee-training and add a <link to your support-facing preso> |
| QE | Test plans in Polarion | <link or reference to Polarion> |
| QE | Automated tests merged | <link or reference to automated tests> |
| DOC | Downstream documentation merged | <link to meaningful PR> |
