Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upreload of rules doesn't work, removed/updated rules should get removed/updated #2182
Comments
This comment has been minimized.
This comment has been minimized.
|
Can you give a more concrete example? From what you are saying above, I cannot reproduce the problem. |
beorn7
added
component/rules
kind/bug
labels
Nov 14, 2016
This comment has been minimized.
This comment has been minimized.
|
Without further information, we cannot confirm this is an issue. |
brian-brazil
closed this
Feb 13, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
fvigotti commentedNov 11, 2016
when rules are updated, and reload is triggered ( both using http or signals ) new rules are reloaded correctly
BUT..
this point seems to be a fault of alertmanager but I suppose that really the whole issue is inside prometheus which is the one who loads the new rules and should also have the responsability to update alertmanager.
now imagine a monitoring with some microservices / nodes that gets added/removed and maybe a CI system which update alerts from a SCM repository, It's very very frustrating having to reload the whole monitoring system ( prometheus) ( which also cause flush/reload databases ) for every rule added ( which could happen very frequently during some devops working session )
Because I think that alerting is one of the major features of a monitoring system this is a serious bug in my opinion (unfortunately I'm not fluent enough in go to PR myself :( )
Thank you,
Francesco