public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: Hannes Laimer <h.laimer@proxmox.com>, pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-backup v5 04/20] api: s3: add endpoint to reset s3 request counters
Date: Thu, 12 Mar 2026 15:43:29 +0100	[thread overview]
Message-ID: <3bb38383-5056-419d-812a-9fdc301342b1@proxmox.com> (raw)
In-Reply-To: <4787283f-b5e5-49b6-9f4a-34045b6556eb@proxmox.com>

On 3/12/26 3:07 PM, Hannes Laimer wrote:
> On 2026-03-11 14:08, Christian Ebner wrote:
>> Allows to reset the current counter states. This can be done
>> manually or possibly by a scheduled task in the future.
>>
>> The intent is to start fresh in case of e.g. monthly limit warnings.
>>
>> Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
>> ---
>>   src/api2/admin/s3.rs | 71 ++++++++++++++++++++++++++++++++++++++++++--
>>   1 file changed, 68 insertions(+), 3 deletions(-)
>>
>> diff --git a/src/api2/admin/s3.rs b/src/api2/admin/s3.rs
>> index d08ab3246..fb3488eb8 100644
>> --- a/src/api2/admin/s3.rs
>> +++ b/src/api2/admin/s3.rs
>> @@ -1,13 +1,16 @@
>>   //! S3 bucket operations
>>   
>> -use anyhow::{Context, Error};
>> +use std::path::Path;
>> +use std::sync::atomic::Ordering;
>> +
>> +use anyhow::{bail, Context, Error};
>>   use serde_json::Value;
>>   
>>   use proxmox_http::Body;
>>   use proxmox_router::{list_subdirs_api_method, Permission, Router, RpcEnvironment, SubdirMap};
>>   use proxmox_s3_client::{
>>       S3Client, S3ClientConf, S3ClientOptions, S3ObjectKey, S3RequestCounterOptions,
>> -    S3_BUCKET_NAME_SCHEMA, S3_CLIENT_ID_SCHEMA, S3_HTTP_REQUEST_TIMEOUT,
>> +    SharedRequestCounters, S3_BUCKET_NAME_SCHEMA, S3_CLIENT_ID_SCHEMA, S3_HTTP_REQUEST_TIMEOUT,
>>   };
>>   use proxmox_schema::*;
>>   use proxmox_sortable_macro::sortable;
>> @@ -97,8 +100,70 @@ pub async fn check(
>>       Ok(Value::Null)
>>   }
>>   
>> +#[api(
>> +    input: {
>> +        properties: {
>> +            "s3-endpoint-id": {
> ^ we do `match_all` for `s3-client-id` in the router, so this should be
> `s3-client-id`

Will be fixed as well with an upcoming v6, thanks!

> 
>> +                schema: S3_CLIENT_ID_SCHEMA,
>> +            },
>> +            bucket: {
>> +                schema: S3_BUCKET_NAME_SCHEMA,
>> +            },
>> +            "store-prefix": {
>> +                type: String,
>> +                description: "Store prefix within bucket for S3 object keys (commonly datastore name)",
>> +                optional: true,
>> +            },
>> +        },
>> +    },
>> +    access: {
>> +        permission: &Permission::Privilege(&[], PRIV_SYS_MODIFY, false),
>> +    },
>> +)]
>> +/// Reset the S3 request counters for matching endpoint, bucket or datastore (if prefix is given).
>> +pub async fn reset_counters(
>> +    s3_endpoint_id: String,
>> +    bucket: String,
>> +    store_prefix: Option<String>,
>> +    _rpcenv: &mut dyn RpcEnvironment,
>> +) -> Result<(), Error> {
>> +    let (config, _digest) = pbs_config::s3::config()?;
>> +    // only check if the provided endpoint id exists
>> +    let _config: S3ClientConf = config
>> +        .lookup(S3_CFG_TYPE_ID, &s3_endpoint_id)
>> +        .context("config lookup failed")?;
>> +
>> +    let request_counter_id = if let Some(store) = &store_prefix {
>> +        format!("{s3_endpoint_id}-{bucket}-{store}")
>> +    } else {
>> +        format!("{s3_endpoint_id}-{bucket}")
>> +    };
>> +
>> +    let path = format!("{S3_CLIENT_REQUEST_COUNTER_BASE_PATH}/{request_counter_id}.shmem");
>> +    let path = Path::new(&path);
>> +    // Fail early to not create the file when opening shared memory map below. Accept that
>> +    // this can race, with a new counter file being created in the mean time, but that is
>> +    // not an issue.
>> +    if !path.is_file() {
>> +        bail!("Cannot find s3 counters file '{path:?}'");
>> +    }
>> +
>> +    let user = pbs_config::backup_user()?;
>> +    let request_counters = SharedRequestCounters::open_shared_memory_mapped(path, user)
>> +        .context("failed to open shared request counters")?;
>> +    request_counters.reset(Ordering::Release);
>> +
>> +    Ok(())
>> +}
>> +
>>   #[sortable]
>> -const S3_OPERATION_SUBDIRS: SubdirMap = &[("check", &Router::new().put(&API_METHOD_CHECK))];
>> +const S3_OPERATION_SUBDIRS: SubdirMap = &[
>> +    ("check", &Router::new().put(&API_METHOD_CHECK)),
>> +    (
>> +        "reset-counters",
>> +        &Router::new().put(&API_METHOD_RESET_COUNTERS),
>> +    ),
>> +];
>>   
>>   const S3_OPERATION_ROUTER: Router = Router::new()
>>       .get(&list_subdirs_api_method!(S3_OPERATION_SUBDIRS))
> 





  reply	other threads:[~2026-03-12 14:43 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
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 [this message]
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=3bb38383-5056-419d-812a-9fdc301342b1@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal