Technology: otel-collector

ID	Title	Description	Category	Technology	Tags
prequel-2025-0072 Low Impact: 3/10 Mitigation: 2/10	OTel Collector Dropped Data to to High Memory Usage	The OpenTelemetry Collector’s memory_limiter processor (added by default in most distro Helm charts) protects the process RSS by monitoring the Go heap and rejecting exports once the soft limit (default 85 % of container/VM memory) is exceeded. After a queue/exporter exhausts its retry budget you’ll see log records such as: ``` no more retries left: rpc error: code = Unavailable desc = data refused due to high memory usage ``` The batches being dropped can be traces, metrics, or logs, depending on which pipeline hit the limit.	OTEL Problems	otel-collector	OTEL Memory Backpressure
prequel-2025-0073 Low Impact: 5/10 Mitigation: 1/10	OTel Collector Resource Detection Failure	The resource_detection processor fails while trying to determine basic host attributes and repeatedly logs: ``` failed getting OS type: failed to fetch Docker OS type: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? ``` The Collector keeps running but exports traces, metrics, or logs without mandatory resource labels, leading to data loss or mis-grouping in the backend.	OTEL Problems	otel-collector	OTEL Known Issue