Do you have any data loaded into Elasticsearch? Check this by accessing the URL http://localhost:9200/_cat/indices. Change localhost to the IP of your elasticsearch instance (if you are not running everything locally). Do you see your index in the results? Can the server running your kibana instance execute the same URL?
Did you change the Elasticsearch port? The default is 9200. If this changed than the kibana configuration file will need to be updated to the new value.
If you have data loaded in Elasticsearch and the machine running kibana can access Elasticsearch then kibana should be able to access the index pattern. Enter the index name into the Index name or pattern field.
So, I tried to follow the same process (above) with metricbeat... results:
a) the dashboards deploy
b) the metricbeat-* index shows in the Index Patterns, but I still get the errpr: No matching indices found: No indices match pattern "metricbeat-*"
I feel like I'm missing a step to close the deal - what am I missing?
It is not evident to me what I'm missing. It would be great if there was a step-by-step when you run into this type of issue. Thanks for everyone's assistance.
So, I figured out the process to get indexes to load. On to integrating logs via filebeat locally with logstash. I will post my process & findings when done.
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.