Splunk® Enterprise

Updating Splunk Enterprise Instances

Acrobat logo Download manual as PDF


Splunk Enterprise version 7.2 is no longer supported as of April 30, 2021. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see How to upgrade Splunk Enterprise.
Acrobat logo Download topic as PDF

Use forwarder management to manage clients

You can use forwarder management to edit client mappings and view client status.

Edit client mapping

To change the client mapping for a server class:

1. Go to the Server Classes tab, where you'll see a list of all server classes.

2. Find the server class whose client mapping you want to change, and click its Edit action.

3. Select the Edit Clients option. This takes you to the Edit Clients page, with the filter fields at the top: Include, Exclude, and Filter by Machine Type.

4. Edit the set of filters. For information on filters, see "Set up client filters".

5. Click Save.

If changing a filter results in a client getting unmapped from the server class, any previously downloaded deployment apps remain on the client but they will no longer get updated by the deployment server.

View client status

To view the status of a particular client, go to the Clients tab, where you'll see a list of all clients. At the top of the list are various options for filtering the list.

The list provides information on each client, including its host name, client name, IP address, machine type, how many apps have been deployed to it, and the last time it contacted the deployment server. You can get more information on a client by clicking the arrow on the far left of the row.

The list also contains an action, Delete Record. This action just temporarily deletes the client's record from the deployment server. The next time the client contacts the deployment server, the record will be regenerated. The action does not affect the client itself in any way.

Last modified on 03 October, 2014
PREVIOUS
Use forwarder management to manage apps
  NEXT
Use serverclass.conf to define server classes

This documentation applies to the following versions of Splunk® Enterprise: 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.0.13, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, 8.0.10, 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.10, 8.1.11, 8.1.12, 8.1.13, 8.1.14, 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.9, 8.2.10, 8.2.11, 8.2.12, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.2.0, 9.2.1


Was this documentation topic helpful?


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