thiagoftsm

@Ferroin I was taking a look in the Actions to verify the final result of CI, and I observed an unexpected result: ```sh bash-5.2$ rpm2targz netdata-plugin-ebpf-code-1.36.0-1.el8.x86_64.rpm bash-5.2$ rpm2targz netdata-plugin-ebpf-1.36.0-1.el8.x86_64.rpm bash-5.2$...

> > @Ferroin I was taking a look in the Actions to verify the final result of CI, and I observed an unexpected result: > > ```shell > > bash-5.2$...

Hello @nodiscc , Thank you for your feedback. We are now working with sockets again, and we are going to consider everything you wrote to improve. Best regards!

Yes, it is possible. I can isolate code from the collector that loads an eBPF program and unload it. Case everything goes fine, we know it is running like we...

I agree. I will only copy the code from the agent to this test.

> I _think_ your test program requires a real Machine with the proper Kernel options enabled to work thinking The requirements were written on issue https://github.com/netdata/netdata/issues/7771, it is necessary to...

I was testing now the libraries that were made in our CI and I detected that the final file `artifacts.zip` is compressing a symbolic link instead a shared library.

I only rebased PR.

@stelfrag this PR was only rebased.

> Mentioning this here as discussed in the sync: > > Because the changes to the network viewer plugin involve new dependencies on code from the kernel-collector and ebpf CO-RE...