Merge pull request #64112 from zdover23/wip-doc-2025-06-23-backport-64103-to-tentacle

tentacle: doc/radosgw: improve "pubsub_push_pending" info

Reviewed-by: Anthony D'Atri <anthony.datri@gmail.com>
Reviewed-by: Yuval Lifshitz <ylifshit@ibm.com>

diff --cc doc/radosgw/notifications.rst
index c0781266384144a4e7f54079ecb8cc9629456a5d,e0afd0db1b602496368b6af5c9fd5e3ffa1d1bca..c12aa46ec3f736646774b36c718a0db86257b4e9
--- 1/doc/radosgw/notifications.rst
--- 2/doc/radosgw/notifications.rst
+++ b/doc/radosgw/notifications.rst
@@@ -125,11 -125,14 +125,14 @@@ Dump (in JSON format) all pending bucke
  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
 -- ``pubsub_event_lost``: a running counter of events that had topics associated with them, but that were not pushed to any of the endpoints
  - ``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
+ - ``pubsub_push_pending``: the gauge value of events pushed to an endpoint but
+   not acked or nacked yet. This does not include the notifications waiting in
+   the persistent queue. Only the notifications that are in flight in both
+   persistent and non-persistent cases are counted.
  
  .. note::