Alerting

Error when adding new whitelist in inputs.conf

azrad
Engager

Hi Splunk Community

We have created few whitelist in our inputs.conf file. It was all fine until i try to enter the following:

 

whitelist10=Type="Information" SourceName="Customer.Service" Message="*Request Info:ContactCustomer - CreateNewContact*"

 

after restarting my splunk, i get the following:
 
Invalid key in stanza [WinEventLog://Application] in C:\Program Files\SplunkUniversalForwarder\etc\system\local\inputs.conf, line 38: whitelist12 (value: Type="Information" SourceName="Customer.Service" Message="*Request Info:ContactCustomer - CreateNewContact*").
 
and it gives me the following:
 
Did you mean 'whitelist'?
Did you mean 'whitelist1'?
Did you mean 'whitelist2'?
Did you mean 'whitelist3'?
Did you mean 'whitelist4'?
Did you mean 'whitelist5'?
Did you mean 'whitelist6'?
Did you mean 'whitelist7'?
Did you mean 'whitelist8'?
Did you mean 'whitelist9'?

 

Is there a limit to number of whitelist we can create?

Or what is the next correct key to use after whitelist9 ?

 

thanks!!

Azrad

0 Karma
1 Solution

harsmarvania57
Ultra Champion

Hi,

 

Yes there is limitation when you specify whitelist/blacklist for Windows Event Montitoring

https://docs.splunk.com/Documentation/Splunk/8.0.4/Admin/Inputsconf#Windows_Event_Log_Monitor

* Numbered whitelist settings are permitted from 1 to 9, so whitelist1 through
  whitelist9 and blacklist1 through blacklist9 are supported.
* If no whitelist or blacklist rules are present, the input reads all events.

View solution in original post

harsmarvania57
Ultra Champion

Hi,

 

Yes there is limitation when you specify whitelist/blacklist for Windows Event Montitoring

https://docs.splunk.com/Documentation/Splunk/8.0.4/Admin/Inputsconf#Windows_Event_Log_Monitor

* Numbered whitelist settings are permitted from 1 to 9, so whitelist1 through
  whitelist9 and blacklist1 through blacklist9 are supported.
* If no whitelist or blacklist rules are present, the input reads all events.

azrad
Engager

hi @harsmarvania57 

Thanks for the answer. We made some changes to our config and combined the whitelist where possible.

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!

Introducing ITSI 5.0: Unified Visibility and Actionable Insights

Introducing ITSI 5.0: Unified Visibility and Actionable Insights Tuesday, July 21, 2026  |  10:00AM PT / ...

Inside Splunk Agent Observability: Understanding Agent Behavior, Tokens & Costs

Inside Splunk Agent Observability:Understanding Agent Behavior, Tokens & Costs Thursday, August 06, ...

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...