topic Re: How to use values in lookup table not as fields but as search strings? in Splunk Search

How to use values in lookup table not as fields but as search strings?

christopheryu — Tue, 29 Sep 2020 13:22:11 GMT

Using lookup table to search events but having some issues:

|inputlookup router_lookup | rename Router_Name as DEVICE_NAME Router_Interface as INTERFACE | fields DEVICE_NAME, INTERFACE | format

results to:

( ( DEVICE_NAME="ROUTERA" AND INTERFACE="xe-5/2/0" ) OR ( DEVICE_NAME="ROUTERB" AND INTERFACE="xe-9/3/1" ) OR ( DEVICE_NAME="ROUTERC" AND INTERFACE="xe-6/7/0" ) ... etc

However, I found out that DEVICE_NAME is not a defined field for all routers, so I tried doing this:

results to:

( ("ROUTERA AND xe-5/2/0" ) OR ( "ROUTERB AND xe-9/3/1" ) OR ( "ROUTERC AND xe-6/7/0" ) ... etc

this is NOT the result I was looking for since they have quotation marks.

this is what I need:

( (ROUTERA AND xe-5/2/0 ) OR (ROUTERB AND xe-9/3/1 ) OR (ROUTERC AND xe-6/7/0) ... etc

thank you in advance!

Re: How to use values in lookup table not as fields but as search strings?

jkat54 — Tue, 29 Sep 2020 13:22:14 GMT

Try this with your second search:

| return $query | format

But then simplify, you've got renames and such tht are really unnecessary.

Re: How to use values in lookup table not as fields but as search strings?

christopheryu — Wed, 22 Mar 2017 14:34:22 GMT

Thank you for the response. Here is what I got using your suggestion:

( ("ROUTERA AND xe-5/2/0" ))

Returned only one item and did not remove the quotation marks. Removing the "| return $query" yields the same result as my second search.

Re: How to use values in lookup table not as fields but as search strings?

woodcock — Wed, 22 Mar 2017 23:31:26 GMT

Like this:

|inputlookup router_lookup | rename Router_Name as DEVICE_NAME Router_Interface as INTERFACE | eval Interface_Name=DEVICE_NAME." AND ".INTERFACE | fields Interface_Name | rename Interface_Name as query | format | rex field=search mode=sed "s/\"//g"

Re: How to use values in lookup table not as fields but as search strings?

christopheryu — Thu, 23 Mar 2017 14:03:55 GMT

That worked, thank you!