Getting Data In

set delimiter

newbiesplunk
Path Finder

Hi,
The key-pair values delimiter is ":" instead of "=", how to configure such that the colon ":" is also a delimiter? thks
I configured below:

props.conf
[test]
TRANSFORMS-delim=AddDelimiter

transforms.conf
[AddDelimiter]
DELIMS=":"

But it does not works.

Tags (1)

lguinn2
Legend

I think this will work

props.conf

[yoursourcetypehere]
KV_MODE = none
REPORT-extract1 = special-field-extraction

transforms.conf

[special-field-extraction]
DELIMS = " ", ":"
MV_ADD = true

I believe that you need two values for the DELIMS attribute - the first is the list of characters that can separate fields, so I set it to a space. The second value identifies the separator between the field name and its value, so I set it to ":".
Setting KV_MODE to none in props.conf disables the default field extraction, which is based on "=". MV_ADD allows multi-value fields, but you can remove this line if it doesn't apply.

somesoni2
Revered Legend

Try adding this to props.conf

[test]
SEDCMD-replacecolon = s/:/=/g
0 Karma

kristian_kolb
Ultra Champion

Hmm, since that would mean that _raw is rewritten, it could mess up timestamps, which regularly use colons.
/k

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!

Casting Call: Compete in Cyber Games

Lights, Camera, SecOps: Apply to Compete in Cyber Games     Think you have what it takes to beat the clock? ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

How Edge Processor's Durable Queue Works

Edge Processor sits in one of the most consequential places in any Splunk pipeline: between your data sources ...