Splunk Search

Why dedup when we have stats values function

palisetty
Communicator

@gcusello @woodcock @richgalloway
Why do we need two functions for the same functionality?
'dedup' displays unique values while 'stats values' do the same, is there any difference other than 'stats' is transforming command and 'dedup' is not?

Tags (2)
0 Karma
1 Solution

jpolvino
Builder

stats transforms, so your original fields are no longer accessible. dedup is a great way to limit the number of rows to be used further down the line, and still have full access to the fields and their values.

View solution in original post

jpolvino
Builder

stats transforms, so your original fields are no longer accessible. dedup is a great way to limit the number of rows to be used further down the line, and still have full access to the fields and their values.

starcher
Influencer

Because there are times you want to dedup without using stats. So both commands are valid. If you are going to stats then you would be redundant to also use dedup.

Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...