Replies: 3 comments 3 replies
|
Pushed a fix in 3b83638 that should address the backup age threshold resetting to 0. Root cause: When editing any threshold for a VM/LXC and saving, the Fix:
This will be in the next release. Would appreciate confirmation it works once you can test it! |
|
Sorry about the delay — I dug deeper and found the real issue. The previous fix (5.0.17) addressed a different problem than the one you hit. The actual issue: the Global Defaults card in the VMs & Containers section was showing a "Backup" number input that looked editable but didn't actually control backup alert thresholds. Any value entered there was silently discarded on save, which is why it kept resetting to 0. Backup age thresholds (Warning Days / Critical Days) are configured in the dedicated Backups section of the alerts page — that's where you can set your 32-day threshold. Pushed a fix in 6b237db that removes the misleading Backup and Snapshot inputs from the Global Defaults card so this confusion shouldn't happen again. This will be in the next release. |
|
@rcourtman |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I back up my Proxmox LXC containers on the first day of each month.
I’d like to configure alerts so that I’m notified only if the backup age reaches 32 days.
I first tried setting the Backup value to 32 in VMs & Containers.

However, no matter what I do, the value is always reset to 0 after saving.
Is this expected behavior?
As a result, I currently receive an alert when the backup age exceeds 14 days.

I assume that 14 days is the default value, even though it doesn’t appear anywhere in the settings.
Is that correct?
I managed to adjust the dashboard by tweaking some values, as shown below.


But this seems to be completely independent from the alerting system.
Am I right?
Any help would be greatly appreciated.
Thanks!
All reactions