Skip to main content

Tag: Memory

Problems related to memory usage, such as leaks, pressure, or out-of-memory crashes

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-0101
Medium
Impact: 6/10
Mitigation: 5/10
Loki Ingester Memcache Out of MemoryLoki ingester reports memcached errors indicating out-of-memory conditions while caching objects, logging messages such as "SERVER_ERROR out of memory storing object". When this occurs, cache writes fail and can lead to degraded ingestion performance, retries, and increased memory pressure on the ingester.Observability ProblemsingesterLokiIngesterMemcachedStorageCacheMemoryData LossThreshold ExceededObservabilityConfiguration