public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Lukas Wagner <l.wagner@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>,
	Gabriel Goller <g.goller@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox{, -backup} v6 0/4] proxmox-log introduction
Date: Fri, 28 Jun 2024 11:25:09 +0200	[thread overview]
Message-ID: <2b069a9b-93ff-4d3d-bacc-81fb852f406d@proxmox.com> (raw)
In-Reply-To: <20240626131120.336868-1-g.goller@proxmox.com>



On  2024-06-26 15:10, Gabriel Goller wrote:
> Removed the task_log! (and friends task_warn!, task_debug!, etc.) macro
> and introduced the `tracing` crate. We now initiate the tracing crate
> using two layer, which are logging to the syslog and the tasklog.
> It uses the `tracing-journald` crate and the original `FileLogger`.
> 
> To write to the task logs from the worker threads and tasks, we now
> have a task_local logger (and warning counter), which
> will get instantiated when a task/thread is created. This means that
> when we call `info!` or any other `tracing` log macros, it will get 
> the file_logger from TLS and write to the file.
> 
> v6, thanks @Lukas:
>  - rebase
>  - reorder imports, inline variables
>  - introduce `tracing-journald` and throw out `syslog`
>  - split single layer into two, one for syslog and for tasklog
> 
> 
> 
> Summary over all repositories:
>   46 files changed, 809 insertions(+), 1114 deletions(-)
> 

LGTM now.

Could you post a cargo fmt'd v7? There are
some whitespace errors (trailing spaces) and some minor
formatting issues, nothing major. Feel free to already
augment the following trailers to your v7 commits:

Reviewed-by: Lukas Wagner <l.wagner@proxmox.com>
Tested-by: Lukas Wagner <l.wagner@proxmox.com>

-- 
- Lukas


_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel


  parent reply	other threads:[~2024-06-28  9:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 13:10 Gabriel Goller
2024-06-26 13:10 ` [pbs-devel] [PATCH proxmox v6 1/4] proxmox-log: add tracing infrastructure Gabriel Goller
2024-06-26 13:10 ` [pbs-devel] [PATCH proxmox v6 2/4] enable tracing logger, remove task_log macros Gabriel Goller
2024-06-26 13:10 ` [pbs-devel] [PATCH proxmox-backup v6 3/4] switch from task_log! macro to tracing Gabriel Goller
2024-06-26 13:10 ` [pbs-devel] [PATCH proxmox-backup v6 4/4] api: " Gabriel Goller
2024-06-28  9:25 ` Lukas Wagner [this message]
2024-07-01  9:27 ` [pbs-devel] [PATCH proxmox{, -backup} v6 0/4] proxmox-log introduction Gabriel Goller

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=2b069a9b-93ff-4d3d-bacc-81fb852f406d@proxmox.com \
    --to=l.wagner@proxmox.com \
    --cc=g.goller@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal