Skip to main content

Category: OTEL Problems

Problems related to OTEL

IDTitleDescriptionCategoryTechnologyTags
prequel-2025-0072
Low
Impact: 3/10
Mitigation: 2/10
OTel Collector Dropped Data to to High Memory UsageThe 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 Problemsotel-collectorOTELMemoryBackpressure
prequel-2025-0073
Low
Impact: 5/10
Mitigation: 1/10
OTel Collector Resource Detection FailureThe **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 Problemsotel-collectorOTELKnown Issue
prequel-2025-0077
Low
Impact: 2/10
Mitigation: 2/10
OTEL Target Allocator Could Not Find Colletgor on Fargate NodeThe OTEL Collector is not scheduled on the Fargate node.OTEL Problemsotel-operatorOTELAWSFargate