anchor.diff:  
   Tags (or labels) play an important role in modern microservices and microservice scheduling systems (like e.g. Kubernetes).
   Application code can run on any node and can be re-scheduled to a different node at any time. Each container in such
  -an environment gets its own ID; when the container is stopped and a new one started for the same iamge, it will get a
  +an environment gets its own ID; when the container is stopped and a new one started for the same image, it will get a
   different id. The classical mapping of host/node and application runtime on it, therefore no longer works.
   
   Tags have taken over the role to for example identify an application (`app=myShop`), the tier inside the application
  
positive.code:  * Bean holding the metadata of one single metric
   */
  @SuppressWarnings("unused")
  public class MetadataEntry {
  
    /**
     * Name of the metric.
  
negative.code: === Metric Registry
  <TO DO>
  
  [[rest-api]]
  === Exposing metrics via REST API
  
  Data is exposed via REST over http under the `/metrics` base path in two default data formats for `GET` requests:
  