7 docs tagged with "loki"

Grafana can get into a state where it writes more errors messages than it can process. The problem is compounded when Grafana is collecting its own error logs that include the related warnings that it can no longer keep up.

Grafana alloy Loki fanout crashes when the number of log files exceeds the number of ingesters.

\- When deploying Grafana Loki with AWS S3 as the storage backend and specifying a custom S3 endpoint (e.g., for FIPS compliance or GovCloud regions), Loki may fail to retrieve AWS credentials via IAM Roles for Service Accounts (IRSA). This results in errors during startup or when attempting to upload index tables, preventing Loki from functioning correctly.

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.

Grafana Loki may emit errors when attempting to write to a Memcached backend that has run out of available memory. This results in dropped index or query cache entries, which can degrade query performance but does not interrupt ingestion.

Alloy detects the Loki is dropping log lines because they exceed the configured maximum line size.

Loki is experiencing an out of disk space error due to the WAL (Write\-Ahead Logging) filling up the disk. This can happen when the WAL is not properly configured or when the disk is full.