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

Routing Alerts to AlertManager from Thanos Ruler - How to set custom PromQL address? #6284

Closed
diranged opened this issue Apr 16, 2023 · 3 comments

Comments

@diranged
Copy link

Is your proposal related to a problem?

When we have the thanos-ruler pods pointing to a thanos-query-frontend endpoint, our alerts get a nice friendly Alert Source: https://…./query/… label that helps our developers get right to the source of the alert.

However, when we run the thanos-ruler pods against either Amazon Managed Prometheus or Grafana Cloud, we get a shortened URL that just gives us a query-path .. the problem is neither Grafana Cloud nor Amazon Managed Prometheus provide a /graph endpoint.

Describe the solution you'd like

It would be ideal if there were a few options here..

  1. Allow us to templatize the URL to anything we want (with the alert query as an argument).
  2. Have some native understanding of the Grafana /explore endpoint URL structure and allow us to route to that.

Additional context

https://cloud-native.slack.com/archives/CK5RSSC10/p1681574164937839

@bwplotka
Copy link
Member

Great issue!

The acceptance criteria

  • Thanos Rule has configuration flag that allows customizing (template?) Alert Source field.

@matej-g
Copy link
Collaborator

matej-g commented Sep 13, 2023

PR has been merged ✅, thank you @zhuoyuan-liu 🙇

@matej-g matej-g closed this as completed Sep 13, 2023
@jkroepke
Copy link

@diranged

Have some native understanding of the Grafana /explore endpoint URL structure and allow us to route to that.

Do you have such an template to share?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants