3 ms·
With ebpf-exporter it is not possible to implement complex logic, such as converting the PID of each TCP connection into a container name and the destination IP
by nikolay_sivko 4y ago
With ebpf-exporter it is not possible to implement complex logic, such as converting the PID of each TCP connection into a container name and the destination IP into a real IP according to the conntrack table.
- alexeldeib 4y agoThis seems like a limitation that could be lifted instead of introducing a separate product (disclaimer: familiar with ebpf exporter but haven’t dug into OP). Iirc ebpf exporter had some limitations, but they weren’t fundamental. However it was also fairly light, so maybe another tool is just the right solve.
- nikolay_sivko 4y agoCoroot's agent collects data from various sources to cover all aspects of container behavior. Ebpf-exporter perfectly solves the problem of running custom ebpf programs and turning their output into metrics, but using it as a foundation for more specific solutions doesn't seem reasonable