pirgeo
commented
10 months ago I think the issue you are seeing is caused by the fact that the current release of the autoconfigure package always creates an OtlpGrpc exporter: https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/release/v1.30.x/instrumentation/spring/spring-boot-autoconfigure/src/main/java/io/opentelemetry/instrumentation/spring/autoconfigure/exporters/otlp/OtlpLoggerExporterAutoConfiguration.java#L30. It seems like it has been updated since then and should be fixed in the next release (see the code on main for the same class now: https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/instrumentation/spring/spring-boot-autoconfigure/src/main/java/io/opentelemetry/instrumentation/spring/autoconfigure/exporters/otlp/OtlpLoggerExporterAutoConfiguration.java).
In the meantime, what you could do is disable the autoconfigured exporters in your application.properties file:
otel.exporter.otlp.traces.enabled=false
otel.exporter.otlp.metrics.enabled=false
otel.exporter.otlp.logs.enabled=falseand manually create beans for the OtlpHttp exporters:
@SpringBootApplication
public class MyApplication {
@Bean
OtlpHttpSpanExporter spanExporter() {
// configure these with the right endpoint / headers etc. here if you need to, otherwise it will export HTTP/protobuf to localhost:4318/v1/traces
return OtlpHttpSpanExporter.getDefault();
}
@Bean
OtlpHttpMetricExporter metricExporter() {
return OtlpHttpMetricExporter.getDefault();
}
@Bean
OtlpHttpLogRecordExporter logExporter() {
return OtlpHttpLogRecordExporter.getDefault();
}
public static void main(String[] args) {
SpringApplication.run(MyApplication.class, args);
}
}Also, if you want to export logs, make sure to setup logback/log4j as described in https://opentelemetry.io/docs/instrumentation/java/automatic/spring-boot/#logging-instrumentation. This will take all the Spring Boot logs and forward them via OTLP.
Ah, one more thing. I think you don't need to add all of these dependencies, this was enough for me to get the above example working:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>io.opentelemetry</groupId>
<artifactId>opentelemetry-bom</artifactId>
<version>1.33.0</version>
<type>pom</type>
</dependency>
<dependency>
<groupId>io.opentelemetry.instrumentation</groupId>
<artifactId>opentelemetry-instrumentation-bom-alpha</artifactId>
<version>1.32.0-alpha</version>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-test</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-web</artifactId>
</dependency>
<dependency>
<groupId>io.opentelemetry.instrumentation</groupId>
<artifactId>opentelemetry-spring-boot-starter</artifactId>
<version>1.32.0-alpha</version>
</dependency>
</dependencies>The opentelemetry-spring-boot-starter contains everything you need.
jeanbisutti
NicolaeVasile1997
NicolaeV
zeitlinger
Greetings.
I am setting
export OTEL_EXPORTER_OTLP_PROTOCOL="http/protobuf"and also trying to pass-Dotel.exporter.otlp.protocol=http/protobufwhen running my.jarfile. Logs indicate it is still trying to use gRPC (which is unsupported by DynaTrace)I have a Spring Boot 2.7 application. I am following these two docs for implementing opentelemetry: https://opentelemetry.io/docs/instrumentation/java/exporters/#otlp-dependencies https://opentelemetry.io/docs/instrumentation/java/automatic/spring-boot/
I've taken the instruction of the former and excluded the
opentelemetry-exporter-sender-okhttpfromopentelemetry-exporter-otlpand includedopentelemetry-exporter-sender-jdk. Now it is still trying to use gRPC:(Not the full stack trace)
I'll see about producing a minimal project to duplicate the but I wont be able to do it expeditiously.
I expect that setting
OTEL_EXPORTER_OTLP_PROTOCOLtohttp/protobufwould prevent gRPC from being used. I also expected that excluding thesender-okhttpdependency per the docs, and includingsender-jdkwould prevent gRPC from being used.Instead the application insists on using gRPC even and will even throw an exception instead of choosing another protocol
Here is a shortened version of my pom that should have all otel related dependencies included:
Environment Compiler: openjdk 11.0.20.1 2023-08-24 OS: MacOS 13.6
Additional context A similar issue happened here: https://github.com/open-telemetry/opentelemetry-python/issues/2586