How parca-dev/opentelemetry-ebpf-profiler works
Main Components
a) Core System Components:
• eBPF Programs (Kernel Space)
• Host Agent (User Space)
• Backend Collector
• Visualization Layer (devfiler)
b) Key Subsystems:
• Tracer
• Process Manager
• Trace Handler
• Reporter
• Interpreter Handlers
• Stack Delta Provider
[Kernel Space]
• ↑↓
[User Space Agent]
• ↑↓
[Collection & Visualization]
Component Relationships
a) Kernel Space Layer:
• EBPF Programs attached to kernel probes
• BPF maps for data sharing
• Unwinder components for different languages
b) User Space Layer:
• Process Manager's connections to interpreters
• Trace processing pipeline
• Conversion flow from BPF to user-space trace format
c) Collection Layer:
• GRPC communication with the backend
• OTLP protocol integration
• Devfiler visualization connection
Detailed Component Representation
[Kernel Space]
• BPF Programs
• Native Unwinder
• Language-specific Unwinders
• PID Event Tracking
• BPF Maps
• Kernel Probes
[User Space Agent]
• Tracer
• Event Pump
• BPF Program Manager
• Process Manager
• Executable Mapping
• Interpreter Handlers
• Trace Handler
• Format Converter
• Hash Cache
• Reporter
• Trace Aggregator
• gRPC Client
[Collection & Visualization]
• Backend Collector
• OTLP Receiver
• Symbolization Service
• devfiler UI
Data Flow Representation
• Stack trace collection flow
• Process creation/termination events
• Symbolization requests
• Trace conversion and enrichment
• Data reporting to backend
Additional Elements
• Version compatibility notes
• Supported language interpreters
• Configuration points
• Critical monitoring paths
Implementation Notes
• Nested components
• Export to standard formats
This system design should emphasize: