Hi, I'm trying to ship Fortigate300E Log to my Elasticstack with topo: Fortigate syslog port 514 -> Filebeat (fortinet module) -> Elasticsearch -> Kibana. I have 2 question:
First, is it possible?
And when I run filebeat filebeat setup -e
with config (below comment) , then it error Exiting: 1 error: error loading config file: invalid config: yaml: line 21: did not find expected key
I have check and not find the cause. Hope to get help. Thanks
[root@localhost ~]# filebeat setup -e
2020-12-14T13:01:33.488+0700 INFO [index-management] idxmgmt/std.go:2 61 Auto ILM enable success.
2020-12-14T13:01:33.489+0700 INFO [index-management.ilm] ilm/std.go:139 d o not generate ilm policy: exists=true, overwrite=false
2020-12-14T13:01:33.489+0700 INFO [index-management] idxmgmt/std.go:2 74 ILM policy successfully loaded.
2020-12-14T13:01:33.489+0700 INFO [index-management] idxmgmt/std.go:4 07 Set setup.template.name to '{filebeat-7.10.1 {now/d}-000001}' as ILM is enabled.
2020-12-14T13:01:33.489+0700 INFO [index-management] idxmgmt/std.go:4 12 Set setup.template.pattern to 'filebeat-7.10.1-*' as ILM is enabled.
2020-12-14T13:01:33.489+0700 INFO [index-management] idxmgmt/std.go:4 46 Set settings.index.lifecycle.rollover_alias in template to {filebeat-7.1 0.1 {now/d}-000001} as ILM is enabled.
2020-12-14T13:01:33.489+0700 INFO [index-management] idxmgmt/std.go:4 50 Set settings.index.lifecycle.name in template to {filebeat {"policy":{"p hases":{"hot":{"actions":{"rollover":{"max_age":"30d","max_size":"50gb"}}}}}}} a s ILM is enabled.
2020-12-14T13:01:33.490+0700 INFO template/load.go:183 Existing templat e will be overwritten, as overwrite is enabled.
2020-12-14T13:01:34.900+0700 INFO template/load.go:117 Try loading temp late filebeat-7.10.1 to Elasticsearch
2020-12-14T13:01:35.153+0700 INFO template/load.go:109 template with na me 'filebeat-7.10.1' loaded.
2020-12-14T13:01:35.153+0700 INFO [index-management] idxmgmt/std.go:2 98 Loaded index template.
2020-12-14T13:01:35.155+0700 INFO [index-management] idxmgmt/std.go:3 09 Write alias successfully generated.
Index setup finished.
Loading dashboards (Kibana must be running and reachable)
2020-12-14T13:01:35.155+0700 INFO kibana/client.go:119 Kibana url: http ://localhost:5601
2020-12-14T13:01:36.463+0700 INFO [add_cloud_metadata] add_cloud_metadata/add_cloud_metadata.go:89 add_cloud_metadata: hosting provider type not detected.
2020-12-14T13:01:36.947+0700 INFO kibana/client.go:119 Kibana url: http://localhost:5601
2020-12-14T13:02:45.821+0700 INFO instance/beat.go:815 Kibana dashboards successfully loaded.
Loaded dashboards
2020-12-14T13:02:45.821+0700 WARN [cfgwarn] instance/beat.go:556 DEPRECATED: Setting up ML using Filebeat is going to be removed. Please use the ML app to setup jobs. Will be removed in version: 8.0.0
Setting up ML using setup --machine-learning is going to be removed in 8.0.0. Please use the ML app instead.
See more: https://www.elastic.co/guide/en/machine-learning/current/index.html
2020-12-14T13:02:45.822+0700 INFO eslegclient/connection.go:99 elasticsearch url: http://localhost:9200
2020-12-14T13:02:45.823+0700 INFO [esclientleg] eslegclient/connection.go:314 Attempting to connect to Elasticsearch version 7.10.0
2020-12-14T13:02:45.824+0700 INFO kibana/client.go:119 Kibana url: http://localhost:5601
2020-12-14T13:02:45.860+0700 WARN fileset/modules.go:421 X-Pack Machine Learning is not enabled
2020-12-14T13:02:45.862+0700 ERROR instance/beat.go:956 Exiting: 1 error: error loading config file: invalid config: yaml: line 21: did not find expected key
Exiting: 1 error: error loading config file: invalid config: yaml: line 21: did not find expected key