Example: deploy a light forwarder

Example: deploy a light forwarder

This example walks through the configuration needed to deploy an app, in this case, the Splunk light forwarder.

On the deployment server

Edit serverclass.conf in /system/local on the deployment server and add a server class named lightforwarders that includes the light forwarder app by name:

[global]
whitelist.0=*

[serverClass:lightforwarders]
whitelist.0=*

[serverClass:lightforwarders:app:SplunkLightForwarder]
stateOnClient=enabled
restartSplunkd=true

• The [global] stanza is required, and contains any settings that should be globally applied.
• The whitelist.0 specifies that all server classes defined in this configuration file are matched by all clients--in this case, just the lighforwarders server class.
• lightforwarders is the name we specified for the server class. You can call your server classes anything you want.
• stateOnClient specifies that this app should be enabled on the client when it is deployed.
• restartSplunkd specifies that when this app is deployed, splunkd should be restarted.
• If you created a new serverclass.conf to add these definitions, you must restart Splunk for the settings to take effect.

On the deployment client

Edit deploymentclient.conf in /system/local on the deployment client to tell the client how to contact the deployment server:

[deployment-client]
[target-broker:deploymentServer]
targetUri=<IP:port>

which points this client at the deployment server at IP:port, where it will pick up the Splunk light forwarder app, enable it, and restart.

• deploymentServer is the default name for a deployment server.
• <IP:port> are the IP and port for the deployment server.

• Was this topic useful?
• Post a comment