How cloudflare/ebpf_exporter works
a. Primary Flow:
• Linux Kernel -> eBPF Programs -> Maps -> Exporter Service -> Prometheus Metrics
b. Configuration Flow:
• Config Files -> Config System -> Exporter Service -> eBPF Program Loading
c. Decoding Flow:
• Raw Map Data -> Decoder System -> Formatted Metrics
a. Metrics Processing:
• Counters
• Histograms
• Labels
• Decoders (various types)
b. Program Types:
• Kprobes
• Tracepoints
• Fentry
• Uprobes
Integration Points (use interface symbols)
a. External Systems:
• Prometheus
• OpenTelemetry
• Linux Kernel APIs
• BPF CO-RE
Monitoring Components (use monitoring symbols)
a. Built-in Metrics:
• enabled_configs
• ebpf_program_info
• ebpf_program_attached
• ebpf_program_run_time_seconds
• decoder_errors_total
Implementation Details (use notes/callouts)
a. Key Features:
• CO-RE (Compile Once Run Everywhere) support
• Dynamic program loading
• Multiple config support
• Various decoder types
• Performance monitoring
Security Boundaries (use security symbols)
a. Required Capabilities:
• CAP_BPF
• CAP_PERFMON
• Optional: CAP_SYSLOG, CAP_IPC_LOCK, etc.
Important details
• Types (hash maps, per-CPU maps)
• Program types (kprobes, tracepoints)
• Metric types (counters, histograms)
• Decoder chains