| 1234567891011121314151617181920212223242526272829 | [[monitoring-troubleshooting]]== Troubleshooting monitoring++++<titleabbrev>Troubleshooting</titleabbrev>++++Use the information in this section to troubleshoot common problems and findanswers 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 createa ticket in thehttps://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. Forexample, use the <<cat-indices,cat indices>> command to verify thatthere is a `.monitoring-kibana*` index for your {kib} monitoring data and a`.monitoring-es*` index for your {es} monitoring data. If you are collectingmonitoring data by using {metricbeat} the indices have `-mb` in their names. Ifthe indices do not exist, review your configuration. For example, see<<monitoring-production>>.
 |