Getting Data In

Why is configured prod_forwarder getting serverClass blacklist/whitelist configs from other environments?

emalenfant
Explorer

So I seem to be having an issue with blacklists and whitelists.
I've got the following configured below, but for some reason, my prod_forwarder
keeps getting configs for other environments.
I'm trying to blacklist the specific indexers/sh/heavy fwd for each 'environment' and only have each environment pull down it's respective configs, notably their specific outputs.conf file

Help.... ?

Let's take my prod env for example:


[serverClass:prod_forwarder]
filterType = blacklist
blacklist.0 = *
blacklist.1 = 10.1.5.169
blacklist.2 = 10.1.5.170
whitelist.0 = 10.1.*.*

This config for some reason also pulls down the dqp and the bak below.


[serverClass:bak_forwarder]
filterType = blacklist
blacklist.0 = *
blacklist.1 = 10.4.5.169
blacklist.2 = 10.4.5.169
whitelist.0 = 10.4.*.*

[serverClass:bak-forwarder:app:bak-forwarder_outputs]

restartSplunkd = True

^^ this will get loaded to prod and dqp environments, where it should not be


[serverClass:dqp_forwarder]
filterType = blacklist
blacklist.0 = *
blacklist.1 = 10.2.5.*
blacklist.2 = 10.1.*.*
blacklist.3 = 10.4.*.*
whitelist.0 = 10.6.*.*
whitelist.1 = 10.7.*.*
whitelist.2 = 10.8.*.*
whitelist.3 = 10.9.*.*

[serverClass:dqp-forwarder:app:dqp-forwarder_outputs]
restartSplunkd = True

^^ gets loaded onto prod and bak

1 Solution

cramasta
Builder

What happens if you apply the same rules to the app?

[serverClass:dqp_forwarder]
filterType = blacklist
blacklist.0 = Blank?
blacklist.1 = 10.2.5.
blacklist.2 = 10.1..
blacklist.3 = 10.4.
.
whitelist.0 = 10.6..
whitelist.1 = 10.7.
.
whitelist.2 = 10.8..
whitelist.3 = 10.9.
.

[serverClass:dqp-forwarder:app:dqp-forwarder_outputs]
filterType = blacklist
blacklist.0 = Blank?
blacklist.1 = 10.2.5.
blacklist.2 = 10.1..
blacklist.3 = 10.4.
.
whitelist.0 = 10.6..
whitelist.1 = 10.7.
.
whitelist.2 = 10.8..
whitelist.3 = 10.9.
.
restartSplunkd = True

View solution in original post

cramasta
Builder

What happens if you apply the same rules to the app?

[serverClass:dqp_forwarder]
filterType = blacklist
blacklist.0 = Blank?
blacklist.1 = 10.2.5.
blacklist.2 = 10.1..
blacklist.3 = 10.4.
.
whitelist.0 = 10.6..
whitelist.1 = 10.7.
.
whitelist.2 = 10.8..
whitelist.3 = 10.9.
.

[serverClass:dqp-forwarder:app:dqp-forwarder_outputs]
filterType = blacklist
blacklist.0 = Blank?
blacklist.1 = 10.2.5.
blacklist.2 = 10.1..
blacklist.3 = 10.4.
.
whitelist.0 = 10.6..
whitelist.1 = 10.7.
.
whitelist.2 = 10.8..
whitelist.3 = 10.9.
.
restartSplunkd = True

ppablo
Retired

Glad you got your issue solved @emalenfant 🙂 I converted @cramasta's response to an answer. Please be sure to accept their answer so people with similar issues/questions will refer to this post for help. Thanks!

Patrick

emalenfant
Explorer

I self-corrected the issue with the following solution, as indicated by cramasta:


[serverClass:cira_prod_forwarder]
filterType = whitelist
blacklist.0 = 10.2.5.164
blacklist.1 = 10.2.5.166
blacklist.2 = 10.2.5.169
blacklist.3 = 10.2.5.170
blacklist.4 = 10.4.5.169
blacklist.5 = 10.1.5.169
blacklist.6 = 10.1.5.170
whitelist.0 = 10.1.0.*
whitelist.1 = 10.1.5.*
whitelist.2 = 10.1.35.*
whitelist.3 = 10.1.36.*
whitelist.4 = 10.1.53.*
whitelist.5 = 10.1.80.*
whitelist.6 = 10.1.90.*
whitelist.7 = 10.1.91.*
whitelist.8 = 10.1.153.*
whitelist.9 = 10.1.91.*

emalenfant
Explorer

I'll try that now.

as for the blacklist.0, it does = *

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...