Splunk Search

Lookup: Escaping quotation character in field value

MHibbin
Influencer

Hi SB,

Playing around with lookup tables and it appears I can not have an escaped quotation character (e.g. ") within a field in my lookup file.... Unless i'm being very "thick" today and have missed something. I thought I could trying enclosing my string in a set of '' (e.g. 'foo \"bar\"'), but this apparently doesn't work?

I've had a look at the configuration file and can not see a method for changing the quotation character for lookups.

Can anyone help here?

Cheers.

P.S Apologies if this has been asked already, not seen anything on my search... Also, apologies again if I'm just being stupid.

Tags (2)
0 Karma
1 Solution

MHibbin
Influencer

Okay, in the mean time I have work around using the \x special character and the hex equivalent of ". Using this in my example above this would be:

foo \x22bar\x22

This (if you haven't already guessed) is for regex... it's added/modified from the Splunkweb and then used in scripts in the background. This is for an odd use-case.

Any other suggestions are welcome of course.

View solution in original post

0 Karma

MHibbin
Influencer

Okay, in the mean time I have work around using the \x special character and the hex equivalent of ". Using this in my example above this would be:

foo \x22bar\x22

This (if you haven't already guessed) is for regex... it's added/modified from the Splunkweb and then used in scripts in the background. This is for an odd use-case.

Any other suggestions are welcome of course.

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...