Getting Data In

Splunk Metadata for Windows EVTX Files

sdwilkerson
Contributor

I am at a site where we are using a Splunk Forwarder to mount a DFS share and read EVTX Archive Files placed there by another entity.

The Splunk Forwarder is 4.1.5 x64 on Windows 2008. The Splunk Forwarder is also a Search Head federating search requests to the same indexer where it is sending these evtx logs (not that it should make a difference).

There are no problems with the reads/parse of the EVTX files; however, we appear to have a problem with modifying the Splunk Metadata for these events.

Ideally, we would customize the Index field. This appears to not work.

In the inputs.conf I have tried setting the index and the sourcetype but no matter what I enter, here is where the events show up:

  • index=main
  • sourcetype=WinEventLog:Security

I have also tried using props/transforms to set the Metatdata DEST_KEY on both the Forwarder and the Indexer (several ways). No matter, what I select or set, it appears that I can have no impact on the index or sourcetype.

My thought is that since the evtx files are binary, that a separate process handles these that isn't accepting modification.

Is this crazy or some limitation of the (evt|evtx) parser?

Sean

Tags (3)
1 Solution

Ledio_Ago
Splunk Employee
Splunk Employee

Sean, that is true. You can't set index, source or any other metadata for ".evt(x)" type inputs. There is a special process that does the parsing, instead of the tailing processor, and it doesn't support setting those type of metadata.

This has been fixed and will be shipped with next major version of Splunk, 4.2

Thanks, Ledio

View solution in original post

Ledio_Ago
Splunk Employee
Splunk Employee

Sean, that is true. You can't set index, source or any other metadata for ".evt(x)" type inputs. There is a special process that does the parsing, instead of the tailing processor, and it doesn't support setting those type of metadata.

This has been fixed and will be shipped with next major version of Splunk, 4.2

Thanks, Ledio

malmoore
Splunk Employee
Splunk Employee

Done. (from the docs team)

Ledio_Ago
Splunk Employee
Splunk Employee

That's a good point. I will send this to the docs team and them updated.

Thanks!

sdwilkerson
Contributor

Ledio,
Much appreciated. I thought I was going nuts. Wish the docs had warned me.
Sean

0 Karma
Get Updates on the Splunk Community!

Welcome to the Splunk Community!

(view in My Videos) We're so glad you're here! The Splunk Community is place to connect, learn, give back, and ...

Tech Talk | Elevating Digital Service Excellence: The Synergy of Splunk RUM & APM

Elevating Digital Service Excellence: The Synergy of Real User Monitoring and Application Performance ...

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...