-
Hey there, The alert is triggered but is stopped by an error like below:
I set the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
I don't use cardinality rules myself, so I could be wrong, but I don't think you can do what you're attempting. Cardinality is matching on the uniqueness of a field's values. Suppose you created an alert for when field "host" has less than two unique values over the past 5 minutes. Then in the 5 minute window, no events were logged. That should trigger the alert, correct? But then since there are no events, how is ElastAlert going to give your alerter an arbitrary field value, such as your |
Beta Was this translation helpful? Give feedback.
I don't use cardinality rules myself, so I could be wrong, but I don't think you can do what you're attempting.
Cardinality is matching on the uniqueness of a field's values. Suppose you created an alert for when field "host" has less than two unique values over the past 5 minutes. Then in the 5 minute window, no events were logged. That should trigger the alert, correct? But then since there are no events, how is ElastAlert going to give your alerter an arbitrary field value, such as your
observer[geo][region]
field? It can't because there was no event in the first place.