-
Notifications
You must be signed in to change notification settings - Fork 23
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
Unable to handle metrics data larger than grpc default max message size #32
Comments
Ah, cool! That is an interesting twist. I did not realize that prometheus data sources could ingest such large data elements. I know how to deal with large msgs in gRPC. Give me a few days to work on it and I will get back to you. |
I added support for large messages in the 1.6.0 release. Give it a try and see if it fixes your problem. |
I should also mention that the default streaming message size in the 1.6.0 chunking implementation is 32kb, which is based on this thread: grpc/grpc.github.io#371 |
I added support for zipping chunked and non-chunked content in 1.6.1. Give that a try. |
I just updated and it looks very promising. No issues so far and data is coming in as expected. Thanks for a great tool and quick response time! |
I have many docker containers running on a host and the /metrics endpoint exposed from cAdvisor is over 4Mb (default max message size in grpc). I would like to be able to configure the max message size on the proxy. (I'm guessing around here: https://github.com/pambrose/prometheus-proxy/blob/master/src/main/kotlin/io/prometheus/proxy/ProxyGrpcService.kt#L76)
Related issues: grpc/grpc-java#3996
Error on the agent
Stacktrace on the proxy
The text was updated successfully, but these errors were encountered: