-
Notifications
You must be signed in to change notification settings - Fork 489
Support defining Cortex Rules in Agent config #523
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
Comments
This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
Here's a recap of what we discussed today regarding this task:
Given what we discussed, I assume we don't have to care that much about files from Cortex that aren't in the local file system, only about local files that aren't on the remote server. The cortextool can be used as a reference, especially the |
I'm removing myself from this task, as it's been for a while in my queue and I can't seem to even get started with it. I'll try to get a smaller issue first to get myself more comfortable with this codebase and might work on this again in the future. Sorry about that :-/ |
Any update on this issue? This is a blocker to adopting grafana |
No updates for now, this isn't being actively worked on at the moment. |
This was implemented as a Grafana Agent Flow component in #2604. I'm going to close this as completed. At this time, there's no plan to backport this functionality into the static mode (i.e., the default mode the agent runs in). |
Thank you! |
Based on this discussion, I'd like it if the Agent could support recording and alerting rule definitions that are synced against the Cortex Ruler API.
The text was updated successfully, but these errors were encountered: