From: Christian Ebner <c.ebner@proxmox.com>
To: Hannes Laimer <h.laimer@proxmox.com>, pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox v5 05/13] s3-client: add counters for upload/download traffic
Date: Thu, 12 Mar 2026 15:40:10 +0100 [thread overview]
Message-ID: <b3126a4d-ae1e-4b3b-995a-7bc76b7c3eac@proxmox.com> (raw)
In-Reply-To: <4d7f81dc-8bae-4942-8eba-c19785c9a42c@proxmox.com>
On 3/12/26 3:28 PM, Hannes Laimer wrote:
> do we want to also `reset` bytes, cause the reset api endpoint does not
> currently? We have thresholds, but we don't seem to check them, so no I
> guess. On the other hand, given the current implementation it looks like
> they are intended to behave like the counter ones.
Yes, indeed! The uploaded/downloaded traffic should be reset as well,
will adapt that, thanks! In general, I still plan to include a schedule
based resetting, so users can configure to e.g. perform a monthly reset
of the counters.
>
>
> On 2026-03-11 14:08, Christian Ebner wrote:
>> In addition to accounting for requests, also allow to track the
>> number of bytes uploaded or downloaded via the s3 clients.
>>
>> With the intention to estimate shared upload/download bandwidth in
>> Proxmox Backup Server as well as easily estimate the total traffic
>> volume.
>>
>> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
>> ---
>> .../src/shared_request_counters.rs | 63 +++++++++++++++++++
>> 1 file changed, 63 insertions(+)
>>
>> diff --git a/proxmox-s3-client/src/shared_request_counters.rs b/proxmox-s3-client/src/shared_request_counters.rs
>> index edd1df3d..a5cd286c 100644
>> --- a/proxmox-s3-client/src/shared_request_counters.rs
>> +++ b/proxmox-s3-client/src/shared_request_counters.rs
>> @@ -37,6 +37,9 @@ struct RequestCounters {
>> put: AlignedAtomic,
>> head: AlignedAtomic,
>> post: AlignedAtomic,
>> + // traffic in bytes
>> + upload: AlignedAtomic,
>> + download: AlignedAtomic,
>> }
>>
>> impl Init for RequestCounters {
>> @@ -81,6 +84,30 @@ impl RequestCounters {
>> self.post.0.store(0, ordering);
>> self.put.0.store(0, ordering);
>> }
>> +
>> + /// Account for new upload traffic.
>> + ///
>> + /// Returns the previously stored value.
>> + pub fn add_upload_traffic(&self, count: u64, ordering: Ordering) -> u64 {
>> + self.upload.0.fetch_add(count, ordering)
>> + }
>> +
>> + /// Returns upload traffic count.
>> + pub fn get_upload_traffic(&self, ordering: Ordering) -> u64 {
>> + self.upload.0.load(ordering)
>> + }
>> +
>> + /// Account for new download traffic.
>> + ///
>> + /// Returns the previously stored value.
>> + pub fn add_download_traffic(&self, count: u64, ordering: Ordering) -> u64 {
>> + self.download.0.fetch_add(count, ordering)
>> + }
>> +
>> + /// Returns download traffic count.
>> + pub fn get_download_traffic(&self, ordering: Ordering) -> u64 {
>> + self.download.0.load(ordering)
>> + }
>> }
>>
>> /// Size of the padding to align the mmapped request counters to 4k default
>> @@ -180,4 +207,40 @@ impl SharedRequestCounters {
>> pub fn reset(&self, ordering: Ordering) {
>> self.shared_memory.data().counters.reset(ordering)
>> }
>> +
>> + /// Account for new upload traffic.
>> + ///
>> + /// Returns the previously stored value.
>> + pub fn add_upload_traffic(&self, count: u64, ordering: Ordering) -> u64 {
>> + self.shared_memory
>> + .data()
>> + .counters
>> + .add_upload_traffic(count, ordering)
>> + }
>> +
>> + /// Returns upload traffic count.
>> + pub fn get_upload_traffic(&self, ordering: Ordering) -> u64 {
>> + self.shared_memory
>> + .data()
>> + .counters
>> + .get_upload_traffic(ordering)
>> + }
>> +
>> + /// Account for new download traffic.
>> + ///
>> + /// Returns the previously stored value.
>> + pub fn add_download_traffic(&self, count: u64, ordering: Ordering) -> u64 {
>> + self.shared_memory
>> + .data()
>> + .counters
>> + .add_download_traffic(count, ordering)
>> + }
>> +
>> + /// Returns download traffic count.
>> + pub fn get_download_traffic(&self, ordering: Ordering) -> u64 {
>> + self.shared_memory
>> + .data()
>> + .counters
>> + .get_download_traffic(ordering)
>> + }
>> }
>
next prev parent reply other threads:[~2026-03-12 14:40 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 13:07 [PATCH proxmox{,-backup} v5 00/33] partially fix #6563: add s3 request and traffic counter statistics Christian Ebner
2026-03-11 13:07 ` [PATCH proxmox v5 01/13] proxmox-sys: expose msync to flush mmapped contents to filesystem Christian Ebner
2026-03-12 11:20 ` applied: " Fabian Grünbichler
2026-03-11 13:07 ` [PATCH proxmox v5 02/13] shared-memory: add method without tmpfs check for mmap file location Christian Ebner
2026-03-12 11:20 ` applied: " Fabian Grünbichler
2026-03-11 13:07 ` [PATCH proxmox v5 03/13] shared-memory: expose msync to flush in-memory contents to filesystem Christian Ebner
2026-03-12 11:20 ` applied: " Fabian Grünbichler
2026-03-11 13:07 ` [PATCH proxmox v5 04/13] s3-client: add persistent shared request counters for client Christian Ebner
2026-03-11 13:07 ` [PATCH proxmox v5 05/13] s3-client: add counters for upload/download traffic Christian Ebner
2026-03-12 14:28 ` Hannes Laimer
2026-03-12 14:40 ` Christian Ebner [this message]
2026-03-11 13:07 ` [PATCH proxmox v5 06/13] s3-client: account for upload traffic on successful request sending Christian Ebner
2026-03-11 13:07 ` [PATCH proxmox v5 07/13] s3-client: account for downloaded bytes in incoming response body Christian Ebner
2026-03-12 14:14 ` Hannes Laimer
2026-03-12 14:42 ` Christian Ebner
2026-03-11 13:07 ` [PATCH proxmox v5 08/13] s3-client: request counters: periodically persist counters to file Christian Ebner
2026-03-13 14:16 ` Hannes Laimer
2026-03-11 13:07 ` [PATCH proxmox v5 09/13] s3-client: sync flush request counters on client instance drop Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox v5 10/13] pbs-api-types: define api type for s3 request statistics Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox v5 11/13] s3-client: api-types: define request counter thresholds Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox v5 12/13] pbs-api-types: add notification thresholds to datastore config Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox v5 13/13] s3-client: implement request counter threshold and exceeding callback Christian Ebner
2026-03-12 14:11 ` Hannes Laimer
2026-03-13 14:27 ` Hannes Laimer
2026-03-13 14:56 ` Christian Ebner
2026-03-16 10:36 ` Hannes Laimer
2026-03-16 10:38 ` Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 01/20] metrics: split common module imports into individual use statements Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 02/20] datastore: collect request statistics for s3 backed datastores Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 03/20] datastore: expose request counters " Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 04/20] api: s3: add endpoint to reset s3 request counters Christian Ebner
2026-03-12 14:08 ` Hannes Laimer
2026-03-12 14:43 ` Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 05/20] bin: s3: expose request counter reset method as cli command Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 06/20] datastore: add helper method to get datastore backend type Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 07/20] ui: improve variable name indirectly fixing typo Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 08/20] ui: datastore summary: move store to be part of summary panel Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 09/20] ui: expose s3 request counter statistics in the datastore summary Christian Ebner
2026-03-16 14:02 ` Hannes Laimer
2026-03-11 13:08 ` [PATCH proxmox-backup v5 10/20] metrics: collect s3 datastore statistics as rrd metrics Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 11/20] api: admin: expose s3 statistics in datastore rrd data Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 12/20] partially fix #6563: ui: expose s3 rrd charts in datastore summary Christian Ebner
2026-03-13 14:45 ` Hannes Laimer
2026-03-11 13:08 ` [PATCH proxmox-backup v5 13/20] datastore: refactor shared request counter loading into helper Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 14/20] api: config: update notification thresholds for config and counters Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 15/20] ui: utils: add helper to render notification threshold property string Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 16/20] ui: add notification thresholds edit window Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 17/20] notifications: template data: fix typos in docstrings Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 18/20] notification: define templates and template data for thresholds Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 19/20] datastore: add thresholds notification callback on datastore lookup Christian Ebner
2026-03-11 13:08 ` [PATCH proxmox-backup v5 20/20] api/ui: notifications: add 'thresholds' as notification type value Christian Ebner
2026-03-16 14:04 ` [PATCH proxmox{,-backup} v5 00/33] partially fix #6563: add s3 request and traffic counter statistics Hannes Laimer
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=b3126a4d-ae1e-4b3b-995a-7bc76b7c3eac@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=h.laimer@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