anchor.diff:  standard to expose metrics, but remote-JMX is not easy to deal with and
   especially does not fit well in a polyglot environment where other services
   are not running on the JVM.
  -To enable monitoring in an easy fashion it is necessary that all Microprofile
  +To enable monitoring in an easy fashion it is necessary that all MicroProfile
   implementations follow a certain standard with respect to (base) API path,
   data types involved, always available metrics and return codes used.
   
  
positive.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
  
negative.code: 
  The following three sets of sub-resource (scopes) are exposed.
  
  * base: metrics that all MicroProfile vendors have to provide
  * vendor: vendor specific metrics (optional)
  * application: application-specific metrics (optional)
  
  NOTE: It is expected that a future version of this specification will also have a sub-resource for integrations
  with other specifications of MicroProfile.
  
  [[scopes]]
  ==== Scopes
  
  ===== Required Base metrics
  
  Each vendor of a MicroProfile-compliant server can implement setting up the metrics in the _base_ scope in a
  vendor-specific way.
  The metrics can be hard coded into the server or read from a configuration file or supplied via the Java-API described in <<app-metrics-api>>.
  The Appendix shows a possible data format for such a configuration.
  