Open novohool opened 9 months ago
I will discuss that topic with the @open-telemetry/operator-approvers.
Could you go into more detail about what exactly you'd like to the operator to support? Are we talking about a separate CRD for the EBPF collector?
Could you go into more detail about what exactly you'd like to the operator to support? Are we talking about a separate CRD for the EBPF collector?
The current opentelemetry operator does not support opentelemetry ebpf. What we are talking about here is the support of operator crd for ebpf.
From what I understand, the EBPF stack is a set of applications which can ultimately emit metrics via OTLP. If we wanted to directly support this, I think we'd introduce a separate CRD for it, maybe a small embedded section in the collector CRD similar to how we want the target allocator to work. Either way, this would be a significant undertaking, and needs to be discussed during our next SIG meeting.
Component(s)
collector
Is your feature request related to a problem? Please describe.
kind: OpenTelemetryCollector ebpf network monitoring support https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/charts/opentelemetry-ebpf
Describe the solution you'd like
get network incoming/outcoming/dns info
Describe alternatives you've considered
add also add it's metrics to prometheus service.
Additional context
No response