I have a question about Kapacitor.
Is there a way to prevent kapacitor to automatcally close alerts when the criteria is not matched anymore.
For example, i trigger some alert based on a combinaison of criteria and I would lile to keep my alert open in Opsgenie so i can go and manually check the problem.
If the criterias are not matched anymore then kapacitor automatically closes my alert on opsgenie and then i don’t see.
Thank you in advance for helping me with this case
What exactly do you mean by keeping your alert open? Like once your conditions are met keep sending alerts even after the conditions have returned to normal? How will you determine when you have met your alert conditions again if you ignore the change back to normal conditions?
Okay so here is my setup
I have some influxDB instance
I have telegraf that forwards data every 3h based on some measurements made on several vms.
I have a tick script that checks when some vms lose connectivity for a period of time. For that i made an alert that tells me when we I had an interruption. Even if the connectivity comes back, i still want to see my alert about that connectivity interruption so i can manually check for root cause analysis.
FYI, kapacitor sends alerts to Opsgenie.
But if this happen during the night, since it’s not CRITICAL, it will close it in opsgenie.
Here is an example of data:
At instant t:
At instant t-3h:
Alert is raised if status(t-3h) - status(t) is < 0
But let say that it stays with status = 1 forever.
Then criteria is not matched and i won’t be alerted for new alerts but i would like to keep the first one open. ( hope this helps )
other option, is there a way to close an alert when matching condition X and only close it when matching condition Y ?
Or another option
Lets assume that Kapacitor closes the alert on its side but is it possible that it doesn’t send an event to opsgenie so at least it stays open on Opsgenie ? ( idk if NoRecoveries can make the trick ) @Anaisdg
Thanks for the answer ! Thanks @Anaisdg for the support !
Just for my knowledge, could noRecovies() help me to not send closing alert events to opsgenie ?
I saw in the opsgenie v2 doc that i could also overwrite the closing behavior with .recoveryAction(). Could this work ?