Migration Guide 3.13

Table of Contents

• Redis Client
  • Fixed parameter ordering in JSON.MGET
• OpenTelemetry
  • OpenTelemetry metrics support
  • Documentation updates
  • Breaking Changes
• Grafana LGTM (all-in-one) Observability Dev Service.

Redis Client

Fixed parameter ordering in JSON.MGET

The JsonCommands.jsonMget() method (and similar methods like ReactiveJsonCommands.jsonMget()) declare parameters in the following order:

• String path

• K... keys

This is opposite to the Redis JSON.MGET command, which accepts keys first and path last.

The implementation of the jsonMget() method used to follow the Redis order, despite its own declaration. That is, the path had to be last, even though it should be first.

This is now fixed. All users of this method have to check and fix the call sites.

OpenTelemetry

Many changes on this release, affecting documentation, Metrics support and breaking changes due to the new semantic conventions for HTTP.

OpenTelemetry metrics support

Added with experimental status, please set quarkus.otel.metrics.enabled=true to enable it at build time.

Now you can create OpenTelemetry Metrics by following the Metrics Guide.

There are no automatic OpenTelemetry metrics instrumentation in Quarkus, for now. Metrics in Quarkus are implemented by the Micrometer extension. We plan to provide, in the future, a bridge for those metrics to be available in OpenTelemetry as well.

Documentation updates

The old OpenTelemetry guide has been split into this generic guide, the OpenTelemetry Tracing Guide and the new OpenTelemetry Metrics Guide has been created.

Breaking Changes

• Upgrade to OpenTelemetry SDK 1.39.0 and OpenTelemetry instrumentation 2.5.0. We haven’t upgraded OpenTelemetry for a while to allow a transition period from the old, deprecated HTTP semantic conventions, as announced in this wiki migration guide for Quarkus 3.9 and the Dev mailing list. The transition period has now ended with the upgrade of the OpenTelemetry SDK to 1.39.0 and OpenTelemetry instrumentation to 2.5.0. These versions require the new semantic conventions for HTTP. The full list of changes.

• quarkus.otel.semconv-stability.opt-in system property was removed because users cannot opt-in anymore;

• DB Span names have changed in the case of table creation;

• Deprecated annotation for io.opentelemetry.extension.annotations.WithSpan has been removed. Please use the new io.opentelemetry.instrumentation.annotations.WithSpan, as previously announced.

Grafana LGTM (all-in-one) Observability Dev Service.

The extension now detects which extensions (Otel, Micrometer OTLP registry) are being used and sets their properties accordingly. Update documentation

• Breaking Change*

The following properties are removed because they are not needed anymore:

• quarkus.otel-collector.url

• quarkus.grafana.url