Duansg commented on issue #3757: URL: https://github.com/apache/hertzbeat/issues/3757#issuecomment-3288080368
> > Does this new alert fall within the repeat_interval or group_interval window? > > Yes, Like i said, The alarm is triggered at time A, and it is resolved at A+1 minute. I hope to see an alarm when it is triggered again at A+10 minutes, even if I set the interval time to 4 hours Understood, thank you for your reply. Based on your description, the scenario you're encountering should be: If the configuration is: ``` group_wait: 30s group_interval: 15m ``` The phenomenon you are experiencing is: ``` T=0: alertA-0 -> firing T=30s: alertA-0 -> send notification T=5min: alertA-1 -> resolved T=8min: alertA-2 -> firing again T=15min: alertA-2 -> timer expired, send notification ``` Your issue is: `Alarm A-2` should not have occurred within this 15-minute interval window. Regarding this issue, I reviewed the current design of `hertzbeat` and `alertmanager`. In `alertmanager`, whether an alert notification is `firing` or `resolved`, they are both calculated as part of the same `group_interval`. It does not reset the `group_interval` cycle. I understand this is indeed a design trade-off in `alertmanager`, prioritizing simplicity and system stability. However, it may lack flexibility in certain scenarios. Of course, this can be mitigated through configuration (though that falls outside the scope of our current discussion). Based on my personal understanding (which may not be authoritative), the current design of `hertzbeat` builds upon the concept of `alertmanager`. `hertzbeat` introduces an additional reset mechanism: when a new alert is generated, it checks whether all alerts have been `resolved`. If this condition is met, it triggers the notification and then resets the `aggregate group` status. This is quite unique and, in my view, essential. Following the alert lifecycle logic, once an alert is `resolved`, its current lifecycle is considered complete. Any new alerts that occur will be treated as a separate lifecycle. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
