Add auto-configuration for OpenTelemetry SdkMeterProvider #46640
Conversation
Signed-off-by: Thomas Vitale <[email protected]>
spring-projects-issues
added
the
status: waiting-for-triage
| ObjectProvider<SdkMeterProviderBuilderCustomizer> customizers) { | ||
| SdkMeterProviderBuilder builder = SdkMeterProvider.builder().setClock(clock).setResource(resource); | ||
| if (properties.getExemplars().isEnabled()) { | ||
| SdkMeterProviderUtil.setExemplarFilter(builder, exemplarFilter); |
There was a problem hiding this comment.
Exemplars are disabled by default because even though the Spec/API is GA, the method in the Java SDK to configure them is not exposed publicly, but through this util. Is that acceptable for Spring Boot?
The API (mapped closely by the configuration properties) won't change as it's stable. So, any change to the SDK internals will not require any code/configuration change from Spring Boot users (a.k.a. stable feature). See: https://opentelemetry.io/docs/specs/otel/metrics/sdk/#exemplar (stable API). More context: open-telemetry/opentelemetry-java#7503.
My recommendation would be to keep this functionality, but disabled by default. Considering that the OTLP Meter Registry doesn't support exemplars yet, this would be the only way in Spring Boot to support exemplars in OpenTelemetry.
metricssub-package in thespring-boot-opentelemetrymodule.SdkMeterProviderwith customisation options via configuration properties and customizer bean.Clockbean used to initialise observability signals providers.Fixes gh-36546