Michael Montgomery

run/e2e-tests tags=beat

run/e2e-tests tags=beat

> All that is ingested are the sidecars own logs. I'm working through this... seeing odd issue where something is listening on 5066, even though I am disabling this http...

metricbeat, and filebeat (or any 2x beats) running on the same host, listening on `127.0.0.1:5066` seem to be the cause of this... I'm investigating a solution. ``` metricbeat-beat-metricbeat-4bs56 2/3 CrashLoopBackOff...

> metricbeat, and filebeat (or any 2x beats) running on the same host, listening on `127.0.0.1:5066` seem to be the cause of this... I'm investigating a solution. As I suspected,...

@barkbay I don't currently have a solution to this problem. I'll document here some potential (partial) solutions here that I've been working through, but none of them fully stop the...

@barkbay unix sockets/windows pipes appear to be a valid option, which could be named according to namespace/name, and solve this problem: https://www.elastic.co/guide/en/beats/metricbeat/current/http-endpoint.html. I'll do some testing and see what comes...

 Beats stack monitoring now works over unix sockets, which solves the issues where we were getting port conflicts on host network.

run/e2e-tests tags=beat

> This looks good! I'm testing with this [manifest](https://gist.github.com/thbkrkr/10094ceca3fc6f148b5253223f8f678b) and I get a socket permission error for Filebeat: > > ```json > { > "log.level": "error", > "@timestamp": "2022-09-09T13:40:34.362Z", >...