Getting Data In

XmlWinEventLog:ForwardedEvents sourcetype field extraction issue

tech_g706
Path Finder

Hi,

I’m currently receiving Windows logs in Splunk via the (UF → HF → Splunk Cloud). The logs are being assigned to two sourcetypes:

  • XmlWinEventLog

  • XmlWinEventLog:ForwardedEvents

For the XmlWinEventLog sourcetype, field extractions are working correctly. However, for the XmlWinEventLog:ForwardedEvents sourcetype, no field extractions are being applied, even though the log format appears to be the same.

Since I am not very familiar with the XmlWinEventLog:ForwardedEvents sourcetype, I would like guidance on how to configure the Heavy Forwarder so that it applies the same field extractions used by XmlWinEventLog to XmlWinEventLog:ForwardedEvents.

Thank you for your support.

 

0 Karma

richgalloway
SplunkTrust
SplunkTrust

To ensure proper processing of data, EVERY sourcetype should have settings in a props.conf file.  This keeps Splunk from having to guess about the data and improves onboarding performance.

If data with the XmlWinEventLog:ForwardedEvents sourcetype looks similar to data with the XmlWinEventLog sourcetype then it's a simple matter of copying the XmlWinEventLog stanza in props.conf to create a XmlWinEventLog:ForwardedEvents stanza.

---
If this reply helps you, Karma would be appreciated.
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!

Splunk App Dev Quarterly Roundup: AI, Agents, and Innovation!

Another quarter, another wave of innovation. From complex integrations to pushing the limits ...

What’s New in Splunk AI: Volume 02

Welcome to the second edition of “What’s New in Splunk AI” where we look at the latest and greatest updates, ...

Value Insights: Now Generally Available in the CMC

Organizations are under pressure to move faster, control cost, expand AI adoption, and prove value with more ...