diff --git a/docs/en/stack/index.asciidoc b/docs/en/stack/index.asciidoc index b50b0a3cd..e21a61f8c 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::troubleshooting.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 c989fa0ee..000000000 --- a/docs/en/stack/monitoring/how-monitoring-works.asciidoc +++ /dev/null @@ -1,42 +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/architecture1.jpg[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}. For example: - -image::monitoring/images/architecture4.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/architecture3.jpg[A monitoring environment with separate {kib} instances] diff --git a/docs/en/stack/monitoring/images/architecture1.jpg b/docs/en/stack/monitoring/images/architecture1.jpg deleted file mode 100644 index b91086dc6..000000000 Binary files a/docs/en/stack/monitoring/images/architecture1.jpg and /dev/null differ diff --git a/docs/en/stack/monitoring/images/architecture2.jpg b/docs/en/stack/monitoring/images/architecture2.jpg deleted file mode 100644 index 98a3f9396..000000000 Binary files a/docs/en/stack/monitoring/images/architecture2.jpg and /dev/null differ diff --git a/docs/en/stack/monitoring/images/architecture3.jpg b/docs/en/stack/monitoring/images/architecture3.jpg deleted file mode 100644 index 2cbabec74..000000000 Binary files a/docs/en/stack/monitoring/images/architecture3.jpg and /dev/null differ diff --git a/docs/en/stack/monitoring/images/architecture4.png b/docs/en/stack/monitoring/images/architecture4.png deleted file mode 100644 index b52867956..000000000 Binary files a/docs/en/stack/monitoring/images/architecture4.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 41e62a5a9..000000000 --- a/docs/en/stack/monitoring/production.asciidoc +++ /dev/null @@ -1,148 +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. - -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: - -. {ref}/configuring-monitoring.html[Set up the {es} cluster you want to use for monitoring]. -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. -=============================== - --- - -. {kibana-ref}/monitoring-xpack-kibana.html[Configure {monitoring}] in {kib}. -+ --- -NOTE: {kib} makes requests to the monitoring cluster as the logged in user. -The username and password credentials must therefore be valid on both the {kib} -server and the monitoring cluster. - --- - -. Create a user on the monitoring cluster that has the -`remote_monitoring_agent` role. These credentials will be used when -data is shipped from the {es} cluster you are monitoring to -your dedicated monitoring cluster. 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 --- - -. Configure each {es} node in the cluster you are -monitoring to send metrics to your monitoring cluster by -configuring an HTTP exporter in the -`xpack.monitoring.exporters` settings in `elasticsearch.yml`. -+ --- -[source,yaml] --------------------------------------------------- -xpack.monitoring.exporters: - id1: - type: http - host: ["http://es-mon-1:9200", "http://es-mon2:9200"] <1> - auth.username: remote_monitor <2> - auth.password: changeme --------------------------------------------------- -<1> If SSL/TLS is enabled on the monitoring cluster, you must -connect through HTTPS. -<2> If {security} is disabled on the monitoring cluster, you can -omit `auth.username` and `auth.password`. --- - -. If SSL/TLS is enabled on the monitoring cluster, specify the trusted -CA certificate(s) that will be used to verify the identity of the nodes -in the monitoring cluster. -+ --- -To add a CA certificate to an {es} node's trusted certificates, you -can specify the location of the PEM encoded certificate with the -`certificate_authorities` setting: - -[source,yaml] --------------------------------------------------- -xpack.monitoring.exporters: - id1: - type: http - host: ["https://es-mon1:9200", "https://es-mon2:9200"] - auth: - username: agent-user - password: password - ssl: - certificate_authorities: [ "/path/to/ca.crt" ] --------------------------------------------------- - -Alternatively, you can configure trusted certificates using a truststore -(a Java Keystore file that contains the certificates): - -[source,yaml] --------------------------------------------------- -xpack.monitoring.exporters: - id1: - type: http - host: ["https://es-mon1:9200", "https://es-mon2:9200"] - auth: - username: remote_monitor - password: changeme - ssl: - truststore.path: /path/to/file - truststore.password: password --------------------------------------------------- - --- - -. Restart {es} on the nodes in your production cluster. -+ --- -TIP: You may want to temporarily {ref}/modules-cluster.html[disable shard -allocation] before you restart your nodes to avoid unnecessary shard -reallocation during the install process. - --- - -. To verify your {monitoring} installation, point your web browser at your {kib} -host, and select **Monitoring** from the side navigation. When security is enabled, -to view the monitoring dashboards you must log in to {kib} as a user who has -both the `kibana_user` and `monitoring_user` roles. For example: -+ --- -[source,js] --------------------------------------------------- -POST /_xpack/security/user/stack-monitor -{ - "password" : "changeme", - "roles" : [ "kibana_user", "monitoring_user" ] -} --------------------------------------------------- -// CONSOLE - -//image:images/monitoring.jpg["Monitoring",link="images/monitoring.jpg"] --- 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 e4818a15b..3becd6e97 100644 --- a/docs/en/stack/redirects.asciidoc +++ b/docs/en/stack/redirects.asciidoc @@ -270,3 +270,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 acd203dc1..ff1282926 100644 --- a/docs/en/stack/troubleshooting.asciidoc +++ b/docs/en/stack/troubleshooting.asciidoc @@ -11,8 +11,6 @@ Having trouble? Here are solutions to common problems you might encounter. * {kibana-ref}/graph-troubleshooting.html[{graph}] -* <> - * {kibana-ref}/reporting-troubleshooting.html[{reporting}] * <> @@ -38,6 +36,4 @@ GET /_xpack include::security/troubleshooting.asciidoc[] -include::monitoring/troubleshooting.asciidoc[] - include::ml/troubleshooting.asciidoc[]