-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
ruler: Use notifier
Prometheus package when decoupled from config package.
#660
Comments
First part of it is to move relabel to not use |
First part merged, whole thing in review: prometheus/prometheus#5025 |
Is this work still planned, or is full relabeling in Ruler already supported in some other way? |
Hi, I believe for now there are the |
We're still in the early stages of figuring out our Thanos alerting setup, so I'm not sure yet if we'll need richer relabeling or not. I was just curious since it seemed like the PR linked above was pretty much there, it just needed a final 👍. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@bwplotka Can we remove this note that links to issue in the docs? https://github.com/thanos-io/thanos/blob/master/docs/components/rule.md#ruler-ha If not all is implemented do you think it makes sense to open a new issue about this? |
We might need another issue if we need such, so far we did not seen the need ): Anyway the comment in doc is confusing (: |
We require full alert relabeling within Thanos Rule. |
IIUC, we still want to use |
Rationales: Ensure similar logic and usage of powerful relabelling in Thanos Ruler.
Acceptance Criteria
pkg/alert
package and instead usenotifier
from Prometheus codebase.config
package that depends on lots of 3rd party packages (k8s, consul, ec2, etc)Right now our code mimics notifier.
The text was updated successfully, but these errors were encountered: