-
Notifications
You must be signed in to change notification settings - Fork 8
Description
After deploying helm elastiflow, the log output is as follows:
{"level":"info","ts":"2025-01-04T00:03:46.818Z","logger":"flowcoll.bootstrapper[elasticsearch]","caller":"elasticsearch/bootstrap.go:163","msg":"index template insert process is enabled"} {"level":"error","ts":"2025-01-04T00:03:46.819Z","logger":"flowcoll.bootstrapper[elasticsearch]","caller":"elasticsearch/bootstrap.go:148","msg":"failed to bootstrap elasticsearch. retrying...","code":"elasticsearch/bootstrap-failure","reason":"error while creating default ilm policy: error while checking if ilm policy exists: error while checking ilm policy 'elastiflow' exists: Get \"http://127.0.0.1:9200/_ilm/policy/elastiflow\": dial tcp 127.0.0.1:9200: connect: connection refused","stacktrace":"github.com/elastiflow/flowcoll/pkg/outputs/elasticsearch.(*Bootstrap).Run\n\t/app/pkg/outputs/elasticsearch/bootstrap.go:148\ngithub.com/elastiflow/flowcoll/pkg/outputs/elasticsearch.NewInstantiatorRegistration.newCreateInstanceFunc.func1\n\t/app/pkg/outputs/elasticsearch/instance_registration.go:159\ngithub.com/elastiflow/go-env-conf/instantiator.(*Instantiator).Run\n\t/go/pkg/mod/github.com/elastiflow/[email protected]/instantiator/instantiator.go:78\ngithub.com/elastiflow/flowcoll/pkg/apps/unified_flowcoll.(*App).Run\n\t/app/pkg/apps/unified_flowcoll/app.go:156\nmain.main\n\t/app/cmd/flowcoll/main.go:108\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:271"}
I believe there is a missing field to indicate the elasticsearch connection service
As a future improvement, they could customize the helm to include the field EF_OUTPUT_ELASTICSEARCH_ADDRESSES