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
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
|tstats count WHERE case=test responseCode=200 requestStatus!=legal by clientIp _time span=1h| sort +clientIp |timechart sum(count) span=1h
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
sort truncates at 10k values - try something like this
| sort 0 -clientip
sort truncates at 10k values - try something like this
| sort 0 -clientip
Thanks!
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
It just suited my work sequence...