My conclusion is right now this is not possible with Fleet Managed Agents, just standalone ones via dynamic inputs.
Found some issues about:
opened 01:57PM - 12 Jul 22 UTC
Team:Cloudnative-Monitoring
cloudnative-observability
### Context
Picking up context from https://github.com/elastic/beats/issues/238… 76
We want to enable users to monitor Kubernetes workloads through user-provided conditions on the fleet UI
### Problem definition
Elastic operators need to collect and ingest data from workloads that have a characteristic that is not necessarily aligned with the Kubernetes infrastructure.
<img width="498" alt="image" src="https://user-images.githubusercontent.com/39376769/195316666-626fde1d-ebc8-42e8-bb5f-7096d0085d0d.png">
### User outcome
Elastic operators can define the conditions that a workload which is to be monitored needs to meet in order for it to be observed. Workloads that meet the conditions defined by the Elastic Operator will have a frictionless experience that will not require further steps from the user side.
Solution hypothesis
We believe that providing Elastic operators with a conditions field in the fleet UI will enable them to decide which workloads need to be monitored
### Dependency on Fleet UI
Kibana issue: https://github.com/elastic/kibana/issues/108525
opened 12:17PM - 30 Jul 20 UTC
Team:Elastic-Agent-Control-Plane
discuss
I'd like to ask for your recommendation for users that prefer to run Elastic Age… nt in the container (let's say due to security reasons).
Let's discuss the scenario:
The integrated product is nginx running in a container. It produces logs stored locally in the image and which are rotated. As the agent is running in a different container, it can't simply access produced logs.
What is your recommendation in this particular case? Should the user expose somehow log files? Mirror them?
Background -
I had an interesting talk with @ycombinator about possibilites and testing scenarios and it looks that we will both have to nail this problem (force agent to watch logs produced in a different container).
Would be great if someone from Elastic can validate this.
Gustavo