Add section for conceptual info

karenzone · karenzone · commit ee90e8033b9b · 2020-06-09T21:27:10.000Z
Backport of #11715 to 7.8
diff --git a/docs/index.asciidoc b/docs/index.asciidoc
@@ -55,6 +55,11 @@ include::static/advanced-pipeline.asciidoc[]
 :edit_url: https://github.com/elastic/logstash/edit/{branch}/docs/static/life-of-an-event.asciidoc
 include::static/life-of-an-event.asciidoc[]
 
+// Processing details
+
+:edit_url!:
+include::static/processing-info.asciidoc[]
+
 // Logstash setup
 
 :edit_url: https://github.com/elastic/logstash/edit/{branch}/docs/static/setting-up-logstash.asciidoc
diff --git a/docs/static/life-of-an-event.asciidoc b/docs/static/life-of-an-event.asciidoc
@@ -96,3 +96,4 @@ By default, Logstash uses in-memory bounded queues between pipeline stages
 unsafely, any events that are stored in memory will be lost. To help prevent data
 loss, you can enable Logstash to persist in-flight events to disk. See
 <<persistent-queues>> for more information.
+
diff --git a/docs/static/processing-info.asciidoc b/docs/static/processing-info.asciidoc
@@ -0,0 +1,18 @@
+[[processing]]
+=== Processing Details
+
+Understanding how {ls} works and how components interrelate can help you make better
+decisions when you are setting up or adjusting your {ls} environment. This
+section is designed to elevate concepts to assist with that level of
+knowledge.
+
+NOTE: This is a new section. We're still working on it.
+
+[float] 
+[[event-ordering]] 
+==== Event ordering 
+
+Event ordering info goes here. 
+
+//todo: Document event ordering guaranties or lack thereof with multiple worker versus single worker
+
