From ae4fc43d1c401d7a88041107c20dcefa039bddee Mon Sep 17 00:00:00 2001 From: dedemorton Date: Wed, 1 Mar 2023 20:58:13 -0800 Subject: [PATCH 1/9] [DOCS] Describe how to use Elastic Agent to monitor Kibana --- .../configuring-monitoring.asciidoc | 16 ++- .../user/monitoring/logstash-details.asciidoc | 2 +- .../monitoring-elastic-agent.asciidoc | 98 +++++++++++++++++++ .../monitoring/monitoring-kibana.asciidoc | 11 ++- .../monitoring/monitoring-metricbeat.asciidoc | 14 ++- .../monitoring-troubleshooting.asciidoc | 9 +- docs/user/monitoring/viewing-metrics.asciidoc | 9 ++ .../user/monitoring/xpack-monitoring.asciidoc | 23 +++-- docs/user/setup.asciidoc | 1 + 9 files changed, 160 insertions(+), 23 deletions(-) create mode 100644 docs/user/monitoring/monitoring-elastic-agent.asciidoc diff --git a/docs/user/monitoring/configuring-monitoring.asciidoc b/docs/user/monitoring/configuring-monitoring.asciidoc index f158dcc3eee6f..364f9ebafd9f1 100644 --- a/docs/user/monitoring/configuring-monitoring.asciidoc +++ b/docs/user/monitoring/configuring-monitoring.asciidoc @@ -5,11 +5,19 @@ Configure monitoring ++++ -If you enable the {monitor-features} in your cluster, there are two methods to -collect metrics about {kib}: +If you enable the {monitor-features} in your cluster, there are a few methods +available to collect metrics about {kib}: -* <> -* <> +* <>: Uses a single agent to gather +logs and metrics. Can be managed from a central location in {fleet}. + +* <>: Uses a lightweight {beats} +shipper to gather metrics. May be preferred if you have an existing investment +in {beats} or are not yet ready to use {agent}. + +* <>: Uses internal collectors to gather +metrics. Not recommended. If you have previously configured legacy collection +methods, you should migrate to using {agent} or {metricbeat}. You can also use {kib} to <>. diff --git a/docs/user/monitoring/logstash-details.asciidoc b/docs/user/monitoring/logstash-details.asciidoc index 1a38f4f0204db..2b4cd120c3b09 100644 --- a/docs/user/monitoring/logstash-details.asciidoc +++ b/docs/user/monitoring/logstash-details.asciidoc @@ -18,4 +18,4 @@ status of each Logstash node. . Click the name of a node to view its statistics over time. For more information, refer to -{logstash-ref}/monitoring-logstash.html[Monitoring Logstash]. +{logstash-ref}/configuring-logstash.html[Monitoring Logstash]. diff --git a/docs/user/monitoring/monitoring-elastic-agent.asciidoc b/docs/user/monitoring/monitoring-elastic-agent.asciidoc new file mode 100644 index 0000000000000..8fab480e14596 --- /dev/null +++ b/docs/user/monitoring/monitoring-elastic-agent.asciidoc @@ -0,0 +1,98 @@ +[[monitoring-elastic-agent]] += Collect {kib} monitoring data with {agent} +++++ +Collect monitoring data with {agent} +++++ + +preview::[] + +In 8.5 and later, you can use {agent} to collect data about {kib} and ship it to +the monitoring cluster, rather than <> +or routing data through the production cluster as described in +<>. + +To learn about monitoring in general, see +{ref}/monitor-elasticsearch-cluster.html[Monitor a cluster]. + +[discrete] +== Prerequisites + +**** +**Question for reviewers:** + +Please verify these prereqs. I have not tested sending metrics to a +dedicated monitoring cluster, but I assume we want to recommend that with agent +as we have with Metricbeat in the past. +**** + +* Set up {es} monitoring and optionally create a monitoring cluster as described +in the {ref}/monitoring-production.html[{es} monitoring documentation]. + +* If you decide to use a monitoring cluster, add an {es} output under +**Fleet Settings** to send data to the monitoring cluster. To learn how, refer +to the documentation about +{fleet-guide}/fleet-settings.html#output-settings[Output settings]. +If the monitoring cluster uses encrypted communications, you must access it via +HTTPS. For example, use a `hosts` setting like `https://es-mon-1:9200`. + +* Create a user on the production cluster that has the +`remote_monitoring_collector` {ref}/built-in-roles.html[built-in role]. + +**** +**Question for reviewers:** + +Is there a way to provide an API key instead of username/password to collect +monitoring data? +**** + +[discrete] +== Add {kib} monitoring data + +To collect {kib} monitoring data, add a {kib} integration to an {agent} and +deploy it to the host where {kib} is running. + +. Go to the {kib} home page and click **Add integrations**. +. In the query bar, search for and select the **Kibana** integration for +{agent}. ++ +TIP: If you don't see the integration, scroll down and select the +**Display beta integrations** and **Elastic Agent only** options to see all +integrations that work with {agent}. + +. Read the overview to make sure you understand integration requirements and +other considerations. +. Click **Add Kibana**. ++ +TIP: If you're installing an integration for the first time, you may be prompted +to install {agent}. Click **Add integration only (skip agent installation)**. + +. Configure the integration name and optionally add a description. Make sure you +configure all required settings: +* Under **Collect Kibana logs**, modify the log paths to match your {kib} +environment. +* Under **Collect Kibana metrics**, make sure the hosts setting points to your +Kibana host URLs. By default, the integration collects {kib} monitoring metrics +from `localhost:5601`. If that host and port number are not correct, update the +`hosts` setting. If you configured {kib} to use encrypted communications, you +must access it via HTTPS. For example, use a `hosts` setting like +`https://localhost:5601`. +* If the Elastic {security-features} are enabled, expand **Advanced options** +under the Hosts setting and enter the username and password of a user that has +the `remote_monitoring_collector` role. +. Choose where to add the integration policy. Click **New hosts** to add it to +new agent policy or **Existing hosts** to add it to an existing agent policy. +. Click **Save and continue**. This step takes a minute or two to complete. When +it's done, you'll have an agent policy that contains an integration for +collecting monitoring data from {kib}. +. (Optional) If you're sending data to a monitoring cluster, edit the agent +policy, and under **Settings**, change the **Output for integrations** to the +output you created for the monitoring cluster. +. If an {agent} is already assigned to the policy and deployed to the host where +{kib} is running, you're done. Otherwise, you need to deploy an {agent}. To +deploy an {agent}: +.. Go to **{fleet} -> Agents**, then click **Add agent**. +.. Follow the steps in the **Add agent** flyout to download, install, +and enroll the {agent}. Make sure you choose the agent policy you created +earlier. +. Wait a minuter or two until incoming data is confirmed. +. <>. diff --git a/docs/user/monitoring/monitoring-kibana.asciidoc b/docs/user/monitoring/monitoring-kibana.asciidoc index 047fcc08775e6..bcdd08be447f3 100644 --- a/docs/user/monitoring/monitoring-kibana.asciidoc +++ b/docs/user/monitoring/monitoring-kibana.asciidoc @@ -10,14 +10,15 @@ optionally collect metrics about {kib}. [IMPORTANT] ========================= -{metricbeat} is the recommended method for collecting and shipping monitoring -data to a monitoring cluster. +{agent} or {metricbeat} are the recommended methods for collecting and shipping +monitoring data to a monitoring cluster. If you have previously configured legacy collection methods, you should migrate -to using {metricbeat} collection methods. Use either {metricbeat} collection or -legacy collection methods; do not use both. +to using {agent} or {metricbeat} collection methods. Use only one collection +method. -For the recommended method, refer to <>. +For more information, refer to <> and +<>. ========================= The following method involves sending the metrics to the production cluster, diff --git a/docs/user/monitoring/monitoring-metricbeat.asciidoc b/docs/user/monitoring/monitoring-metricbeat.asciidoc index 101377e047588..3ad42475c671d 100644 --- a/docs/user/monitoring/monitoring-metricbeat.asciidoc +++ b/docs/user/monitoring/monitoring-metricbeat.asciidoc @@ -15,12 +15,21 @@ image::user/monitoring/images/metricbeat.png[Example monitoring architecture] To learn about monitoring in general, see {ref}/monitor-elasticsearch-cluster.html[Monitor a cluster]. -//NOTE: The tagged regions are re-used in the Stack Overview. +**** +**Question for reviewers:** + +Is it still necessary to disable default collection? I didn't test this with +Metricbeat, but when I tested Elastic Agent + the Kibana integration, I did not +need to change any default settings. I did not need to set +monitoring.kibana.collection.enabled: false, and I didn't see +a monitoring.enabled setting. + +Question for Lisa C: Are these tagged regions used anywhere? +**** . Disable the default collection of {kib} monitoring metrics. + + -- -// tag::disable-kibana-collection[] Add the following setting in the {kib} configuration file (`kibana.yml`): [source,yaml] @@ -29,7 +38,6 @@ monitoring.kibana.collection.enabled: false ---------------------------------- Leave the `monitoring.enabled` set to its default value (`true`). -// end::disable-kibana-collection[] For more information, see <>. -- diff --git a/docs/user/monitoring/monitoring-troubleshooting.asciidoc b/docs/user/monitoring/monitoring-troubleshooting.asciidoc index 5bec56df0398b..9280eb846aa67 100644 --- a/docs/user/monitoring/monitoring-troubleshooting.asciidoc +++ b/docs/user/monitoring/monitoring-troubleshooting.asciidoc @@ -56,9 +56,12 @@ from a different monitoring cluster, set `monitoring.ui.elasticsearch.hosts`. See <>. . Confirm that there is monitoring data available at that URL. It is stored in -indices such as `.monitoring-kibana-*` and `.monitoring-es-*`. At a minimum, you -must have monitoring data for the {es} production cluster. Once that data exists, -{kib} can display monitoring data for other products in the cluster. +indices such as `.monitoring-kibana-*` and `.monitoring-es-*` or +`.ds-metrics-kibana.stack_monitoring-*` and +`.ds-metrics-elasticsearch.stack_monitoring-*`, depending on which method is +used to collect monitoring data. At a minimum, you must have monitoring data +for the {es} production cluster. Once that data exists, {kib} can display +monitoring data for other products in the cluster. . Set the time filter to “Last 1 hour”. When monitoring data appears in your cluster, the page automatically refreshes with the monitoring summary. diff --git a/docs/user/monitoring/viewing-metrics.asciidoc b/docs/user/monitoring/viewing-metrics.asciidoc index 9507b70c4f72e..da64fd8e5b65e 100644 --- a/docs/user/monitoring/viewing-metrics.asciidoc +++ b/docs/user/monitoring/viewing-metrics.asciidoc @@ -71,6 +71,15 @@ remote monitoring cluster, you must use credentials that are valid on both the .. Create users that have the `monitoring_user` and `kibana_admin` {ref}/built-in-roles.html[built-in roles]. ++ +**** +**Question for reviewers:** + +What do we recommend here for viewing data collected by Elastic Agent? Looks like the +monitoring_user role has read and read_cross_cluster on .monitoring-* and +metricbeat-* indices, not the ones created by the agent. + +**** . Open {kib} in your web browser. + diff --git a/docs/user/monitoring/xpack-monitoring.asciidoc b/docs/user/monitoring/xpack-monitoring.asciidoc index 751710d1e74f5..83f07678e0fc4 100644 --- a/docs/user/monitoring/xpack-monitoring.asciidoc +++ b/docs/user/monitoring/xpack-monitoring.asciidoc @@ -8,16 +8,25 @@ The {kib} {monitor-features} serve two separate purposes: . To visualize monitoring data from across the {stack}. You can view health and -performance data for {es}, {ls}, and Beats in real time, as well as analyze past -performance. +performance data for {es}, {ls}, {ents}, APM, and Beats in real time, +as well as analyze past performance. . To monitor {kib} itself and route that data to the monitoring cluster. -If you enable monitoring across the {stack}, each {es} node, {ls} node, {kib} -instance, and Beat is considered unique based on its persistent -UUID, which is written to the <> directory when the node -or instance starts. +**** +**Question for reviewers:** +Is the following paragraph correct? Do all of the products listed above have +UUIDs? +**** + +If you enable monitoring across the {stack}, each monitored component is +considered unique based on its persistent UUID, which is written to the +<> directory when the node or instance starts. For more information, see <> and -{ref}/monitor-elasticsearch-cluster.html[Monitor a cluster]. +{ref}/monitor-elasticsearch-cluster.html[Monitor a cluster]. + +Want to monitor your fleet of {agent}s, too? Use {fleet} instead of the Stack +Monitoring UI. To learn more, refer to +{fleet-guide}/monitor-elastic-agent.html[Monitor {agent}s]. -- \ No newline at end of file diff --git a/docs/user/setup.asciidoc b/docs/user/setup.asciidoc index 87213249e0d97..87c398f1d44e0 100644 --- a/docs/user/setup.asciidoc +++ b/docs/user/setup.asciidoc @@ -67,6 +67,7 @@ include::{kib-repo-dir}/setup/configuring-reporting.asciidoc[] include::{kib-repo-dir}/setup/configuring-logging.asciidoc[] include::monitoring/configuring-monitoring.asciidoc[leveloffset=+1] +include::monitoring/monitoring-elastic-agent.asciidoc[leveloffset=+2] include::monitoring/monitoring-metricbeat.asciidoc[leveloffset=+2] include::monitoring/viewing-metrics.asciidoc[leveloffset=+2] include::monitoring/monitoring-kibana.asciidoc[leveloffset=+2] From ec637ebfe97e5317ae26eedf66919f7574b64cff Mon Sep 17 00:00:00 2001 From: DeDe Morton Date: Mon, 6 Mar 2023 14:46:07 -0800 Subject: [PATCH 2/9] Fix typo --- docs/user/monitoring/monitoring-elastic-agent.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user/monitoring/monitoring-elastic-agent.asciidoc b/docs/user/monitoring/monitoring-elastic-agent.asciidoc index 8fab480e14596..6e0d0ac52973e 100644 --- a/docs/user/monitoring/monitoring-elastic-agent.asciidoc +++ b/docs/user/monitoring/monitoring-elastic-agent.asciidoc @@ -94,5 +94,5 @@ deploy an {agent}: .. Follow the steps in the **Add agent** flyout to download, install, and enroll the {agent}. Make sure you choose the agent policy you created earlier. -. Wait a minuter or two until incoming data is confirmed. +. Wait a minute or two until incoming data is confirmed. . <>. From da123936924cd362510ef7a4581c8b15588377d4 Mon Sep 17 00:00:00 2001 From: DeDe Morton Date: Wed, 8 Mar 2023 15:39:42 -0800 Subject: [PATCH 3/9] Apply suggestions from code review Make text consistent with note in docs about monitoring ES --- docs/user/monitoring/monitoring-kibana.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/user/monitoring/monitoring-kibana.asciidoc b/docs/user/monitoring/monitoring-kibana.asciidoc index bcdd08be447f3..7f060d7aab738 100644 --- a/docs/user/monitoring/monitoring-kibana.asciidoc +++ b/docs/user/monitoring/monitoring-kibana.asciidoc @@ -10,12 +10,12 @@ optionally collect metrics about {kib}. [IMPORTANT] ========================= -{agent} or {metricbeat} are the recommended methods for collecting and shipping +{agent} and {metricbeat} are the recommended methods for collecting and shipping monitoring data to a monitoring cluster. If you have previously configured legacy collection methods, you should migrate -to using {agent} or {metricbeat} collection methods. Use only one collection -method. +to using {agent} or {metricbeat} collection. Do not use legacy collection +alongside other collection methods. For more information, refer to <> and <>. From f655901ebd3436162298dd9328acd9882464e67b Mon Sep 17 00:00:00 2001 From: dedemorton Date: Thu, 9 Mar 2023 22:21:44 -0800 Subject: [PATCH 4/9] Apply changes from review --- .../monitoring-elastic-agent.asciidoc | 30 +++---------------- .../monitoring-troubleshooting.asciidoc | 3 +- .../user/monitoring/xpack-monitoring.asciidoc | 6 ---- 3 files changed, 5 insertions(+), 34 deletions(-) diff --git a/docs/user/monitoring/monitoring-elastic-agent.asciidoc b/docs/user/monitoring/monitoring-elastic-agent.asciidoc index 6e0d0ac52973e..02d4db64656d2 100644 --- a/docs/user/monitoring/monitoring-elastic-agent.asciidoc +++ b/docs/user/monitoring/monitoring-elastic-agent.asciidoc @@ -17,34 +17,12 @@ To learn about monitoring in general, see [discrete] == Prerequisites -**** -**Question for reviewers:** - -Please verify these prereqs. I have not tested sending metrics to a -dedicated monitoring cluster, but I assume we want to recommend that with agent -as we have with Metricbeat in the past. -**** - * Set up {es} monitoring and optionally create a monitoring cluster as described in the {ref}/monitoring-production.html[{es} monitoring documentation]. -* If you decide to use a monitoring cluster, add an {es} output under -**Fleet Settings** to send data to the monitoring cluster. To learn how, refer -to the documentation about -{fleet-guide}/fleet-settings.html#output-settings[Output settings]. -If the monitoring cluster uses encrypted communications, you must access it via -HTTPS. For example, use a `hosts` setting like `https://es-mon-1:9200`. - * Create a user on the production cluster that has the `remote_monitoring_collector` {ref}/built-in-roles.html[built-in role]. -**** -**Question for reviewers:** - -Is there a way to provide an API key instead of username/password to collect -monitoring data? -**** - [discrete] == Add {kib} monitoring data @@ -52,12 +30,12 @@ To collect {kib} monitoring data, add a {kib} integration to an {agent} and deploy it to the host where {kib} is running. . Go to the {kib} home page and click **Add integrations**. ++ +NOTE: If you're using a monitoring cluster, use the {kib} instances connected to +the monitoring cluster. + . In the query bar, search for and select the **Kibana** integration for {agent}. -+ -TIP: If you don't see the integration, scroll down and select the -**Display beta integrations** and **Elastic Agent only** options to see all -integrations that work with {agent}. . Read the overview to make sure you understand integration requirements and other considerations. diff --git a/docs/user/monitoring/monitoring-troubleshooting.asciidoc b/docs/user/monitoring/monitoring-troubleshooting.asciidoc index 9280eb846aa67..02141c2ccc69e 100644 --- a/docs/user/monitoring/monitoring-troubleshooting.asciidoc +++ b/docs/user/monitoring/monitoring-troubleshooting.asciidoc @@ -57,8 +57,7 @@ See <>. . Confirm that there is monitoring data available at that URL. It is stored in indices such as `.monitoring-kibana-*` and `.monitoring-es-*` or -`.ds-metrics-kibana.stack_monitoring-*` and -`.ds-metrics-elasticsearch.stack_monitoring-*`, depending on which method is +`metrics-kibana.stack_monitoring-*`, depending on which method is used to collect monitoring data. At a minimum, you must have monitoring data for the {es} production cluster. Once that data exists, {kib} can display monitoring data for other products in the cluster. diff --git a/docs/user/monitoring/xpack-monitoring.asciidoc b/docs/user/monitoring/xpack-monitoring.asciidoc index 83f07678e0fc4..88164407007a1 100644 --- a/docs/user/monitoring/xpack-monitoring.asciidoc +++ b/docs/user/monitoring/xpack-monitoring.asciidoc @@ -12,12 +12,6 @@ performance data for {es}, {ls}, {ents}, APM, and Beats in real time, as well as analyze past performance. . To monitor {kib} itself and route that data to the monitoring cluster. -**** -**Question for reviewers:** -Is the following paragraph correct? Do all of the products listed above have -UUIDs? -**** - If you enable monitoring across the {stack}, each monitored component is considered unique based on its persistent UUID, which is written to the <> directory when the node or instance starts. From a85576eb0e6b2b9f131ee9b75890565cd918f086 Mon Sep 17 00:00:00 2001 From: dedemorton Date: Thu, 9 Mar 2023 22:23:27 -0800 Subject: [PATCH 5/9] Fix typo --- docs/user/monitoring/monitoring-elastic-agent.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user/monitoring/monitoring-elastic-agent.asciidoc b/docs/user/monitoring/monitoring-elastic-agent.asciidoc index 02d4db64656d2..6a326efaf7c69 100644 --- a/docs/user/monitoring/monitoring-elastic-agent.asciidoc +++ b/docs/user/monitoring/monitoring-elastic-agent.asciidoc @@ -31,7 +31,7 @@ deploy it to the host where {kib} is running. . Go to the {kib} home page and click **Add integrations**. + -NOTE: If you're using a monitoring cluster, use the {kib} instances connected to +NOTE: If you're using a monitoring cluster, use the {kib} instance connected to the monitoring cluster. . In the query bar, search for and select the **Kibana** integration for From 308edeb594ea85d734b51d8818407564e2d39e38 Mon Sep 17 00:00:00 2001 From: DeDe Morton Date: Fri, 10 Mar 2023 13:10:21 -0800 Subject: [PATCH 6/9] Removing step about changing the output to point to the monitoring cluster --- docs/user/monitoring/monitoring-elastic-agent.asciidoc | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/user/monitoring/monitoring-elastic-agent.asciidoc b/docs/user/monitoring/monitoring-elastic-agent.asciidoc index 6a326efaf7c69..3757781b26cb1 100644 --- a/docs/user/monitoring/monitoring-elastic-agent.asciidoc +++ b/docs/user/monitoring/monitoring-elastic-agent.asciidoc @@ -62,9 +62,6 @@ new agent policy or **Existing hosts** to add it to an existing agent policy. . Click **Save and continue**. This step takes a minute or two to complete. When it's done, you'll have an agent policy that contains an integration for collecting monitoring data from {kib}. -. (Optional) If you're sending data to a monitoring cluster, edit the agent -policy, and under **Settings**, change the **Output for integrations** to the -output you created for the monitoring cluster. . If an {agent} is already assigned to the policy and deployed to the host where {kib} is running, you're done. Otherwise, you need to deploy an {agent}. To deploy an {agent}: From 311134f1271e39c8856f1e3738f0177c5417a95b Mon Sep 17 00:00:00 2001 From: dedemorton Date: Tue, 21 Mar 2023 18:24:40 -0700 Subject: [PATCH 7/9] Clarify security privileges needed to read monitoring data --- docs/user/monitoring/viewing-metrics.asciidoc | 17 +++++++---------- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git a/docs/user/monitoring/viewing-metrics.asciidoc b/docs/user/monitoring/viewing-metrics.asciidoc index da64fd8e5b65e..0aaf7ad6bd332 100644 --- a/docs/user/monitoring/viewing-metrics.asciidoc +++ b/docs/user/monitoring/viewing-metrics.asciidoc @@ -48,6 +48,11 @@ must provide a user ID and password so {kib} can retrieve the data. .. Create a user that has the `monitoring_user` {ref}/built-in-roles.html[built-in role] on the monitoring cluster. ++ +NOTE: Make sure the `monitoring_user` role has read privileges on `metrics-*` +indices. If it doesn't, create a new role with `read` and `read_cross_cluster` +index privileges on `metrics-*`, then assign the new role (along with +`monitoring_user`) to your user. .. Add the `monitoring.ui.elasticsearch.username` and `monitoring.ui.elasticsearch.password` settings in the `kibana.yml` file. @@ -70,16 +75,8 @@ remote monitoring cluster, you must use credentials that are valid on both the -- .. Create users that have the `monitoring_user` and `kibana_admin` -{ref}/built-in-roles.html[built-in roles]. -+ -**** -**Question for reviewers:** - -What do we recommend here for viewing data collected by Elastic Agent? Looks like the -monitoring_user role has read and read_cross_cluster on .monitoring-* and -metricbeat-* indices, not the ones created by the agent. - -**** +{ref}/built-in-roles.html[built-in roles]. If you created a new role with +read privileges on `metrics-*` indices, also assign that role to the users. . Open {kib} in your web browser. + From 2772ccd114e8960613635af0f5bc9661994a73ae Mon Sep 17 00:00:00 2001 From: dedemorton Date: Wed, 22 Mar 2023 11:54:54 -0700 Subject: [PATCH 8/9] Remove reviewer commments --- docs/user/monitoring/monitoring-metricbeat.asciidoc | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/docs/user/monitoring/monitoring-metricbeat.asciidoc b/docs/user/monitoring/monitoring-metricbeat.asciidoc index 3ad42475c671d..b6718c41d005a 100644 --- a/docs/user/monitoring/monitoring-metricbeat.asciidoc +++ b/docs/user/monitoring/monitoring-metricbeat.asciidoc @@ -15,18 +15,6 @@ image::user/monitoring/images/metricbeat.png[Example monitoring architecture] To learn about monitoring in general, see {ref}/monitor-elasticsearch-cluster.html[Monitor a cluster]. -**** -**Question for reviewers:** - -Is it still necessary to disable default collection? I didn't test this with -Metricbeat, but when I tested Elastic Agent + the Kibana integration, I did not -need to change any default settings. I did not need to set -monitoring.kibana.collection.enabled: false, and I didn't see -a monitoring.enabled setting. - -Question for Lisa C: Are these tagged regions used anywhere? -**** - . Disable the default collection of {kib} monitoring metrics. + + -- From 7fb5ee3ca630bf620361553d65125fbcfa0a3d4b Mon Sep 17 00:00:00 2001 From: Kevin Lacabane Date: Thu, 23 Mar 2023 18:16:36 +0100 Subject: [PATCH 9/9] fix typo in data stream name --- docs/user/monitoring/monitoring-troubleshooting.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user/monitoring/monitoring-troubleshooting.asciidoc b/docs/user/monitoring/monitoring-troubleshooting.asciidoc index 02141c2ccc69e..cf3148cf38352 100644 --- a/docs/user/monitoring/monitoring-troubleshooting.asciidoc +++ b/docs/user/monitoring/monitoring-troubleshooting.asciidoc @@ -57,7 +57,7 @@ See <>. . Confirm that there is monitoring data available at that URL. It is stored in indices such as `.monitoring-kibana-*` and `.monitoring-es-*` or -`metrics-kibana.stack_monitoring-*`, depending on which method is +`metrics-kibana.stack_monitoring.*`, depending on which method is used to collect monitoring data. At a minimum, you must have monitoring data for the {es} production cluster. Once that data exists, {kib} can display monitoring data for other products in the cluster.