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!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...