anchor.diff:  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 `quarkiverse-micrometer-registry-statsd`, define a producer for registry-specific configuration objects that
  -are integrated with the Quarkus configuration model.
  +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
   
  
positive.code:         return MeterFilter.commonTags(Arrays.asList(
                  Tag.of("env", deploymentEnv)));
      }
  }
  ----
  
  
negative.code: 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
  `quarkus-micrometer-registry-stackdriver` extension:
  
  [source,xml]
  ----
  <dependency>
      <groupId>io.quarkiverse</groupId>
      <artifactId>quarkus-micrometer-registry-stackdriver</artifactId>
  </dependency>
  ----
  
  