Hi pulsar community, 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.
For more detail, please read PIP-235 issue page [1] It's my first PIP, I'm looking forward to hearing what you think and open for any suggestions. [1]: https://github.com/apache/pulsar/issues/19112 [https://opengraph.githubassets.com/abebee001c4e8297f9418e3b78bd77a854f26d1c4b73bfea5fb203251968a18e/apache/pulsar/issues/19112]<https://github.com/apache/pulsar/issues/19112> PIP-235: Add metric for subscription back size · Issue #19112 · apache/pulsar<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 cor... github.com Yike Xiao
