I have a scheduled savedsearch that may return a result such as this
_time, host, _raw
2023-01-01, host A, <some message>
2023-01-02, host A, <some message>
2023-01-03, host A, <some message>
In this example, the content of <some message> causes an alert to fire, which is what I expect.
Now, assume that a new event occurs and the next scheduled search returns this (changes in bold):
2023-01-01, host A, <some message>
2023-01-02, host A, <some message>
2023-01-03, host A, <some message>
2023-01-04, host A, <some message>
2023-01-05, host A, <some message>
Problem: The next scheduled search will return the entire list (5 events) and thus trigger an alert containing these 5 events. However, 3 of these events were contained in a previous alert and are thus superfluous.
Desired outcome: The new alert should only be triggered based on the two "new" events (in bold)
What I have tried: Set trigger type to "for each event" and suppress for fields _time and host because I would assume that the combination of _time and host will uniquely identify the event to suppress
I also tried to learn about dynamic input lookups, but the documentation seems to be lost / unavailable (http://wiki.splunk.com/Dynamically_Editing_Lookup_Tables)
... View more