Getting Data In

transforms.conf delimiter ASCII

pierre_weg
Path Finder

Hi all!

A have a log file that use ASCII Dec 031 (US - Unit Separator) as delimiter.
How can I configure my transforms and props to work with this delimiter?

Thanks a lot.

0 Karma
1 Solution

woodcock
Esteemed Legend

Use RegEx encoding for this character: \x1F.

View solution in original post

woodcock
Esteemed Legend

Use RegEx encoding for this character: \x1F.

pierre_weg
Path Finder

I set my props as follow:
[mailheader]
NO_BINARY_CHECK = 1
pulldown_type = 1
CHECK_FOR_HEADER = false
REPORT-AutoHeader = MailHeader

and my transforms as follow:
[MailHeader]
DELIMS="\1f"
FIELDS="FILENAME","TIMESTAMP","IP","FROM","RETURN_PATH","TO","CC","SUBJECT","AUTH"

Is not running... 😞
The fields aro not correctly separated.

0 Karma

woodcock
Esteemed Legend

I am not sure if DELIMS method will work but try this transforms.conf and see:

[MailHeader]
DELIMS="\x1F"
FIELDS=FILENAME, TIMESTAMP, IP, FROM, RETURN_PATH, TO, CC, SUBJECT, AUTH

If you can't make it work then keep your props.conf the same and try this for transforms.conf:

[MailHeader]
REGEX=^([^\x1F]*)\x1F([^\x1F]*)\x1F([^\x1F]*)\x1F([^\x1F]*)\x1F([^\x1F]*)\x1F([^\x1F]*)\x1F([^\x1F]*)\x1F([^\x1F]*)\x1F([^\x1F]*)
FORMAT=FILENAME::$1 TIMESTAMP::$2 IP::$3 FROM::$4 RETURN_PATH::$5 TO::$6 CC::$7 SUBJECT::$8 AUTH::$9
0 Karma

pierre_weg
Path Finder

Great!
DELIMS do not work, but REGEX works very fine.
Thanks a lot

0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...