In elastic/beats#35135 (comment) the initial design of the shipper Filebeat input was finalized. One of the decisions was that each shipper input unit would implement its own gRPC server provisioned with a separate unix socket. Modify how the agent provisions the shipper to create a unix socket per input unit, instead of a single unix socket per shipper process.
We will need to decide what the naming convention for these unix sockets should be, considering that they must be unique per component that connects to the shipper and also that there can be multiple instances of a shipper. As outputs are added and removed from an agent policy over time the number of running shipper processes changes and the provisioned unix sockets must be removed in sync with this.
In elastic/beats#35135 (comment) the initial design of the shipper Filebeat input was finalized. One of the decisions was that each shipper input unit would implement its own gRPC server provisioned with a separate unix socket. Modify how the agent provisions the shipper to create a unix socket per input unit, instead of a single unix socket per shipper process.
We will need to decide what the naming convention for these unix sockets should be, considering that they must be unique per component that connects to the shipper and also that there can be multiple instances of a shipper. As outputs are added and removed from an agent policy over time the number of running shipper processes changes and the provisioned unix sockets must be removed in sync with this.