mirror of
https://github.com/elastic/kibana.git
synced 2025-04-25 10:23:14 -04:00
## Summary Add Elastic Agent as another way to collect monitoring data. This work is tracked by https://github.com/elastic/observability-docs/issues/2602. There will be additional PRs to address changes required to monitoring docs for other stack components. TBH, it pains me a bit to see how many places users need to go to find info about stack monitoring, but fixing that problem is not in scope for these updates unfortunately. :-/ Please respond to questions addressed to reviewers. ### Checklist Delete any items that are not applicable to this PR. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md) ### To Do before merging - [x] Remove questions to reviewers. --------- Co-authored-by: Kevin Lacabane <klacabane@gmail.com>
67 lines
2.3 KiB
Text
67 lines
2.3 KiB
Text
[role="xpack"]
|
|
[[monitor-troubleshooting]]
|
|
= Troubleshooting monitoring in {kib}
|
|
++++
|
|
<titleabbrev>Troubleshooting</titleabbrev>
|
|
++++
|
|
|
|
Use the information in this section to troubleshoot common problems and find
|
|
answers for frequently asked questions related to the {kib} {monitor-features}.
|
|
|
|
[float]
|
|
== Cannot view the cluster because the license information is invalid
|
|
|
|
*Symptoms:*
|
|
|
|
The following error appears in a banner at the top of the screen in {kib} on the
|
|
*Stack Monitoring > Clusters* page:
|
|
`You can't view the "<my_cluster>" cluster because the license information is invalid.`
|
|
|
|
*Resolution:*
|
|
|
|
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]
|
|
== {filebeat} index is corrupt
|
|
|
|
*Symptoms:*
|
|
|
|
The *Stack Monitoring* application displays a Monitoring Request error indicating
|
|
that an illegal argument exception has occurred because fielddata is disabled on
|
|
text fields by default.
|
|
|
|
*Resolution*
|
|
|
|
. Stop all your {filebeat} instances.
|
|
. Delete indices beginning with `filebeat-$VERSION`, where `VERSION` corresponds
|
|
to the version of {filebeat} running.
|
|
. Restart all your {filebeat} instances.
|
|
|
|
|
|
[float]
|
|
== No monitoring data is visible in {kib}
|
|
|
|
*Symptoms:*
|
|
|
|
The *Stack 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.hosts` setting in the `kibana.yml` file. If you want to retrieve it
|
|
from a different monitoring cluster, set `monitoring.ui.elasticsearch.hosts`.
|
|
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-*` or
|
|
`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.
|
|
|
|
. Set the time filter to “Last 1 hour”. When monitoring data appears in your
|
|
cluster, the page automatically refreshes with the monitoring summary.
|
|
|