Alerting

Alert Condition and Indexer

rzessin
New Member

I have a saved search which triggeres if there are are less than 2 items within an hour.
Sometimes the Trigger happens but the condition wasn't true. The file contains the items,
but the indexer has not made the work for hours, last time it was true for 17 hours.

I've nothing found in logs, maybe I've looked in wrong place, is there any chance to see if indexex get stucks to see on which file ?

Definition of scheduled Search:



[CRL-Copy]
action.email = 1
action.email.inline = 1
action.email.sendresults = 1
action.email.subject = [Splunk Alert: $name$]
action.email.to =
alert.suppress = 0
alert.track = 1
counttype = number of events
cron_schedule = */30 * * * *
dispatch.earliest_time = -60m
dispatch.latest_time = now
displayview = flashtimeline
enableSched = 1
quantity = 2
relation = less than
request.ui_dispatch_view = flashtimeline
search = CRL-copy sourcetype="syslog-ng-modified" host="" ok


The intention is if the Certificate Revocation List isn't published at least one time in past hour an alert has t be sent. The CRL-Copy-Task itselfs run each 15 minutes via cron

And if i doing the search now I see for each hour bound to quarter the four entries which is telling me that the indexer has got stuck.

Tags (1)
0 Karma

yannK
Splunk Employee
Splunk Employee

What are the search that you used to alert, the condition and the schedule ?

Were the events searchable in splunk, with the correct timestamp ?

0 Karma

rzessin
New Member

I've added missing infos in question

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!

Mastering Threat Intelligence in ES 8.5, Splunk AI Assistant v2, and More from Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...