[Feature] Esplanation on what the warning "stale" beside the vm is

[buzzzo]

---

Describe the feature

As per topic and as nobody takes care of my previous opened issue i would like to know why many of my vms
in the resources list have the red text "stale" labeled.

Could be useful to add this kind of info in the docs

Use Case

It le me know if is a bug or not

Alternatives considered

No workaround exists.

How important is this for you?

I would like to know if this is a proxmox issue or is a pegaprox ones

Checklist

• I have searched existing issues and discussions to make sure this hasn't been requested before

[mkellermann97]

Hey @buzzzo — sorry the previous tickets (#425, #423) didn't get a proper explanation. Let me clear it up now since it's your third try asking.

The red "stale" badge means the VM's most recent PBS backup is older than 7 days. It's a backup-freshness warning, not a bug or a PegaProx ↔ Proxmox sync issue. Exact thresholds (from pegaprox/api/pbs.py around line 2300):

• < 36 hours since last backup → no badge (ok)
• < 7 days → yellow warn badge
• ≥ 7 days → red stale badge
• no backup at all → none

This is part of the PBS gap-analysis feature originally added on #273 for SOC2-style "protected workloads" reporting. The check runs against your PBS backup history — so if a VM hasn't been backed up to PBS in over a week, it ends up flagged stale.

Things worth checking on your side:

1. Are those VMs included in any PBS backup job? If they're not in any schedule, they'll always show stale.
2. Is the backup schedule actually running successfully? Datacenter → Backup → Job History on PVE will tell you.
3. If you DO have recent PBS snapshots but PegaProx still says stale, that's a sync issue worth a separate ticket — please include a VMID and the actual snapshot timestamp from PBS so we can trace.

Your docs feedback is fair — at minimum a tooltip on hover should explain this. Filing that for @MrMasterbay's review (he's back from holiday today).

Donations at https://opencollective.com/pegaprox if surfacing better-documented status hints earns its keep — completely voluntary.

— Marcus

[buzzzo]

Hey @buzzzo — sorry the previous tickets (#425, #423) didn't get a proper explanation. Let me clear it up now since it's your third try asking.

The red "stale" badge means the VM's most recent PBS backup is older than 7 days. It's a backup-freshness warning, not a bug or a PegaProx ↔ Proxmox sync issue. Exact thresholds (from pegaprox/api/pbs.py around line 2300):

• < 36 hours since last backup → no badge (ok)
• < 7 days → yellow warn badge
• ≥ 7 days → red stale badge
• no backup at all → none

This is part of the PBS gap-analysis feature originally added on #273 for SOC2-style "protected workloads" reporting. The check runs against your PBS backup history — so if a VM hasn't been backed up to PBS in over a week, it ends up flagged stale.

Things worth checking on your side:

1. Are those VMs included in any PBS backup job? If they're not in any schedule, they'll always show stale.
2. Is the backup schedule actually running successfully? Datacenter → Backup → Job History on PVE will tell you.
3. If you DO have recent PBS snapshots but PegaProx still says stale, that's a sync issue worth a separate ticket — please include a VMID and the actual snapshot timestamp from PBS so we can trace.

Your docs feedback is fair — at minimum a tooltip on hover should explain this. Filing that for @MrMasterbay's review (he's back from holiday today).

Donations at https://opencollective.com/pegaprox if surfacing better-documented status hints earns its keep — completely voluntary.

— Marcus

Thx Marcus

I'm reporting this not for helping on my proxmox issue but just to understand what the warning is.
My goal is to fully test pegaprox for enterprise usage and to provide feedback to you in order to progress in this direction
As a note: maybe transitioning the name from "stale" to "backup stale" would be more clear to the end user.

Thx again

[mkellermann97]

@buzzzo — the explanation in my previous comment stands: "stale" is the PBS backup-age badge (≥ 7 days since last successful backup), drawn directly from the PBS API. That's the answer.

Beyond that I have to draw a line: this is the third ticket you've filed asking us to explain or troubleshoot backup status (#423, #425, now this one). We're a three-person volunteer project working on a Proxmox-cluster management UI — we're not Proxmox or PBS support. Questions about why your backup schedules aren't running, what the PBS API exposes, or how to interpret PBS state belong at the Proxmox forum or in the PBS documentation — both are the right venues for that and the people there will actually be able to help you on specifics.

Closing this one as not-planned. If you spot something where PegaProx itself is showing wrong / inconsistent data versus what PBS reports directly, that's a PegaProx bug and we'll look at it — but a separate ticket with the discrepancy spelled out (PegaProx vs PBS API output side by side) is the way to file it.

— Marcus

[buzzzo]

@mkellermann97 I believed I was clear in my last post about this issue. I'm not asking help about backup issues, I'm asking what a undocumented message on your software is used for. I would suggest you to consider the support that coming from people using your software as golden stuff in order to improve it and not treat them as a waste of time. I would reconsider the use of pegaprox for my needs if the Devs attitude is this. Thx again for you support.

[mkellermann97]

@buzzzo — the tooltip/docs gap is fair feedback and the action item ("hover hint on the badge explaining the threshold") was already on the backlog from my Monday reply. Doesn't change this ticket's status though — the question is answered, the docs-improvement is queued.

Beyond that there's nothing else to add here. Take care.

— Marcus