Knowledge Management

Are '.' characters in KV lookup field names supported?

jthunnissen
Path Finder

I notice that whenever I create a KV-store lookup definition with a field containing a '.' character, it does not work properly. Surrounding the fieldname with """ does not help.

Writing to the lookup with the outputlookup command results in the message:
"Could not write to collection 'my_collection': An error occurred while saving to the KV Store.

When I remove the '.' character(s) from the field names in de lookup definition it works again.

0 Karma

gjanders
SplunkTrust
SplunkTrust

According to mongodb

 Restrictions on Field Names

        Field names cannot contain the null character.
        Top-level field names cannot start with the dollar sign ($) character.
        Otherwise, starting in MongoDB 3.6, the server permits storage of field names that contain dots (i.e. .) and dollar signs (i.e. $).

I know Splunk 7 uses an older version of mongodb (3.4 perhaps), I believe Splunk 7.2.x uses 3.6 but I also could not use "." characters in field names in that version, so I suspect you will need to avoid the $ symbol and the . symbol is field names via kvstore.

0 Karma
Get Updates on the Splunk Community!

Celebrating Fast Lane: 2025 Authorized Learning Partner of the Year

At .conf25, Splunk proudly recognized Fast Lane as the 2025 Authorized Learning Partner of the Year. This ...

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 ...