Splunk Cloud Platform

Getting Data In

About hosts

The host field value of an event is the name of the physical device from which the event originates. Because the host field value is a default field, which means that assigns a host to every event it indexes, you can use it to search for all events that have been generated by a particular host.

The host value is typically the hostname, IP address, or fully qualified domain name of the networked machine on which the event originated.

Both Splunk Cloud Platform and Splunk Enterprise assign host names at index time, but whereas you can configure host assignment directly on a Splunk Enterprise instance, you must do this configuration on a universal or heavy forwarder for Splunk Cloud Platform.

If you have access to the Edge Processor solution, you can also assign host names before index time using Edge Processors. See About the Edge Processor solution in the Use Edge Processors manual.

How determines the host value

assigns a host value to each event by examining settings in the following order and using the first host setting it encounters:

  1. Any event-specific host assignment that you specify in the transforms.conf configuration file. For Splunk Cloud Platform, you can use a heavy forwarder to assign host names through events.
  2. The default host value for the input that created the event, if any.
  3. The default host value for the indexer or forwarder that initially ingests the data.

The default host value

If you don't specify host rules for a source, assigns the host field a default value that applies to all data coming into the instance from any input. The default host value is the hostname or IP address of the indexer or forwarder that initially ingests the data. When Splunk Enterprise or, in the case of Splunk Cloud Platform, the heavy forwarder, runs on the server where the event occurred, the behavior is correct and requires no manual intervention.

For more information, see Set a default host for a Splunk platform instance.

If you have access to the Edge Processor solution, you can also write a custom regular expression in SPL2 to assign both static and dynamically-determined values. See Understanding SPL2 syntax in the SPL2 search reference manual.

The default host for a file or directory input

If you run Splunk Cloud Platform, Splunk Enterprise on a central log archive, or you work with files that are forwarded from other machines in your environment, you might need to override the default host assignment for events that come from particular inputs.

There are two methods for assigning a host value to data that's received through a particular input: You can define a static host value for all data that comes through a specific input, or you can have the Splunk platform dynamically assign a host value to a portion of the path or filename of the source. The latter method can be helpful when you have a directory structure that segregates each host's log archive in a different subdirectory.

For more information, see Set a default host for a file or directory input.

Event-specific assignments

Some situations require that you assign host values by examining the event data. For example, if you have a central log host sending events to a Splunk Enterprise deployment, you might have several machines that feed data to that main log server. To ensure that each event has the host value of its originating server, you need to use the event data to determine the host value.

For more information, see Set host values based on event data.

Handle incorrectly assigned host values

If your event data gets tagged with the wrong host value, there are a number of ways to either fix or work around the problem. See Change host values after indexing for fixes to the most common scenarios.

Tag host values

You can tag host values to aid in the execution of robust searches. Tags let you cluster groups of hosts into useful, searchable categories.

For details, see About tags and aliases in the Splunk Enterprise Knowledge Manager Manual.

Last modified on 28 March, 2024
Reduce lookup overhead with ingest-time lookups   Set a default host for a Splunk platform instance

This documentation applies to the following versions of Splunk Cloud Platform: 8.2.2112, 8.2.2201, 8.2.2202, 9.0.2205, 8.2.2203, 9.0.2208, 9.0.2209, 9.0.2303, 9.0.2305, 9.1.2308 (latest FedRAMP release), 9.1.2312, 9.2.2403

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