Splunk Search

Weird result when using *| dedup somthing | timechart count

RadishBu
New Member

Hi I am now creating splunk dashboard, but I am facing a weird result that I am really confused:

I tried two queries:

query1: * | dedup somthing | timechart count(somthing) as total

query2: * | timechart distinct_count(something) as total

In my understanding, these two queries should give me total number of distinct "something" in every bucket.

But the thing is I get different result:

for example I use last 7 day time range:

I get this:

query1: 1,1,0,0,1,1,3

query2: 1,3,0,0,1,4,3

 

Actually query 2 is correct. I do have 3 and 4 "something" at day2 and day 6.

 

So what is the difference between these two queries??

 

Labels (1)
0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

Query 1 has dedup'd across the whole result set so the timechart is counting how many of the unique things have been found on each day.

Query 2 is counting how many different things happened each day.

Day1234567
dcga,b,f  ea,b,c,da,b,c
dedupgf  eda,b,c

Dedup'ing right to left

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!

Cisco Data Fabric from Architecture to Investigation, Better SOC Visibility, and More ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

The Trust Gap: Why a Data Foundation is Fundamental to an Agentic Enterprise

The Trust Gap: Why a data foundation is fundamental to an  Agentic Enterprise.   Agentic AI is transforming ...

Data Management Digest – September 2026

    Welcome to the September 2026 edition of Data Management Digest! September brought a fresh wave of ...