Earlier this week I upgraded from ES/Kibana 7.16.2 to 7.17.5. My setup consisted of a Production ES cluster and a separate single server as the monitoring cluster. The production cluster would push info to the monitoring cluster via exporter.
Symptoms: After upgrading I now get a screen asking if I'd like to setup metric beat or continue doing legacy. I started out by trying to do the legacy option, but it wasn't recognizing that anything was in the .monitoring-es-7-*. Kibana would also complain that the kibana node didn't have things like xpack.monitoring.collection.enabled: true. Which makes me think it wants to monitor itself and I don't want that.
Secondary Attempt: After beating my head with the legacy setup I decided to bread down and install metric beat on the production cluster (and the kibana node which I don't think I need). I set everything up so that the production cluster pushes elastic and system module data to the kibana node and I can see the data in a metricbeat-* index. I can even go into the dashboards section and view the graphs from the system module. However I want the data from the ES module.
After installing metric beat I went back into the monitoring tab of Kibana and tried navigating through the 'Setup Monitoring with Metric Beat'. The nodes from my production cluster don't show up. Clicking the 'Setup monitoring for a new node' and following all the steps is fine until I get to the bottom section 'Monitoring status' and the message 'No monitoring data detected, but we’ll continue checking.'
Quick tidbits about the system that I don't know where to put into this:
- No security features enabled
- The Kibana node and the Production cluster have different cluster UUIDs as expected