Sync documentation of main branch

Author: actions-user

_data/versioned/main/index/quarkus.yaml

@@ -193,6 +193,22 @@ types:
     id: telemetry-micrometer
     type: reference
     url: /guides/telemetry-micrometer
+  - title: Micrometer and OpenTelemetry extension
+    filename: telemetry-micrometer-to-opentelemetry.adoc
+    summary: Guide to send Micrometer data to OpenTelemetry.
+    categories: observability
+    topics:
+    - observability
+    - opentelemetry
+    - metrics
+    - micrometer
+    - tracing
+    - logs
+    extensions:
+    - io.quarkus:quarkus-micrometer-opentelemetry
+    id: telemetry-micrometer-opentelemetry
+    type: reference
+    url: /guides/telemetry-micrometer-to-opentelemetry
   - title: Native Reference Guide
     filename: native-reference.adoc
     summary: "This guide is a companion to the Building a Native Executable, Using SSL With Native Images, and Writing Native Applications, guides."

_data/versioned/main/index/relations.yaml

@@ -1740,6 +1740,10 @@
     url: /guides/management-interface-reference
     type: reference
     matches: 1
+  - title: Micrometer and OpenTelemetry extension
+    url: /guides/telemetry-micrometer-to-opentelemetry
+    type: reference
+    matches: 1
   - title: Micrometer Metrics
     url: /guides/telemetry-micrometer
     type: reference
@@ -8141,6 +8145,10 @@
     url: /guides/management-interface-reference
     type: reference
     matches: 1
+  - title: Micrometer and OpenTelemetry extension
+    url: /guides/telemetry-micrometer-to-opentelemetry
+    type: reference
+    matches: 1
   - title: Micrometer Metrics
     url: /guides/telemetry-micrometer
     type: reference
@@ -9702,6 +9710,10 @@
     url: /guides/management-interface-reference
     type: reference
     matches: 1
+  - title: Micrometer and OpenTelemetry extension
+    url: /guides/telemetry-micrometer-to-opentelemetry
+    type: reference
+    matches: 1
   - title: Micrometer Metrics
     url: /guides/telemetry-micrometer
     type: reference
@@ -9896,6 +9908,10 @@
     url: /guides/logging
     type: reference
     matches: 1
+  - title: Micrometer and OpenTelemetry extension
+    url: /guides/telemetry-micrometer-to-opentelemetry
+    type: reference
+    matches: 1
   - title: Micrometer Metrics
     url: /guides/telemetry-micrometer
     type: reference
@@ -10705,6 +10721,10 @@
     url: /guides/management-interface-reference
     type: reference
     matches: 1
+  - title: Micrometer and OpenTelemetry extension
+    url: /guides/telemetry-micrometer-to-opentelemetry
+    type: reference
+    matches: 1
   - title: Micrometer Metrics
     url: /guides/telemetry-micrometer
     type: reference
@@ -10797,6 +10817,10 @@
     matches: 1
 /guides/opentelemetry:
   sameTopics:
+  - title: Micrometer and OpenTelemetry extension
+    url: /guides/telemetry-micrometer-to-opentelemetry
+    type: reference
+    matches: 2
   - title: Migrate from OpenTracing to OpenTelemetry tracing
     url: /guides/telemetry-opentracing-to-otel-tutorial
     type: tutorial
@@ -10876,6 +10900,10 @@
     url: /guides/logging
     type: reference
     matches: 2
+  - title: Micrometer and OpenTelemetry extension
+    url: /guides/telemetry-micrometer-to-opentelemetry
+    type: reference
+    matches: 2
   - title: Migrate from OpenTracing to OpenTelemetry tracing
     url: /guides/telemetry-opentracing-to-otel-tutorial
     type: tutorial
@@ -10939,6 +10967,10 @@
     matches: 1
 /guides/opentelemetry-metrics:
   sameTopics:
+  - title: Micrometer and OpenTelemetry extension
+    url: /guides/telemetry-micrometer-to-opentelemetry
+    type: reference
+    matches: 3
   - title: Migrate from OpenTracing to OpenTelemetry tracing
     url: /guides/telemetry-opentracing-to-otel-tutorial
     type: tutorial
@@ -11010,6 +11042,10 @@
     matches: 1
 /guides/opentelemetry-tracing:
   sameTopics:
+  - title: Micrometer and OpenTelemetry extension
+    url: /guides/telemetry-micrometer-to-opentelemetry
+    type: reference
+    matches: 3
   - title: Migrate from OpenTracing to OpenTelemetry tracing
     url: /guides/telemetry-opentracing-to-otel-tutorial
     type: tutorial
@@ -19183,6 +19219,10 @@
     url: /guides/management-interface-reference
     type: reference
     matches: 1
