-
Notifications
You must be signed in to change notification settings - Fork 795
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
Support for DNS discovery for alertmanagers to find peers in a cluster #2883
Comments
I think this is slightly different but can use similar mechanisms. I've added the capability to discover Alertmanagers from the ruler, this is about discovering other Alertmanagers from the Alertmanager itself. |
Could you please assign this to me @pracucci? |
Definitely, done! 🙏 |
This issue has been automatically marked as stale because it has not had any activity in the past 60 days. It will be closed in 15 days if no further activity occurs. Thank you for your contributions. |
Still valid |
This issue has been automatically marked as stale because it has not had any activity in the past 60 days. It will be closed in 15 days if no further activity occurs. Thank you for your contributions. |
Still valid |
This issue has been automatically marked as stale because it has not had any activity in the past 60 days. It will be closed in 15 days if no further activity occurs. Thank you for your contributions. |
Still valid |
Do we still want this? Moving forward, I'm not sure I see a point in improving the old clustering form. |
I think the way ahead is the ring-based alertmanager scalability, which is what we're currently working on. |
Closing this because we will be solving the use case of this issue using a ring-based scalable alertmanager |
It might be a good addition to add DNS discovery capability in multi-tenant alertmanager to discover peers. Right now there is a
-cluster.peer
flag which can be used multiple times but that has to be done statically. I tried with a dns host with multiple IP targets with-cluster.peer
but it seems like the dns name does not get re-resolved when a host goes down.The text was updated successfully, but these errors were encountered: