anchor.diff:  + latencies
       + gateway: 100 (number) - Latency in **micro**seconds.
       + upstream: 100 (number) - Latency in **micro**seconds.
  -    + client_request: 100 (number) - Latency in **micro**seconds.+    + client_request: 100 (number) - Latency in **micro**seconds.
  +
  +### `Requests_Status_Codes`
  ++ api_id: 56c31536a60ad644060041af (string) - Unique ID for API.
  ++ count: 1 (number) - Count of occurances or `status_code` in a given `tick - interval` range.
  ++ status_code: 301 (number) - HTTP status code.
  ++ tick: `2017-04-20T19:15:00Z` (string, required) - ISO 8601 date and time in UTC timezone.
positive.code: + run_queue: 0 (number)
  + uptime: 239.873 (number) - Seconds since node VM start.
  
  ## APIs
  ### `API__Request`
  + name: my_api (string, required) - Unique name for API.
  
negative.code:     + Attributes (Response_OK)
          + data (`Cluster_Status`)
  
  ## APIs Status [/apis_status{?interval}]
  
  This endpoint can be publicly available (just configure API for it).
  
  ### Get APIs Status [GET]
  
  This endpoint returns list of disclosed APIs statuses and can be used to render service status page.
  
  + Parameters
      + `interval`: `5 minute` (string, optional) - Interval for time-based aggregation of latencies data. Supports following formats: `5 minites`, `1 minute`, `1 hour, `5 hours`, `1 day`, `5 days`. Term count can be any number.
  
  + Response 200 (application/json)
      + Attributes (Response_Collection)
  