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
The current prometheus exporter doesn't alert when there are warnings in backup sets. I.e. this backup had a warning because it could not find the wordpress-wp-uploads volume, because it was renamed (rather serious i.m.o.):
❯ velero get backup
NAME STATUS ERRORS WARNINGS CREATED EXPIRES STORAGE LOCATION SELECTOR
velero-daily-20220908033056 Completed 0 1 2022-09-08 05:30:56 +0200 CEST 14d default <none>
...
❯ velero backup logs velero-daily-20220908033056 | grep -i warn
time="2022-09-08T03:31:36Z" level=warning msg="No volume named wordpress-wp-uploads found in pod stackspin-apps/wordpress-0, skipping" backup=velero/velero-daily-20220908033056 logSource="pkg/restic/backupper.go:143" name=wordpress-0 namespace=stackspin-apps resource=pods
But the velero exporter still shows velero_backup_failure_total as 0.
Describe the solution you'd like
I'd like to propose an additional metric called velero_backup_warning_total.
OS (e.g. from /etc/os-release): Server: Debian bullseye
Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
👍 for "The project would be better with this feature added"
👎 for "This feature will not enhance the project in a meaningful way"
The text was updated successfully, but these errors were encountered:
Describe the problem/challenge you have
The current prometheus exporter doesn't alert when there are warnings in backup sets. I.e. this backup had a warning because it could not find the
wordpress-wp-uploads
volume, because it was renamed (rather serious i.m.o.):But the velero exporter still shows
velero_backup_failure_total
as 0.Describe the solution you'd like
I'd like to propose an additional metric called
velero_backup_warning_total
.Environment:
velero version
) :Client: v1.9.1, Server: Version: v1.9.1
kubectl version
):v1.24.4
v1.24.4+k3s1
/etc/os-release
): Server: Debian bullseyeVote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
The text was updated successfully, but these errors were encountered: