Open belimawr opened 1 year ago
Pinging @elastic/elastic-agent (Team:Elastic-Agent)
Hi! We just realized that we haven't looked into this issue in a while. We're sorry!
We're labeling this issue as Stale
to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1
.
Thank you for your contribution!
When the Elastic-Agent computes Unit Configs and send them to Beats, there might be some values in the format
${var}
in the config, Beats tries to process them as environment variables and will fail to start the input if they cannot be resolved.An example of where this can happen is when using Traeffik HTTP Middleware: https://doc.traefik.io/traefik/middlewares/http/redirectregex/.
The
BeatV2Manager
should escape all configurations received by the Elastic-Agent as they're ready to use and any variable replacement will be done by the Elastic-Agent, not the Beat.For some reasoning/discussion about this solution, see the related issue.
Steps to reproduce
1. Deploy a container with the following docker-compose file
2. Deploy Elastic-Agent with Docker integration configured to collect logs
3. On the host run
elastic-agent status --output=json
You'll see the error:
4. If you inspect the container `docker inspect you'll see the label
Related issues
For confirmed bugs, please report: