30 lines
1.2 KiB
Plaintext
30 lines
1.2 KiB
Plaintext
|
[[monitoring-troubleshooting]]
|
|||
|
|
== Troubleshooting monitoring
|
|||
|
|
++++
|
|||
|
|
<titleabbrev>Troubleshooting</titleabbrev>
|
|||
|
|
++++
|
|||
|
|
|
|||
|
|
Use the information in this section to troubleshoot common problems and find
|
|||
|
|
answers for frequently asked questions. See also
|
|||
|
|
{logstash-ref}/monitoring-troubleshooting.html[Troubleshooting monitoring in {ls}].
|
|||
|
|
|
|||
|
|
For issues that you cannot fix yourself … we’re here to help.
|
|||
|
|
If you are an existing Elastic customer with a support contract, please create
|
|||
|
|
a ticket in the
|
|||
|
|
https://support.elastic.co/customers/s/login/[Elastic Support portal].
|
|||
|
|
Or post in the https://discuss.elastic.co/[Elastic forum].
|
|||
|
|
|
|||
|
|
*Symptoms*:
|
|||
|
|
There is no information about your cluster on the *Stack Monitoring* page in
|
|||
|
|
{kib}.
|
|||
|
|
|
|||
|
|
*Resolution*:
|
|||
|
|
Check whether the appropriate indices exist on the monitoring cluster. For
|
|||
|
|
example, use the <<cat-indices,cat indices>> command to verify that
|
|||
|
|
there is a `.monitoring-kibana*` index for your {kib} monitoring data and a
|
|||
|
|
`.monitoring-es*` index for your {es} monitoring data. If you are collecting
|
|||
|
|
monitoring data by using {metricbeat} the indices have `-mb` in their names. If
|
|||
|
|
the indices do not exist, review your configuration. For example, see
|
|||
|
|
<<monitoring-production>>.
|
|||
|
|
|