Loki log storage fails on Minio because of an S3 object name error
A 1.36 cluster is running on 1.13, with Alloy collecting pod logs and sending them to Loki. The setup works for a short time after , then one Loki write component fails. The failure happens when Loki tries to save log chunks into an , and Minio rejects the write because the object name contains unsupported characters.
The error includes `XMinioInvalidObjectName`, a failed `PutObject` request, and HTTP status code 400. The log labels include a value like `flux-system/flux-operator-...:manager`, which contains slashes and a colon. Minio is installed on a Windows , and the same S3 storage works for other tasks, but not for this Loki log-writing path.
The Alloy setup was changed to rewrite the `instance` value so it should not include colons or slashes, but the issue is not fully resolved in the provided details.
Key points
- The setup uses 1.36 on 1.13.
- Alloy collects pod logs and sends them to Loki.
- Loki fails while writing log chunks to an backed by Minio.
- Minio reports `XMinioInvalidObjectName`, meaning the object name has unsupported characters.
- Labels containing slashes and a colon may be involved in the failure.