all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 2/2] traffic-control: add debug log when we found a matching rule
Date: Fri,  4 Feb 2022 10:12:21 +0100	[thread overview]
Message-ID: <20220204091221.1781533-2-d.csapak@proxmox.com> (raw)
In-Reply-To: <20220204091221.1781533-1-d.csapak@proxmox.com>

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
optional, at least one user in the forum has a problem with traffic
control, this could help debug that in the future...

 src/cached_traffic_control.rs | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/cached_traffic_control.rs b/src/cached_traffic_control.rs
index 2f077d36..cd13bc1b 100644
--- a/src/cached_traffic_control.rs
+++ b/src/cached_traffic_control.rs
@@ -342,6 +342,7 @@ impl TrafficControlCache {
             Some((rule, _)) => {
                 match self.limiter_map.get(&rule.config.name) {
                     Some((read_limiter, write_limiter)) => {
+                        log::debug!("found traffic control rule for {:?} : {}", peer_ip, &rule.config.name);
                         (&rule.config.name, read_limiter.clone(), write_limiter.clone())
                     }
                     None => ("", None, None), // should never happen
-- 
2.30.2





  reply	other threads:[~2022-02-04  9:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04  9:12 [pbs-devel] [PATCH proxmox-backup 1/2] use PROXMOX_DEBUG env variable to control loglevel Dominik Csapak
2022-02-04  9:12 ` Dominik Csapak [this message]
2022-02-04 10:05   ` [pbs-devel] [PATCH proxmox-backup 2/2] traffic-control: add debug log when we found a matching rule Thomas Lamprecht
2022-02-04 10:09     ` Dominik Csapak
2022-02-04 10:21       ` Thomas Lamprecht
2022-02-04 10:22 ` [pbs-devel] applied: [PATCH proxmox-backup 1/2] use PROXMOX_DEBUG env variable to control loglevel Thomas Lamprecht

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=20220204091221.1781533-2-d.csapak@proxmox.com \
    --to=d.csapak@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal