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!

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