anchor.diff:  have been wrapped in
   https://github.com/quarkiverse/quarkiverse-micrometer-registry[Quarkiverse extensions].
   To use the Micrometer StackDriver MeterRegistry, for example, you would use the
  -`quarkiverse-micrometer-registry-stackdriver` extension:
  +`quarkus-micrometer-registry-stackdriver` extension:
   
   [source,xml]
   ----
   <dependency>
       <groupId>io.quarkiverse</groupId>
  -    <artifactId>quarkiverse-micrometer-registry-stackdriver</artifactId>
  +    <artifactId>quarkus-micrometer-registry-stackdriver</artifactId>
   </dependency>
   ----
   
  
positive.code:         return MeterFilter.commonTags(Arrays.asList(
                  Tag.of("env", deploymentEnv)));
      }
  }
  ----
  
  
negative.code: This example corresponds to the following instructions in the Micrometer documentation:
  https://micrometer.io/docs/registry/statsD#_customizing_the_metrics_sink
  
  Note that the method returns the specific type of `MeterRegistry` as a `@Singleton`. Use MicroProfile Config
  to inject any configuration attributes you need to configure the registry. Most Micrometer registry extensions,
  like `quarkus-micrometer-registry-statsd`, define a producer for registry-specific configuration objects
  that are integrated with the Quarkus configuration model.
  
  == Support for the MicroProfile Metrics API
  
  