diff --git a/docs/en/stack/index.asciidoc b/docs/en/stack/index.asciidoc index fa1b176a6..2de24e462 100644 --- a/docs/en/stack/index.asciidoc +++ b/docs/en/stack/index.asciidoc @@ -22,8 +22,6 @@ include::introduction.asciidoc[] include::security/index.asciidoc[] -include::monitoring/index.asciidoc[] - include::ml/index.asciidoc[] include::{es-repo-dir}/ccr/index.asciidoc[] diff --git a/docs/en/stack/introduction.asciidoc b/docs/en/stack/introduction.asciidoc index f2eed130d..a2b264d83 100644 --- a/docs/en/stack/introduction.asciidoc +++ b/docs/en/stack/introduction.asciidoc @@ -12,7 +12,6 @@ For a quick overview, see: https://www.elastic.co/products * {stack-gs}/get-started-elastic-stack.html[Getting started with the {stack}] * <> -* <> * {kibana-ref}/reporting-getting-started.html[Getting Started with Reporting] * {kibana-ref}/graph-getting-started.html[Getting Started with Graph] diff --git a/docs/en/stack/monitoring/how-monitoring-works.asciidoc b/docs/en/stack/monitoring/how-monitoring-works.asciidoc deleted file mode 100644 index d8496ff31..000000000 --- a/docs/en/stack/monitoring/how-monitoring-works.asciidoc +++ /dev/null @@ -1,43 +0,0 @@ -[role="xpack"] -[[how-monitoring-works]] -== How monitoring works - -Monitoring collects data from {es} nodes, Logstash nodes, and {kib} instances. - -In general, the {es} cluster you are monitoring controls where the monitoring -metrics for the stack are stored. By default, they are stored in local indices. - -TIP: In production, we strongly recommend using a separate monitoring -Elasticsearch 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. For the same reason, we also -recommend to use a separate Kibana instance that is connected to the separate -monitoring cluster. - -The following diagram illustrates a typical monitoring architecture with separate -production and monitoring clusters: - -image::monitoring/images/architecture10.png["A typical monitoring environment"] - -beta[] In 6.4 and later, you can use {metricbeat} to collect and ship data about -{kib}, rather than routing it through {es}. In 6.5 and later, you can also use -{metricbeat} to collect and ship data about {es}. For example: - -image::monitoring/images/architecture20.png[A typical monitoring environment that includes {metricbeat}] - -If you have at least a gold license, you can route data from multiple production -clusters to a single monitoring cluster. For more information about the -differences between various subscription levels, see: https://www.elastic.co/subscriptions - -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. - -If you use {kib} to visualize data and administer the cluster, 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/architecture30.png["A separate {kib} instance accesses the monitoring cluster"] diff --git a/docs/en/stack/monitoring/images/architecture10.png b/docs/en/stack/monitoring/images/architecture10.png deleted file mode 100644 index dfcb417d8..000000000 Binary files a/docs/en/stack/monitoring/images/architecture10.png and /dev/null differ diff --git a/docs/en/stack/monitoring/images/architecture20.png b/docs/en/stack/monitoring/images/architecture20.png deleted file mode 100644 index 9a45ce042..000000000 Binary files a/docs/en/stack/monitoring/images/architecture20.png and /dev/null differ diff --git a/docs/en/stack/monitoring/images/architecture30.png b/docs/en/stack/monitoring/images/architecture30.png deleted file mode 100644 index e2f820d9f..000000000 Binary files a/docs/en/stack/monitoring/images/architecture30.png and /dev/null differ diff --git a/docs/en/stack/monitoring/index.asciidoc b/docs/en/stack/monitoring/index.asciidoc deleted file mode 100644 index 1c449c32d..000000000 --- a/docs/en/stack/monitoring/index.asciidoc +++ /dev/null @@ -1,3 +0,0 @@ -include::intro.asciidoc[] -include::how-monitoring-works.asciidoc[] -include::production.asciidoc[] diff --git a/docs/en/stack/monitoring/intro.asciidoc b/docs/en/stack/monitoring/intro.asciidoc deleted file mode 100644 index 9d1f01f9b..000000000 --- a/docs/en/stack/monitoring/intro.asciidoc +++ /dev/null @@ -1,32 +0,0 @@ -[role="xpack"] -[[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: - -* <> -* <> -* {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] - - - --- diff --git a/docs/en/stack/monitoring/production.asciidoc b/docs/en/stack/monitoring/production.asciidoc deleted file mode 100644 index a2f1693ee..000000000 --- a/docs/en/stack/monitoring/production.asciidoc +++ /dev/null @@ -1,125 +0,0 @@ -[[monitoring-production]] -== Monitoring in a production environment - -By default, monitoring agents store data in the cluster where they're running. -In production, you should -send data to a separate _monitoring cluster_ so that historical monitoring -data is available even when the nodes you are monitoring are not. - -beta[] In 6.4 and later, you can use {metricbeat} to ship monitoring data about -{kib} to a separate monitoring cluster. In 6.5 and later, you can do the same -for {es}. - -If you have at least a gold license, using a dedicated monitoring cluster also -enables you to monitor multiple clusters from a central location. - -To store monitoring data in a separate cluster: - -. Set up the {es} cluster you want to use as the monitoring cluster. -For example, you might set up a two host cluster with the nodes `es-mon-1` and -`es-mon-2`. -+ --- -[IMPORTANT] -=============================== -* To monitor an {es} 6.x cluster, you must run {es} -6.x on the monitoring cluster. -* There must be at least one {ref}/ingest.html[ingest node] in the monitoring -cluster; it does not need to be a dedicated ingest node. -=============================== --- - -.. (Optional) Verify that the collection of monitoring data is disabled on the -monitoring cluster. By default, the `xpack.monitoring.collection.enabled` setting -is `false`. -+ --- -For example, you can use the following APIs to review and change this setting: - -[source,js] ----------------------------------- -GET _cluster/settings - -PUT _cluster/settings -{ - "persistent": { - "xpack.monitoring.collection.enabled": false - } -} ----------------------------------- -// CONSOLE --- - -.. If the {es} {security-features} are enabled on the monitoring cluster, create -users that can send and retrieve monitoring data. -+ --- -NOTE: If you plan to use {kib} to view monitoring data, username and password -credentials must be valid on both the {kib} server and the monitoring cluster. - --- - -*** beta[] If you plan to use {metricbeat} to collect data about {es} or {kib}, -create a user that has the `remote_monitoring_collector` built-in role and a -user that has the `remote_monitoring_agent` -<>. Alternatively, use the -`remote_monitoring_user` <>. - -*** If you plan to use HTTP exporters to route data through your production -cluster, create a user that has the `remote_monitoring_agent` -<>. -+ --- -For example, the -following request creates a `remote_monitor` user that has the -`remote_monitoring_agent` role: - -[source, sh] ---------------------------------------------------------------- -POST /_xpack/security/user/remote_monitor -{ - "password" : "changeme", - "roles" : [ "remote_monitoring_agent"], - "full_name" : "Internal Agent For Remote Monitoring" -} ---------------------------------------------------------------- -// CONSOLE -// TEST[skip:needs-gold+-license] - -Alternatively, use the `remote_monitoring_user` <>. --- - -. Configure your production cluster to collect data and send it to the -monitoring cluster. - -** beta[] {ref}/configuring-metricbeat.html[Use {metricbeat}]. This option -is available in 6.5 and later versions. - -** {ref}/configuring-monitoring.html[Use HTTP exporters]. - -. (Optional) -{logstash-ref}/configuring-logstash.html[Configure {ls} to collect data and send it to the monitoring cluster]. -+ --- -NOTE: You must configure HTTP exporters in the production cluster to route this -data to the monitoring cluster. It cannot be accomplished by using {metricbeat}. - --- - -. (Optional) Configure {kib} to collect data and send it to the monitoring cluster: - -** beta[] {kibana-ref}/monitoring-metricbeat.html[Use {metricbeat}]. This -option is available in 6.4 and later versions. - -** {kibana-ref}/monitoring-kibana.html[Use HTTP exporters]. - -. (Optional) Create a dedicated {kib} instance for monitoring, rather than using -a single {kib} instance to access both your production cluster and monitoring -cluster. - -.. (Optional) Disable the collection of monitoring data in this {kib} instance. -Set the `xpack.monitoring.kibana.collection.enabled` setting to `false` in the -`kibana.yml` file. For more information about this setting, see -{kibana-ref}/monitoring-settings-kb.html[Monitoring settings in {kib}]. - -. {kibana-ref}/monitoring-data.html[Configure {kib} to retrieve and display the monitoring data]. diff --git a/docs/en/stack/monitoring/troubleshooting.asciidoc b/docs/en/stack/monitoring/troubleshooting.asciidoc deleted file mode 100644 index 85b64983b..000000000 --- a/docs/en/stack/monitoring/troubleshooting.asciidoc +++ /dev/null @@ -1,8 +0,0 @@ -[[monitoring-troubleshooting]] -== Troubleshooting monitoring -++++ -Monitoring -++++ - -See -{logstash-ref}/monitoring-troubleshooting.html[Troubleshooting {monitoring} in Logstash]. diff --git a/docs/en/stack/redirects.asciidoc b/docs/en/stack/redirects.asciidoc index 6a08f24ea..6625550fc 100644 --- a/docs/en/stack/redirects.asciidoc +++ b/docs/en/stack/redirects.asciidoc @@ -283,3 +283,37 @@ See {ref}/watcher-troubleshooting.html[Troubleshooting Watcher]. This page has moved. See {ref}/watcher-limitations.html[Watcher limitations]. + +[role="exclude",id="monitoring-production"] +=== Monitoring in a production environment + +This page has moved. +See {ref}/monitoring-production.html[Monitoring in a production environment]. + +[role="exclude",id="how-monitoring-works"] +=== How monitoring works + +This page has moved. +See {ref}/how-monitoring-works.html[How monitoring works]. + +[role="exclude",id="monitoring-troubleshooting"] +=== Troubleshooting monitoring + +This page has moved. +See {ref}/monitoring-troubleshooting.html[Troubleshooting monitoring]. + +[role="exclude",id="xpack-monitoring"] +=== Monitoring the {stack} + +This page has moved. See: + +* {ref}/monitor-elasticsearch-cluster.html[Monitor a cluster] +* {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] diff --git a/docs/en/stack/troubleshooting.asciidoc b/docs/en/stack/troubleshooting.asciidoc index 644958a02..4048f4ca0 100644 --- a/docs/en/stack/troubleshooting.asciidoc +++ b/docs/en/stack/troubleshooting.asciidoc @@ -9,8 +9,6 @@ Having trouble? Here are solutions to common problems you might encounter. * <> -* <> - * <> -- @@ -34,6 +32,4 @@ GET /_xpack include::security/troubleshooting.asciidoc[] -include::monitoring/troubleshooting.asciidoc[] - include::ml/troubleshooting.asciidoc[]