[PATCH proxmox-backup 0/3] followups s3 datastores

[PATCH proxmox-backup 0/3] followups s3 datastores

[Christian Ebner]

These patches are some followups for the s3 datastores, which are
moving from tech preview to be fully supported. Therefore extend
on still missing documentation and drop a still present tech preview
label in the datastore create dialog.

Christian Ebner (3):
  docs: describe s3 request notifications and threshold reset schedule
  docs: mention still missing field in the configuration subtree
  ui: drop 'tech preview' label for s3 stores in creation dialog

 docs/gui.rst                | 10 ++++++--
 docs/notifications.rst      | 47 +++++++++++++++++++++++++++++++++++++
 docs/storage.rst            |  4 ++++
 www/window/DataStoreEdit.js |  2 +-
 4 files changed, 60 insertions(+), 3 deletions(-)

-- 
2.47.3

[PATCH proxmox-backup 1/3] docs: describe s3 request notifications and threshold reset schedule

[Christian Ebner]

Add a section describing the counter, how they can be used to trigger
notifications and how to periodically reset them.

Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
---
 docs/notifications.rst | 47 ++++++++++++++++++++++++++++++++++++++++++
 docs/storage.rst       |  4 ++++
 2 files changed, 51 insertions(+)

diff --git a/docs/notifications.rst b/docs/notifications.rst
index 992ef152e..440c700a4 100644
--- a/docs/notifications.rst
+++ b/docs/notifications.rst
@@ -371,3 +371,50 @@ The template files follow the naming convention of
 ``gc-err-body.txt.hbs`` contains the template for rendering notifications for
 garbage collection errors, while ``package-updates-subject.txt.hbs`` is used to
 render the subject line of notifications for available package updates.
+
+.. _s3_notification_thresholds:
+
+Notification Thresholds and Reset Schedule (S3 Datastores Only)
+---------------------------------------------------------------
+
+Datastores of type S3 keep track of the number of requests being send to the
+corresponding S3 endpoint and the amount of data being send. Proxmox Backup
+Server allows to configure threshold for these request and traffic counters to
+send out notifications if one of the set threshold values is exceeded.
+
+The notification threshold value can be set individually by request method or
+traffic volume. Notifications will be send out only once per threshold when the
+threshold has been exceeded. A counter reset is required to bring it below the
+threshold again in order to get further notifications. Therefore, it is possible
+to define a threshold reset schedule so request and traffic counters get
+periodically reset.
+
+Per datastore notification thresholds and their reset schedule are configurable
+in the :ref:`Datastore Options <datastore_options>` for S3 backed datastores.
+
+The following counters thresholds are available for configuration:
+
+==================== ==========================================================
+Counter Threshold    Description and Usage
+==================== ==========================================================
+``s3-get``           Number of ``GET`` requests: Mainly used for download of
+                     data and metadata among the following operations: restore,
+                     verification, S3 refresh, garbage collection.
+``s3-put``           Number of ``PUT`` requests: Mainly used for upload of data
+                     and metadata among the following operations: backup, syncs,
+                     metadata changes, content moves.
+``s3-post``          Number of ``POST`` requests: Mainly used for modification
+                     of data and metadata among the following operations: bulk
+                     deletion during garbage collection, content moves.
+``s3-head``          Number of ``HEAD`` requests: Mainly used to check for
+                     access and existence among which the following operations:
+                     checking bucket access, fetching of metadata.
+``s3-delete``        Number of ``DELETE`` requests: Mainly used for deleting
+                     single objects by the following operations: garbage
+                     collection, content moves.
+``s3-upload``        Amount of bytes uploaded to the S3 endpoint, independent of
+                     request method.
+``s3-download``      Amount of bytes downloaded from the S3 endpoint,
+                     independent of request method.
+==================== ==========================================================
+
diff --git a/docs/storage.rst b/docs/storage.rst
index c24051941..e096d47e6 100644
--- a/docs/storage.rst
+++ b/docs/storage.rst
@@ -593,6 +593,7 @@ Required privileges:
 - ``move-namespace``: ``DATASTORE_MODIFY`` on the parent of both the
   source and the target namespace.
 
+.. _datastore_options:
 
 Options
 ~~~~~~~
@@ -606,6 +607,9 @@ There are a few per-datastore options:
 
 * :ref:`Notification mode and legacy notification settings <notification_mode>`
 * :ref:`Maintenance Mode <maintenance_mode>`
+* :ref:`Maintenance Mode <maintenance_mode>`
+* :ref:`Notification Thresholds (S3 datastores only) <s3_notification_thresholds>`
+* :ref:`Threshold Reset Schedule (S3 datastores only) <s3_notification_thresholds>`
 * Verification of incoming backups
 
 .. _datastore_tuning_options:
-- 
2.47.3

[PATCH proxmox-backup 2/3] docs: mention still missing field in the configuration subtree

[Christian Ebner]

There are several new menu entries, which still are not listed in
the documentation. Add them including a concise description of the
functionality they refer to.

Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
---
 docs/gui.rst | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/docs/gui.rst b/docs/gui.rst
index 7e59ac102..d71f774a3 100644
--- a/docs/gui.rst
+++ b/docs/gui.rst
@@ -93,9 +93,15 @@ WebAuthn, and HTTP proxy configuration. It also contains the following
 subsections:
 
 * **Access Control**: Add and manage users, API tokens, and the permissions
-  associated with these items
-* **Remotes**: Add, edit and remove remotes (see :term:`Remote`)
+  associated with these items.
+* **Remotes**: Add, edit and remove remotes (see :term:`Remote`).
+* **S3 Endpoints**: Add, edit and remove S3 endpoints to be used by datastores.
+* **Traffic Control**: Manage rules for traffic limits on users, networks and
+  timeframes.
 * **Certificates**: Manage ACME accounts and create SSL certificates.
+* **Encryptioin Keys**: Manage encryption keys for tape backups and sync jobs.
+* **Notifications**: Configure notification targets and control when
+  notifications should be send by defining match rules.
 * **Subscription**: Upload a subscription key, view subscription status and
   access a text-based system report.
 
-- 
2.47.3

[PATCH proxmox-backup 3/3] ui: drop 'tech preview' label for s3 stores in creation dialog

[Christian Ebner]

Since S3 backed datastore's are going to be fully supported with
the next release, drop the now outdated label.

Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
---
 www/window/DataStoreEdit.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/www/window/DataStoreEdit.js b/www/window/DataStoreEdit.js
index 1b935ddd3..911bf47d6 100644
--- a/www/window/DataStoreEdit.js
+++ b/www/window/DataStoreEdit.js
@@ -61,7 +61,7 @@ Ext.define('PBS.DataStoreEdit', {
                         comboItems: [
                             ['__default__', gettext('Local')],
                             ['removable', gettext('Removable')],
-                            ['s3', gettext('S3 (tech preview)')],
+                            ['s3', gettext('S3')],
                         ],
                         cbind: {
                             disabled: '{!isCreate}',
-- 
2.47.3

applied: [PATCH proxmox-backup 0/3] followups s3 datastores

[Thomas Lamprecht]

On Fri, 24 Apr 2026 14:50:23 +0200, Christian Ebner wrote:
> These patches are some followups for the s3 datastores, which are
> moving from tech preview to be fully supported. Therefore extend
> on still missing documentation and drop a still present tech preview
> label in the datastore create dialog.
> 
> Christian Ebner (3):
>   docs: describe s3 request notifications and threshold reset schedule
>   docs: mention still missing field in the configuration subtree
>   ui: drop 'tech preview' label for s3 stores in creation dialog
> 
> [...]

Applied, thanks!

[1/3] docs: describe s3 request notifications and threshold reset schedule
      commit: 304f6d19251f8be33ef784386617002e939b7557
[2/3] docs: mention still missing field in the configuration subtree
      commit: dedf4e83fab2f9a9c7a73510124921e93f3c178a
[3/3] ui: drop 'tech preview' label for s3 stores in creation dialog
      commit: ecd8e0dff2b46ddb37ce62702c6f5b8528eedf97