Splunk® Enterprise

Updating Splunk Enterprise Instances

How deployment updates happen

The deployment update process works like this:

1. Each deployment client periodically polls the deployment server, identifying itself.

2. The deployment server determines the set of deployment apps for the client, based on which server classes the client belongs to.

3. The deployment server gives the client the list of apps that belong to it, along with those apps' current checksums.

4. The client compares the app info from the deployment server with its own app info, to determine whether there are any new or changed apps that it needs to download.

5. If there are new or updated apps, the deployment client downloads them.

6. Depending on the configuration for a given app, the client might restart itself before the app changes take effect.

Last modified on 09 December, 2024
Deployment server architecture   Forwarder management overview

This documentation applies to the following versions of Splunk® Enterprise: 9.4.0


Was this topic useful?







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

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters