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
SplunkTrust
SplunkTrust

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!

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...

Welcome to the Splunk Community!

(view in My Videos) We're so glad you're here! The Splunk Community is place to connect, learn, give back, and ...

Tech Talk | Elevating Digital Service Excellence: The Synergy of Splunk RUM & APM

Elevating Digital Service Excellence: The Synergy of Real User Monitoring and Application Performance ...