anchor.diff:  }
   ----
   
  +[[metric_units]]
   ==== Units
   
   [source]
  
positive.code: ----
  <1> Metric names are turned from camel case into snake_case.
  <2> The description goes into the HELP line
  <3> Metric names gets the base unit of the family appended with `_` and defined labels. Values are scaled accordingly
  
  ===== Translation rules for metric names
  
  Prometheus text format does not allow for all characters and adds the base unit of a family to the name.
  
  
negative.code: 
  Accessing `/metrics/<scope>` will only return metrics registered for the respective scope. Scopes are listed in <<metrics-setup>>.
  
  == REST endpoints
  
  
  === JSON format
  
  * When using JSON format, the REST API will respond to GET requests with data formatted in a tree like fashion with sub-trees for the sub-resources mentioned in the previous section.
  A sub-tree that does not contain data must be omitted.
  * A 'shadow tree' that responds to OPTIONS will provide the metadata.
  
  *REST-API Objects*
  
  API-objects MAY include one or more metrics as in
  
  [source]
  ----
  {
    "thread.count" : 33,
    "thread.max.count" : 47,
    "memory.maxHeap" : 3817863211,
    "memory.usedHeap" : 16859081,
    "memory.committedHeap" : 64703546
  }
  ----
  
  