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
Get Updates on the Splunk Community!

Webinar Recap | Revolutionizing IT Operations: The Transformative Power of AI and ML ...

The Transformative Power of AI and ML in Enhancing Observability   In the realm of IT operations, the ...

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...