Sync documentation of main branch

actions-user · actions-user · commit 168cc2a33074 · 2025-06-19T02:02:15.000Z
diff --git a/_generated-doc/main/config/quarkus-all-config.adoc b/_generated-doc/main/config/quarkus-all-config.adoc
@@ -35139,7 +35139,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The topic-partition pairs to create in the Dev Services Kafka broker. After the broker is started, given topics with partitions are created, skipping already existing topics. For example, `quarkus.kafka.devservices.topic-partitions.test=2` will create a topic named `test` with 2 partitions.
+The topic-partition pairs to create in the Dev Services Kafka broker. After the broker is started, given topics with partitions are created, skipping already existing topics. For example, `quarkus.kafka.devservices.topic-partitions.my-topic=2` will create a topic named `test` with 2 partitions.
 
 The topic creation will not try to re-partition existing topics with different number of partitions.
 
@@ -96604,7 +96604,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The maximum size of a frame in bytes. The default values is `io.vertx.core.http.HttpClientOptions++#++DEFAULT_MAX_WEBSOCKET_FRAME_SIZEX`.
+The maximum size of a frame in bytes. The default values is `io.vertx.core.http.HttpClientOptions++#++DEFAULT_MAX_WEBSOCKET_FRAME_SIZE`.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -96661,6 +96661,27 @@ endif::add-copy-button-to-env-var[]
 |link:https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/time/Duration.html[Duration] link:#duration-note-anchor-all-config[icon:question-circle[title=More information about the Duration format]]
 |
 
+a| [[quarkus-websockets-next_quarkus-websockets-next-client-connection-closing-timeout]] [.property-path]##link:#quarkus-websockets-next_quarkus-websockets-next-client-connection-closing-timeout[`quarkus.websockets-next.client.connection-closing-timeout`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.websockets-next.client.connection-closing-timeout+++[]
+endif::add-copy-button-to-config-props[]
+
+
+[.description]
+--
+The amount of time a client will wait until it closes the TCP connection after sending a close frame. Any value will be `Duration++#++toSeconds() converted to seconds` and limited to `Integer++#++MAX_VALUE`. The default value is `io.vertx.core.http.HttpClientOptions++#++DEFAULT_WEBSOCKET_CLOSING_TIMEOUT`s
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_WEBSOCKETS_NEXT_CLIENT_CONNECTION_CLOSING_TIMEOUT+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_WEBSOCKETS_NEXT_CLIENT_CONNECTION_CLOSING_TIMEOUT+++`
+endif::add-copy-button-to-env-var[]
+--
+|link:https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/time/Duration.html[Duration] link:#duration-note-anchor-all-config[icon:question-circle[title=More information about the Duration format]]
+|
+
 a| [[quarkus-websockets-next_quarkus-websockets-next-client-unhandled-failure-strategy]] [.property-path]##link:#quarkus-websockets-next_quarkus-websockets-next-client-unhandled-failure-strategy[`quarkus.websockets-next.client.unhandled-failure-strategy`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.websockets-next.client.unhandled-failure-strategy+++[]
diff --git a/_generated-doc/main/config/quarkus-kafka-client.adoc b/_generated-doc/main/config/quarkus-kafka-client.adoc
@@ -232,7 +232,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The topic-partition pairs to create in the Dev Services Kafka broker. After the broker is started, given topics with partitions are created, skipping already existing topics. For example, `quarkus.kafka.devservices.topic-partitions.test=2` will create a topic named `test` with 2 partitions.
+The topic-partition pairs to create in the Dev Services Kafka broker. After the broker is started, given topics with partitions are created, skipping already existing topics. For example, `quarkus.kafka.devservices.topic-partitions.my-topic=2` will create a topic named `test` with 2 partitions.
 
 The topic creation will not try to re-partition existing topics with different number of partitions.
 
diff --git a/_generated-doc/main/config/quarkus-kafka-client_quarkus.kafka.adoc b/_generated-doc/main/config/quarkus-kafka-client_quarkus.kafka.adoc
@@ -232,7 +232,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The topic-partition pairs to create in the Dev Services Kafka broker. After the broker is started, given topics with partitions are created, skipping already existing topics. For example, `quarkus.kafka.devservices.topic-partitions.test=2` will create a topic named `test` with 2 partitions.
+The topic-partition pairs to create in the Dev Services Kafka broker. After the broker is started, given topics with partitions are created, skipping already existing topics. For example, `quarkus.kafka.devservices.topic-partitions.my-topic=2` will create a topic named `test` with 2 partitions.
 
 The topic creation will not try to re-partition existing topics with different number of partitions.
 
diff --git a/_generated-doc/main/config/quarkus-kafka-client_quarkus.kafka.devservices.adoc b/_generated-doc/main/config/quarkus-kafka-client_quarkus.kafka.devservices.adoc
@@ -161,7 +161,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The topic-partition pairs to create in the Dev Services Kafka broker. After the broker is started, given topics with partitions are created, skipping already existing topics. For example, `quarkus.kafka.devservices.topic-partitions.test=2` will create a topic named `test` with 2 partitions.
+The topic-partition pairs to create in the Dev Services Kafka broker. After the broker is started, given topics with partitions are created, skipping already existing topics. For example, `quarkus.kafka.devservices.topic-partitions.my-topic=2` will create a topic named `test` with 2 partitions.
 
 The topic creation will not try to re-partition existing topics with different number of partitions.
 
diff --git a/_generated-doc/main/config/quarkus-websockets-next.adoc b/_generated-doc/main/config/quarkus-websockets-next.adoc
@@ -422,7 +422,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The maximum size of a frame in bytes. The default values is `io.vertx.core.http.HttpClientOptions++#++DEFAULT_MAX_WEBSOCKET_FRAME_SIZEX`.
+The maximum size of a frame in bytes. The default values is `io.vertx.core.http.HttpClientOptions++#++DEFAULT_MAX_WEBSOCKET_FRAME_SIZE`.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -479,6 +479,27 @@ endif::add-copy-button-to-env-var[]
 |link:https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/time/Duration.html[Duration] link:#duration-note-anchor-quarkus-websockets-next_quarkus-websockets-next[icon:question-circle[title=More information about the Duration format]]
 |
 
