anchor.diff:  === Responsibility of the Microprofile Metrics implementation
   
   * The implementation must scan the application at deploy time for <<api-annotations>> and register the
  -Metrics along with their metadata in the MetricsRegistry.
  +Metrics along with their metadata in the _application_ MetricsRegistry.
   * The implementation must watch the annotated objects and update its internal data structures when the values of the
   annotated objects change.
   * The implementation must expose the values of the objects registered in the MetricsRegistry via REST-API as described
  
positive.code: All annotations (Except `RegistryType`) have the following fields that correspond to the metadata fields described
  in <<meta-data-def>>.
  
  `String name`::  the name of the metric. If not explicitly given it is determined from the annotated object and the
  fully qualified name of the surrounding class, unless `absolute` is true.
  `boolean absolute`:: If `true` use the given name as an absolute name. If `false`, use the given name relative to
  the annotated class
  `String displayName`:: Optionally provide a human readable display name for metadata.
  `String description`:: Optionally provide a description of the metric.
  `MetricUnit unit:: Unit of the metric
  `String[] tags`:: Array of Strings in the `<key>=<value>` format to supply special tags to a metric.
  
  NOTE:: Implementors are encouraged to issue warnings in the server log if metadata is missing. While this is
  less important for description and displayName, it is very important for Units.
  
  
  === Metric Registry
  
  
  === Java API Classes
  
negative.code: [[app-metrics-api]]
  == Application Metrics Programming Model
  
  Microprofile Metrics provides a way to register Application-specific metrics to allow applications to expose metrics in
  the _application_ scope (see <<_scopes>> for the description of scopes).
  
  Metrics and their metadata are added to a _Metric Registry_ upon definition and can afterwards have their values set
  