+  - title: Micrometer and OpenTelemetry extension
+    url: /guides/telemetry-micrometer-to-opentelemetry
+    type: reference
+    matches: 1
   - title: Micrometer Metrics
     url: /guides/telemetry-micrometer
     type: reference
@@ -19221,6 +19261,10 @@
     matches: 1
 /guides/smallrye-metrics:
   sameTopics:
+  - title: Micrometer and OpenTelemetry extension
+    url: /guides/telemetry-micrometer-to-opentelemetry
+    type: reference
+    matches: 2
   - title: Using OpenTelemetry Metrics
     url: /guides/opentelemetry-metrics
     type: guide
@@ -20340,6 +20384,10 @@
     url: /guides/telemetry-micrometer-tutorial
     type: tutorial
     matches: 2
+  - title: Micrometer and OpenTelemetry extension
+    url: /guides/telemetry-micrometer-to-opentelemetry
+    type: reference
+    matches: 2
   - title: "Centralized log management (Graylog, Logstash, Fluentd)"
     url: /guides/centralized-log-management
     type: guide
@@ -20393,8 +20441,70 @@
     url: /guides/telemetry-micrometer-tutorial
     type: tutorial
     matches: 1
+/guides/telemetry-micrometer-to-opentelemetry:
+  sameTopics:
+  - title: Migrate from OpenTracing to OpenTelemetry tracing
+    url: /guides/telemetry-opentracing-to-otel-tutorial
+    type: tutorial
+    matches: 3
+  - title: Using OpenTelemetry Metrics
+    url: /guides/opentelemetry-metrics
+    type: guide
+    matches: 3
+  - title: Using OpenTelemetry Tracing
+    url: /guides/opentelemetry-tracing
+    type: guide
+    matches: 3
+  - title: Collect metrics using Micrometer
+    url: /guides/telemetry-micrometer-tutorial
+    type: tutorial
+    matches: 2
+  - title: Micrometer Metrics
+    url: /guides/telemetry-micrometer
+    type: reference
+    matches: 2
+  - title: SmallRye Metrics
+    url: /guides/smallrye-metrics
+    type: guide
+    matches: 2
+  - title: Using OpenTelemetry
+    url: /guides/opentelemetry
+    type: reference
+    matches: 2
+  - title: Using OpenTelemetry Logging
+    url: /guides/opentelemetry-logging
+    type: guide
+    matches: 2
+  - title: "Centralized log management (Graylog, Logstash, Fluentd)"
+    url: /guides/centralized-log-management
+    type: guide
+    matches: 1
+  - title: Logging configuration
+    url: /guides/logging
+    type: reference
+    matches: 1
+  - title: Management interface reference
+    url: /guides/management-interface-reference
+    type: reference
+    matches: 1
+  - title: Observability Dev Services
+    url: /guides/observability-devservices
+    type: guide
+    matches: 1
+  - title: SmallRye Health
+    url: /guides/smallrye-health
+    type: guide
+    matches: 1
+  - title: Using Java Flight Recorder
+    url: /guides/jfr
+    type: guide
+    matches: 1
 /guides/telemetry-micrometer-tutorial:
   sameTopics:
+  - title: Micrometer and OpenTelemetry extension
+    url: /guides/telemetry-micrometer-to-opentelemetry
+    type: reference
+    matches: 2
   - title: Micrometer Metrics
     url: /guides/telemetry-micrometer
     type: reference
@@ -20454,6 +20564,10 @@
     matches: 1
 /guides/telemetry-opentracing-to-otel-tutorial:
   sameTopics:
+  - title: Micrometer and OpenTelemetry extension
+    url: /guides/telemetry-micrometer-to-opentelemetry
+    type: reference
+    matches: 3
   - title: Using OpenTelemetry Tracing
     url: /guides/opentelemetry-tracing
     type: guide

_generated-doc/main/config/quarkus-all-config.adoc

@@ -69536,6 +69536,34 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`false`
 
+a| [[quarkus-oidc_quarkus-oidc-authentication-fail-on-unresolved-kid]] [.property-path]##link:#quarkus-oidc_quarkus-oidc-authentication-fail-on-unresolved-kid[`quarkus.oidc.authentication.fail-on-unresolved-kid`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.oidc.authentication.fail-on-unresolved-kid+++[]
+endif::add-copy-button-to-config-props[]
+
+
+`quarkus.oidc."tenant".authentication.fail-on-unresolved-kid`
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.oidc."tenant".authentication.fail-on-unresolved-kid+++[]
+endif::add-copy-button-to-config-props[]
+
+[.description]
+--
+Fail with the HTTP 401 error if the ID token signature can not be verified during the re-authentication only due to an unresolved token key identifier (`kid`).
+
+This property might need to be disabled when multiple tab authentications are allowed, with one of the tabs keeping an expired ID token with its `kid` unresolved due to the verification key set refreshed due to another tab initiating an authorization code flow. In such cases, instead of failing with the HTTP 401 error, redirecting the user to re-authenticate with the HTTP 302 status may provide better user experience.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_OIDC_AUTHENTICATION_FAIL_ON_UNRESOLVED_KID+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_OIDC_AUTHENTICATION_FAIL_ON_UNRESOLVED_KID+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`true`
+
 a| [[quarkus-oidc_quarkus-oidc-authentication-user-info-required]] [.property-path]##link:#quarkus-oidc_quarkus-oidc-authentication-user-info-required[`quarkus.oidc.authentication.user-info-required`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.oidc.authentication.user-info-required+++[]
