Deploy in multi-tenant environments
Note: This feature has been deprecated in Splunk Enterprise version 6.0. For a list of all deprecated features, see the topic "Deprecated features" in the Release Notes.
Important: It is recommended that you work with Splunk Professional Services when designing a multi-tenant deployment.
A multi-tenant deployment server topology means that you have more than one deployment server running on the same Splunk Enterprise instance, and each deployment server is serving content to its own set of deployment clients. (You can also achieve the same effect by using two instances, each with its own configuration.)
Use tenants.conf to redirect incoming requests from deployment clients to another deployment server or servers. The typical reason for doing this is to offload splunkd's HTTP server -- if too many deployment clients are simultaneously hitting the splunkd HTTP server to download apps and configurations, it can overload the deployment server. Over 400 connections at one time has been shown to bog down splunkd's HTTP server, but this does not take into account hardware or the size of the package the client is downloading.
To set up multiple deployment servers on a single instance, you:
- Create a
tenants.confcontaining a whitelist or blacklist that tells deployment clients which deployment server instance to use.
- Create a separate instance of
serverclass.conffor each deployment server, named for that deployment server, like so:
- For each deployment client, configure
deploymentclient.confthe way you would if there were just one deployment server.
What you can define in tenants.conf
You identify the different deployment servers as "tenants" in
tenants.conf on the instance that will host these deployment servers. There isn't a
tenants.conf file by default, so you must create one in
$SPLUNK_HOME/etc/system/local and define the tenants in it.
For each tenant, create a stanza with the heading
[tenant:<tenantName>] with these attributes:
|Attribute||What it's for||Default|
|| Set to
Set the attribute to one of these value categories:
Here is an example of defining two tenants in the
# Define two tenants - dept1 and dept2. # Deployment server configuration for dept1 will be in a matching dept1-serverclass.conf # Deployment server configuration for dept2 will be in a matching dept2-serverclass.conf [tenant:dept1] whitelist.0=*.dept1.splunk.com [tenant:dept2] whitelist.0=*.dept2.splunk.com
Compatibility and forwarder management
Extended example: Deploy configurations to several forwarders
This documentation applies to the following versions of Splunk® Enterprise: 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.0.6, 6.0.7, 6.0.8, 6.0.9, 6.0.10, 6.0.11, 6.0.12, 6.0.13, 6.0.14, 6.0.15, 6.1.11, 6.1.12, 6.1.13, 6.1.14