Unify HTTP SSL, K probes and NodeJS tracer in a single tracer

[marctc]

This is a required step in order to reduce privileges required to run Beyla.
This PR unifies the different tracers used for non-Go programs into a generic tracer.

Fixes #1212 and #1213

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 82.12766% with 42 lines in your changes missing coverage. Please review.

Project coverage is 81.64%. Comparing base (8c3c9db) to head (fe61e4e).

Files with missing lines	Patch %	Lines
pkg/internal/ebpf/tracer_linux.go	41.66%	10 Missing and 4 partials ⚠️
pkg/internal/ebpf/instrumenter.go	83.33%	7 Missing and 4 partials ⚠️
pkg/internal/discover/attacher.go	79.41%	4 Missing and 3 partials ⚠️
pkg/internal/ebpf/generictracer/generictracer.go	95.19%	2 Missing and 3 partials ⚠️
pkg/internal/ebpf/gotracer/gotracer.go	0.00%	3 Missing ⚠️
pkg/internal/ebpf/logger/logger.go	0.00%	1 Missing ⚠️
pkg/internal/ebpf/watcher/watcher.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1215      +/-   ##
==========================================
- Coverage   81.89%   81.64%   -0.26%     
==========================================
  Files         137      135       -2     
  Lines       11489    11435      -54     
==========================================
- Hits         9409     9336      -73     
- Misses       1544     1561      +17     
- Partials      536      538       +2     

Flag	Coverage Δ
integration-test	60.47% <77.44%> (-0.55%)	⬇️
k8s-integration-test	58.91% <77.87%> (+0.41%)	⬆️
oats-test	36.54% <61.70%> (+0.11%)	⬆️
unittests	53.37% <0.00%> (+0.25%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mariomac]

Isn't "generic_tracer" too generic name? If we have to change this name to avoid other confunsion/duplicities, I would maybe choose a name that describes what instruments and where are the probes attached (kernel, lib...).

[marctc]

Isn't "generic_tracer" too generic name? If we have to change this name to avoid other confunsion/duplicities, I would maybe choose a name that describes what instruments and where are the probes attached (kernel, lib...).

Do you have any ideas? I can't think of anything better now

[grcevski]

Isn't "generic_tracer" too generic name? If we have to change this name to avoid other confunsion/duplicities, I would maybe choose a name that describes what instruments and where are the probes attached (kernel, lib...).

Do you have any ideas? I can't think of anything better now

I'd keep it as k_tracer or use generic tracer, maybe protocol_tracer? When you think about it, what the tracer does is detect telemetry signals at the protocol level, by using kprobes and uprobes to parse send/receive buffers. As a contrast to Go tracer, which injects Go uprobes to parts of the Go libraries.

[grcevski]

LGTM!

[mariomac]

🚢