Database Access Monitoring (DAM)

the ebpf receiver includes built in database activity monitoring that automatically profiles database traffic at the kernel level no database side agents or plugins needed supported databases database captured metrics mysql query operations, latency (avg + p99), prepared statements, read/write ratio postgresql query operations, latency (avg + p99), prepared statements, read/write ratio supported messaging systems system captured metrics redis command operations, latency, throughput kafka producer/consumer metrics, throughput elasticsearch request operations, latency, throughput key dam capabilities table level hotspot detection — identify your most queried and slowest tables read vs write ratio analysis — understand workload characteristics per table p99 latency tracking — surface tail latency issues before they impact users zero configuration — automatically detected via ebpf kernel hooks; no database credentials required when to use when you need instant database visibility with zero setup when you cannot or prefer not to create a monitoring user on the database when running on linux with kernel ≥ 5 8 when you want to monitor traffic across all supported databases and messaging systems from a single agent for deeper query analytics, including execution plans and schema discovery, see direct database monitoring for distributed trace context from your application sdks, see opentelemetry database monitoring configuration enable heuristic sql detection and tune caches for high load environments ebpf heuristic sql detect true mysql prepared statements cache size 1024 postgres prepared statements cache size 1024 prerequisites linux kernel ≥ 5 8 (recommended; some features work on 4 18+) root privileges or cap sys admin + cap bpf capabilities the ebpf receiver must be enabled in the agent configuration (see docid\ v4xbpr5npc 3 wrbchpl )