From 30c84a06e3928cbe334e5d3e4659558c21f82746 Mon Sep 17 00:00:00 2001 From: Zac Dover Date: Mon, 23 Jun 2025 18:07:40 +1000 Subject: [PATCH] doc/radosgw: remove "pubsub_event_triggered" Remove "pubsub_event_triggered" from the list of "Notification Performance Statistics". It is obsolete. Fixes: https://tracker.ceph.com/issues/71789 Signed-off-by: Zac Dover (cherry picked from commit 44dc57fc15749583fc13560c9409b7687df7c223) --- doc/radosgw/notifications.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/radosgw/notifications.rst b/doc/radosgw/notifications.rst index c0781266384..c4c03bd3b47 100644 --- a/doc/radosgw/notifications.rst +++ b/doc/radosgw/notifications.rst @@ -126,16 +126,17 @@ Notification Performance Statistics ----------------------------------- - ``persistent_topic_size``: queue size in bytes. -- ``pubsub_event_triggered``: a running counter of events that have at least one topic associated with them +- ``persistent_topic_len``: shows how many notifications are currently waiting + in the queue - ``pubsub_push_ok``: a running counter, for all notifications, of events successfully pushed to their endpoints - ``pubsub_push_fail``: a running counter, for all notifications, of events that failed to be pushed to their endpoints - ``pubsub_push_pending``: the gauge value of events pushed to an endpoint but not acked or nacked yet .. note:: - ``pubsub_event_triggered`` is incremented per event on each notification, - but ``pubsub_push_ok`` and ``pubsub_push_fail`` are incremented per push - action on each notification. + ``pubsub_event_lost`` is incremented per event on each notification, but + ``pubsub_push_ok`` and ``pubsub_push_fail`` are incremented per push action + on each notification. Bucket Notification REST API ---------------------------- -- 2.39.5