anchor.diff:  The status of the data feed, which can be one of the following values: +
   started::: The data feed is actively receiving data.
   stopped::: The data feed is stopped and will not receive data until it is re-started.
  -//TBD: How to restart data feeds in Kibana?
  +//TBD: How to restart data feeds in Kibana? 
   
   Latest timestamp::
   The timestamp of the last processed record.
  -//TBD: Is that right?
  +
   
   If you click the arrow beside the name of job, you can show or hide additional
   information, such as the settings, configuration information, or messages for
  
positive.code: information about installing each of the components.
  
  NOTE: To get started, you can install Elasticsearch and Kibana on a
  single VM or even on your laptop. As you add more data and your traffic grows,
  you'll want to replace the single Elasticsearch instance with a cluster.
  
  When you install {xpack} into Elasticsearch and Kibana, the {ml} features are
  
negative.code: key performance indicator to track this, which is the total requests over time.
  It is therefore logical to start by creating a single metric job for this KPI.
  
  TIP: If you are using aggregated data, you can create an advanced job
  and configure it to use a `summary_count_field`. The {ml} algorithms will
  make the best possible use of summarized data in this case. For simplicity in this tutorial
  we will not make use of that advanced functionality.
  
  
  