From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>,
"Christian Ebner" <c.ebner@proxmox.com>,
pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-backup v6 11/15] server: pull: prefix log messages and add error context
Date: Tue, 21 Apr 2026 14:57:29 +0200 [thread overview]
Message-ID: <b10d90a2-8e75-4a62-95e5-0b357355f688@proxmox.com> (raw)
In-Reply-To: <1776684473.p5hg4a1vym.astroid@yuna.none>
Am 20.04.26 um 13:55 schrieb Fabian Grünbichler:
> should we pad the labels? the buffered logger knows all currently active
> labels and could adapt it? otherwise especially for host backups the
> logs are again not really scannable by humans, because there will be
> weird jumps in alignment.. or (.. continued below)
IMO it might be better to keep these simple and plain and rather do any
"touching up" on the frontend UI side when rendering such a log.
For now that would need to be a parser for some specific task-log types
to make them aware of the format, which is naturally not that great, in
the mid/long term it might be much nicer to have some structured logging
available for task logs, as then we could encode more info that a task log
render could either render nicer or also allow filtering on.
Am 20.04.26 um 13:55 schrieb Fabian Grünbichler:
> the way the prefix and snapshot are formatted could also be interpreted
> at first glance as a timestamp of the log line.. why not just prepend
> the prefix on the logger side, and leave it up to the caller to do the
> formatting? then we could us "{type}/{id}/" as prefix here? or add
> 'snapshot' in those lines to make it clear? granted, this is more of an
> issue when viewing the log via `proxmox-backup-manager`, as in the UI we
> have the log timestamps up front..
ah, my comment above is partially overlapping with this part of the
reply. And I'd also always prefix the time upfront, IMO a bit odd if
it's in the "middle". But more importantly, I'd not sweat the details
here that much and would rather target staying closer with pre-existing
format (to avoid going back-and-forth), we can still improve on that later.
next prev parent reply other threads:[~2026-04-21 12:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 9:26 [PATCH proxmox{,-backup} v6 00/15] fix #4182: concurrent group pull/push support for sync jobs Christian Ebner
2026-04-17 9:26 ` [PATCH proxmox v6 01/15] pbs api types: add `worker-threads` to sync job config Christian Ebner
2026-04-17 9:26 ` [PATCH proxmox-backup v6 02/15] tools: group and sort module imports Christian Ebner
2026-04-17 9:26 ` [PATCH proxmox-backup v6 03/15] tools: implement buffered logger for concurrent log messages Christian Ebner
2026-04-20 10:57 ` Fabian Grünbichler
2026-04-20 17:15 ` Christian Ebner
2026-04-21 6:49 ` Fabian Grünbichler
2026-04-17 9:26 ` [PATCH proxmox-backup v6 04/15] tools: add bounded join set to run concurrent tasks bound by limit Christian Ebner
2026-04-20 11:15 ` Fabian Grünbichler
2026-04-17 9:26 ` [PATCH proxmox-backup v6 05/15] client: backup writer: fix upload stats size and rate for push sync Christian Ebner
2026-04-20 12:29 ` Fabian Grünbichler
2026-04-17 9:26 ` [PATCH proxmox-backup v6 06/15] api: config/sync: add optional `worker-threads` property Christian Ebner
2026-04-17 9:26 ` [PATCH proxmox-backup v6 07/15] sync: pull: revert avoiding reinstantiation for encountered chunks map Christian Ebner
2026-04-17 9:26 ` [PATCH proxmox-backup v6 08/15] sync: pull: factor out backup group locking and owner check Christian Ebner
2026-04-17 9:26 ` [PATCH proxmox-backup v6 09/15] sync: pull: prepare pull parameters to be shared across parallel tasks Christian Ebner
2026-04-17 9:26 ` [PATCH proxmox-backup v6 10/15] fix #4182: server: sync: allow pulling backup groups in parallel Christian Ebner
2026-04-17 9:26 ` [PATCH proxmox-backup v6 11/15] server: pull: prefix log messages and add error context Christian Ebner
2026-04-20 11:56 ` Fabian Grünbichler
2026-04-21 7:21 ` Christian Ebner
2026-04-21 7:42 ` Christian Ebner
2026-04-21 8:00 ` Fabian Grünbichler
2026-04-21 8:04 ` Christian Ebner
2026-04-21 12:57 ` Thomas Lamprecht [this message]
2026-04-17 9:26 ` [PATCH proxmox-backup v6 12/15] sync: push: prepare push parameters to be shared across parallel tasks Christian Ebner
2026-04-17 9:26 ` [PATCH proxmox-backup v6 13/15] server: sync: allow pushing groups concurrently Christian Ebner
2026-04-17 9:26 ` [PATCH proxmox-backup v6 14/15] server: push: prefix log messages and add additional logging Christian Ebner
2026-04-17 9:26 ` [PATCH proxmox-backup v6 15/15] ui: expose group worker setting in sync job edit window Christian Ebner
2026-04-20 12:33 ` [PATCH proxmox{,-backup} v6 00/15] fix #4182: concurrent group pull/push support for sync jobs Fabian Grünbichler
2026-04-21 10:28 ` superseded: " Christian Ebner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b10d90a2-8e75-4a62-95e5-0b357355f688@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.ebner@proxmox.com \
--cc=f.gruenbichler@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.