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.

Based on CNV-31126 -
Created doc https://docs.google.com/spreadsheets/d/1xYCyn-Y35ZA3ABZNYowt9ZonCIoUtNps0P7GhrLMTFY/edit?usp=sharing that include logs that we need to check and this epic includes the spikes to go over each of the issues found in the logs.

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