Hi,
In lookup definition,
IT_server_list is created in lookup definition which is mapped to CSV named (server_list.csv)
In Lookup Table,
server_list.csv file is there
In automatic lookup,
IT_server_list is created
why do we need automatic lookup?
Hi @VijaySrrie
Your transforms.conf should be having lookup definition, that is enough for you to run | lookup command in UI.
What if the search events to be enriched automatically by adding additional field when someone search the sourcetype/host/source. Then props.conf automatic lookup LOOKUP-<class>= syntax works.
Docs says: you can optionally create an additional props.conf configuration that makes the lookup "automatic." This means that it runs in the background at search time and automatically adds output fields to events that have the correct match fields.
Splunk user doesn't need to use | lookup command everytime, if automatic lookup been configured one time. Refer - Make your lookup automatic - Splunk Documentation
---
An upvote would be appreciated and Accept solution if this reply helps!
Hi @VijaySrrie
Your transforms.conf should be having lookup definition, that is enough for you to run | lookup command in UI.
What if the search events to be enriched automatically by adding additional field when someone search the sourcetype/host/source. Then props.conf automatic lookup LOOKUP-<class>= syntax works.
Docs says: you can optionally create an additional props.conf configuration that makes the lookup "automatic." This means that it runs in the background at search time and automatically adds output fields to events that have the correct match fields.
Splunk user doesn't need to use | lookup command everytime, if automatic lookup been configured one time. Refer - Make your lookup automatic - Splunk Documentation
---
An upvote would be appreciated and Accept solution if this reply helps!