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.

Sign up for GitHub

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

Jump to bottom

Unable to specify datasource for rules creation #264

Open
justinTM opened this issue Oct 11, 2022 · 0 comments
Open

Unable to specify datasource for rules creation #264

justinTM opened this issue Oct 11, 2022 · 0 comments

Comments

@justinTM
Copy link
Contributor

I'm trying to tell Grafana which datasource to use for an alerting query, but I can't find any documentation for this in the rules YAML syntax. I see in the web UI there is a dropdown for Datasource, and a corresponding API request with the datasource name and UID, but I can't figure out how cortextool implements this feature...
@justinTM justinTM changed the title [BUG} Unable to specify datasource for rules creation [BUG] Unable to specify datasource for rules creation Oct 11, 2022
@justinTM justinTM changed the title [BUG] Unable to specify datasource for rules creation Unable to specify datasource for rules creation Oct 11, 2022
friedrichg pushed a commit to cortexproject/cortex-tools that referenced this issue Aug 1, 2023
@jmcarp
Optionally set service account per dep/statefulset. (grafana#264)
07a840c 
Different cortex components might require different cloud provider
permissions. When using gke workload identity, pod iam permissions are
managed by kubernetes service account. This patch allows operators to
use different service accounts for each deployment or statefulset to
support fine-grained control of iam permissions in this scenario.

[Resolves #251]

Signed-off-by: Josh Carp <jm.carp@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@justinTM