We are dealing with the same situation as the one described above, that is, we importe some Kibana visualization dashboards that display errors simply because de fields they rely on have not been generated yet by the applications whose data we are trying to visualize with Kibana.
I think that the propossed solution could be titled something like "Stimulate the APIs for all the features before the dashboards can work" and I was wondering if this solution is still the best one or there is a better alternative to deal with this issue.
I don't think there is a current solution to this other than having your mapping already created for your index that the visualizations are targeting. If you still have the ES instance where those visualizations were created, you can export the index template from there and import them in the new one, then the fields won't be missing from the index pattern even though you have no data yet containing that field.
Just to clarify, when you talk about "[...] export the index template where those visualizations were created [...]" are you making reference to something like:
"./metricbeat export template > metricbeat.template.json" to export and them, a similar process to import it?
I have been googling and looking for documentation regarding how to export an index template but, am not sure if what I have found [link] is that right documentation or not.
If you are using metricbeat as the source of your data you do not need to do anything other than just starting Metricbeat connected to your new ES instance. It automatically creates it's own mapping.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.