Alerting

Alerts not working

ridutta
New Member

I have enabled few alerts and these are the criterias:

Alert Type: Scheduled by CRON
Time Range: 24 Hours
Cron Expression: * */4 * * *

So as per this expression: The search query will run every 4 hour for the last 24 hours and trigger alerts. (Mail in my case)

Last day my search event count was 350. So why it didnt trigger after it crossed the 120 mark?

Can any one help me on this?

0 Karma

mayurr98
Super Champion

Can you put the search query in 101010 sample code format? Also, are you setting any threshold on the number of results? I see from your question that 120 is the threshold.
My advice is to set the threshold in a query itself and just create an alert as it is without setting any threshold on the UI.

0 Karma

MousumiChowdhur
Contributor

Hi! Can you please modify your cron expression with 0 */4 * * * and check if that's working?

0 Karma

ridutta
New Member

My cron expression is that only "0 */4 * * *"... but its not working. there is someting with this portal... However the suggested one is my cron expression.

0 Karma

MousumiChowdhur
Contributor

Can you mention the search and the alert conditions you have configured, so that it's easier to find the solution.

0 Karma

ridutta
New Member

Current Search Query:
(index=mesb "Status_c=ERROR") source="*/mule-app-csone_logging_v2.0-v201712091010.log" Attribute_1c=CM_ROLE_UNAVAILABLE | eval _time=strptime(CreatedDate, "%Y-%m-%dT%H:%M:%S.%3N%Z") | timechart span=1h count by Attribute_1_c

Should I change to :
(index=mesb "Status_c=ERROR") source="*/mule-app-csone_logging_v2.0-v201712091010.log" Attribute_1c=CM_ROLE_UNAVAILABLE | timechart span=1h count by Attribute_1_c??

0 Karma

MousumiChowdhur
Contributor

Yes, you should try the 2nd search, set the alert and check.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...