+a| [[quarkus-websockets-next_quarkus-websockets-next-client-connection-closing-timeout]] [.property-path]##link:#quarkus-websockets-next_quarkus-websockets-next-client-connection-closing-timeout[`quarkus.websockets-next.client.connection-closing-timeout`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.websockets-next.client.connection-closing-timeout+++[]
+endif::add-copy-button-to-config-props[]
+
+
+[.description]
+--
+The amount of time a client will wait until it closes the TCP connection after sending a close frame. Any value will be `Duration++#++toSeconds() converted to seconds` and limited to `Integer++#++MAX_VALUE`. The default value is `io.vertx.core.http.HttpClientOptions++#++DEFAULT_WEBSOCKET_CLOSING_TIMEOUT`s
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_WEBSOCKETS_NEXT_CLIENT_CONNECTION_CLOSING_TIMEOUT+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_WEBSOCKETS_NEXT_CLIENT_CONNECTION_CLOSING_TIMEOUT+++`
+endif::add-copy-button-to-env-var[]
+--
+|link:https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/time/Duration.html[Duration] link:#duration-note-anchor-quarkus-websockets-next_quarkus-websockets-next[icon:question-circle[title=More information about the Duration format]]
+|
+
 a| [[quarkus-websockets-next_quarkus-websockets-next-client-unhandled-failure-strategy]] [.property-path]##link:#quarkus-websockets-next_quarkus-websockets-next-client-unhandled-failure-strategy[`quarkus.websockets-next.client.unhandled-failure-strategy`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.websockets-next.client.unhandled-failure-strategy+++[]
diff --git a/_generated-doc/main/config/quarkus-websockets-next_quarkus.websockets-next.adoc b/_generated-doc/main/config/quarkus-websockets-next_quarkus.websockets-next.adoc
@@ -422,7 +422,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The maximum size of a frame in bytes. The default values is `io.vertx.core.http.HttpClientOptions++#++DEFAULT_MAX_WEBSOCKET_FRAME_SIZEX`.
+The maximum size of a frame in bytes. The default values is `io.vertx.core.http.HttpClientOptions++#++DEFAULT_MAX_WEBSOCKET_FRAME_SIZE`.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -479,6 +479,27 @@ endif::add-copy-button-to-env-var[]
 |link:https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/time/Duration.html[Duration] link:#duration-note-anchor-quarkus-websockets-next_quarkus-websockets-next[icon:question-circle[title=More information about the Duration format]]
 |
 
