<![CDATA[Backup verbosity levels seems to high]]>

<![CDATA[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 sizes

Example 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.

]]>https://forum.multiportal.io/topic/20/backup-verbosity-levels-seems-to-highRSS for NodeThu, 18 Jun 2026 03:39:21 GMTTue, 26 May 2026 07:49:11 GMT60<![CDATA[Reply to Backup verbosity levels seems to high on Tue, 26 May 2026 11:14:09 GMT]]>Yep great feedback. I’ll get this logged and into our backlog with a priority. Thanks @pean !

]]>https://forum.multiportal.io/post/42https://forum.multiportal.io/post/42Tue, 26 May 2026 11:14:09 GMT