Splunk Search

Timechart after sort display

Hod152
Explorer

Hey,
Iv'e noticed some wierd behviour that is making me suspect the relaibility of my queries so I'm really looking for an explanation, I was making some searches and displaying them on a timechart, for some reason the timechart looks completly different when I sort the fields befor.

this is the basic search and it's results:

 

 

|tstats count WHERE case=test responseCode=200 requestStatus!=legal by clientIp _time span=1h| timechart sum(count) span=1h

 

 

Hod152_2-1721131756532.png


After sorting clientIp field this is how the graph looks like:

 

 

|tstats count WHERE case=test  responseCode=200 requestStatus!=legal by clientIp _time span=1h| sort -clientIp |timechart sum(count) span=1h

 

 

Hod152_1-1721131709287.png

 

 

|tstats count WHERE case=test responseCode=200 requestStatus!=legal by clientIp _time span=1h| sort +clientIp |timechart sum(count) span=1h

 

 

Hod152_3-1721132009680.png

Note that the count is decreased on the sorted search.

 

 


What can explain that behaviour? Which chart should I relay on? Is that a feature of sorting?

Thanks

 

Labels (1)
0 Karma
1 Solution

ITWhisperer
SplunkTrust
SplunkTrust

sort truncates at 10k values - try something like this

| sort 0 -clientip

View solution in original post

ITWhisperer
SplunkTrust
SplunkTrust

sort truncates at 10k values - try something like this

| sort 0 -clientip

Hod152
Explorer

Thanks!

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @Hod152,

why you did this?

if you have tstats BY _time, you already have the timechart:

 

| tstats 
     count 
     WHERE case=test  responseCode=200 requestStatus!=legal 
     BY clientIp _time span=1h

 

Anyway, it's always better to indicate the indexes to use in the search, to have more performant searces  and avoid default search path issues.

Ciao.

Giuseppe

0 Karma

Hod152
Explorer

It just suited my work sequence...

0 Karma
Get Updates on the Splunk Community!

Message Parsing in SOCK

Introduction This blog post is part of an ongoing series on SOCK enablement. In this blog post, I will write ...

Exploring the OpenTelemetry Collector’s Kubernetes annotation-based discovery

We’ve already explored a few topics around observability in a Kubernetes environment -- Common Failures in a ...

Use ‘em or lose ‘em | Splunk training units do expire

Whether it’s hummus, a ham sandwich, or a human, almost everything in this world has an expiration date. And, ...