+a| [[quarkus-websockets-next_quarkus-websockets-next-client-connection-closing-timeout]] [.property-path]##link:#quarkus-websockets-next_quarkus-websockets-next-client-connection-closing-timeout[`quarkus.websockets-next.client.connection-closing-timeout`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.websockets-next.client.connection-closing-timeout+++[]
+endif::add-copy-button-to-config-props[]
+
+
+[.description]
+--
+The amount of time a client will wait until it closes the TCP connection after sending a close frame. Any value will be `Duration++#++toSeconds() converted to seconds` and limited to `Integer++#++MAX_VALUE`. The default value is `io.vertx.core.http.HttpClientOptions++#++DEFAULT_WEBSOCKET_CLOSING_TIMEOUT`s
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_WEBSOCKETS_NEXT_CLIENT_CONNECTION_CLOSING_TIMEOUT+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_WEBSOCKETS_NEXT_CLIENT_CONNECTION_CLOSING_TIMEOUT+++`
+endif::add-copy-button-to-env-var[]
+--
+|link:https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/time/Duration.html[Duration] link:#duration-note-anchor-quarkus-websockets-next_quarkus-websockets-next[icon:question-circle[title=More information about the Duration format]]
+|
+
 a| [[quarkus-websockets-next_quarkus-websockets-next-client-unhandled-failure-strategy]] [.property-path]##link:#quarkus-websockets-next_quarkus-websockets-next-client-unhandled-failure-strategy[`quarkus.websockets-next.client.unhandled-failure-strategy`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.websockets-next.client.unhandled-failure-strategy+++[]
diff --git a/_versions/main/guides/databases-dev-services.adoc b/_versions/main/guides/databases-dev-services.adoc
@@ -150,12 +150,14 @@ Dev Services volumes can be mapped to the filesystem or the classpath:
 # Using a filesystem volume:
 quarkus.datasource.devservices.volumes."/path/from"=/container/to <1>
 # Using a classpath volume:
-quarkus.datasource.devservices.volumes."classpath:./file"=/container/to <2>
+quarkus.datasource.devservices.volumes."classpath\:./file"=/container/to <2>
 ----
 
 <1> The file or folder "/path/from" from the local machine will be accessible at "/container/to" in the container.
 <2> When using classpath volumes, the location has to start with "classpath:". The file or folder "./file" from the project's classpath will be accessible at "/container/to" in the container.
 
+CAUTION: The colon character `:` needs to be escaped in `.properties` files as `\:`, or it will be interpreted as a key/value separator.
+
 IMPORTANT: when using a classpath volume, the container will only be granted read permission. On the other hand, when using a filesystem volume, the container will be granted read and write permission.
 
 === Example of mapping volumes to persist the database data
diff --git a/_versions/main/guides/kafka-dev-services.adoc b/_versions/main/guides/kafka-dev-services.adoc
@@ -89,8 +89,14 @@ quarkus.kafka.devservices.image-name=quay.io/strimzi-test-container/test-contain
 
 You can configure the Dev Services for Kafka to create topics once the broker is started.
 Topics are created with given number of partitions and 1 replica.
+The syntax is the following:
 
-The following example creates a topic named `test` with 3 partitions, and a second topic named `messages` with 2 partitions.
+[source, properties]
+----
+quarkus.kafka.devservices.topic-partitions.<topic-name>=<number-of-partitions>
+----
+
+The following example creates a topic named `test` with three partitions, and a second topic named `messages` with two partitions.
 
 [source, properties]
 ----
diff --git a/_versions/main/guides/telemetry-micrometer-to-opentelemetry.adoc b/_versions/main/guides/telemetry-micrometer-to-opentelemetry.adoc
@@ -137,7 +137,7 @@ The JVM and HTTP server metrics are collected by Micrometer.
 Next, are examples of the metrics collected by Micrometer and a comparison of what would be the `quarkus-micrometer-registry-prometheus` output vs the one on this bridge. A link to the equivalent OpenTelemetry Semantic Convention is also provided for reference and is not currently used in the bridge.
 
 |===
-|Micrometer Meter |Quarkus Micrometer Prometheus output | This bridge OpenTelemetry output name | Related OpenTelemetry Semantic Convention (not applied)
+|Micrometer Meter |Quarkus Micrometer Prometheus client v0.x output | This bridge OpenTelemetry output name | Related OpenTelemetry Semantic Convention (not applied)
 
 |Using the @Timed interceptor.
 |
diff --git a/_versions/main/guides/telemetry-micrometer-tutorial.adoc b/_versions/main/guides/telemetry-micrometer-tutorial.adoc
@@ -88,7 +88,7 @@ You should find something like this:
 ----
 # HELP http_server_requests_seconds
 # TYPE http_server_requests_seconds summary
-http_server_requests_seconds_count{method="GET",outcome="SUCCESS",status="200",uri="/example/prime/{number}"} 2.0
+http_server_requests_seconds_count{method="GET",outcome="SUCCESS",status="200",uri="/example/prime/{number}"} 2
 http_server_requests_seconds_sum{method="GET",outcome="SUCCESS",status="200",uri="/example/prime/{number}"} 0.017385896
 # HELP http_server_requests_seconds_max
 # TYPE http_server_requests_seconds_max gauge
diff --git a/_versions/main/guides/telemetry-micrometer.adoc b/_versions/main/guides/telemetry-micrometer.adoc
@@ -24,6 +24,8 @@ IMPORTANT: Micrometer is the recommended approach to metrics for Quarkus.
 NOTE: By default, the metrics are exposed on the main HTTP server.
 If you would like to surface metrics from a separate management port, see the <<management-interface,Managed interface>> section.
 
+NOTE: `quarkus-micrometer` now uses the Prometheus client v1.x. For help migrating from the old client, please check the https://github.com/micrometer-metrics/micrometer/wiki/1.13-Migration-Guide[Prometheus Java client 0.x to 1.x upgrade]  from Micrometer.
+
 == Micrometer and monitoring system extensions
 
 Quarkus Micrometer extensions are structured in the same way as the Micrometer project.
@@ -33,7 +35,7 @@ Other Quarkus and Quarkiverse extensions use the Quarkus Micrometer extension to
 Quarkus extensions:
 
 - micrometer
-- micrometer-registry-prometheus
+- micrometer-registry-prometheus (Prometheus client v1.x)
 
 link:https://github.com/quarkiverse/quarkus-micrometer-registry[Quarkiverse extensions] (may be incomplete):
 
@@ -172,7 +174,7 @@ Micrometer applies naming conventions to convert registered meter names to match
 
 Given the following declaration of a timer: `registry.timer("http.server.requests")`, applied naming conventions will emit the following metrics for different monitoring systems:
 
-- Prometheus: `http_server_requests_duration_seconds`
+- Prometheus: `http_server_requests_seconds`
 - Atlas: `httpServerRequests`
 - Graphite: `http.server.requests`
 - InfluxDB: `http_server_requests`
@@ -569,7 +571,6 @@ public class CustomConfiguration {
                 if(id.getName().startsWith("myservice")) {
                     return DistributionStatisticConfig.builder()
                         .percentiles(0.5, 0.95)     // median and 95th percentile, not aggregable
-                        .percentilesHistogram(true) // histogram buckets (e.g. prometheus histogram_quantile)
                         .build()
                         .merge(config);
                 }

Original file line number	Diff line number	Diff line change
`@@ -137,7 +137,7 @@ The JVM and HTTP server metrics are collected by Micrometer.`
`137`	`137`	Next, are examples of the metrics collected by Micrometer and a comparison of what would be the `quarkus-micrometer-registry-prometheus` output vs the one on this bridge. A link to the equivalent OpenTelemetry Semantic Convention is also provided for reference and is not currently used in the bridge.
`138`	`138`
`139`	`139`	`\|===`
`140`		`-\|Micrometer Meter \|Quarkus Micrometer Prometheus output \| This bridge OpenTelemetry output name \| Related OpenTelemetry Semantic Convention (not applied)`
	`140`	`+\|Micrometer Meter \|Quarkus Micrometer Prometheus client v0.x output \| This bridge OpenTelemetry output name \| Related OpenTelemetry Semantic Convention (not applied)`
`141`	`141`
`142`	`142`	`\|Using the @Timed interceptor.`
`143`	`143`	`\|`