With an attached connector, the collector correctly will add a "site-service" process to act as a placeholder for the real workload, but it is not associating network traffic with it, and the connector API endpoint references process IDs that do not exist.
Expected
Attached connectors should work like connectors using a host name instead of a selector. Flow traffic should be associated with the site-service process, and the connector api should correctly reference the site service as well.
Describe the bug
With an attached connector, the collector correctly will add a "site-service" process to act as a placeholder for the real workload, but it is not associating network traffic with it, and the connector API endpoint references process IDs that do not exist.
Expected
Attached connectors should work like connectors using a host name instead of a selector. Flow traffic should be associated with the site-service process, and the connector api should correctly reference the site service as well.