Monitoring Splunk

Splunk optimization : dedup or latest()?


For last 2 months i created a lot of dashboards on Splunk.
In most of my searchs i need to get only the last series of results.
I see i use 2 methods, both work well, but i would know which one is more optimized.
Sometimes I use

search|dedup MyField sortby -_time|table MyField aField bField

and sometimes I use

search|stats latest(aField),latest(bField) by MyField

What is the best to use for short periods/long periods?

0 Karma

Splunk Employee
Splunk Employee

In a distributed environment, stats is likely to be faster, because the indexers can "prestats" before sending their results to the search head. I think that dedup may do a little of this, but the notable distinction is that dedup can't be used with report acceleration searches. I tend to use stats for this purpose.

Ultra Champion

I would think that dedup should be slightly faster, but not by a big margin. Best way to find out is to use the Job Inspector for the searches and look for yourself. It's far more important to limit the initial search, i.e. what comes before the first pipe. Specifying correct index, host, sourcetype and time-limits will have far more effect on the search performance.

However, your dedup syntax looks a bit off, shouldn't it be sortby instead of by?



Ure right for dedup, i wrote all from mind so mistakes 🙂

0 Karma
Get Updates on the Splunk Community!

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...

March Community Office Hours Security Series Uncovered!

Hello Splunk Community! In March, Splunk Community Office Hours spotlighted our fabulous Splunk Threat ...

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

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars in April. This post ...