Splunk Search

Timechart and Order of Operations

mistydennis
Communicator

I am struggling with the order of operations in my timechart query. I need to show the number of Users who accessed a system daily over a 7 day period. My query shows the correct numbers for 1 day, but when I extend the timepicker to 7 days the numbers are incorrect. I've tried using dedup to get the distinct number of users, but this causes a problem when I extend the timepicker (it then dedupes users across 7 days instead of per day). Help.

index=foo sourcetype="bar" realm="keywords"
| stats dc(User) by _time, status
| timechart span=1d count by status

0 Karma
1 Solution

mistydennis
Communicator

Finally figured it out. The correct timechart command was:
index=foo sourcetype="bar" realm="keywords"
| timechart span=1d distinct_count(User) by status

View solution in original post

0 Karma

mistydennis
Communicator

Finally figured it out. The correct timechart command was:
index=foo sourcetype="bar" realm="keywords"
| timechart span=1d distinct_count(User) by status

0 Karma

richgalloway
SplunkTrust
SplunkTrust

How are the 7-day numbers incorrect?
Have you tried ignoring status? Status shouldn't matter when you only care about user count.

---
If this reply helps you, Karma would be appreciated.
0 Karma

mistydennis
Communicator

So, for example, if I look at April 2 only I get 100 users (correct). If I extend the time picker to April 1 - 2, the numbers are April 1: 25 users (should be 50), April 2: 30 users (should be 100). I need status because I need the split-by count.

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...