-
Notifications
You must be signed in to change notification settings - Fork 40.7k
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
Spring Boot 3 does not provide a configuration property for configuring red metrics custom tag keys #34194
Comments
We can't proceed with this until we've got some input from the Wavefront team. |
We (Wavefront team) recommend a new property be added to While the above property name is different from the Spring Boot 2 property ( This would be wired into the |
Thanks, @oppegard. Given that this was supported with Spring Boot 2 and the separate starter (albeit with a different property name), I think we should consider it to be a bug of omission in Spring Boot 3.0. |
@wilkinsona that makes sense to me too. Thank you. |
In
WavefrontTracingAutoConfiguration
, it defines aWavefrontSpanHandler
bean.This passes an empty collection to the
redMetricsCustomTagKeys
in the constructor.spring-boot/spring-boot-project/spring-boot-actuator-autoconfigure/src/main/java/org/springframework/boot/actuate/autoconfigure/tracing/wavefront/WavefrontTracingAutoConfiguration.java
Lines 62 to 69 in 0e67fbc
Per this documentation in Wavefront, the
redMetricsCustomTagKeys
should be populated by thewavefront.tracing.red-metrics-custom-tag-keys
property.I believe this bean definition is the corresponding part for the property.
So, what the doc mentioned to work, I think populated values need to be passed to
redMetricsCustomTagKeys
rather than an empty set.The text was updated successfully, but these errors were encountered: