-
Notifications
You must be signed in to change notification settings - Fork 626
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
"observationEnabled" defaults to TRUE #1549
Comments
It is false by default by design; adding observation is quite expensive, especially for those who only want metrics (and not tracing). When observation is not enabled, we maintain Micrometer timers outside of observation, avoiding its overhead. We could consider setting it based on an environment property, but we cannot set it to |
Don't we need to expose such an auto-configuration property, @garyrussell , in Spring Boot? |
It could be done there, yes; but, again, I would not want it to default to |
Right, |
Thank you, I understand the design. |
You could open a request against Boot, but I don't know if the Boot team will add new properties in patch releases. |
Expected Behavior
I want the auto-configuration to set the
observationEnabled
parameter ofRabbitTemplate
andAbstractRabbitListenerContainerFactory
to true by default.Current Behavior
Micrometer Tracing does not work out of the box because the default value of their
observationEnabled
are now set tofalse
.Context
Spring Boot 3.0 provides auto-configuration for Micrometer Tracing, and it works out of the box with Spring Web and Spring Cloud Stream, but it doesn't work with Spring AMQP. I found Spring Cloud Stream (binder-rabbitmq) sets it
true
.I think Spring AMQP should also be friendly towards Micrometer Tracing.
The text was updated successfully, but these errors were encountered: