Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: alertmanager: too many 404 errors with S3 backend to /mimir-alertmanager/grafana_alertmanager/org/grafana_fullstate #10661

Open
pschiffe opened this issue Feb 15, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@pschiffe
Copy link

What is the bug?

Even with grafana_alertmanager_compatibility_enabled: false my S3 backend (minio) is receiving a lot of requests for file /mimir-alertmanager/grafana_alertmanager/org/grafana_fullstate, but that path doesn't exist. The correct path is /mimir-alertmanager/alertmanager/org/fullstate. This is then generating lot of 404 errors. Otherwise the alertmanager seems to be working fine.

When I enable grafana_alertmanager_compatibility_enabled: true, the number of 404 errors is roughly doubled.

How to reproduce it?

Enable alertmanager with S3 backend.

What did you think would happen?

No 404 errors.

What was your environment?

Mimir 2.15.0 cluster running in Docker on 3 hosts.

Any additional context to share?

No response

@pschiffe pschiffe added the bug Something isn't working label Feb 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant