Okay, so I've ran into this "famous" issue where the index pattern cannot be located. This was a fresh install, although I was experimenting a bit with the index patterns. At one moment some visualizations in the Metricbeat System overview wasn't working (number of hosts and host histogram). In all this, the actual index pattern of course exists, so you are pulling your hairs.
Elasticsearch 7.4.0, installed using the ansible scripts
Kibana 7.4.0, install from repository
- I've installed the metricbeat index and dashboard using the --setup option. Everything works
- Go to Kibana > management > kibana > index patterns
- select the metricbeat-* pattern
- delete it
- Re-create the same index pattern
- Go to the system overview dashboard and you will notice that several visualizations are broken.
It's an absolute nightmare to figure out which visualizations are broken. There is no way to navigate to the visualization to figure out which one is broken. From a working visualization you can edit and click to go to that specific visualization. The name is missing, the edit visualization is missing. I will write up a reply with a way to figure out which visualization is broken.
The problem lies in the fact that the old index ID is not there any more. So you need to update the object itself.
- Figure out which object is broken
- Go to management > kibana > saved objects > search for object
- Click on inspect
- In the references section you will find "id": "metricbeat-*",
- Change this to the new ID of the index pattern, for example "id": "16844e00-0530-11ea-ab45-8b85a0a14acf",
- How can I update the cached value that is referenced in the references section of the object. Somewhere in elastic there is a link stored between the index pattern and the actual UUID. Updating this value should save me a lot of hunting individual objects and changing them one by one.
- We need to have a better way of tracking down the objects from within the dashboard. To know that something is broken is fine, however, not having a method to quickly navigate to the broken object is kind of frustrating