-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Monitoring #20
Comments
What do you think @connor4312 ? |
Apologies, been busy. I will look into this more deeply this weekend. |
The circuit breaker now includes a general Levee actually includes a basic statistics store, but I think this is out of scope for the library--there are numerous, differently configurable ways to collect call duration, for instance, which can be handled better by a specific telemetry library. |
Thank you @connor4312 for this improvement 👏. This will enable monitoring what I am looking for, will try it in upcoming week. Great work 💪🏼 |
We would like to start monitor of circuit breakers and retry's and timeouts in production.
I like this library the most from others but I am missing a way how to monitor current state.
I've tried to get at least
breaker.stats
and someonRetry
and other, but would be better to have more holistic way how to get this events and state out of cockatiel.Is there a way how to get this statistics?
i.e. here is some inspiration in Levee project.
Example how such output could one day look.
Article from Hystrix with video.
This image actually aggregates all instances of circuit breaker per concrete service.
I can image taking this information with every request (or batching can be done by another tool).
I am thinking now about this metrics:
The text was updated successfully, but these errors were encountered: