-
Notifications
You must be signed in to change notification settings - Fork 39
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
Micrometer configuration lifecycle violation #224
Comments
I'll look into it |
I read the logs in the comment posted by @sanyarnd in micrometer-metrics/micrometer#4920 The warning is logged when the Vert.x Metrics instance is created. No meter is registered by Vert.x at this stage. Users must either:
Feel free to reach out if more info is needed |
@tsegismont Is there a way to guide the users towards how to register heir own |
@jonatan-ivanov I don't believe we should document how to register their own meters, the Micrometer doc is does it well. But thanks for mentioning docs, I think it would be nice to have a note that explains that Vert.x can register meter filters and, for this reason, they can see Micrometer's warning in the logs. |
See #224 Signed-off-by: Thomas Segismont <tsegismont@gmail.com>
See #224 Signed-off-by: Thomas Segismont <tsegismont@gmail.com>
Closed by caca2d7 |
Micrometer's
MeterRegistry
should be "configured" (seeMeterRegistry.Config
) before registeringMeter
instances to it. For exampleMeterFilter
s should be configured before aMeter
has been registered to the registry.Historically, Micrometer has allowed configuring
MeterFilter
s after meters have been registered but due to certain performance optimizations with micrometer-metrics/micrometer#4917 we took a step toward warning users about this situation.See:
It seems in certain cases Vert.x configures a
MeterFilter
after aMeter
has been registered to the registry causing the warning mentioned above. See micrometer-metrics/micrometer#4920 (comment) by @sanyarnd with a reproducer.@sanyarnd could you please provide the Vert.x version you are using and any additional details you have?
The text was updated successfully, but these errors were encountered: