Project

General

Profile

Actions

Bug #63396

open

notifications: bucket notification stats are inconsistent

Added by Yuval Lifshitz 6 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
notifications
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

see: https://docs.ceph.com/en/latest/radosgw/notifications/#notification-performance-statistics
  • l_rgw_pubsub_push_failed is incremented only in the case of persistent notifications, while l_rgw_pubsub_push_ok is incremented both in the case of persistent and non-persistent notifications
  • in case of persistent notifications, the failure counter should be incremented in case that the queue if full, and in the case that we give up on rertying a notification
  • the "l_rgw_pubsub_event_lost" and "l_rgw_pubsub_event_triggered" counters are not used anymore, and should be removed (a note must be added to release notes)
  • the "l_rgw_pubsub_push_pending" gauge value is used on in the case of an HTTP endpoint. we should make sure it is used around all "send_to_completion_async()" calls
  • currently these counters are not tested. we should add integration tests for them (at least manual tests in test_bn.py)

No data to display

Actions

Also available in: Atom PDF