You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2019/12/20 23:08:54 UTC

[GitHub] [pulsar] one70six commented on issue #5854: Prometheus - Add Metrics Around Message Storage

one70six commented on issue #5854: Prometheus - Add Metrics Around Message Storage
URL: https://github.com/apache/pulsar/issues/5854#issuecomment-568120360
 
 
   @jiazhai thanks for the response! I would think:
   
   - pulsar_msg_ttl: Yes, the number of messages that will not be in backlog after a TTL. Or maybe you could calculate a histogram of the avg. TTL for 1m, 5m, 30m, 1h, etc. so that you can visualize how the messages are being affected by TTL.
   
   - pulsar_msg_retention: Yes, this aimed to show the messages in retention. After the TTL expires, the messages should show up here. You could also do a histogram here as well to visualize how the messages are being removed from Pulsar completely.
   
   Thanks!
   

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


With regards,
Apache Git Services