Hi Community,
We are encountering the following error when attempting to send logs to Loki:
msg=“error sending batch, will retry” component_path=/ component_id=loki.write.logs_alloy component=client host=loki:3100 status=429 tenant=“” error=“server returned HTTP status 429 Too Many Requests (429): Ingestion rate limit exceeded for user fake (limit: 4194304 bytes/sec) while attempting to ingest ‘4213’ lines totaling ‘1048378’ bytes, reduce log volume or contact your Loki administrator to see if the limit can be increased”
We have 200+ pods, each representing a different microservice, and they all generate logs. These logs are mounted to a host path (on-prem server with a single-node cluster). The logs are stored under /var/log/CustomerLog/. The ingestion rate limit is being exceeded, resulting in this error message. We request advice on how to manage or reduce the ingestion rate, whether it’s possible to increase the ingestion limit to accommodate the log volume, and any best practices for scaling Loki in a single-node cluster setup to handle this load.
Thanks for response @yosiasz
yes, Loki is single server setup
we are using alloy as agent
and this config of alloy
logging {
level = “debug”
format = “logfmt”
}
in loki ```
deploymentMode: DistributedordeploymentMode: SimpleScalable`
will those support filesystem since we have single node cluster
and we not using cloud storges, like s3 etc.
we are using host level mounts