Filebeat DNS resolution fail


I have encountered similar issue as in this thread: DNS lookup failure "elasticsearch":

Unfortunatelly the filebeat is not able to resolve elasticsearch name.

2020-03-17T16:01:06.506Z ERROR pipeline/output.go:100 Failed to connect to backoff(elasticsearch(https://quickstart-es-http:9200)): Get https://quickstart-es-http:9200: lookup quickstart-es-http on server misbehaving

2020-03-17T16:01:06.506Z INFO pipeline/output.go:93 Attempting to reconnect to backoff(elasticsearch(https://quickstart-es-http:9200)) with 33 reconnect attempt(s)

2020-03-17T16:01:06.506Z INFO [publisher] pipeline/retry.go:196 retryer: send unwait-signal to consumer

2020-03-17T16:01:06.506Z INFO [publisher] pipeline/retry.go:198 done

2020-03-17T16:01:06.506Z INFO [publisher] pipeline/retry.go:173 retryer: send wait signal to consumer

2020-03-17T16:01:06.506Z INFO [publisher] pipeline/retry.go:175 done

2020-03-17T16:01:14.513Z WARN transport/tcp.go:52 DNS lookup failure "quickstart-es-http": lookup quickstart-es-http on server misbehaving

Curl to es from different POD works fine:

curl -u "elastic:password" -k "https://quickstart-es-http:9200"
  "name" : "quickstart-es-default-0",
  "cluster_name" : "quickstart",
  "version" : {
    "number" : "7.6.1",

elastic deployment:
filebeat deployment:

Any ideas please?

Thank you!

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.