Index "doesn't exist" but Kibana offers it as a replacement?

Hi Folks: Newbie here. Any guesses on this one? This happens while importing a JSON full of searches and visualizations. Note the package we import has worked fine on standalone ELK; this is Elastic Cloud running ELK 5.6.7 if that helps anyone:

In Kibana 5.5 we moved to using unique ID's for the patterns. Previously, they would be based on the actual pattern being used. This allowed you to re-create the pattern and import any objects with references to it. Since the exports don't contain the index pattern, when you re-create the index pattern it will contain a unique ID. This modal allows you to tell the importer what index pattern you would like to use for those objects.

Thanks Tyler; that explains it!

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.