[DOCS] Copies x-pack folders to docs

Author: lcawl

docs/en/stack/InstallationFlow.jpg

@@ -0,0 +1,33 @@
+= X-Pack for the Elastic Stack
+:doctype:           book
+
+:forum:             https://discuss.elastic.co/c/x-pack
+:security-forum:    https://discuss.elastic.co/c/shield
+:watcher-forum:     https://discuss.elastic.co/c/watcher
+:monitoring-forum:  https://discuss.elastic.co/c/marvel
+:graph-forum:       https://discuss.elastic.co/c/graph
+
+include::{asciidoc-dir}/../../shared/versions60.asciidoc[]
+include::{asciidoc-dir}/../../shared/attributes.asciidoc[]
+
+:xkb-repo-dir: {docdir}/../../../kibana-extra/x-pack-kibana/docs/en
+:xes-repo-dir: {docdir}/../../../elasticsearch-extra/x-pack-elasticsearch/docs/en
+
+:gs-mini:      true
+
+
+include::xpack-introduction.asciidoc[]
+
+include::xpack-installing.asciidoc[]
+
+include::{xes-repo-dir}/security/gs-index.asciidoc[]
+
+include::{xkb-repo-dir}/monitoring/gs-index.asciidoc[]
+
+include::{xes-repo-dir}/watcher/gs-index.asciidoc[]
+
+include::{xkb-repo-dir}/reporting/gs-index.asciidoc[]
+
+include::{xkb-repo-dir}/graph/gs-index.asciidoc[]
+
+include::{xkb-repo-dir}/searchprofiler/gs-index.asciidoc[]

docs/en/stack/gs-index.asciidoc

@@ -0,0 +1,53 @@
+= Elastic Stack Overview
+
+:doctype:           book
+
+:forum:             https://discuss.elastic.co/c/x-pack
+:security-forum:    https://discuss.elastic.co/c/shield
+:watcher-forum:     https://discuss.elastic.co/c/watcher
+:monitoring-forum:  https://discuss.elastic.co/c/marvel
+:graph-forum:       https://discuss.elastic.co/c/graph
+
+:blog-ref:          https://www.elastic.co/blog/
+:wikipedia:         https://en.wikipedia.org/wiki
+
+:xkb-repo-dir:      {docdir}/../../../../../kibana/x-pack/docs/en
+:kib-repo-dir:      {docdir}/../../../../../kibana/docs
+:xes-repo-dir:      {docdir}/../../../../../elasticsearch/x-pack/docs/en
+:es-repo-dir:      {docdir}/../../../../../elasticsearch/docs
+
+include::{asciidoc-dir}/../../shared/versions.asciidoc[]
+include::{asciidoc-dir}/../../shared/attributes.asciidoc[]
+
+include::xpack-introduction.asciidoc[]
+
+include::xpack-setup.asciidoc[]
+
+include::xpack-breaking-changes.asciidoc[]
+
+include::xpack-apis.asciidoc[]
+
+include::xpack-features.asciidoc[]
+
+:edit_url: https://github.com/elastic/elasticsearch/edit/{branch}/x-pack/docs/en/security/index.asciidoc
+include::{xes-repo-dir}/security/index.asciidoc[]
+
+:edit_url:
+include::monitoring/index.asciidoc[]
+
+:edit_url: https://github.com/elastic/elasticsearch/edit/{branch}/x-pack/docs/en/watcher/index.asciidoc
+include::{xes-repo-dir}/watcher/index.asciidoc[]
+
+:edit_url: https://github.com/elastic/elasticsearch/edit/{branch}/x-pack/docs/en/ml/index.asciidoc
+include::{xes-repo-dir}/ml/index.asciidoc[]
+
+:edit_url:
+include::xpack-troubleshooting.asciidoc[]
+
+:edit_url:
+include::xpack-limitations.asciidoc[]
+
+:edit_url:
+include::xpack-license.asciidoc[]
+
+include::xpack-release-notes.asciidoc[]

docs/en/stack/images/InstallationFlow.jpg

@@ -0,0 +1,32 @@
+[[how-monitoring-works]]
+== How monitoring works
+
+Monitoring collects data from {es} nodes, Logstash nodes, and {kib} instances.
+The {es} cluster you are monitoring controls where the monitoring metrics for
+the entire stack are stored. By default, they are stored in local indices. In
+production, we strongly recommend using a separate monitoring cluster. Using a
+separate monitoring cluster prevents production cluster outages from impacting
+your ability to access your monitoring data. It also prevents monitoring
+activities from impacting the performance of your production cluster.
+
+IMPORTANT: In general, the monitoring cluster and the clusters being monitored
+should be running the same version of the stack. A monitoring cluster cannot
+monitor production clusters running newer versions of the stack. If necessary,
+the monitoring cluster can monitor production clusters running older versions,
+but the versions cannot differ by more than one major version.
+
+The following diagram illustrates a typical monitoring architecture with
+separate production and monitoring clusters:
+
+image::monitoring/images/architecture1.jpg[A typical monitoring environment]
+
+If you have at least a Gold license, you can route data from multiple production
+clusters to a single monitoring cluster:
+
+image::monitoring/images/architecture2.jpg[A monitoring environment with multiple production clusters]
+
+If {kib} is a regular part of your stack, you might want to create a dedicated
+{kib} instance for monitoring, rather than using a single {kib} instance to
+access both your production cluster and monitoring cluster:
+
+image::monitoring/images/architecture3.jpg[A monitoring environment with separate {kib} instances]

docs/en/stack/index.asciidoc

@@ -0,0 +1,3 @@
+include::intro.asciidoc[]
+include::how-monitoring-works.asciidoc[]
+include::production.asciidoc[]

docs/en/stack/monitoring/how-monitoring-works.asciidoc

@@ -0,0 +1,31 @@
+[[xpack-monitoring]]
+= Monitoring the {stack}
+
+[partintro]
+--
+
+{monitoring} gives you insight into the operation of {es}, Logstash, and {kib}.
+All of the monitoring metrics are stored in {es}, which enables you to easily
+visualize the data from {kib}. From the {kib} Monitoring UI, you can spot issues
+at a glance and delve into the system behavior over time to diagnose operational
+issues. In addition to the built-in status warnings, you can set up custom alerts
+based on the data in the monitoring indices.
+
+For more information, see:
+
+* <<how-monitoring-works>>
+* <<monitoring-production>>
+* {ref}/es-monitoring.html[Monitoring {es}]
+* {kibana-ref}/xpack-monitoring.html[Monitoring {kib}]
+* {logstash-ref}/monitoring-logstash.html[Monitoring Logstash]
+* Monitoring Beats:
+** {auditbeat-ref}/monitoring.html[Auditbeat]
+** {filebeat-ref}/monitoring.html[Filebeat]
+** {heartbeat-ref}/monitoring.html[Heartbeat]
+** {metricbeat-ref}/monitoring.html[Metricbeat]
+** {packetbeat-ref}/monitoring.html[Packetbeat]
+** {winlogbeat-ref}/monitoring.html[Winlogbeat] 
+
+
+
+--