[GitHub] [pulsar] one1zero1one opened a new issue #6891: Expose topic/subscription/consumer number of messages as counter.

[GitBox <gi...@apache.org>]

one1zero1one opened a new issue #6891:
URL: https://github.com/apache/pulsar/issues/6891


   **Is your feature request related to a problem? Please describe.**
   Topic metrics are expressed as computed rates, e.g. gauges: `pulsar_rate_in` `pulsar_rate_out`. This makes Prometheus scraping miss any change of rate in between the scrape interval.  
   
   **Describe the solution you'd like**
   Exposing the metrics as counters instead/in addition to gauges, e.g. `pulsar_count_in`  would allow the rate to be computed in prometheus, and would not miss change of rates within the scraping interval.
   
   **Describe alternatives you've considered**
   Increasing the scrape interval to <15s however it still misses spikes. 
   I have considered using a sidecar container that would create the counters from gauges, but it adds unwanted complexity.
   
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [pulsar] sijie commented on issue #6891: Expose topic/subscription/consumer number of messages as counter.

[GitBox <gi...@apache.org>]

sijie commented on issue #6891:
URL: https://github.com/apache/pulsar/issues/6891#issuecomment-624980933


   @one1zero1one I think @PierreZ already added this feature. We will check if it will be released as part of 2.6.0.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org