Getting Data In

Alert for syslog

asarolkar
Builder

I am trying to set an alert that notifies the admin of a situation when we dont get any data from syslog (no messages on udp:514) :

Alerts based on the following searches seem to be failing:

index=_internal (source=*/metrics.log* OR source=*\\metrics.log*) group=per_sourcetype_thruput series=syslog | eval flag= if(isnull(kb) OR len(kb)<=1,"Y","N") | table flag | search flag="Y"

sourcetype=syslog | timechart count span=1d | search count=0

Neither seems to be working out (there is no data written to that sourcetype which clearly one of the two ought to capture)

Any other/ideas suggestions ? I do not want to use deployment monitor (unless IN deployment monitor, there happens to be a way to configure an alert when it sees a missing sourcetype/no data from sourcetype ) ?

0 Karma
1 Solution

hjwang
Contributor

I think you can use a simple way to do this by searching source=udp:514

then set alert condition when number of events equals zero

View solution in original post

hjwang
Contributor

I think you can use a simple way to do this by searching source=udp:514

then set alert condition when number of events equals zero

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 ...