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.

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!

Splunk App Dev Quarterly Roundup: AI, Agents, and Innovation!

Another quarter, another wave of innovation. From complex integrations to pushing the limits ...

What’s New in Splunk AI: Volume 02

Welcome to the second edition of “What’s New in Splunk AI” where we look at the latest and greatest updates, ...

Value Insights: Now Generally Available in the CMC

Organizations are under pressure to move faster, control cost, expand AI adoption, and prove value with more ...