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
Get Updates on the Splunk Community!

Aligning Observability Costs with Business Value: Practical Strategies

 Join us for an engaging Tech Talk on Aligning Observability Costs with Business Value: Practical ...

Mastering Data Pipelines: Unlocking Value with Splunk

 In today's AI-driven world, organizations must balance the challenges of managing the explosion of data with ...

Splunk Up Your Game: Why It's Time to Embrace Python 3.9+ and OpenSSL 3.0

Did you know that for Splunk Enterprise 9.4, Python 3.9 is the default interpreter? This shift is not just a ...