anchor.diff:  ====
   
   . Once connected to an Elasticsearch container, you can use the certificates mounted
  -from the secret to communicate with Elasticsearch per its 1.5
  -link:https://www.elastic.co/guide/en/elasticsearch/reference/1.5/docs.html[Document APIs].
  -+
  -Fluentd sends its logs to Elasticsearch using the index format *{project_name}.{project_uuid}.YYYY.MM.DD*
  +from the secret to communicate with Elasticsearch per its doc
  +link:https://www.elastic.co/guide/en/elasticsearch/reference/2.3/indices.html[Indices APIs].
  ++
  +Fluentd sends its logs to Elasticsearch using the index format *project.{project_name}.{project_uuid}.YYYY.MM.DD*
   where YYYY.MM.DD is the date of the log record.
   +
   For example, to delete all logs for the *logging* project with uuid *3b3594fa-2ccd-11e6-acb7-0eb6b35eaee3*
  
positive.code: You can see the user interface by visiting the site specified at the
  `*KIBANA_HOSTNAME*` variable.
  
  See the link:https://www.elastic.co/guide/en/kibana/4.1/discover.html[Kibana
  documentation] for more information on Kibana.
  
  [[configuring-curator]]
  
negative.code: $ curl --key /etc/elasticsearch/secret/admin-key \
    --cert /etc/elasticsearch/secret/admin-cert \
    --cacert /etc/elasticsearch/secret/admin-ca -XDELETE \
    "https://localhost:9200/project.logging.3b3594fa-2ccd-11e6-acb7-0eb6b35eaee3.2016.06.15"
  ----
  ====
  