Getting Data In

Duplicated Events: Local Log4net_xml Monitor

JacobCarrell
Explorer

I've got an issue where a significant portion of my ingested Log4Net_xml sourcetype logs have duplicate events. I'm currently using a file monitor on a Ubuntu 16.04 LTS, Splunk 7.3.0 machine with a local Monitor stanza to ingest the logs which looks like this:

[monitor:///mnt/CALogs/.../*.log]
disabled = 0
host_segment = 4
index = ca
sourcetype = log4net_xml
#initCrcLength = 1024 # Tried this, it started reindexing all the log file.

Our Log4Net configs looks like this:

<appender name="RollingFile" type="log4net.Appender.RollingFileAppender">
               <file type="log4net.Util.PatternString" value="\\server1\ca\Logs\Application\%property{log4net:HostName}\Application.log" />
               <appendToFile value="true" />
               <rollingStyle value="Size" />
               <maximumFileSize value="5MB" />
               <staticLogFileName value="true" />
               <maxSizeRollBackups value="10" />
               <layout type="log4net.Layout.XMLLayout" />
          </appender>

I have that directory mounted over SMB/CIFS with the following entry in fstab:

//server1/LogsCA /mnt/CALogs cifs username=user,password=Password,domain=somedomain.dev,sec=ntlm 0 0

 

Can anybody spot what I'm doing wrong?

 

Here's a picture of the search that I'm using to estimate duplicates:

JacobCarrell_0-1595945517609.png

 

Labels (3)
Tags (1)
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!

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

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