https://community.splunk.com/t5/Getting-Data-In/Hide-an-entry/m-p/111414#M23346 <P>You can route data to the null queue to avoid having it stored or seen in Splunk. See the doc link below.</P> <P><A href="http://docs.splunk.com/Documentation/Splunk/6.0.1/Forwarding/Routeandfilterdatad#Discard_specific_events_and_keep_the_rest">http://docs.splunk.com/Documentation/Splunk/6.0.1/Forwarding/Routeandfilterdatad#Discard_specific_events_and_keep_the_rest</A></P> Mon, 13 Jan 2014 23:38:12 GMT sdaniels 2014-01-13T23:38:12Z https://community.splunk.com/t5/Getting-Data-In/Hide-an-entry/m-p/111413#M23345 <P>Hello All,</P> <P>I'm seeing a lot of port 68 broadcast from the WAN side. This is normal for a someone on a cable network. Is there a way that I can tell Splunk not to log these and drop the entries all together?</P> <P>Thanks for your time and attention, </P> Mon, 13 Jan 2014 22:54:20 GMT https://community.splunk.com/t5/Getting-Data-In/Hide-an-entry/m-p/111413#M23345 rlocone 2014-01-13T22:54:20Z https://community.splunk.com/t5/Getting-Data-In/Hide-an-entry/m-p/111414#M23346 <P>You can route data to the null queue to avoid having it stored or seen in Splunk. See the doc link below.</P> <P><A href="http://docs.splunk.com/Documentation/Splunk/6.0.1/Forwarding/Routeandfilterdatad#Discard_specific_events_and_keep_the_rest">http://docs.splunk.com/Documentation/Splunk/6.0.1/Forwarding/Routeandfilterdatad#Discard_specific_events_and_keep_the_rest</A></P> Mon, 13 Jan 2014 23:38:12 GMT https://community.splunk.com/t5/Getting-Data-In/Hide-an-entry/m-p/111414#M23346 sdaniels 2014-01-13T23:38:12Z https://community.splunk.com/t5/Getting-Data-In/Hide-an-entry/m-p/111415#M23347 <P>Or Google "Splunk filter event data null queue"</P> Mon, 13 Jan 2014 23:45:52 GMT https://community.splunk.com/t5/Getting-Data-In/Hide-an-entry/m-p/111415#M23347 lguinn2 2014-01-13T23:45:52Z