Migrate deprecated Jaeger client

[sophokles73]

The Jaeger client used in Hono has been deprecated and will be archived mid 2022 as announced on the project website. The client should be replaced with corresponding OpenTelemetry SDKs as described in the migration guide.

[calohmn]

Regarding the Jaeger support in Hono, I think there are 2 options.
We could use the quarkus-opentelemetry-exporter-jaeger Quarkus extension and thereby support directly sending the traces from the Hono components to the Jaeger collector. This doesn't require the OpenTelemetry Collector.
Or, we could use the quarkus-opentelemetry-exporter-otlp Quarkus extension and require usage of the OpenTelemetry Collector. The OpenTelemetry Collector can then be configured to export to the Jaeger Collector.

I guess the 2nd option, setting up the Hono containers each with an OpenTelemetry Collector sidecar (i.e. using the agent deployment method), would be the preferred deployment setup.
So, I would rather remove the explicit jaeger build option (maven profile) and focus just on the open telemetry support.
@sophokles73 WDYT?

[sophokles73]

guess the 2nd option, setting up the Hono containers each with an OpenTelemetry Collector sidecar (i.e. using the agent deployment method), would be the preferred deployment setup.

This seems to be analogous to how we deploy the Hono components in the Helm chart, right? However, for running the Hono integration tests, this sounds like we would need to start an additional container for the OpenTelemetry Collector, right?

[calohmn]

However, for running the Hono integration tests, this sounds like we would need to start an additional container for the OpenTelemetry Collector, right?

Yes, but I think this is manageable. The quarkus-opentelemetry-exporter-jaeger extension is anyway being phased out of the main Quarkus repo at some point (see quarkusio/quarkus#17771).

[sophokles73]

Ok, then let's go for the quarkus-opentelemetry-exporter-otlp ...

[sophokles73]

@calohmn can this be closed?

[calohmn]

Yes, closing this - implemented via ad0f629.
#3212 and #3213 are follow-up issues.