Shawyeok opened a new issue, #19112: URL: https://github.com/apache/pulsar/issues/19112
### Motivation Now we have `pulsar_storage_backlog_size` for topic backlog size, user can create an alarm rule like `pulsar_storage_backlog_size > THRESHOLD`, typically this alarm is going to notify corresponding subscription owner, but it need extra process to identify subscriptions that backlog size exceed the threshold. So we could add a new metric for subscription back size. #9302 Added subscription backlog size info for topic stats and a configuration `exposeSubscriptionBacklogSizeInPrometheus` (default false) for topic metrics, but the latter was unimplemented. ### Goal New metric `pulsar_subscription_back_log_size` ### API Changes Since `0` is a valid value for subscription backlog size, `change subscriptionStats.backlogSize to -1 from 0` if request the stats of topic with `subscriptionBacklogSize=false`. ### Implementation If and only if `exposeSubscriptionBacklogSizeInPrometheus` is enabled, expose the metric as `pulsar_subscription_back_log_size` ### Alternatives _No response_ ### Anything else? _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
