Admin Manual

 


How Splunk Works

deployment.conf

This documentation does not apply to the most recent version of Splunk. Click here for the latest version.

deployment.conf

deployment.conf contains settings for configuring both deployment servers and clients.

To edit this configuration for your local Splunk server, make your edits in $SPLUNK_HOME/etc/bundles/local/deployment.conf.


You can create this file by copying examples from $SPLUNK_HOME/etc/bundles/README/deployment.conf.example.


Never edit files in our default bundle in $SPLUNK_HOME/etc/bundles/default or your changes may be overwritten in an upgrade.


deployment.conf.spec

# Copyright (C) 2005-2007 Splunk Inc.  All Rights Reserved.  Version 3.0
[distributedDeployment]
#This is the directory which contains the base of your server class bundles
#default is $SPLUNK_HOME/etc/modules/distributedDeployment/classes
serverClassPath=/opt/splunk/etc/modules/distributedDeployment/classes
#Only use this group of tags if you are using multicast to notify deployment clients
[distributedDeployment-multicast]
#Use multicast true or false
#defaults to false
sendMulticast=true
#What mcast group to send it to.  Only used if 'sendMulticast == true'.
#If this is not specified, multicast will be turned off
#No default.
multicastUri=225.0.0.39:9999
#The IP address of the interface to send mcast packets on
#defaults to whatever the kernel picks (usually sufficient)
interfaceIP=x.x.x.x
#How often to send the multicast packet out (in seconds)
#defaults to 30 seconds if not specified
frequency=60
#Lookup host name 
#defaults to false if not specified
useDNS=true
#Map IP ranges or DNS addresses to server classes
#You can put a wildcard anywhere in the string 
[distributedDeployment-classMaps]
www.* = web,apache
10.1.*.1 = osx
#******************************************************************************
#The following configuration only pertains to those splunk instances
#which are to be "deployment clients" (deployed by a deployment server)
[deployment-client]
#Listen on the following list of multicast address for deployment server
#instructions. Each deployment server needs to be in control over a
#unique set of server classes.  Typically there is only zero or one entry
#in this list.
multicastUri=225.0.0.39:9999, w.x.y.z:pppp, ...
#Use the physical interface bound to this IP address for listening
#to muliticasts. (used only if listening to multicasts)
mcastInterfaceIp=x.x.x.x
#List of deployment server to poll.  This can be used concurrently with
#listening to multicasts, but typically this is used *instead*.
deploymentServerUri=x.x.x.x:pppp, y.y.y.y:pppp, ...
#How often to poll each deployment server in 'deploymentServerUri'.
#Only used if deploymentServerUri is specified
pollingFrequency = 30
#Backoff randomly between 0 and this number of seconds before sending data
#to the deployment server, or asking the deployment server for configuration
#bundles.  The more deployment clients controlled by a single deployment server,
#the higher this number should be.  What it does is effectively "smooth" the
#number of concurrent requests on the server.
maxBackoff=20
#List of server classes that this deployment client is a member of. 
#Usually this list is kept on the server and is empty, but occasionally
#you might want to specify this on a client-by-client basis.
serverClasses=class1, class2, class3, ...

This documentation applies to the following versions of Splunk: 3.0 , 3.0.1 , 3.0.2 , 3.1 , 3.1.1 , 3.1.2 , 3.1.3 View the Article History for its revisions.


You must be logged into splunk.com in order to post comments. Log in now.

Was this documentation topic helpful?

If you'd like to hear back from us, please provide your email address:

We'd love to hear what you think about this topic or the documentation as a whole. Feedback you enter here will be delivered to the documentation team.

Feedback submitted, thanks!