CRE-2025-0032
Loki generates excessive logs when memcached service port name is incorrectLowImpact: 2/10Mitigation: 4/10
CRE-2025-0032View on GitHub
Description
Loki instances using memcached for caching may emit excessive warning or error logs when the configured`memcached_client` service port name does not match the actual Kubernetes service port. This does not cause a crash or failure, but it results in noisy logs and ineffective caching behavior.\n
Mitigation
- Ensure that the `memcached_client` configuration references the correct Kubernetes service **port name**.\n- Match the port name exactly as defined in your memcached service. \n- For example:\n```yaml \n ports: \n - name: memcache \n port: 11211 \n```\n- Update your Helm values or Loki configuration accordingly.\n