Getting Data In

why lookup with outputnew doesn't work, when configured in props.conf

marcokrueger
Path Finder

Hi,
I have a search with two lookups
... | lookup user_agent_filter OUTPUT botstatus | lookup ipnet_filter cidr AS ip OUTPUTNEW botstatus | ...
this works fine, but if I put it in my props.conf like
LOOKUP-user_agent_filter = user_agent_filter http_user_agent OUTPUT botstatus
LOOKUP-ipnet_filter = ipnet_filter cidr AS ip OUTPUTNEW botstatus

only the first filter works. There is no result from the second.
Is there a order or something like this how to put rules in the props.conf?

best regards
Marco

0 Karma

somesoni2
Revered Legend

As per the splunk documentation,

"OUTPUTNEW behavior has changed since 4.1.x (where none of the output fields were
written to if any of the output fields previously existed)"

0 Karma

marcokrueger
Path Finder

Okay, can you tell me, why it works in the search but if I configure it in the props.conf it doesn't work, as in the question asked? 😉
Best regards

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!

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas     Cisco Live 2026 is almost here, and this ...

What Is the Name of the USB Key Inserted by Bob Smith? (BOTS Hint, Not the Answer)

Hello Splunkers,   So you searched, “what is the name of the usb key inserted by bob smith?”  Not gonna lie… ...

Automating Threat Operations and Threat Hunting with Recorded Future

    Automating Threat Operations and Threat Hunting with Recorded Future June 29, 2026 | Register   Is your ...