Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Field content value condition broken #1245
The field content value condition for alarm callbacks is somewhat broken.
It does not let the user specify a time range for the condition, but hardcodes it to
With a field content value condition configured like the following and an
I think it makes sense that you are not specifying a time range for this condition, as it is different from the other conditions as in that it's not working on an aggregation of the messages in a time range (count for MessageCoundCondition and min/max/avg/stddev for FieldValueAlertCondition) but responding to single messages. This means, that we should make a search going back to the last time we have checked and search all messages in between for the occurence of a message with field with this content. Therefore, the idea was to just do a relative time range search for the configured alert checking interval.
The '* 60' is the issue here, which probably resulted from the time range in the other alert conditions being specified in minutes while the alert_check_interval config parameter being specified in seconds.