You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experiencing issues with Velero where most of the metrics are always zero, and basic Prometheus metrics are not functioning correctly. This issue significantly affects our ability to monitor the backup status and reliability.
These metrics are crucial for us to monitor the health and status of our backup operations, but they consistently report zero values, which is not accurate.
Expected Behavior:
The above metrics should provide accurate and non-zero values reflecting the actual state of Velero backups.
Additional Context:
Any insights or solutions to this issue would be greatly appreciated as these metrics are critical for our backup monitoring and alerting.
Thank you for your assistance!
The text was updated successfully, but these errors were encountered:
Check for any pod restarts.. these metrics IIUC are incremental as new backup/restores are processed. Velero does not list all existing backups prior to its startup to count attempt/failure totals.
I am experiencing issues with Velero where most of the metrics are always zero, and basic Prometheus metrics are not functioning correctly. This issue significantly affects our ability to monitor the backup status and reliability.
A few problematic metrics:
These metrics are crucial for us to monitor the health and status of our backup operations, but they consistently report zero values, which is not accurate.
Expected Behavior:
The above metrics should provide accurate and non-zero values reflecting the actual state of Velero backups.
Environment:
Velero version: 1.13.0
Kubernetes version: 1.28
Cloud provider: AWS EKS
Additional Context:
Any insights or solutions to this issue would be greatly appreciated as these metrics are critical for our backup monitoring and alerting.
Thank you for your assistance!
The text was updated successfully, but these errors were encountered: