Monitoring Splunk

Monitoring EVTX file on different partition provides garbled data

bobmc859
New Member

I've moved the Windows Event log Forwarded Events log to another partition because I expect it to out grow the C partition on our W2K16 machine. In my input conf, before I moved the log I had it set to the following:

[WinEventLog://ForwardedEvents]
disabled = 0
index = wineventlog

Which seem to work fine, however after moving the evtx file I set up the following in my input conf file and it doesn't seem to work as expected

[monitor://E:\ForwardedEventsLogs\ForwardedEvents.evtx]
sourcetype=WinEventLog:ForwardedEvents
index = wineventlog
disabled = 0

What I get is garbage like this:
ElfFile\x00\x00\x00\x00\x00\x00\x00\x00\x00@!\x00\x00\x00\x00\x00ԏ\x00\x00\x00\x00\x00\x80\x00\x00\x00\x00\x00\x00

Any suggestions on what I'm doing wrong?

Thanks!

Tags (1)
0 Karma
Get Updates on the Splunk Community!

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...