Using the below conditions (along with the required conditions) to configure alert
| head 100
The challenge facing is, sometimes observing it is considering the transactions which has previously already generated an alert
for example, an alert got generated at 12:00 PM and then again it is generating at 01:30 PM. This is happening because there were some failures between 11:00 AM and 11:30 AM and even if there is 1 or 2 failures around 1:25 PM, it is considering the failures from 11:00 AM to 11:30 AM.
The reason to consider
head 100 is because the transactions for this application is very less. Thought of using suppression for a longer time (currently it is set to 1 hr) but that might give rise to situations were valid scenario might get miss.
Is there any other way (other than reducing the earliest time or head or increasing the suppression) to mitigate this?
Typically how this works is you have the alert search running in the same interval as what you define in its time range so it runs on exclusive events only (i.e. it doesn't overlap on to same events). So for example, if you set your search time-range to be 1 hour then you set up your alert search to run after 1-hour intervals.
Please elaborate if I am misunderstanding your question. I'd be happy to help.
Hope this helps.
It does not seem to happening like that, it is considering the occurrences of the previously considered events as well
Could you provide the exact stanza and config from your savedsearches.conf?
I dont have access to the backend. I am only using the GUI. Is this something i can retrieve from the GUI?
You can check what are the settings under Settings > Searches and Reports and click on edit on the search that you are having trouble with to see its details.