Fleet agent

[trudyc]

@mostlyjason
I was encountering similar problems on my RHEL8 hosts. I found a way to get the filebeat and metricbeat data to come through, and documented that in my post here:

Beats in elastic-agent reporting "failed to connect to backoff"

I found a work around, but still am working to find out why this was necessary. As noted earlier in the Elastic/Agent/data/elastic-agent-*/logs/default/filebeat-json.log file (and the metricbeat-json.log file) I was seeing this message repeating. {"log.level":"error","@timestamp":"2022-03-15T17:03:41.086Z","log.logger":"publisher_pipeline_output","log.origin":{"file.name":"pipeline/output.go","file.line":154},"message":"Failed to connect to backoff(elasticsearch(http://localhost:9200)): Get \"…

I plan to open a support ticket with Elastic to try to get an explanation for why this would be necessary.