Use the server class configuration viewer to inspect the configuration, effective serverclass.conf settings, and agent assignments for a server class.
The server class configuration viewer displays the merged btool output for serverclass.conf directly in the agent management UI. For background on how the Splunk platform merges configuration files and the limitations of btool, see View server class configuration .
You can inspect the effective configuration at two levels:
- Global settings on the Settings page, which apply to all server classes and applications.
- Per-server-class settings on the server class details screen, which apply only to a specific server class.
View the global effective configuration
- Log in to Splunk Enterprise, select the settings icon (
), and then, under the Distributed Environment section, select Agent management.
- On the Forwarders tab, select Settings.
- On the Settings page, review the effective configuration for the
[global] stanza.
The global stanza defines defaults that apply to every server class and every application managed by agent management. It also includes properties that work only at the global level. For more information about global setting, see serverclass.conf.
View the effective configuration for a specific server class
- Log in to Splunk Enterprise, select the settings icon (
), and then, under the Distributed Environment section, select Agent management.
- On the Agent management - Forwarders page, select the Server Classes tab.
- In the server class list, select the server class you want to inspect.
- On the server class details screen, review the configuration section.
The server class configuration viewer displays the btool output that applies only to this server class. You can review the following information:
- The resolved settings for the
[global] stanza, because some global settings also apply to individual server classes.
- The resolved settings for the server class stanza, for example
[serverClass:myServerClass].
- The resolved settings for each application assigned to the server class, for example
[serverClass:myServerClass:app:myApp].
- The source configuration file that each setting comes from, so you can trace unexpected values back to a specific file.
If the effective configuration doesn't match your expectations, identify the source file that is contributing the unexpected setting and update the appropriate serverclass.conf file. Return to the server class configuration viewer to verify that your changes produce the intended result.