-
Notifications
You must be signed in to change notification settings - Fork 83
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
Expose collecting metrics as separate functionality #19
Comments
Hey @vhatsura, It would definitely be possible but it would require a bit of work on my part. Currently, the event consumption code is tightly coupled to some of the concepts of prometheus (histograms, labels + pull-based metrics to name a few). I'll have a think about how best to split this out. |
It's nice hear. If you need some help I will be appreciated to help you with such stuff. |
Thanks for the offer but I can't make any guarantees about when this work might even begin, let alone be completed. To do this right will take time. |
+1 to this, we are using graphite for metrics and couldn't find any implementation of those collectors other than in this repo. Would be nice if the collectors were reusable somehow. |
I don't know if this helps you but as of V4, event collection and metrics production has now been separated- might be of use to you if I published the event collection as a separate library. |
Hey, @djluck. First of all, a huge thanks to your effort to make such great library. This is what was missing in dotnet community.
My question is quite simple: do you have plans to expose metrics collector functionality as a separate package? It will allow integrate such functionality with various profiling, metrics and performance monitoring tools.
I will glad to hear your thoughts about it.
The text was updated successfully, but these errors were encountered: