https://community.splunk.com/t5/Getting-Data-In/WMI-input-and-whitelisting/m-p/568242#M100856 <P>Hello there.</P><P>I finally managed to set up WMI-based event log monitoring and it seems to work <span class="lia-unicode-emoji" title=":slightly_smiling_face:">🙂</span></P><P>The problem is that it's gonna give me way to many events. I want to pull just a subset of the events from the Applicatonlog. With ordinary WinEventLog input I could set up a whitelist/blacklist to limit the processed events at the forwarder level. The same doesn't seem to work with the WMI:whatever type of input.</P><P>Is there indeed no way to limit the ingested events? Do I have to do it further down the stream by selective routing on HF?</P> Thu, 23 Sep 2021 13:26:34 GMT PickleRick 2021-09-23T13:26:34Z https://community.splunk.com/t5/Getting-Data-In/WMI-input-and-whitelisting/m-p/568242#M100856 <P>Hello there.</P><P>I finally managed to set up WMI-based event log monitoring and it seems to work <span class="lia-unicode-emoji" title=":slightly_smiling_face:">🙂</span></P><P>The problem is that it's gonna give me way to many events. I want to pull just a subset of the events from the Applicatonlog. With ordinary WinEventLog input I could set up a whitelist/blacklist to limit the processed events at the forwarder level. The same doesn't seem to work with the WMI:whatever type of input.</P><P>Is there indeed no way to limit the ingested events? Do I have to do it further down the stream by selective routing on HF?</P> Thu, 23 Sep 2021 13:26:34 GMT https://community.splunk.com/t5/Getting-Data-In/WMI-input-and-whitelisting/m-p/568242#M100856 PickleRick 2021-09-23T13:26:34Z