Server fails to start when Zipkin or Jaeger OpenTelemetry is enabled

[IllangasingheIMDP]

Description

When attempting to configure OpenTelemetry tracing in WSO2 API Manager 4.7.0 using either the zipkin or jaeger exporter types, the API Gateway component (APIHandlerServiceComponent) fails to activate during server startup.

• Zipkin: Fails with java.lang.NoClassDefFoundError : zipkin2/reporter/BytesMessageSender.

• Jaeger: Fails with java.lang.NoSuchMethodError: 'void io.opentelemetry.exporter.internal.grpc.GrpcExporterBuilder.(...)'.

Steps to Reproduce

For Zipkin

1. docker run -d -p 9411:9411 openzipkin/zipkin
2. Add below to deployement.toml

[apim.open_telemetry]
remote_tracer.enable = true
remote_tracer.name = "zipkin"
remote_tracer.hostname = "localhost"
remote_tracer.port = 9411

[[apim.open_telemetry.resource_attributes]]
name = "service.name"
value = "WSO2-APIM-Test"

[[apim.open_telemetry.resource_attributes]]
name = "deployment.environment"

For Jaegar

1. docker run -d --name jaeger -p 16686:16686 -p 14250:14250 jaegertracing/all-in-one:latest
2. Add below to deployement.toml

[apim.open_telemetry]
remote_tracer.enable = true
remote_tracer.name = "jaeger"
remote_tracer.hostname = "localhost"
remote_tracer.port = 14250

[[apim.open_telemetry.resource_attributes]]
name = "service.name"
value = "WSO2-APIM-Test"

[[apim.open_telemetry.resource_attributes]]
name = "deployment.environment"
value = "Development"
value = "Development"

Version

WSO2 API Manager 4.7.0-m2

Environment Details (with versions)

No response