From: Christian Ebner <c.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [PATCH proxmox{,-backup} v3 00/22] partially fix #6563: add s3 request and traffic counter statistics
Date: Tue, 24 Feb 2026 10:13:44 +0100 [thread overview]
Message-ID: <20260224091406.169080-1-c.ebner@proxmox.com> (raw)
This patch series implements request and traffic counters for the s3
client, being shared as atomic counters via shared memory and mmapping
across all s3-client instances.
The shared counters are instantiated on demand for individual
datastores with s3 backend on s3 client instantiation and stored as
part of the datastore implementation by loading the mmapped file on
datastore instantiation, being cached for further access.
Further, counters are being loaded during rrd metrics collection and
exposed as charts in the datastore summary, including the total
request counts per method, the total upload and download traffic as
well as the averaged upload and download rate.
Usage statistics, soft limit and thresholds to send warnings via the
notificatoin system are not included in this series an will be
tackled as followup series.
Link to the bugtracker issue:
https://bugzilla.proxmox.com/show_bug.cgi?id=6563
Changes since version 2:
- Introduce msync flushing mechanism to periodically persist counters
state to mmap backing file.
Changes since version 1 (thanks @Robert for feedback):
- Keep tmpfs check in shmem mapping for pre-existing code, add
dedicated methods to create mmapped files in persistent locations.
- Reorder and align atomic counters to 32-byte (half default cache
line size) to reduce false sharing.
- Rework request counter init logic, avoid unsafe code and undefined
behaviour.
- Rework page size calculation based on new counter alignment.
- Avoid the need to open and mmap counter file for each rrd data
collection, keep the per-datastores filehandle cached instead.
proxmox:
Christian Ebner (10):
proxmox-sys: expose msync to flush mmapped contents to filesystem
shared-memory: add method without tmpfs check for mmap file location
shared-memory: expose msync to flush in-memory contents to filesystem
s3-client: add persistent shared request counters for client
s3-client: add counters for upload/download traffic
s3-client: account for upload traffic on successful request sending
s3-client: account for downloaded bytes in incoming response body
s3-client: request counters: periodically persist counters to file
s3-client: sync flush request counters on client instance drop
pbs-api-types: define api type for s3 request statistics
pbs-api-types/src/datastore.rs | 28 ++
proxmox-s3-client/Cargo.toml | 6 +
proxmox-s3-client/debian/control | 3 +
proxmox-s3-client/examples/s3_client.rs | 1 +
proxmox-s3-client/src/client.rs | 101 ++++-
proxmox-s3-client/src/lib.rs | 7 +-
proxmox-s3-client/src/response_reader.rs | 75 +++-
.../src/shared_request_counters.rs | 410 ++++++++++++++++++
proxmox-shared-memory/src/lib.rs | 48 +-
proxmox-sys/src/mmap.rs | 12 +
10 files changed, 671 insertions(+), 20 deletions(-)
create mode 100644 proxmox-s3-client/src/shared_request_counters.rs
proxmox-backup:
Christian Ebner (12):
metrics: split common module imports into individual use statements
datastore: collect request statistics for s3 backed datastores
datastore: expose request counters for s3 backed datastores
api: s3: add endpoint to reset s3 request counters
bin: s3: expose request counter reset method as cli command
datastore: add helper method to get datastore backend type
ui: improve variable name indirectly fixing typo
ui: datastore summary: move store to be part of summary panel
ui: expose s3 request counter statistics in the datastore summary
metrics: collect s3 datastore statistics as rrd metrics
api: admin: expose s3 statistics in datastore rrd data
partially fix #6563: ui: expose s3 rrd charts in datastore summary
pbs-datastore/src/datastore.rs | 66 +++-
pbs-datastore/src/lib.rs | 2 +-
src/api2/admin/datastore.rs | 23 +-
src/api2/admin/s3.rs | 86 ++++-
src/api2/config/s3.rs | 18 +-
src/bin/proxmox_backup_manager/s3.rs | 33 ++
src/server/metric_collection/metric_server.rs | 8 +-
src/server/metric_collection/mod.rs | 108 +++++-
src/server/metric_collection/pull_metrics.rs | 18 +-
src/server/metric_collection/rrd.rs | 34 +-
www/datastore/Summary.js | 341 ++++++++++++------
11 files changed, 587 insertions(+), 150 deletions(-)
Summary over all repositories:
21 files changed, 1258 insertions(+), 170 deletions(-)
--
Generated by murpp 0.9.0
next reply other threads:[~2026-02-24 9:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 9:13 Christian Ebner [this message]
2026-02-24 9:13 ` [PATCH proxmox v3 01/10] proxmox-sys: expose msync to flush mmapped contents to filesystem Christian Ebner
2026-02-24 9:13 ` [PATCH proxmox v3 02/10] shared-memory: add method without tmpfs check for mmap file location Christian Ebner
2026-02-24 9:13 ` [PATCH proxmox v3 03/10] shared-memory: expose msync to flush in-memory contents to filesystem Christian Ebner
2026-02-24 9:13 ` [PATCH proxmox v3 04/10] s3-client: add persistent shared request counters for client Christian Ebner
2026-02-24 9:13 ` [PATCH proxmox v3 05/10] s3-client: add counters for upload/download traffic Christian Ebner
2026-02-24 9:13 ` [PATCH proxmox v3 06/10] s3-client: account for upload traffic on successful request sending Christian Ebner
2026-02-24 9:13 ` [PATCH proxmox v3 07/10] s3-client: account for downloaded bytes in incoming response body Christian Ebner
2026-02-24 9:13 ` [PATCH proxmox v3 08/10] s3-client: request counters: periodically persist counters to file Christian Ebner
2026-02-24 9:13 ` [PATCH proxmox v3 09/10] s3-client: sync flush request counters on client instance drop Christian Ebner
2026-02-24 9:13 ` [PATCH proxmox v3 10/10] pbs-api-types: define api type for s3 request statistics Christian Ebner
2026-02-24 9:13 ` [PATCH proxmox-backup v3 01/12] metrics: split common module imports into individual use statements Christian Ebner
2026-02-24 9:13 ` [PATCH proxmox-backup v3 02/12] datastore: collect request statistics for s3 backed datastores Christian Ebner
2026-02-24 9:13 ` [PATCH proxmox-backup v3 03/12] datastore: expose request counters " Christian Ebner
2026-02-24 9:13 ` [PATCH proxmox-backup v3 04/12] api: s3: add endpoint to reset s3 request counters Christian Ebner
2026-02-24 9:13 ` [PATCH proxmox-backup v3 05/12] bin: s3: expose request counter reset method as cli command Christian Ebner
2026-02-24 9:14 ` [PATCH proxmox-backup v3 06/12] datastore: add helper method to get datastore backend type Christian Ebner
2026-02-24 9:14 ` [PATCH proxmox-backup v3 07/12] ui: improve variable name indirectly fixing typo Christian Ebner
2026-02-24 9:14 ` [PATCH proxmox-backup v3 08/12] ui: datastore summary: move store to be part of summary panel Christian Ebner
2026-02-24 9:14 ` [PATCH proxmox-backup v3 09/12] ui: expose s3 request counter statistics in the datastore summary Christian Ebner
2026-02-24 9:14 ` [PATCH proxmox-backup v3 10/12] metrics: collect s3 datastore statistics as rrd metrics Christian Ebner
2026-02-24 9:14 ` [PATCH proxmox-backup v3 11/12] api: admin: expose s3 statistics in datastore rrd data Christian Ebner
2026-02-24 9:14 ` [PATCH proxmox-backup v3 12/12] partially fix #6563: ui: expose s3 rrd charts in datastore summary 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=20260224091406.169080-1-c.ebner@proxmox.com \
--to=c.ebner@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