use an http OpenTelemetry exporter instead of gRPC

[jimkont]

By default, quarkus is using a gRPC-based endpoint to export spans. Is it possible to configure quarkus to use an HTTP endpoint instead?

[quarkus-bot[bot]]

/cc @alesj (grpc), @brunobat (opentelemetry), @cescoffier (grpc), @radcortez (opentelemetry)

[brunobat]

Hi Dimitris,
We and the OTel community are thinking about making it the default...
For Quarkus 3 we have a new OTel extension and it should be usable on the next CR1 version.
We are not providing oficial support for HTTP, yet but it will contain the implementation you need... If you could help to test drive it it will be great.

[brunobat]

If the issue is with the lambda extension you should create a specific discussion or bug, if you think it's not behaving as expected.

[jimkont]

Hi @brunobat , quarkus 3.0.3 fixes all the issues I was experiencing and I wanted to try it out now if possible.
The configuration you mentioned above (quarkus.otel.traces.exporter=http) does not work now, is there another way I test the http exporter?

[brunobat]

Do you have any error?

[jimkont]

I get

 ERROR [io.qua.run.Application] (Quarkus Main Thread) Failed to start application (with profile [dev]): io.opentelemetry.sdk.autoconfigure.spi.ConfigurationException: Unrecognized value for otel.traces.exporter: http
        at io.opentelemetry.sdk.autoconfigure.SpanExporterConfiguration.configureExporter(SpanExporterConfiguration.java:102)
        at io.opentelemetry.sdk.autoconfigure.SpanExporterConfiguration.configureSpanExporters(SpanExporterConfiguration.java:66)
...

with this configuration

quarkus:
  otel:
    traces:
      exporter: "http"
      enabled: true
    resource:
      attributes: "service.name=${OTEL_SERVICE_NAME}"
    exporter:
      otlp:
        traces:
          endpoint: ${OTEL_EXPORTER_OTLP_ENDPOINT}

[brunobat]

Will have to look into it...