Use the TZ_ALIAS attribute in nf to change how Splunk software interprets the timezone acronym string occurring in event data. Map timezone strings extracted from event data See list of tz database time zones for a list of tz database time zones.
Windows versions of Splunk software ship with a copy of the TZ database.Solaris versions of Splunk software store TZ information in the /usr/share/lib/zoneinfo directory.Most UNIX distributions store the database in the /usr/share/zoneinfo directory. UNIX versions of Splunk software rely on a TZ database included with the UNIX distribution you're running on.The following list shows the locations of the TZ database for several common operating systems. The location and content of the TZ database depend on your operating system. The zoneinfo database is a publicly maintained database of time zone values. The first example sets the time zone to U.S./Eastern for any events coming from hosts whose names match the regular expression nyc.*: To correctly handle the timestamps for these two sets of events, you must set the time zone for the nf for the forwarder to be specified as U.S./Eastern and U.S./Pacific respectively. In the first example, events come into the forwarder from New York City in the U.S./Eastern time zone and Mountain View, California in the U.S./Pacific time zone.
The following are examples of how to specify time zones in nf. As long as the time is set correctly on the host system of the indexer, the offsets to event time zones are calculated correctly.Įxamples of time zone specification in nf You do not configure the time zone for the indexer on the Splunk Platform, but instead in the underlying operating system. To view a list of all the time zone TZ IDs, see. Make sure that the time zone of the events you enter is the time zone coming from that host, source, or source type. Inside the stanza for a host, source, or source type, set the TZ attribute to the TZ ID for the desired time zone. The TZ attribute recognizes zone info TZ IDs.
For information on configuration files in general, see About configuration files in the Splunk Enterprise Admin Manual.Ĭonfigure time zones by adding a TZ attribute to the appropriate stanza in the nf file. To configure time zone settings, edit the nf file in $FORWARDER_HOME/etc/system/local/ or in your own custom application directory in $FORWARDER_HOME/etc/apps/. If Splunk has multiple specified time zones, it will use the one higher in precedence. Use the time zone of the host that indexes the event.If the forwarder and the receiving indexer are version 6.0 or higher, use the time zone that the forwarder provides.Use the TZ attribute set in nf, if the event matches the host, source, or source type that the stanza specifies.Use the time zone specified in raw event data (for example, PST, -0800), if present.To determine the time zone to assign to a timestamp, Splunk software uses the following logic in order of precedence: How Splunk software determines time zones If you have Splunk Enterprise and need to modify timestamp extraction, perform the configuration on your indexer machines or, if you are forwarding data, use heavy forwarders and perform the configuration on the machines where the heavy forwarders run. file, see Configure timestamp recognition. If you change the time zone setting of the host machine, you must restart Splunk Enterprise or the forwarder for the software to detect the change.įor general information on editing timestamps in the nf. Perform the configuration on the machines where your heavy forwarders run. To modify timestamp extraction, your Splunk Cloud Platform architecture must include a heavy forwarder and you must edit the nf file on the heavy forwarder. You can configure time zones based on the host, source, or source type of an event. If you index data from different time zones, you can use time zone offsets to check that they correlate correctly when you search.