Splunk Search

Why Stats count command is counting events that are missing in other searches?

abhijeetallu
Engager

The first search query returns a count of 26 for domain X :

index="web" sourcetype="weblogic_stdout" loglevel IN ("Emergency") | stats count by domain

 

But when I run the below query to just see the events corresponding to domain=X, I get zero events:

 index="web" sourcetype="weblogic_stdout" loglevel IN ("Emergency") domain="X"

 

Any clue why this might be happening

Labels (1)
Tags (1)
0 Karma
1 Solution

bowesmana
SplunkTrust
SplunkTrust

That generally means X is not X, i.e. if you put 

index="web" sourcetype="weblogic_stdout" loglevel IN ("Emergency") domain="*X*"

do you get results

If you do this in your first search

index="web" sourcetype="weblogic_stdout" loglevel IN ("Emergency")
| eval trimmed_domain=trim(domain)
| eval bounded_domain=":".domain.":"
| stats count by domain trimmed_domain bounded_domain
| eval trimmed_equal_domain=if(trimmed_domain=domain, "YES", "NO")

you may see whether you have leading or trailing spaces around X and if trimmed_equal_domain is NO, then there are leading/trailing spaces.

The bounded domain makes it easier to see what's what by adding : before and after

View solution in original post

0 Karma

bowesmana
SplunkTrust
SplunkTrust

That generally means X is not X, i.e. if you put 

index="web" sourcetype="weblogic_stdout" loglevel IN ("Emergency") domain="*X*"

do you get results

If you do this in your first search

index="web" sourcetype="weblogic_stdout" loglevel IN ("Emergency")
| eval trimmed_domain=trim(domain)
| eval bounded_domain=":".domain.":"
| stats count by domain trimmed_domain bounded_domain
| eval trimmed_equal_domain=if(trimmed_domain=domain, "YES", "NO")

you may see whether you have leading or trailing spaces around X and if trimmed_equal_domain is NO, then there are leading/trailing spaces.

The bounded domain makes it easier to see what's what by adding : before and after

0 Karma

abhijeetallu
Engager

Thank you so much ! it worked. I was clueless what was happening and all this time it was a trailing space character !

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