Backup verbosity levels seems to high
-
I wanted to share some feedback regarding the current backup management output/logging.
Right now it exposes a lot of internal infrastructure and operational details that probably should not be visible in customer-facing UI/API responses.Examples from the current output include:
API usernames/service accounts and token names
internal node/hostnames
storage backend names
VMIDs
raw vzdump commands
internal UUIDs/job IDs
disk names, layouts and sizesExample output:
UPID:NODENAME:0004C45B:0415EAAB:6A154BC9:vzdump:105:multiportal-API-user@pve!proxmox-api-user creating Proxmox Backup Server archive 'vm/105/2026-05-26T07:29:13Z' include disk 'scsi0' 'linstor-05:pm-9ed46057_105' 67108872K VM Name: testvm starting new backup job: vzdump 105 --node NODENAME --storage STORAGENAME ...This makes it possible to map internal infrastructure, naming conventions, storage layout and automation details very easily.
Would recommend sanitizing or abstracting raw Proxmox/PBS output and only exposing high-level backup status information unless debug/admin mode is explicitly enabled.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login