Getting Data In

Unique Contraint in Splunk

akshgpt25
Explorer

We have a number of files containing events. Each event has a unique id in itself. but the same event(with the same event_id) can exist in other files as well. We want 1 event to be indexed 1 time in Splunk and if the event with the same event_id comes again just avoid it. This is the same as _id in Elastic Search or another database's primary key.

Is it possible to achieve the same in Splunk? If yes, How?

 

 

Labels (1)
Tags (1)
0 Karma

bowesmana
SplunkTrust
SplunkTrust

I'm not sure if this can first validate if an event is in Splunk before it routes data to Splunk and I don't know a great deal about it, but the DSP component may do what you want

https://www.splunk.com/en_us/software/stream-processing.html

 

0 Karma

kamlesh_vaghela
SplunkTrust
SplunkTrust

@akshgpt25 

Not sure it is possible during indexing, but you can get unique event in SPL by using dedup command. 

https://docs.splunk.com/Documentation/Splunk/8.0.4/SearchReference/Dedup

Thanks

0 Karma

akshgpt25
Explorer

Thanks, @kamlesh_vaghela 

But we have millions of events with this behavior and every time end-user have to use dedup in all their queries.

Is there any other way to achieve the same?

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @akshgpt25 ,

as @kamlesh_vaghela  said it isn't possible to filter events before indexing to avoid duplicates, but you could ingest all the data and schedule a search that extract the unduplicated events and store them in a summary_index, then you can use this index for your searches.

Ciao.

Giuseppe

0 Karma
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...