Goal

We need to report the VM migrations in a reliable way .

Currently we collect the Libvirt metrics that don't provide us with the accuracy that we require. See bug https://issues.redhat.com/browse/CNV-35287 

Prometheus supports specifying timestamps for metrics.
This approach would involves tracking the migration events and their timestamps and then submitting these metrics with their specific timestamps to Prometheus.
This requires a custom solution for metric submission that includes the timestamps, and it's more complex but ensures that the precise timing of short-lived events is captured.

Impacted metrics:

• kubevirt_vmi_migration_data_processed_bytes
• kubevirt_vmi_migration_data_remaining_bytes

User Stories

• As an admin I would like to be able to track the progress of the VMs migrations.
• another user story

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