Alerting

Splunk outer join issue

ashutoshc21
Engager

I am using a query as below

| inputlookup lookup_name where (Environment=PROD) AND sourcetype="name"
| join type=inner Environment, host
[| savedsearch "name" | stats count as Total by Environment, App, host ]
| fillnull value=NULL Total | search Total=NULL

Lookup is having only 2 columns Environment & Host returning PROD & Server_name, the saved search returns approx 10000 rows. This alert runs every 15 minutes but many times gets triggered with NULL result even when the actual result is not NULL. Alert condition is that if Total=NULL comes up it will send email but 90% of them are false alarms. Is it because the saved search is taking time to output and splunk is having some threshold appending just NULL in case it exceeds.

Labels (2)
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!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...