Splunk Search

Lookup Table for all Sourcetype

marendra
Explorer

Hi All,

Quick question, in Manager » Lookups » Automatic lookups » Add New
on Apply to drop down box, we can select from SOurcetype, source, or host.
If I choose any of the choices, can I put * on the sourcetype field. The reason is the lookup table that I created meant for any sourcetype, and any host those are currently indexed by my SPlunk.
I tried before it wouldn't do the trick. If possible, do I need to put other character value?

Please advise on this

Thanks

Tags (1)
0 Karma
1 Solution

hazekamp
Builder

The UI will create a stanza which did not work in my testing.

## props.conf
[*]
LOOKUP-all_test = my_test_lookup sourcetype OUTPUTNEW foo

If you want this lookup to be global I would recommend specifying this property in props.conf without a stanza:

## props.conf
LOOKUP-all_test = my_test_lookup sourcetype OUTPUTNEW foo

Based on a similar Q/A it is also possible use wildcards in sourcetype for props.conf if you don't want to make the lookup global: wildcards in sourcetypes.conf

View solution in original post

marendra
Explorer

Thanks It works. Just delete the [*] and put on top of the props.conf.

Thanks again

0 Karma

NeerajDhapola7
Path Finder

Just need to select HOST as Apply To and * in named field as below while
Lookups » Automatic lookups » Add new

No need to edit Props.conf gile

Thanks
Neeraj Singh Dhapola

0 Karma

hazekamp
Builder

The UI will create a stanza which did not work in my testing.

## props.conf
[*]
LOOKUP-all_test = my_test_lookup sourcetype OUTPUTNEW foo

If you want this lookup to be global I would recommend specifying this property in props.conf without a stanza:

## props.conf
LOOKUP-all_test = my_test_lookup sourcetype OUTPUTNEW foo

Based on a similar Q/A it is also possible use wildcards in sourcetype for props.conf if you don't want to make the lookup global: wildcards in sourcetypes.conf

ASealey_Nike
Engager

I also accomplished similar using [default] as the stanza header.

gfriedmann
Communicator

A cleaner method may be using [host:*] stanza header.

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!

May 2026 Splunk Expert Sessions: Security & Observability

Level Up Your Operations: May 2026 Splunk Expert Sessions Whether you are refining your security posture or ...

Network to App: Observability Unlocked [May & June Series]

In today’s digital landscape, your environment is no longer confined to the data center. It spans complex ...

SPL2 Deep Dives, AppDynamics Integrations, SAML Made Simple and Much More on Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...