I have already used ELK 5.2 and i'm now testing ELK 5.6.7 (currently, the latest 5+ version).
When i'm automatically setting up my Elastic node, i configure the Kibana index-pattern.
Basically, I send some HTTP requests to the my elasticsearch. For example, for the index-pattern "syslog-*" i perform this kind of POST request:
In Kibana 5.2 i didn't encounter any error when my Elasticsearch indices were not existing (probably because this API was not part of this version).
Is there a way to disable this type of error on Kibana (through its configuration file for example) or any workaround to don't check that the indices exist in Elasticsearch ?
Thanks for your answer, but i guess that it's not the same "issue".
In fact, I can create index pattern even with non existing Elastic indices (at the opposite of the issue given in your link).
In my case, i would like to disable the error message ("No matching indices found: [...]") that is displayed when i have an index pattern but no data in Elastic, thus no indices.
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.