-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
The alarm cannot be triggered according to the specified rule. #6684
Comments
When the alert moves to the firing state, a notification will be sent, now, if the alert still remains in the firing, no new notification will be sent for the next repeat interval (4 hours). This is expected behaviour, as your value is always above the threshold. |
Thank you very much for your answer. |
Closing since your question is answered. |
Bug description
Set memory alarms. The alarm rules are as follows:
The corresponding alarm chart is as follows:
In this case, alarms are recorded only when the alarm is created and when the query-service service is restarted. It is unknown whether the fault is caused by the alarm rule configuration or back-end code processing. The alarm history is as follows:
Expected behavior
When the threshold is always greater than the alarm value, a message is periodically sent to the channel.
How to reproduce
1.Create a webhook channel.
2.Create metrics-based memory alarms.
3.Observe the alarm triggering frequency and webhook email sending.
Version information
The text was updated successfully, but these errors were encountered: