anchor.diff:          return MeterFilter.commonTags(Arrays.asList(
                   Tag.of("env", deploymentEnv)));
       }
  +
  +    /** Enable histogram buckets for a specific timer */
  +    @Produces
  +    @Singleton
  +    public MeterFilter enableHistogram() {
  +        return new MeterFilter() {
  +            @Override
  +            public DistributionStatisticConfig configure(Meter.Id id, DistributionStatisticConfig config) {
  +                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);
  +                }
  +                return config;
  +            }
  +        };
  +    }
   }
   ----
   
  
positive.code: ----
  
  This command generates a Maven project, that imports the `micrometer-registry-prometheus` extension as a dependency.
  This extension will load the `micrometer` extension as well as additional library dependencies required to support
  prometheus.
  
  If you already have your Quarkus project configured, you can add the `micrometer` extension
  to your project by running the following command in your project base directory:
  
  [source,bash]
  
negative.code: Note that metrics appear lazily, you often won't see any data for your endpoint until
  something tries to access it, etc.
  
  == Using MeterFilter to configure metrics
  
  Micrometer uses `MeterFilter` instances to customize the metrics emitted by `MeterRegistry` instances.
  The Micrometer extension will detect `MeterFilter` CDI beans and use them when initializing `MeterRegistry`
  instances.
  
  [source,java]
  ----
  