Splunk Search

What are some solutions for high cardinality field reporting?

the_wolverine
Champion

We have high cardinality data -- virtually every event is unique except for a small percentage of cases that we care about. So we're finding that we have count the unique ids, track them somehow in order to find the duplicates. Its just not feasible in Splunk when we have millions of events per minute.

Example:

search | stats count by unique_id | where count>1

(Millions of events per minute, results in a few hundred events where count>1). Summary indexing is not really a solution here since the unique_id could cross time/minute boundary.

0 Karma

valiquet
Contributor

|fields unique_id
|stats list( unique_id) AS id
| where mvfilter(mvcount(id)>1) != NULL

0 Karma

somesoni2
Revered Legend

May be setup indexed time field extraction for your unique_id field so you could use tstats with it.

Get Updates on the Splunk Community!

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

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...