Release Notes

 


Host name issue on new installations

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

Host name issue on new installations

The following issue pertains to the name of the Splunk system in 4.3. It applies only to new installations of 4.3. Direct upgrades are not affected.

Splunk server instance name for a new (not upgraded) 4.3 installation

A new installation of Splunk 4.3 will use a different Splunk instance name from new installations of 4.2.3 or earlier.

This value is exposed as splunk_server in search, and it is used in distributed search to identify each node, which has server-to-server authentication implications for distributed search.

You might see that the value of splunk_server is capitalized on Windows, or looks like hostname-splunk or hostname-root on UNIX.

  • On Windows, Splunk uses %COMPUTERNAME% for the internal instance name.
  • On UNIX, Splunk uses $HOSTNAME.

If you are in a distributed search environment, this is important because you might have searches which select where to run based on the value of the splunk_server field or use the value of splunk_server to report on your data.

This documentation applies to the following versions of Splunk: 4.3 , 4.3.1 , 4.3.2 , 4.3.3 , 4.3.4 , 4.3.5 , 4.3.6 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.

Feedback submitted, thanks!