Splunk Search

Lookups with backslash in key

JensT
Communicator

Hi,

We're analazing database logs. From SyBase, Oracle and MSSQL.

MSSQL full db instances contain a \

e.g. MSNG123\MyInstance

We want to use a lookup to enrich the data.

It works fine with the lookup command. But not using the automatic lookup.

Any suggestions?

Using Splunk 4.3.6

Regards,

Jens

Tags (2)
0 Karma
1 Solution

MuS
SplunkTrust
SplunkTrust

Hi JensT,

to make it short, this works as well with the automatic lookup. I did a quick test on VERSION=4.3.6 BUILD=153775 PRODUCT=splunk PLATFORM=Linux-x86_64 with a lookup file containing the following data:

host,database
myhost,"foo\myDB"
#myhost,bar\\yourDB
#myhost,'bar\yourDB'
#myhost,baryourDB

I did setup an automatic lookup for sourcetype, source and host and all three of them were working. I was able to get back database values like foo\myDB or 'bar\yourDB'

I think the problem is, that either the sourcetype, source or host name do not match. For example automatic lookup in my test for sourcetype=* did not work, but with sourcetype=splunkd_access it worked.

I did use a run everywhere search like this: index=_internal | head 1 | table host database which will return one event of sourcetype=splunkd_access and this was my test automatic lookup in props.conf:

[splunkd_access]
LOOKUP-mydb = mydatabase host AS host OUTPUTNEW database AS database

and the result will be this:

alt text

hope this helps ...

cheers, MuS

PS: Grüsse aus Basel 😉

View solution in original post

MuS
SplunkTrust
SplunkTrust

Hi JensT,

to make it short, this works as well with the automatic lookup. I did a quick test on VERSION=4.3.6 BUILD=153775 PRODUCT=splunk PLATFORM=Linux-x86_64 with a lookup file containing the following data:

host,database
myhost,"foo\myDB"
#myhost,bar\\yourDB
#myhost,'bar\yourDB'
#myhost,baryourDB

I did setup an automatic lookup for sourcetype, source and host and all three of them were working. I was able to get back database values like foo\myDB or 'bar\yourDB'

I think the problem is, that either the sourcetype, source or host name do not match. For example automatic lookup in my test for sourcetype=* did not work, but with sourcetype=splunkd_access it worked.

I did use a run everywhere search like this: index=_internal | head 1 | table host database which will return one event of sourcetype=splunkd_access and this was my test automatic lookup in props.conf:

[splunkd_access]
LOOKUP-mydb = mydatabase host AS host OUTPUTNEW database AS database

and the result will be this:

alt text

hope this helps ...

cheers, MuS

PS: Grüsse aus Basel 😉

JensT
Communicator

Hi!

i retested and you are absolutely right!

1.) \ in any lookup is not a problem.

2.) Its MSSQL not MSSSQL


Thanks,

Jens

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!

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...

Design, Compete, Win: Submit Your Best Splunk Dashboards for a .conf26 Pass

Hello Splunkers,  We’re excited to kick off a Splunk Dashboard contest! We know that dashboards are a primary ...

May 2026 Splunk Expert Sessions: Security & Observability

Level Up Your Operations: May 2026 Splunk Expert Sessions Whether you are refining your security posture or ...