anchor.diff:  It is expected that many existing DropWizard Metrics based applications can easily be
   ported over by exchanging the package names.
   
  -It will be possible to use the non-annotations API, but using the annotations will generally be easier and preferred by developers.
  +It will be possible to use the non-annotations API, but using the annotations will generally be easier for developers.
   
   === Responsibility of the Microprofile Metrics implementation
   
  
positive.code: Prometheus text format does not allow for all characters and adds the base unit of a family to the name.
  
  * Dot (`.`), Space ( ), Dash (`-`) are translated to underscore (`_`).
  * Scope always starts the metric name.
  * Scope and name are separated by colon (`:`).
  * camelCase is translated to camel_case
  * Double underscore is translated to single underscore
  
negative.code: * type:
  ** counter: an incrementally increasing or decreasing numeric value (e.g. total number of requests received or total number of concurrently active HTTP sessions).
  ** gauge: a numeric metric that is sampled to obtain its value (e.g. cpu temperature or disk usage).
  ** meter: a metric which tracks mean throughput and one-, five-, and fifteen-minute exponentially-weighted moving average throughput.
  ** histogram: a metric which calculates the distribution of a value.
  ** timer: a metric which aggregates timing durations and provides duration statistics, plus throughput statistics.
  * description (optional): A human readable description of the metric.
  * displayName (optional): A human readable name of the metric for display purposes if the metric name is not
  human readable. This could e.g. be the case when the metric name is a uuid.
  