github-actions[bot]
commented
1 month ago This issue has not had any activity in the past 30 days, so the needs-attention label has been added to it.
If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue.
The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!
Request
For the mimir/loki.rules.kubernetes components, it would be beneficial to support clustering, to prevent multiple replicas of Alloy, from all loading the same rules into Mimir/Loki, potentially hitting rate limits (especially for GCM/GCL instances)
Use case
Current recommendation would be to run a single instance of Alloy just for running these components, however, most would probably prefer to run these components alongside their Metrics deployments of Alloy, which can have clustering enabled. Without clustering on these downstream components, these can have adverse effects on the rate limits of requests, especially upon retries happening once rate limiting. This would be one solution to alleviate some of overall load on the backend systems.