Splunk Cloud Platform

Moving KVstore lookup using "Lookup definitions" does not work

99eaglez
Explorer

After moving a KVstore to a new Application, Splunk can not longer render the lookup.

When moving a KVstore using the "move" link in "Lookup definitions" it only moves the transforms.conf stanza and not the collections.conf stanza.

The on-prem solution is to manually move collections.conf but this cannot be done in Splunk Cloud.

Labels (3)
0 Karma
1 Solution

99eaglez
Explorer

Although it looks like you should be able to use the "move" link in "Lookup definitions", you cannot.

The best way to achieve this is to create a new KVstore in the desired location then copy the KVstore data there.

| inputlookup my_old_kvstore
| outputlookup my_new_kvstore

I did create a Splunk Idea to resolve this issue. Please vote for it here.

View solution in original post

0 Karma

99eaglez
Explorer

Although it looks like you should be able to use the "move" link in "Lookup definitions", you cannot.

The best way to achieve this is to create a new KVstore in the desired location then copy the KVstore data there.

| inputlookup my_old_kvstore
| outputlookup my_new_kvstore

I did create a Splunk Idea to resolve this issue. Please vote for it here.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...