-
Notifications
You must be signed in to change notification settings - Fork 831
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
gRPC metrics not exposed to prometheus #302
Comments
Does this issue mean that if one uses a GRPC mode for the model then metrics will not be collected by prometheus? |
Sorry missed this. Yes at present micrometer doesn't support grpc our of the box. |
thanks! so if you say it does not support grpc out of the box, is there an existing workaround? |
@cliveseldon Is there any workaround exist for this or will we have to wait until micrometer issue is fixed? |
Well, yes I suppose a workaround is to create our own but was hoping we could continue to use micrometer. Not sure of the short term fixes that could help. |
Also, eventually we want to replace the Java engine with GoLang so then hopefully there is a grpc metrics library in GoLang for this. |
Also, we should allow metrics directly from each model. So I think this also is the best solution going forward. So out python wrappers could expose a /metrics endpoint. |
Any movement on this issue? |
This should be fixed in recent PR #1507 about exposing metrics directly on Python wrapper. |
Please, reopen if issue is not fixed on master. |
Yes - gRPC and REST metrics will be exposed in 1.1 via the new GoLang executor: |
Thanks all! |
Might need to include inspired by linked project in the issue on micrometer
The text was updated successfully, but these errors were encountered: