Databases Reference
In-Depth Information
whitelist.0=web-*
whitelist.1=qa01
whitelist.2=homer-simpson
[serverClass:webservers:app:inputs-web]
#define our dbserver inputs
[serverClass:dbservers]
whitelist.0=db-*
whitelist.1=qa01
[serverClass:dbservers:app:inputs-db]
#define our west coast forwarders
[serverClass:fwd-west]
whitelist.0=app-west*
whitelist.1=web-west*
whitelist.2=db-west*
whitelist.3=qa01
[serverClass:fwd-west:app:outputs-west]
#define our east coast forwarders
[serverClass:fwd-east]
whitelist.0=app-east*
whitelist.1=web-east*
whitelist.2=db-east*
whitelist.3=homer-simpson
[serverClass:fwd-east:app:outputs-east]
You should organize the patterns and classes in a way that makes sense to your
organization and data centers, but I would encourage you to keep it as simple as
possible. I would strongly suggest opting for more lines than more complicated logic.
A few more things to note about the format of
serverclass.conf
:
• The number following whitelist and blacklist
must be sequential
, starting
with zero. For instance, in the following example,
whitelist.3
will not
be processed, since
whitelist.2
is commented:
[serverClass:foo]
whitelist.0=a*
whitelist.1=b*
# whitelist.2=c*
whitelist.3=d*
Search WWH ::
Custom Search