Getting Data In

Automatic removal of duplicate log entries

tpride
Engager

Hi,

I currently have the following configuration:

                       --> rsyslog server (with splunk forwarder) --
                     /                                               \
Many linux Servers --                                                 --> Splunk Indexer/Search Head
                     \                                               /
                       --> rsyslog server (with splunk forwarder) --

All Linux servers have their rsyslog clients configured to forward a copy of each log entry to both of the central rsyslog servers, thus the splunk forwarders are then forwarding both copies onto the Splunk Indexder which creates a duplicate entry for each event. Given this setup is there any way of configuring Splunk to automatically remove the duplicate log entries this setup is generating (aside from disabling one of the splunk forwarders on one of the rsyslog servers)

Cheers,
Tom

Tags (2)
0 Karma
1 Solution

yannK
Splunk Employee
Splunk Employee

No because the events cannot be compared to each other before being indexed. You should stop one of the sources.

At search time you can remove duplicated using "dedup" but this will not reduce your indexed volume.

View solution in original post

yannK
Splunk Employee
Splunk Employee

No because the events cannot be compared to each other before being indexed. You should stop one of the sources.

At search time you can remove duplicated using "dedup" but this will not reduce your indexed volume.

tpride
Engager

Thanks yannK,

I pretty much expected that that would be the answer, but I needed to check because this is my first time using Splunk so I'm not up to speed on all of it's capabilities.

Cheers,
Tom

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!

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

Preparing your Splunk Environment for OpenSSL3

The Splunk platform will transition to OpenSSL version 3 in a future release. Actions are required to prepare ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...