anchor.diff:  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
  +Tags have taken over the role to, for example, identify an application (`app=myShop`), the tier inside the application
   (`tier=database` or `tier=app_server`) and also the node/container id. Aggregation of metrics can then work over label
   queries (Give me the API hit count for `app=myShop && tier=app_server`).
   
  
positive.code: ----
  
  ===== TYPE
  When a type/class is annotated, the implementation must register a meter for each of the constructor and methods using the <<annotated-naming-convention>>. The meters are marked each time the corresponding constructor/method is invoked.
  
  .Example of an annotated type/class
  [source, java]
  
negative.code: |===
  |Annotation | Applies to |  Description | Default Unit
  
  |@Counted | M, C, T | Denotes a counter, which counts the invocations of the annotated object. | MetricUnit.NONE
  |@Gauge   | M, F | Denotes a gauge, which samples the value of the annotated object.  | _none_ Must be supplied by the user
  |@Metered | M, C, T  | Denotes a meter, which tracks the frequency of invocations of the annotated object. | MetricUnit.NANOSECOND
  |@Metric  | M, F, P | An annotation requesting that a metric should be injected. This annotation can be used on the fields
      of type `Meter`, `Timer`, `Counter`, and `Histogram`. | MetricUnit.NONE
  |@Timed   | M, C, T | An annotation for marking a constructor or method of an annotated object as timed.
  