Getting Data In

REGEX help with ingesting XML file. Timestamp not working correctly

joesrepsol
Path Finder

Looking to extract the "2017-06-23 15:48:56.218" from the 2nd line in the log and use it for the timestamp when ingesting this xml log into Splunk. Today Splunk is picking up the wrong timestamp for the timestamp recognition, which causes problems.

Thinking that I need to define some REGEX in a props.conf/transforms.conf file but missing the REGEX experience to pull this out.

Help?

<auditEvent encrypted="n" signed="n">
    <localTime>2017-06-23 15:48:56.218 -0700</localTime>
    <time>2017-06-23 22:48:56.218</time>
    <utc>2017-06-23 22:48:56.218</utc>
    <sessionId>25</sessionId>
    <msg>
        <msgID>AUD0117E</msgID>
        <msgText>SessionId: 25 - Login attempt to CM by intruder through local store Failed with an operator role of UNKNOWN ROLE</msgText>
        <condCode>8</condCode>
    </msg>
</auditEvent>

using Splunk Enterprise 6.5.0 (Linux)

Tags (1)
0 Karma

joesrepsol
Path Finder

Also noticed that Splunk is not automatically figuring out which breaks to use for the entire event... WHOA. In this case, it's XML and I need to also figure out how to tell splunk that each event starts with:

<auditEvent encrypted="n" signed="n">

and ends with:

</auditEvent>
0 Karma

joesrepsol
Path Finder

Clarification...

Looking to pull the date/time stamp between "" and "-0700"

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!

Developer Spotlight with Denis Gladkikh

From Splunk Engineer to Kubernetes App Builder Denis GladkikhWhat happens when a lifelong developer turns a ...

Governing Enterprise AI, Bringing Cisco Telemetry Home, and More from Splunk Lantern

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...