Suggestion to add additional metrics for nats server #6276
Unanswered
YashasAnand
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As per my discussion with @mtmk in https://github.com/nats-io/nats.net/discussions I am suggesting to add these below metrics if possible & would like to know if this is feasible.
In Jetstream, if i have 1 subject & 10 consumers bound to the same subject, Nats server considers this as 1 consumer, but internally does load-balancing amongst all consumer threads. Could we have a metric like NumClientsForConsumer which can give us how many clients are attached to a consumers which can give good visibility in microservice based setups , especially at times when load is high & we want to scale consumers.
In a set-up where jetstream & core-nats are used together, I would like to see some more metrics on the core-nats subscribers like last consumed message on subscriber. Again, in a microservice architecture, it will be difficult to maintain our own caches to get the subscribers last consumed message, if this can be a metric available on server, it can give great visisbility.
Beta Was this translation helpful? Give feedback.
All reactions