I was upgrading the EKS version to 1.15 and after I upgrade the coreDNS version to 1.6.6. I got an error log from the filebeat
2020-06-20T20:00:43.298Z WARN transport/tcp.go:53 DNS lookup failure "logstash-collection-headless.etl.svc.cluster.local": lookup logstash-collection-headless.etl.svc.cluster.local: no such host
2020-06-20T20:00:44.299Z ERROR pipeline/output.go:121 Failed to publish events: lookup logstash-collection-headless.etl.svc.cluster.local: no such host
2020-06-20T20:00:44.299Z INFO pipeline/output.go:95 Connecting to backoff(tcp://logstash-collection-headless.etl.svc.cluster.local:5044)
2020-06-20T20:00:44.340Z INFO pipeline/output.go:105 Connection to backoff(tcp://logstash-collection-headless.etl.svc.cluster.local:5044) established
What might be causing this error. Any other application can easily ping to the logstash application
The configuration for filebeat is
path.data: /usr/local/httpd/logs/filebeat-data
filebeat.inputs:
- type: log
paths:
- /usr/local/httpd/logs/fragment.log*
close_inactive: 1h
close_renamed: false
close_removed: false
fields:
log_type: fragment
fields_under_root: true
logging.level: info
logging.to_files: true
logging.files:
path: /var/log/filebeat
name: filebeat
keepfiles: 7
permissions: 0644
output.logstash:
hosts: [ "${LOGSTASH_URL}" ]
ttl: 1s
pipelining: 0
processors:
- drop_fields:
fields: ["beat", "host", "input", "prospector"]
xpack.monitoring:
enabled: true
elasticsearch:
hosts: ["${ELASTICSEARCH_URL}"]
protocol: "http"
name: ${NODE_NAME}
Environment for filebeat
env:
- name: "LOGSTASH_URL"
value: "logstash-collection-headless.etl.svc.cluster.local:5044"