From: Gabriel Goller <g.goller@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup v2] log: retrieve `ReaderEnvironment` debug flag from tracing
Date: Fri, 16 Aug 2024 12:39:58 +0200 [thread overview]
Message-ID: <20240816103958.187644-1-g.goller@proxmox.com> (raw)
Don't hardcode the debug flag but retrieve the currently enabled level
using tracing. This will change the default log-behavior and disable
some logs that have been printed previously. F.e.: the "protocol upgrade
done" message is not visible anymore per default because it is printed
with debug.
Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
---
Note that this still keeps the behavior of the client controlling the
log-level of the server, except if the server has a minimum log level of
warn.
v2, thanks @Christian:
- call self.log in self.debug
- do the same things in ReaderEnvironment
src/api2/backup/environment.rs | 11 ++++++++---
src/api2/reader/environment.rs | 11 ++++++++---
src/server/pull.rs | 11 +++++++++--
3 files changed, 25 insertions(+), 8 deletions(-)
diff --git a/src/api2/backup/environment.rs b/src/api2/backup/environment.rs
index 0a7c67b672a3..99d885e2e3c8 100644
--- a/src/api2/backup/environment.rs
+++ b/src/api2/backup/environment.rs
@@ -2,6 +2,7 @@ use anyhow::{bail, format_err, Error};
use nix::dir::Dir;
use std::collections::HashMap;
use std::sync::{Arc, Mutex};
+use tracing::info;
use ::serde::Serialize;
use serde_json::{json, Value};
@@ -141,7 +142,7 @@ impl BackupEnvironment {
auth_id,
worker,
datastore,
- debug: false,
+ debug: tracing::enabled!(tracing::Level::DEBUG),
formatter: JSON_FORMATTER,
backup_dir,
last_backup: None,
@@ -687,12 +688,16 @@ impl BackupEnvironment {
}
pub fn log<S: AsRef<str>>(&self, msg: S) {
- self.worker.log_message(msg);
+ info!("{}", msg.as_ref());
}
pub fn debug<S: AsRef<str>>(&self, msg: S) {
if self.debug {
- self.worker.log_message(msg);
+ // This is kinda weird, we would like to use tracing::debug! here and automatically
+ // filter it, but self.debug is set from the client-side and the logs are printed on
+ // client and server side. This means that if the client sets the log level to debug,
+ // both server and client need to have 'debug' logs printed.
+ self.log(msg);
}
}
diff --git a/src/api2/reader/environment.rs b/src/api2/reader/environment.rs
index 602c65e458a3..3b2f06f438fe 100644
--- a/src/api2/reader/environment.rs
+++ b/src/api2/reader/environment.rs
@@ -10,6 +10,7 @@ use pbs_datastore::backup_info::BackupDir;
use pbs_datastore::DataStore;
use proxmox_rest_server::formatter::*;
use proxmox_rest_server::WorkerTask;
+use tracing::info;
/// `RpcEnvironment` implementation for backup reader service
#[derive(Clone)]
@@ -39,7 +40,7 @@ impl ReaderEnvironment {
auth_id,
worker,
datastore,
- debug: false,
+ debug: tracing::enabled!(tracing::Level::DEBUG),
formatter: JSON_FORMATTER,
backup_dir,
allowed_chunks: Arc::new(RwLock::new(HashSet::new())),
@@ -47,12 +48,16 @@ impl ReaderEnvironment {
}
pub fn log<S: AsRef<str>>(&self, msg: S) {
- self.worker.log_message(msg);
+ info!("{}", msg.as_ref());
}
pub fn debug<S: AsRef<str>>(&self, msg: S) {
if self.debug {
- self.worker.log_message(msg);
+ // This is kinda weird, we would like to use tracing::debug! here and automatically
+ // filter it, but self.debug is set from the client-side and the logs are printed on
+ // client and server side. This means that if the client sets the log level to debug,
+ // both server and client need to have 'debug' logs printed.
+ self.log(msg);
}
}
diff --git a/src/server/pull.rs b/src/server/pull.rs
index 823515e9ab02..de1bb5d5f6af 100644
--- a/src/server/pull.rs
+++ b/src/server/pull.rs
@@ -278,8 +278,15 @@ impl PullSource for RemoteSource {
ns: &BackupNamespace,
dir: &BackupDir,
) -> Result<Arc<dyn PullReader>, Error> {
- let backup_reader =
- BackupReader::start(&self.client, None, self.repo.store(), ns, dir, true).await?;
+ let backup_reader = BackupReader::start(
+ &self.client,
+ None,
+ self.repo.store(),
+ ns,
+ dir,
+ tracing::enabled!(tracing::Level::DEBUG),
+ )
+ .await?;
Ok(Arc::new(RemoteReader {
backup_reader,
dir: dir.clone(),
--
2.39.2
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next reply other threads:[~2024-08-16 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 10:39 Gabriel Goller [this message]
2024-08-29 9:42 ` [pbs-devel] applied: " Wolfgang Bumiller
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=20240816103958.187644-1-g.goller@proxmox.com \
--to=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