Splunk Search

regex field extraction; same source, variably different fields

gsawyer1
Engager

I've got input from a syslog source, that looks like this:

2012-10-10 04:04:52[connection-5] AUTH: User xxx authenticated.

2012-10-10 04:04:52[Scan Thread: document1.doc -> /127.0.0.1] MODULES: File analysis

I want to extract the user (xxx) and document1.doc fields at search time, if possible, for inclusion in a table, and charts, etc, but am having trouble devising a rex statement in the search that can extract both values as different fields, yet from the same source. A conditional regex is what I am looking for. This would also be part of a transaction (the next step to undertake). Any suggestions would be great!....

Tags (2)
0 Karma

lguinn2
Legend

You can have multiple extract statements for a source or sourcetype...

[source::/yoursourcehere]
EXTRACT-e1=AUTH: User\s+(?<user>\S+)\s+authenticated.
EXTRACT-e2=Scan Thread:\s+(<file>\S+)\s

lguinn2
Legend

[sourcetype::mysource] is not valid. You need to specify either

[mysourcetypename]

or

[source::/pathto/mysource]

0 Karma

lguinn2
Legend

No reason. It's probably even better to generalize the whitespace with \s as you did.

0 Karma

gsawyer1
Engager

Was there some reason why you did not use the following syntax:

[source::/yoursourcehere]
EXTRACT-e1=AUTH:\s+User\s+(?\S+)\s+authenticated.
EXTRACT-e2=Scan\sThread:\s+(\S+)\s\-\>\s

0 Karma

gsawyer1
Engager

I attempted the following in props.conf only:

[sourcetype::mysource] (because I already have multiple transforms applied to this source)
EXTRACT-e1=AUTH: User\s+(?<submitter>\S+)\s+authenticated.
EXTRACT-e2=Scan Thread:\s+(<file>\S+)\s\-\>\s

....and nothing happened. No fields "submitter" or "file" were extracted when I ran a search for that sourcetype, looking for results that contain this data.

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!

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 ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...