GitHub user hpvd added a comment to the discussion: Monitor/Analyse Pulsar without external instrumentation (eBPF)
just to further clarify and detail: BPF started with the use case of filtering network packets, but has since extended beyond that to cover a range of system calls. This makes eBPF a very interesting technology for observability use cases, as it offers a path for extracting telemetry data without modifying the application code. With that, eBPF offers a new way of achieving auto-instrumentation. eBPF can also work across different types of traffic, which serves the goal of unified observability. For example, you may use eBPF to collect full body request traces, database queries, HTTP requests or gRPC streams. You can also use eBPF to collect system metrics about resource utilization such as CPU usage or bytes sent, which can serve to calculate statistics, as well as profiling data to understand how many resources each function consumes. This sort of hardware or system information is much harder to access when instrumenting with agents or service mesh, which gives eBPF a clear advantage for these use cases. Another advantage of running in the kernel is that eBPF can handle encrypted traffic. source: https://logz.io/blog/ebpf-auto-instrumentation-pixie-kubernetes-observability/ GitHub link: https://github.com/apache/pulsar/discussions/20653#discussioncomment-6303556 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
