Splunk Dev

Indexing Semi-Unified Logs

shayhibah
Path Finder

Hi,

In case I have data source that sends logs to my Splunk server and some logs can be sent more than once since the data source uses semi-unified logs (original log fields + all its updates).

For example:
time: 10:00 am ---- log: key=0x0001; aa=1; bb=2;
time:10:01 am --- log: key=0x0001; aa=2; bb=2;

Is there any option to delete the old log when identifying a new log with the same key?

Thanks

Tags (1)
0 Karma

FrankVl
Ultra Champion

That's not really the idea behind ingesting data in Splunk, at least not for working with normal indexed data.

Sounds like a summary index (or lookup) in which you keep the latest entry for each key might be a direction to look into.

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