-
Notifications
You must be signed in to change notification settings - Fork 34
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
Netty Prometheus Integration #674
Comments
When using
Is prometheus integration in a known good state and I'm doing something wrong? Is there updated documentation on how to use it? I'm dependening on the following targets:
|
It looks a binary incompatibility. Could you please share the output of the sbt I've got this project with a sample server/client using prometheus |
I'm using bazel (not sbt) so that very likely could be the issue.. Thanks for the pointer to the example; I'll take a look tomorrow. |
Looks like I was transitively depending on an incompatible version of grpc_netty_shaded via firebase_admin:
I've now pinned I'm still experiencing the default
netty
Not sure where to go from here, I've made a small IOApp which serves a single service with a single proto endpoint. I've copied the imports from the example app you gave to make sure I wasn't missing anything, and otherwise I have just 3 dependencies beyond my proto definition:
Do I need additional dependencies to support the http requests to /metrics? It doesn't look like example project has any additional dependencies I'm missing that the server is using save slf4j and maybe fs2. But I've attempted adding those as well for a sanity check and they have no impact. I've also enabled the paradise macro compiler plugin, but unsurprisingly that didn't fix it either. Not sure what else to try. |
@TannerYoung yeah, you need to provide that HTTP endpoint. We've got an article that describes all the process: https://www.47deg.com/blog/metrics-integration-with-mu/#checking-metrics-through-prometheus-server-11 Basically, you need to start a server that uses the |
Thanks - got it working. I think this should be an update documentation, because outside of that blog post I haven't seen anything on exporting the metrics. Even something along the lines of "An additional http server integration is required to export the metrics" would have tipped me off. Maybe I just didn't see the right places though. Feel free to close now. Thanks a ton for all the help. |
Glad it worked. I've created an issue #677 |
Following the Metrics Reporting Guide the server sets up a metric reporter using
GrpcServer.default
. When I attempt to useGrpcServer.netty
I get the following error when pointing prometheus at the service:Is it possible to use this metric reporter with the netty server version?
Hopefully relevant code bits:
The text was updated successfully, but these errors were encountered: