Splunk® Enterprise

Admin Manual

Download manual as PDF

Download topic as PDF


The following are the spec and example files for pubsub.conf.


#   Version 7.2.0
# This file contains possible attributes and values for configuring a client of
# the PubSub system (broker).
# To set custom configurations, place a pubsub.conf in
# $SPLUNK_HOME/etc/system/local/.
# For examples, see pubsub.conf.example. You must restart Splunk to enable
# configurations.
# documentation located at


#     the file.
#     file wins.
#     stanza, the value in the specific stanza takes precedence.

# Configure the physical location where deploymentServer is running.
# This configuration is used by the clients of the pubsub system.


disabled = <false or true>
* defaults to 'false'

targetUri = <IP:Port>|<hostname:Port>|direct
* specify either the url of a remote server in case the broker is remote, or
  just the keyword "direct" when broker is in-process.
* It is usually a good idea to co-locate the broker and the Deployment Server
  on the same Splunk. In such a configuration, all 
* deployment clients would have targetUri set to deploymentServer:port.

# The following section is only relevant to Splunk developers.

# This "direct" configuration is always available, and cannot be overridden.


disabled = false
targetUri = direct


* It is possible for any Splunk to be a broker. If you have multiple brokers,
  assign a logicalName that is used by the clients to refer to it.

disabled = <false or true>
* defaults to 'false'

targetUri = <IP:Port>|<hostname:Port>|direct
* The Uri of a Splunk that is being used as a broker.
* The keyword "direct" implies that the client is running on the same Splunk
  instance as the broker.


#   Version 7.2.0





Was this documentation topic helpful?





0 out of 1000 Characters