Splunk Enterprise Security

How to find a Missing Lookup

walsborn
Path Finder

I am new to the Splunk admin role and am having troubles with some errors. When a search is conducting I can see errors coming from all indexers. Starting with [indexer] Could not load lookup=LOOKUP-known_malicious_domains. This is in ES, and I've reviewed splunkd log, var run log, and cannot find additional information on where to look for this lookup. I have tried to manually add this lookup in search with no avail. I have made lookup tables in the search-heads with this filename in etc/apps/search/lookups/known_malicious_domains but that does not seem to help. Anyone else ran into this before?

0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

The lookup file may indeed be missing, but you must add it in the right place. The search app is not the right place.
Go to Settings->Lookups->Lookup Definitions and look for the reported lookup. There you will see the name of the lookup file being used and the app which defines it. Create a replace lookup file by the same name in that app and the error should go away.

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

View solution in original post

0 Karma

richgalloway
SplunkTrust
SplunkTrust

The lookup file may indeed be missing, but you must add it in the right place. The search app is not the right place.
Go to Settings->Lookups->Lookup Definitions and look for the reported lookup. There you will see the name of the lookup file being used and the app which defines it. Create a replace lookup file by the same name in that app and the error should go away.

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

walsborn
Path Finder

Worked! Thanks Rich!

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...