From: Hannes Laimer <h.laimer@proxmox.com>
To: Christian Ebner <c.ebner@proxmox.com>, pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox v5 13/13] s3-client: implement request counter threshold and exceeding callback
Date: Mon, 16 Mar 2026 11:36:35 +0100 [thread overview]
Message-ID: <8d002ea9-e47f-4283-9a6c-4e642768115e@proxmox.com> (raw)
In-Reply-To: <1e802b7c-e65c-482b-af4a-6088e6e70053@proxmox.com>
On 2026-03-13 15:56, Christian Ebner wrote:
> On 3/13/26 3:26 PM, Hannes Laimer wrote:
>> On 2026-03-11 14:09, Christian Ebner wrote:
>>> Allows to set the threshold values to trigger exceeding callbacks
>>> for the s3 request counters.
>>> The globally settable callback function is executed whenever one of
>>> the request counters is exceeding it's set threshold value, but
>>> only once when passing over the threshold.
>>>
>>> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
>>> ---
>>
>> [..]
>>
>>> +
>>> + /// Update the callback executed when one of the set thresholds
>>> is exceeded
>>> + pub fn update_thresholds_exceeded_callback(callback:
>>> ThresholdExceededCallback) {
>>> + SHARED_COUNTER_THRESHOLD_EXCEEDED_CALLBACK
>>> + .write()
>>> + .unwrap()
>>> + .replace(callback);
>>> + }
>>
>> this is called on every datastore load, so
>> `SHARED_COUNTER_THRESHOLD_EXCEEDED_CALLBACK` only holds the callback
>> associated with the latest datastore that was looked-up. Every call
>> would replace whatever callback was there before, at least if we don't
>> hit the cache...
>
> Yes that is true, might be better to only set it once. The callback is
> however shared behind an Arc for all datastores and already should use
> the correct counters and threshold for the given datastore, so the
> notifications are send for that, independent of which was the last store
> to be instantiated since not cached.
>
> But it makes sense to avoid updating the function pointer each time.
>
right, but isn't the datastore's name captured when we assign the
callback?
```
+
SharedRequestCounters::update_thresholds_exceeded_callback(Box::new(
+ move |counter_id, threshold, value| {
+ thresholds_exceeded_callback.map(|cb| {
+ if let Err(err) = cb(&config.name,
counter_id, threshold, value) {
+ log::error!("failed to send
notification: {err:?}");
+ }
+ });
+ },
+ ));
```
am I missing something?
>>> +
>>> + /// Update the request counter thresholds to given values.
>>> + pub fn update_thresholds(&self, thresholds:
>>> &RequestCounterThresholds) {
>>> + self.shared_memory
>>> + .data()
>>> + .counters
>>> + .update_thresholds(thresholds);
>>> + }
>>> }
>>> const FLUSH_THRESHOLD: Duration = Duration::from_secs(5);
>>
>
next prev parent reply other threads:[~2026-03-16 10:36 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
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 [this message]
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=8d002ea9-e47f-4283-9a6c-4e642768115e@proxmox.com \
--to=h.laimer@proxmox.com \
--cc=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