topic Re: add automatic lookup for kvstore in Splunk Search

Add automatic lookup for kvstore?

Shakira1 — Mon, 13 Mar 2023 13:43:28 GMT

I have kvstore which generate the data by API.

when I use | lookup mylookup id output data - its working

I want to convert it to automatic lookup in some index, but its not working.

any idea why?

Re: add automatic lookup for kvstore

gcusello — Sun, 12 Mar 2023 14:56:48 GMT

Hi @Shakira1 ,

whad do you mean with "it's not working"? what's the bahavior?

did you created the lookup definition?

Could you share the related conf files (transforms.conf)?

Ciao.

Giuseppe

Re: add automatic lookup for kvstore

Shakira1 — Tue, 14 Mar 2023 09:50:55 GMT

The purpose is to enrichment the data automatically

I did it in the UI under automatic lookup:

my lookup id AS id OUTPUT my fields_from_the_lookups

it always working but the diff here is that I'm using KVstore

thanks

Re: add automatic lookup for kvstore

yuanliu — Wed, 15 Mar 2023 05:06:24 GMT

I'm not sure if I follow. This is the UI under Automatic Lookup.

Can you illustrate how each field is populated? (Anonymize as needed.)

Re: add automatic lookup for kvstore

Shakira1 — Wed, 15 Mar 2023 10:01:23 GMT

this one? this is working for me in SPL

and I add automatic lookup - which not working ( didnt extract the fields)

Re: add automatic lookup for kvstore

yuanliu — Thu, 16 Mar 2023 06:04:37 GMT

Not sure where the confusion is, but no box in Advanced options accepts an expression like "| lookup mylookup id output data". (Define a KV Store lookup in Splunk Web.) Or maybe I just didn't get what the problem was.

Maybe you can explain/illustrate/screenshot how you "convert it to automatic lookup in some index"; in addition, what is "it" that you are trying to convert? Also, "not working" conveys little information in the best of situations. You need to explain the data set (including event format in the index), what fields are extracted at index time, what fields are extracted automatically at search time, etc. In particular, how is the field id obtained when you use that SPL? For example, calculated fields cannot be used in automatic lookup. The sequence of search-time operations is full of such nuances.