@@ -77802,6 +77830,27 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |
 
+a| [[quarkus-redis-cache_quarkus-cache-redis-invalidation-scan-size]] [.property-path]##link:#quarkus-redis-cache_quarkus-cache-redis-invalidation-scan-size[`quarkus.cache.redis.invalidation-scan-size`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.cache.redis.invalidation-scan-size+++[]
+endif::add-copy-button-to-config-props[]
+
+
+[.description]
+--
+If set, the `SCAN` command (used to implement invalidation) will have the `COUNT` argument with given value. If not set (default), no `COUNT` argument is present.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_CACHE_REDIS_INVALIDATION_SCAN_SIZE+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_CACHE_REDIS_INVALIDATION_SCAN_SIZE+++`
+endif::add-copy-button-to-env-var[]
+--
+|int
+|
+
 h|[[quarkus-redis-cache_section_quarkus-cache-redis]] [.section-name.section-level0]##link:#quarkus-redis-cache_section_quarkus-cache-redis[Additional configuration applied to a specific Redis cache (highest precedence)]##
 h|Type
 h|Default
@@ -77932,6 +77981,27 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |
 
+a| [[quarkus-redis-cache_quarkus-cache-redis-cache-name-invalidation-scan-size]] [.property-path]##link:#quarkus-redis-cache_quarkus-cache-redis-cache-name-invalidation-scan-size[`quarkus.cache.redis."cache-name".invalidation-scan-size`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.cache.redis."cache-name".invalidation-scan-size+++[]
+endif::add-copy-button-to-config-props[]
+
+
+[.description]
+--
+If set, the `SCAN` command (used to implement invalidation) will have the `COUNT` argument with given value. If not set (default), no `COUNT` argument is present.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_CACHE_REDIS__CACHE_NAME__INVALIDATION_SCAN_SIZE+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_CACHE_REDIS__CACHE_NAME__INVALIDATION_SCAN_SIZE+++`
+endif::add-copy-button-to-env-var[]
+--
+|int
+|
+
 
 
 h|[.extension-name]##Redis Client##
@@ -94209,7 +94279,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Virtual thread name prefix. The name of the virtual thread will be the prefix followed by a unique number. The default value is "quarkus-virtual-thread-".
+Virtual thread name prefix. The name of the virtual thread will be the prefix followed by a unique number.
 
 
 ifdef::add-copy-button-to-env-var[]

_generated-doc/main/config/quarkus-oidc.adoc

@@ -3409,6 +3409,34 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`false`
 
+a| [[quarkus-oidc_quarkus-oidc-authentication-fail-on-unresolved-kid]] [.property-path]##link:#quarkus-oidc_quarkus-oidc-authentication-fail-on-unresolved-kid[`quarkus.oidc.authentication.fail-on-unresolved-kid`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.oidc.authentication.fail-on-unresolved-kid+++[]
+endif::add-copy-button-to-config-props[]
+
+
+`quarkus.oidc."tenant".authentication.fail-on-unresolved-kid`
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.oidc."tenant".authentication.fail-on-unresolved-kid+++[]
+endif::add-copy-button-to-config-props[]
+
+[.description]
+--
+Fail with the HTTP 401 error if the ID token signature can not be verified during the re-authentication only due to an unresolved token key identifier (`kid`).
+
+This property might need to be disabled when multiple tab authentications are allowed, with one of the tabs keeping an expired ID token with its `kid` unresolved due to the verification key set refreshed due to another tab initiating an authorization code flow. In such cases, instead of failing with the HTTP 401 error, redirecting the user to re-authenticate with the HTTP 302 status may provide better user experience.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_OIDC_AUTHENTICATION_FAIL_ON_UNRESOLVED_KID+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_OIDC_AUTHENTICATION_FAIL_ON_UNRESOLVED_KID+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`true`
+
 a| [[quarkus-oidc_quarkus-oidc-authentication-user-info-required]] [.property-path]##link:#quarkus-oidc_quarkus-oidc-authentication-user-info-required[`quarkus.oidc.authentication.user-info-required`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.oidc.authentication.user-info-required+++[]