Need to create a bean OtlpHttpSpanExporter before opentelemetry spring boot starter.

[DineshkumarVG]

Hi,
I am using oauth authentication for otel collector, The token needs to be changed one hour once. I need to set that dynamically. I have used your setHeader with supplier and it was working as expected. I am trying to implement that using @bean annotation. but springboot auto configuration injects the bean before the bean i have created. Anyone please help on this or is there anything i have missed?

It was working fine with the version 2.1.0-alpha

Sample code for reference.
build.gradle

`dependencyManagement {
imports {
mavenBom("io.opentelemetry:opentelemetry-bom:1.36.0")
mavenBom("io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha:2.2.0-alpha")
}
}

implementation("io.opentelemetry.instrumentation:opentelemetry-spring-boot-starter")`

Bean File

`@AutoConfiguration
@ConditionalOnClass({OpenTelemetry.class})
@AutoConfigureOrder(Ordered.HIGHEST_PRECEDENCE)
public class RefreshToken {

@bean
public OtlpHttpSpanExporter otlpHttpSpanExporter() {
Supplier<Map<String, String>> mapSupplier = () -> {
Map<String, String> map = new HashMap<>();
try {
map.put("Authorization", "Bearer " + refreshToken());
} catch (Exception e) {
throw new RuntimeException(e);
}
return map;
};
return OtlpHttpSpanExporter.builder().setHeaders(mapSupplier)
.setEndpoint("url").build();
}
}`

[jack-berg]

Transferred to opentelemetry-java-instrumentation because this is related to the spring boot starter.

[jack-berg]

cc @jeanbisutti, @zeitlinger

[zeitlinger]

This breaking change is a consequence of #10453 - I didn't call this out as a breaking change, because I simply couldn't image a use case that would break 😞

Anyways, there's a way to get your setup running:

• You have to create a new exporter with a different name, e.g. "otlp-dynamic-header"
• You have to use "otlp-dynamic-header" instead of the default "otlp"
• You have to register a bean that supplies "otlp-dynamic-header" - similar to this integration test

[zeitlinger]

I'm keeping this issue open to document this use case.

[zeitlinger]

Note: it's also possible to use "otlp" as the key - it will replace the already configured otlp exporter

[DineshkumarVG]

@zeitlinger , Thanks for your input. Correct me if my understanding is wrong. GlobalOpenTelemetry will not set the configuration for second time. How can i make it happen?
Could you please provide the any sample code for reference to use otlp as the key?

[zeitlinger]

I've created a draft PR that demonstrates both: open-telemetry/opentelemetry-java-examples#378

Disclaimer: I haven't tested it manually.

[DineshkumarVG]

I will try it from my end the same you have shared as example code... @zeitlinger Thank you..

[DineshkumarVG]

Thank you @zeitlinger ,
I verified from my end and it was working fine. I simply used like the shared code in my Configuration class.

@Bean
ConfigurableSpanExporterProvider otlpSpanExporterProvider() {
        return new OtlpSpanExporterProvider();
}

 @Bean
 OpenTelemetryInjector registerGlobalOpenTelemetry() {
     return GlobalOpenTelemetry::set;
 }

private static class OtlpSpanExporterProvider
            implements ConfigurableSpanExporterProvider {

        @Override
        public String getName() {
            return "otlp";
        }

        @Override
        public SpanExporter createExporter(ConfigProperties config) {
            OtlpHttpSpanExporterBuilder builder = OtlpHttpSpanExporter.builder();
            Supplier<Map<String, String>> mapSupplier = () -> {
                Map<String, String> map = new HashMap<>();
                try {
                    map.put("AUTHORIZATION", "Bearer " + refreshToken());
                } catch (Exception e) {
                    throw new RuntimeException(e);
                }
                return map;
            };
            return builder.setHeaders(mapSupplier).build();
        }
		
		private String refreshToken(){
		return "token"
		}
    }

I removed AutoConfigureListener implementation but it was working fine . Is there any impact by removing AutoConfigureListener?

As per my understanding, we are just injecting the bean with dynamic header.

Could you please explain me more on this and how it work?

Is this changes will be the standard one in future also?

[zeitlinger]

Thank you @zeitlinger , I verified from my end and it was working fine. I didn't set any GlobalOpenTelemetry object. I simply used like the shared code in my Configuration class.

great 🎉

I removed AutoConfigureListener implementation but it was working fine . Is there any impact by removing AutoConfigureListener?

it creates metrics about the span export (i.e. if there were errors)

As per my understanding, we are just injecting the bean with dynamic header.

correct

Could you please explain me more on this and how it work?
Is this changes will be the standard one in future also?

I can't follow - can you make the questions more concrete or add an example?