anchor.diff:  Each section also contains a `lastModified` element, which contains the last modification time when the
   database was update. All timestamps returned from this API correspond to Unix epoch time in seconds.
   
  -=== Database status (`action=status`)
  -This call provides detailed status of the selected database.
  +=== Database Status
  +The query parameter `action=status` provides detailed status of the selected database.
   
   The following parameters are supported:
   
  -`name`:: string, required: database name
  +`name`:: string, required: database name.
   
   Example:
   [source,bash]
  
positive.code: Also, the response header section (`responseHeader`) contains `zkConnected` boolean property that indicates
  whether the current node is a part of SolrCloud cluster.
  
  === List databases (`action=list`)
  This call produces a list of available databases. It supports the following parameters:
  
  `rows`:: optional integer, default is 500. Maximum number of results to return.
  
  Example:
  In this SolrCloud example the API is in `memory` mode, and the request was made to a node that is
  not Overseer leader. The API transparently forwarded the request to Overseer leader.
  [source,bash]
  ----
  curl http://localhost:7574/solr/admin/metrics/history?action=list&rows=10
  
negative.code: 
  The handler assumes that a simple aggregation (sum of partial metric values from each resource) is
  sufficient. This happens to make sense for the default built-in sets of metrics. Future extensions will
  provide other aggregation strategies (such as, average, max, min, etc.).
  
  == Metrics History Configuration
  There are two ways to configure this subsystem:
  
  * `/clusterprops.json` - this is the primary mechanism. It uses the cluster properties JSON
  file in ZooKeeper. Configuration is stored in the `/metrics/history` element in a JSON map.
  