You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.
Since the alerts are scheduled onto the Kafka queue and read by the alert client, what happens to the queued instances when an alert definition is updated? Does the alert client execute the old alert definitions? Are new instances also scheduled immediately and given preference over the old ones?
If there is a delay between updating the alert definition and the alert client picking it up, what is this delay dependent on?
The text was updated successfully, but these errors were encountered:
Can this question be answered? My experience has been that the alerts that have already been scheduled using the old definition run as scheduled. Only newly scheduled alerts contain changes.
Apologies for the late reply. There is a refreshInterval, which determines how frequently the alert definitions must be updated in the scheduler. So depending on when the alert is updated, there could be a maximum delay of up to "refreshInterval" before the updated alert definition can be evaluated.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since the alerts are scheduled onto the Kafka queue and read by the alert client, what happens to the queued instances when an alert definition is updated? Does the alert client execute the old alert definitions? Are new instances also scheduled immediately and given preference over the old ones?
If there is a delay between updating the alert definition and the alert client picking it up, what is this delay dependent on?
The text was updated successfully, but these errors were encountered: