anchor.diff:  
   ===== Application metrics
   
  -Application specific metrics can not be backed into the server as they are supposed to be provided by the
  +Application specific metrics can not be baked into the server as they are supposed to be provided by the
   application at runtime. Therefore a Java API is provided. Application specific metrics are supposed to be
   portable to other implementations of the MicroProfile. That means that an application written to this
   specification which exposes metrics, can expose the same metrics on a different compliant server
  
positive.code: `boolean absolute`:: If `true`, uses the given name as an absolute name of the metric. If `false`, prepends the package name and class name before the given name. Default value is `false`.
  `String displayName`:: Optional. A human readable display name for metadata.
  `String description`:: Optional. A description of the metric.
  `MetricUnits unit`:: Unit of the metric. For `@Gauge` no default is provided.
  `String[] tags`:: Optional. 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. Implementors
  
negative.code: The `@RegistryType` can be used to retrieve the `MetricRegistry` for a specific scope.
  The implementation must produce the corresponding `MetricRegistry` specified by the `RegistryType`.
  
  NOTE: The implementor can optionally provide a _read_only_ copy of the `MetricRegistry` for _base_ and _vendor_ scopes.
  
  ==== Application Metric Registry
  The implementation must produce the _application_ `MetricRegistry` when no `RegistryType` is provided (`@Default`) or when the `RegistryType` is `APPLICATION`.
  