Splunk Search

Lookup fails unless using a table

klhogan
New Member

The query below produces the results expected, but if I remove the "table PSID" section (bolded) it fails, saying 22 errors were generated while executing. PSID is a parsed field, bolded in the event record shown.

"RA_GENERATED" | table PSID | lookup LocationLookup.csv PeopleSoftId AS PSID OUTPUT Brand

Event record:
1/16/20 11:23:09.989 AM strong text16 Jan 2020 11:23:09:989 | WARN | K320LE100005 | 1019178 | XXXR01 | MOSLoggingAspect | - RA_Generated 111 111 111| LangCode en| CountryCode USA

0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

It sounds like the lookup file is not getting distributed to the indexers. One of the 22 error messages should confirm that.

The table command forces the query to be completed by the search head from that point and the SH is where the lookup file resides.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

It sounds like the lookup file is not getting distributed to the indexers. One of the 22 error messages should confirm that.

The table command forces the query to be completed by the search head from that point and the SH is where the lookup file resides.

---
If this reply helps you, Karma would be appreciated.

klhogan
New Member

I think you're right. Adding a local=true to the lookup seems to work. Thanks!

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...