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
high cardinality tags in micrometer metrics #2875
Comments
@grzegorz-moto Please specify Reactor Netty version. Also why do you need so many connection pools and do you need all of them operational all the time? |
version 1.0.25
where the only TAG |
@grzegorz-moto Update at least to version Then ensure you have configuration for |
This is interesting because the metrics have |
I have ConnectionProvider and TcpClient configured in the following way:
and in versions I'm using: |
@grzegorz-moto Is the code below necessary to NOT be included into the common configuration?
|
@grzegorz-moto I'm closing this one, we can reopen it when you are able to reply to the comment above. |
The metrics tags contains random id that caus high memory usage and leads to memory leak/exhausting. This is due the fact micrometer treats each new tag as new metric.
The example: https://github.com/reactor/reactor-netty/blob/main/reactor-netty-core/src/main/java/reactor/netty/resources/MicrometerPooledConnectionProviderMeterRegistrar.java#L55
The text was updated successfully, but these errors were encountered: