CORD-2535: Update ELK documentation to match implementation
Change-Id: I83b95cccb19a1fc063642151f3c7156d31835a6a
diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md
index 494572e..0b0285f 100644
--- a/docs/SUMMARY.md
+++ b/docs/SUMMARY.md
@@ -19,6 +19,7 @@
* [Powering Up a POD](operate/power_up.md)
* [XOS Internals](xos/xos_internals.md)
* [REST API](operate/rest_apis.md)
+ * [Debugging and Diagnostics](operate/elk_stack.md)
* [TOSCA](xos-tosca/README.md)
* [XOSSH](xos/dev/xossh.md)
* [Defining Models in CORD](xos/README.md)
diff --git a/docs/operate/elk_stack.md b/docs/operate/elk_stack.md
index 672eb7c..cc0c4fe 100644
--- a/docs/operate/elk_stack.md
+++ b/docs/operate/elk_stack.md
@@ -3,7 +3,7 @@
CORD uses ELK Stack for logging information at all levels. CORD’s
ELK Stack logger collects information from several components,
including the XOS Core, API, and various Synchronizers. On a running
-POD, the logs can be accessed at `http://<head-node>:8080/kibana`.
+POD, the logs can be accessed at `http://<head-node>:8080/app/kibana`.
There is also a second way of accessing low-level logs with additional
verbosity that do not make it into ELK Stack. This involves accessing log
@@ -18,6 +18,17 @@
to diagnose problems. Furthermore, these logs thread together facts across
multiple components by using the identifiers of XOS data model objects.
+> Important!
+>
+> Before you can start using ELK stack, you must initialize its index.
+> To do so:
+>
+> 1) Replace `logstash-*` with `*` in the text box marked "Index pattern."
+>
+> 2) Pick `@timestamp` as the "Time Filter Field Name."
+>
+> Configuring the default logstash- index pattern will lead to HTTP errors in your browser. If you did this by accident, then delete it under Management -> Index Patterns, and create another pattern as described above.
+
More information about using
[Kibana](https://www.elastic.co/guide/en/kibana/current/getting-started.html)
to access ELK Stack logs is available elsewhere, but to illustrate how the logging