Hi I'm struggeling in setting up filebeat to work with elastic cloud instance.
all I'm trying to do is enabling a module( without changing any config, yet) and uplouding dashboard setting from filebeat to elastic cloud instance.
I could enable any module successfully but when I issue filebeat setup command I get following error:
filebeat setup
Overwriting ILM policy is disabled. Set `setup.ilm.overwrite: true` for enabling.
Index setup finished.
Loading dashboards (Kibana must be running and reachable)
Exiting: 1 error: error loading index pattern: returned 408 to import file: <nil>. Response: {"statusCode":408,"error":"Request Time-out","message":"Request Time-out"}
it seems it is not a real connection issue because I tried different machines with filebeat but the result is the same. even I tried another new instance but the error still exist.
On the elastic cloud, Kibana is operational with green status also
I'm using filebeat 7.12 with elastic cloud instances running 7.12
detail of the error:
2021-04-11T22:53:06.080+0300 INFO instance/beat.go:304 Setup Beat: filebeat; Version: 7.12.0
2021-04-11T22:53:06.081+0300 INFO [index-management] idxmgmt/std.go:184 Set output.elasticsearch.index to 'filebeat-7.12.0' as ILM is enabled.
2021-04-11T22:53:06.083+0300 INFO eslegclient/connection.go:99 elasticsearch url: https://4e4a0e341f8443b0xxxxxxxxxxxx-central-1.aws.cloud.es.io:443
2021-04-11T22:53:06.084+0300 INFO [publisher] pipeline/module.go:113 Beat name: test-linux
2021-04-11T22:53:06.105+0300 INFO eslegclient/connection.go:99 elasticsearch url: https://4e4a0e341f8443xxxxxxxxxxxxx.eu-central-1.aws.cloud.es.io:443
2021-04-11T22:53:07.706+0300 INFO [esclientleg] eslegclient/connection.go:314 Attempting to connect to Elasticsearch version 7.12.0
Overwriting ILM policy is disabled. Set `setup.ilm.overwrite: true` for enabling.
2021-04-11T22:53:07.869+0300 INFO [index-management] idxmgmt/std.go:261 Auto ILM enable success.
2021-04-11T22:53:07.990+0300 INFO [index-management.ilm] ilm/std.go:139 do not generate ilm policy: exists=true, overwrite=false
2021-04-11T22:53:07.990+0300 INFO [index-management] idxmgmt/std.go:274 ILM policy successfully loaded.
2021-04-11T22:53:07.991+0300 INFO [index-management] idxmgmt/std.go:407 Set setup.template.name to '{filebeat-7.12.0 {now/d}-000001}' as ILM is enabled.
2021-04-11T22:53:07.992+0300 INFO [index-management] idxmgmt/std.go:412 Set setup.template.pattern to 'filebeat-7.12.0-*' as ILM is enabled.
2021-04-11T22:53:07.992+0300 INFO [index-management] idxmgmt/std.go:446 Set settings.index.lifecycle.rollover_alias in template to {filebeat-7.12.0 {now/d}-000001} as ILM is enabled.
2021-04-11T22:53:07.992+0300 INFO [index-management] idxmgmt/std.go:450 Set settings.index.lifecycle.name in template to {filebeat {"policy":{"phases":{"hot":{"actions":{"rollover":{"max_age":"30d","max_size":"50gb"}}}}}}} as ILM is enabled.
2021-04-11T22:53:08.128+0300 INFO template/load.go:183 Existing template will be overwritten, as overwrite is enabled.
2021-04-11T22:53:09.830+0300 INFO template/load.go:117 Try loading template filebeat-7.12.0 to Elasticsearch
2021-04-11T22:53:14.534+0300 INFO template/load.go:109 template with name 'filebeat-7.12.0' loaded.
2021-04-11T22:53:14.538+0300 INFO [index-management] idxmgmt/std.go:298 Loaded index template.
2021-04-11T22:53:14.671+0300 INFO [index-management] idxmgmt/std.go:309 Write alias successfully generated.
Index setup finished.
Loading dashboards (Kibana must be running and reachable)
2021-04-11T22:53:14.697+0300 INFO kibana/client.go:119 Kibana url: https://9b02983a41db488fb5xxxxxxxxxxxxxx.eu-central-1.aws.cloud.es.io:443
2021-04-11T22:53:18.165+0300 INFO kibana/client.go:119 Kibana url: https://9b02983a41db488fb5xxxxxxxxxxxxx.eu-central-1.aws.cloud.es.io:443
2021-04-11T22:53:34.894+0300 ERROR instance/beat.go:971 Exiting: 1 error: error loading index pattern: returned 408 to import file: <nil>. Response: {"statusCode":408,"error":"Request Time-out","message":"Request Time-out"}
Exiting: 1 error: error loading index pattern: returned 408 to import file: <nil>. Response: {"statusCode":408,"error":"Request Time-out","message":"Request Time-out"}