How to disable a particular source temporarily?

[karthikeyansure]

Hi Team,

One of the source throwing more logs and it is consuming more volume, so it leads to the license warning. So I need to the disable the source temporarily. Please help me.

Thanks is advance

[jtacy]

Yes, null queue is an index time transform so it requires a restart.

[karthikeyansure]

Hi Team,

I have tried null queue filtering opting, but eventhough after configuring the same, the indexing is occuring for that source. After configuring the null queue in the props.conf and transforms.conf, is it restart of server is required?

Thanks

[yannK]

You can start to disable the input.
And when you want to re-enable it, move the old log files out of the way, to avoid having them be indexed (and causing a peak of volume for historical data)

More advanced techniques involve :

• setup a filter on the eventcode (for windows event logs ,for recent forwarders only, at the forwarder level)
  see http://docs.splunk.com/Documentation/Splunk/6.1.2/Data/MonitorWindowsdata#Create_advanced_filters_wi...

• use nullqueue filtering at the indexer level to drop some events, see http://docs.splunk.com/Documentation/Splunk/6.1.2/Forwarding/Routeandfilterdatad#Discard_specific_ev...

[yannK]

yes of course, any indextime/inputtime configuration change in the configuration files require a restart to apply.

[karthikeyansure]

Hi Team,

I have tried null queue filtering opting, but eventhough after configuring the same, the indexing is occuring for that source. After configuring the null queue in the props.conf and transforms.conf, is it restart of server is required?

Thanks