From 612384c295be3b3fe4665552feeb3927d43a5af0 Mon Sep 17 00:00:00 2001 From: lcawl Date: Mon, 26 Nov 2018 16:17:28 -0800 Subject: [PATCH 1/2] [DOCS] Clarify monitoring dependencies --- .../monitoring-troubleshooting.asciidoc | 27 ++++++++++++++++++- docs/monitoring/viewing-metrics.asciidoc | 19 +++++-------- 2 files changed, 32 insertions(+), 14 deletions(-) diff --git a/docs/monitoring/monitoring-troubleshooting.asciidoc b/docs/monitoring/monitoring-troubleshooting.asciidoc index 53899c71dc91c..449acc43a3d21 100644 --- a/docs/monitoring/monitoring-troubleshooting.asciidoc +++ b/docs/monitoring/monitoring-troubleshooting.asciidoc @@ -6,7 +6,7 @@ ++++ Use the information in this section to troubleshoot common problems and find -answers for frequently asked questions related to {monitoring}. +answers for frequently asked questions related to the {kib} {monitor-features}. [float] === Cannot view the cluster because the license information is invalid @@ -22,3 +22,28 @@ The following error appears in a banner at the top of the screen in {kib} on the You cannot monitor a version 6.3 or later cluster from {kib} version 6.2 or earlier. To resolve this issue, upgrade {kib} to 6.3 or later. See {stack-ref}/upgrading-elastic-stack.html[Upgrading the {stack}]. + +[float] +=== No monitoring data is visible in {kib} + +*Symptoms:* + +The *Monitoring* page in {kib} is empty. + +*Resolution:* + +. Confirm that {kib} is seeking monitoring data from the appropriate URL. By +default, data is retrieved from the cluster specified in the `elasticsearch.url` +setting in the `kibana.yml` file. If you want to retrieve it from a different +monitoring cluster, set `xpack.monitoring.elasticsearch.url`. See +<>. + +. Confirm that there is monitoring data available at that URL. Depending on +which method you use to collect it and which product version you're using, it is +stored in either `.monitoring-*` or `metricbeat-*` indices. 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/monitoring/viewing-metrics.asciidoc b/docs/monitoring/viewing-metrics.asciidoc index f2f1b7b971711..dca82ec1a5f45 100644 --- a/docs/monitoring/viewing-metrics.asciidoc +++ b/docs/monitoring/viewing-metrics.asciidoc @@ -7,7 +7,11 @@ After you collect monitoring data for one or more products in the {stack}, you can configure {kib} to retrieve that information and display it in on the -*Monitoring* page. +*Monitoring* page. + +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. . Identify where to retrieve monitoring data from. + @@ -91,15 +95,4 @@ Overview, Nodes, Indices, or Instances links. See <>. [role="screenshot"] image::images/monitoring-dashboard.png[Monitoring dashboard] -If {kib} can't activate monitoring, here are some things to do: - -* If you don't have permission to activate monitoring, -contact your system administrator. - -* If {kib} can't find monitoring data, set the time filter to -“Last 1 hour”. When monitoring data appears in your cluster, the page -automatically refreshes with the monitoring summary. - -* Check your `xpack.monitoring.elasticsearch.url` setting. -See <>. - +If you encounter problems, see <>. From 6c03fb9b0a2aed27e3e08ffea87d18ec4fa9f707 Mon Sep 17 00:00:00 2001 From: lcawl Date: Tue, 27 Nov 2018 11:05:00 -0800 Subject: [PATCH 2/2] [DOCS] Addressed feedback --- .../monitoring-troubleshooting.asciidoc | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/docs/monitoring/monitoring-troubleshooting.asciidoc b/docs/monitoring/monitoring-troubleshooting.asciidoc index 449acc43a3d21..f5ea95ffab7a8 100644 --- a/docs/monitoring/monitoring-troubleshooting.asciidoc +++ b/docs/monitoring/monitoring-troubleshooting.asciidoc @@ -32,15 +32,14 @@ The *Monitoring* page in {kib} is empty. *Resolution:* -. Confirm that {kib} is seeking monitoring data from the appropriate URL. By -default, data is retrieved from the cluster specified in the `elasticsearch.url` -setting in the `kibana.yml` file. If you want to retrieve it from a different -monitoring cluster, set `xpack.monitoring.elasticsearch.url`. See -<>. - -. Confirm that there is monitoring data available at that URL. Depending on -which method you use to collect it and which product version you're using, it is -stored in either `.monitoring-*` or `metricbeat-*` indices. At a minimum, you +. Confirm that {kib} is seeking monitoring data from the appropriate {es} URL. +By default, data is retrieved from the cluster specified in the +`elasticsearch.url` setting in the `kibana.yml` file. If you want to retrieve it +from a different monitoring cluster, set `xpack.monitoring.elasticsearch.url`. +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.