Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS] Clarify monitoring dependencies #26229

Merged
merged 2 commits into from
Nov 27, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 25 additions & 1 deletion docs/monitoring/monitoring-troubleshooting.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -22,3 +22,27 @@ 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 {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 <<monitoring-settings-kb>>.

. 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.

. Set the time filter to “Last 1 hour”. When monitoring data appears in your
cluster, the page automatically refreshes with the monitoring summary.

19 changes: 6 additions & 13 deletions docs/monitoring/viewing-metrics.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -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.
+
Expand Down Expand Up @@ -91,15 +95,4 @@ Overview, Nodes, Indices, or Instances links. See <<xpack-monitoring>>.
[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 <<monitoring-settings-kb, Monitoring Settings in Kibana>>.

If you encounter problems, see <<monitor-troubleshooting,Troubleshooting monitoring>>.