Update micrometer docs (tutorial / reference)

quarkusio · May 24, 2023 · 3820138 · 3820138
1 parent 5a9af15
commit 3820138
Show file tree

Hide file tree

Showing 13 changed files with 772 additions and 691 deletions.
diff --git a/docs/src/main/asciidoc/cache.adoc b/docs/src/main/asciidoc/cache.adoc
@@ -764,7 +764,7 @@ Each cache declared using the <<#annotations-api,annotations caching API>> can b
 [NOTE]
 ====
 The cache metrics collection will only work if your application depends on a `quarkus-micrometer-registry-*` extension.
-See the xref:micrometer.adoc[Micrometer metrics guide] to learn how to use Micrometer in Quarkus.
+See the xref:telemetry-micrometer.adoc[Micrometer metrics guide] to learn how to use Micrometer in Quarkus.
 ====
 
 The cache metrics collection is disabled by default.

diff --git a/docs/src/main/asciidoc/getting-started.adoc b/docs/src/main/asciidoc/getting-started.adoc
@@ -472,7 +472,7 @@ Furthermore, users can supply a custom banner by placing the banner file in `src
 == Non Application endpoints
 
 Various Quarkus extensions contribute non-application endpoints that provide different kinds of information about the application.
-Examples of such extensions are the xref:smallrye-health.adoc[health], xref:micrometer.adoc[metrics], xref:openapi-swaggerui.adoc[OpenAPI] and info extensions.
+Examples of such extensions are the xref:smallrye-health.adoc[health], xref:telemetry-micrometer.adoc[metrics], xref:openapi-swaggerui.adoc[OpenAPI] and info extensions.
 
 These non application endpoints are normally accessible under the `/q` prefix like so:
 

diff --git a/docs/src/main/asciidoc/grpc-service-consumption.adoc b/docs/src/main/asciidoc/grpc-service-consumption.adoc
@@ -372,7 +372,7 @@ The default priority, used if the interceptor does not implement the `Prioritize
 
 === Enabling metrics collection
 
-gRPC client metrics are automatically enabled when the application also uses the xref:micrometer.adoc[`quarkus-micrometer`] extension.
+gRPC client metrics are automatically enabled when the application also uses the xref:telemetry-micrometer.adoc[`quarkus-micrometer`] extension.
 Micrometer collects the metrics of all the gRPC clients used by the application.
 
 As an example, if you export the metrics to Prometheus, you will get:

diff --git a/docs/src/main/asciidoc/grpc-service-implementation.adoc b/docs/src/main/asciidoc/grpc-service-implementation.adoc
@@ -371,7 +371,7 @@ dependencies {
 
 === Enabling metrics collection
 
-gRPC server metrics are automatically enabled when the application also uses the xref:micrometer.adoc[`quarkus-micrometer`] extension.
+gRPC server metrics are automatically enabled when the application also uses the xref:telemetry-micrometer.adoc[`quarkus-micrometer`] extension.
 Micrometer collects the metrics of all the gRPC services implemented by the application.
 
 As an example, if you export the metrics to Prometheus, you will get:

diff --git a/docs/src/main/asciidoc/hibernate-orm.adoc b/docs/src/main/asciidoc/hibernate-orm.adoc
@@ -814,7 +814,7 @@ For more information about Hibernate Envers, see link:https://hibernate.org/orm/
 
 [[metrics]]
 == Metrics
-Either xref:micrometer.adoc[Micrometer] or xref:microprofile-metrics.adoc[SmallRye Metrics] are
+Either xref:telemetry-micrometer.adoc[Micrometer] or xref:microprofile-metrics.adoc[SmallRye Metrics] are
 capable of exposing metrics that Hibernate ORM collects at runtime. To enable exposure of Hibernate metrics
 on the `/q/metrics` endpoint, make sure your project depends on a metrics extension and set the configuration property `quarkus.hibernate-orm.metrics.enabled` to `true`.
 When using link:microprofile-metrics[SmallRye Metrics], metrics will be available under the `vendor` scope.

diff --git a/docs/src/main/asciidoc/kafka-streams.adoc b/docs/src/main/asciidoc/kafka-streams.adoc
@@ -1249,7 +1249,7 @@ content-length: 265
 This guide has shown how you can build stream processing applications using Quarkus and the Kafka Streams APIs,
 both in JVM and native modes.
 For running your KStreams application in production, you could also add health checks and metrics for the data pipeline.
-Refer to the Quarkus guides on xref:micrometer.adoc[Micrometer], xref:smallrye-metrics.adoc[SmallRye Metrics], and xref:smallrye-health.adoc[SmallRye Health] to learn more.
+Refer to the Quarkus guides on xref:telemetry-micrometer.adoc[Micrometer], xref:smallrye-metrics.adoc[SmallRye Metrics], and xref:smallrye-health.adoc[SmallRye Health] to learn more.
 
 == Configuration Reference