linkerd_process_resident_memory

The Linkerd tap service may fail to respond to live traffic inspection requests, eliminating critical debugging visibility. Often caused by tap pod crashes, network policy blocks, or resource constraints.

Linkerd proxy sidecars have default CPU and memory limits that may be insufficient for high-throughput services. Proxy resource exhaustion manifests as increased latency, throttling, or connection failures without obvious application issues.