Alerting

Alert when specific sourcetype and event stops indexing

dbuchanan46
New Member

I am trying to create a search/alert that checks to see if a specific sourcetype and event stops indexing data after 1 minute. I have a search that uses metadata and returns the last index time after a minute(or any time) but I am having trouble using the metadata to narrow the search to only specific sourcetype and event. Here is the general Metadata search I am using.

| metadata type=sourcetypes |where recentTime < now() - 60 | eval LastIndex = strftime(recentTime, "%F %T") | fields + sourcetype LastIndex

Any ideas on how to narrow this down to one sourcetype and event?

Thank you

Tags (1)
0 Karma

lguinn2
Legend

@somesoni2 has a good idea, although I would do it even more simply: (1) create a lookup table that contains a list of the sourcetypes that need to be checked. (2) run the following search

| inputlookup sourcetype.csv  
| eval recentTime = 0
| join type=left sourcetype [ metadata type=sourcetypes ]
| where recentTime < now() - 60

This would give you a list of all the sourcetypes in sourcetype.csv that have not seen new data in the last minute. If you wanted to check only one sourcetype, it gets even easier

| metadata type=sourcetypes
| where sourcetype = thesourcetypetocheck and recentTime < now() - 60

This search returns nothing if the sourcetype has received data, and a single event if it has not received data.

In both cases, you might want to set an alert condition of "number of results > 0".

Now, regarding event:message.in - this changes things. If the rule is "all of the sourcetypes in my list must have at least one event with event:message.in during the last minute" then the test needs to look like this (and the alert condition is still "number of results > 0"):

| inputlookup sourcetype.csv  
| join type=left sourcetype [ search earliest=-1m event:message.in=* [ | inputlookup sourcetype.csv  ]   
     | stats count by sourcetype] 
| where count = 0

If the rule is "a particular sourcetype must have at list must have at least one event with event:message.in during the last minute" then this will do it

earliest=-1m event:message.in=* sourcetype=mysourcetype

For this last search, your alert condition should be "number of results = 0".

somesoni2
Revered Legend

Is the sourcetype and field name (event:message.in) fixed? (multiple source types are fine). If yes, then my suggestion would be put them in a lookup table file, and use search like this:
|inputlookup sourcetypeEvent.csv | join type=left sourcetype [search sourcetype=* event:message.in=* earliest=-1m@m latest=now | fields sourcetype, event:message.in] | WHERE isnull(event:message.in)

0 Karma

linu1988
Champion

The condition is wrong

sourcetype[| metadata type=sourcetypes |where recentTime > now() - 60 | eval LastIndex = strftime(recentTime, "%F %T") | fields + sourcetype]|where sourcetype=your_sourcetype AND field_name like "%event:message.in%" |eval a=1| stats count|where count =0

you can replace the your_sourcetype and field_name.

Thanks

0 Karma

dbuchanan46
New Member

Sorry, actually it is by sourcetype and a field. The field was specified event:message.in.

So I'm trying to create an alert when my sourcetype with field event:message.in has not had any new data in the last minute.

0 Karma

somesoni2
Revered Legend

What do you mean by event here?

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!

Index This | What travels the world but is also stuck in place?

April 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Discover New Use Cases: Unlock Greater Value from Your Existing Splunk Data

Realizing the full potential of your Splunk investment requires more than just understanding current usage; it ...

Continue Your Journey: Join Session 2 of the Data Management and Federation Bootcamp ...

As data volumes continue to grow and environments become more distributed, managing and optimizing data ...