Knowledge Management

Delete overlaps from summary index

rroberts
Splunk Employee
Splunk Employee

The knowledge manager manual mentions ""Manually delete the overlaps from the summary index using the search language." I'm familiar with the Delete command and how it works. But, what other command(s) would you use to pipe only the dups to the Delete command, whilst preserving only one copy of each events?

index=summary search_name=xyz et= lt= **Twilight Zone********* | delete**

In other words, how do I output only duplicates, but exclude one copy (or the original)?

Tags (2)

gkanapathy
Splunk Employee
Splunk Employee

You would use the overlap search command, but I'm not sure you can pipe the output of that to delete, which is what I think "manually" is trying to get across.

rroberts
Splunk Employee
Splunk Employee

yes, I used ...index=summary search_name=productPurchased | overlap but I could not pipe to delete (This command cannot be invoked after the non-streaming command 'overlap'.) Pipe to overlap did generate a results table with overlap_latest and overlap_earliest fields but not sure how to use these.

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

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...