Splunk isn't completely parsing the xml into fields in search results, only sections. For example, in the sample event below, the system and userdata sections are fields but the xml headers inside them are not parsed into fields (i.e. Username and IpAddress .)
Based on some of what I've read here in the forums, I've already edited my props.conf for sourcetype=XmlWinEventLog but haven't seen any change.
[source::XmlWinEventLog]
KV_MODE=xml
TRUNCATE = 0
I don't know what I'm missing and could use some help. (Hell, what I put in there, Splunk was probably already doing)
Here's a sample event (I added line breaks to make it easier to read. Raw data in search results it's a single line):
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event" xml:lang="en-US">
<System>
<Provider Name="Microsoft-Windows-TerminalServices-Gateway" Guid="{4D5AE6A1-C7C8-4E6D-B840-4D8080B42E1B}" />
<EventID>200</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>2</Task>
<Opcode>30</Opcode>
<Keywords>0x4020000001000000</Keywords>
<TimeCreated SystemTime="2020-02-21T18:54:19.913701800Z" />
<EventRecordID>1219</EventRecordID>
<Correlation ActivityID="{BEA11342-474B-47DE-907D-F2FBEBD40000}" />
<Execution ProcessID="5480" ThreadID="8416" />
<Channel>Microsoft-Windows-TerminalServices-Gateway/Operational</Channel>
<Computer>gatewayserver.domain.com</Computer>
<Security UserID="S-1-5-20" />
</System>
<UserData>
<EventInfo xmlns="aag">
<Username>domain\username</Username>
<IpAddress>173.x.x.x</IpAddress>
<AuthType>NTLM</AuthType>
<Resource />
<ConnectionProtocol>HTTP</ConnectionProtocol>
<ErrorCode>0</ErrorCode>
</EventInfo>
</UserData>
<RenderingInfo Culture="en-US">
<Message>The user "domain\username", on client computer "173.x.x.x", met connection authorization policy requirements and was therefore authorized to access the RD Gateway server. The authentication method used was: "NTLM" and connection protocol used: "HTTP".</Message>
<Level>Information</Level>
<Task />
<Opcode />
<Channel />
<Provider />
<Keywords>
<Keyword>Audit Success</Keyword>
</Keywords>
</RenderingInfo>
</Event>
... View more