Documentation > Splunk > Admin Manual > About deployment server

Admin Manual

 


Welcome
What to do first
Start Splunk
Meet Splunk Web and Splunk Apps
Before you configure
Add data and configure inputs
Indexing and event processing
Timestamps
Add and manage users
Manage indexes
Define alerts
Set up backups and retention policies
Configure data security
Set up forwarding and receiving
Deploy to other Splunk instances
Set up distributed search
Manage search jobs
Use Splunk's command line interface (CLI)
Configuration file reference
Troubleshooting

About deployment server

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

Contents

About deployment server

This section describes the Splunk deployment server and its features. If you want an overview of the different ways you can design a Splunk deployment in your organization, check out the deployment information in the Community Wiki.

A deployment server is a Splunk instance that acts as a centralized configuration manager, grouping together and collectively managing any number of Splunk instances. Any Splunk instance -- even one indexing data locally -- can act as a deployment server. Splunk instances that are remotely configured by deployment servers are called deployment clients. A Splunk instance can be both a deployment server and client at the same time.

To change the configuration of one or more of your Splunk deployment clients, you push out updated configuration information for a given server class from the deployment server to the deployment clients that belong to the server class.

A server class is a Splunk deployment client configuration that you have defined. To manage client configurations, assign a Splunk deployment client to one or more server classes. Then, you can manage all the Splunk deployment clients that belong to a given server class as a unit. A deployment client may be a member of multiple server classes at once. You can group clients by application, OS, data type to be indexed, or any other feature of your Splunk deployment.

Communication between deployment server and clients

The deployment client periodically polls the deployment server, identifying itself. The deployment server then reviews the information in its configuration to find out if there is something new or updated to push out to that particular client. If there is new content to deploy to a given deployment client, the deployment server instructs the client exactly what it should retrieve and directs the client to use a REST endpoint that it provides to the client. The deployment client then retrieves the new content and treats it according to the instructions specified for the server class it belongs to--maybe it should restart, run a script, or just wait until someone tells it to do something else.

Retrieved from "http://docs.splunk.com/Documentation/Splunk/4.0/Admin/Aboutdeploymentserver"

This documentation applies to the following versions of Splunk: 4.0 , 4.0.1 , 4.0.2 , 4.0.3 , 4.0.4 , 4.0.5 , 4.0.6 , 4.0.7 , 4.0.8 , 4.0.9 , 4.0.10 , 4.0.11 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.