if your Filebeat is installed on the same elasticsearch server, you can follow those instructions with no modification.
Otherwise, if you have your template on a remote machine, transfer the file filebeat.template.json to your server, change to directory where you had copy the file and load the template so (my elasticsearch server is a CentOs 7):
and confirm that the template "filebeat" is there.
I am new in this elastic world and I know that templates can also be referenced directly in other ways and configuration.
but the above example apparently worked for me.
Template is loaded but facing issue while loading dashboard to Kibana ,
2017/11/22 06:43:41.482479 beat.go:625: CRIT Exiting: Error importing Kibana dashboards: fail to create the Elasticsearch loader: Elasticsearch output is not configured/enabled
Exiting: Error importing Kibana dashboards: fail to create the Elasticsearch loader: Elasticsearch output is not configured/enabled
i have mention required setting in filebeat and i am using filebeat-6.0.0 version .
As for dashboards etc. I had used the standard that were mentioned here:
(follow instructions)
I do not know if now filebeat is shipped with up-to-date and targeted dashboards. As for Filebeat in general, I have not investigated those loaded dashboards yet.
Just a note:have you configured the logstash part output.conf ?
And also all input and filter required...
Unfortunately, Filebeat 6.0 is not able to load dashboards without configuring the Elasticsearch output.
In 6.1 a new option setup.dashboards.always_kibana is introduced to solve this problems.
If you cannot upgrade to 6.1, you could load them using the Kibana API:
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.