times.conf

The following are the spec and example files for times.conf.

times.conf.spec

# Version 7.2.6
#
# This file contains possible attribute/value pairs for creating custom time
# ranges.
#
# To set custom configurations, place a times.conf in
# $SPLUNK_HOME/etc/system/local/. For help, see times.conf.example. You
# must restart Splunk to enable configurations.
#
# To learn more about configuration files (including precedence) please see
# the documentation located at
# http://docs.splunk.com/Documentation/Splunk/latest/Admin/Aboutconfigurationfiles

GLOBAL SETTINGS

# Use the [default] stanza to define any global settings.
# * You can also define global settings outside of any stanza, at the top
# of the file.
# * Each conf file should have at most one default stanza. If there are
# multiple default stanzas, attributes are combined. In the case of
# multiple definitions of the same attribute, the last definition in the
# file wins.
# * If an attribute is defined at both the global level and in a specific
# stanza, the value in the specific stanza takes precedence.

[<timerange_name>]

* The token to be used when accessing time ranges via the API or command
line
* A times.conf file can contain multiple stanzas.
label = <string>
* The textual description used by the UI to reference this time range
* Required
header_label = <string>
* The textual description used by the UI when displaying search results in
this time range.
* Optional. If omitted, the <timerange_name> is used instead.
earliest_time = <string>
* The string that represents the time of the earliest event to return,
inclusive.
* The time can be expressed with a relative time identifier or in epoch time.
* Optional. If omitted, no earliest time bound is used.
latest_time = <string>
* The string that represents the time of the earliest event to return,
inclusive.
* The time can be expressed with a relative time identifier or in epoch
time.
* Optional. If omitted, no latest time bound is used. NOTE: events that
occur in the future (relative to the server timezone) may be returned.
order = <integer>
* The key on which all custom time ranges are sorted, ascending.
* The default time range selector in the UI will merge and sort all time
ranges according to the 'order' key, and then alphabetically.
* Optional. Default value is 0.
disabled = <integer>
* Determines if the menu item is shown. Set to 1 to hide menu item.
* Optional. Default value is 0
sub_menu = <submenu name>
* REMOVED. This setting is no longer used.
is_sub_menu = <boolean>
* REMOVED. This setting is no longer used.

[settings]

* List of flags that modify the panels that are displayed in the time range picker.
show_advanced = [true|false]
* Determines if the 'Advanced' panel should be displayed in the time range picker
* Optional. Default value is true
show_date_range = [true|false]
* Determines if the 'Date Range' panel should be displayed in the time range picker
* Optional. Default value is true
show_datetime_range = [true|false]
* Determines if the 'Date & Time Range' panel should be displayed in the time range picker
* Optional. Default value is true
show_presets = [true|false]
* Determines if the 'Presets' panel should be displayed in the time range picker
* Optional. Default value is true
show_realtime = [true|false]
* Determines if the 'Realtime' panel should be displayed in the time range picker
* Optional. Default value is true
show_relative = [true|false]
* Determines if the 'Relative' panel should be displayed in the time range picker
* Optional. Default value is true

times.conf.example

# Version 7.2.6
#
# This is an example times.conf. Use this file to create custom time ranges
# that can be used while interacting with the search system.
#
# To use one or more of these configurations, copy the configuration block
# into times.conf in $SPLUNK_HOME/etc/system/local/. You must restart Splunk
# to enable configurations.
#
# To learn more about configuration files (including precedence) please see
# the documentation located at
# http://docs.splunk.com/Documentation/Splunk/latest/Admin/Aboutconfigurationfiles
# Note: These are examples. Replace the values with your own customizations.
# The stanza name is an alphanumeric string (no spaces) that uniquely
# identifies a time range.
[this_business_week]
# Define the label used in the time range control
label = This business week
# Define the label to be used in display headers. If omitted the 'label' key
# will be used with the first letter lowercased.
header_label = during this business week
earliest_time = +1d@w1
latest_time = +6d@w6
# Define the ordering sequence of this time range. All time ranges are
# sorted numerically, ascending. If the time range is in a sub menu and not
# in the main menu, this will determine the position within the sub menu.
order = 110
# a time range that only has a bound on the earliest time
#
[last_3_hours]
label = Last 3 hours
header_label = in the last 3 hours
earliest_time = -3h
order = 30
# Use epoch time notation to define the time bounds for the Fall Semester
# 2013, where earliest_time is 9/4/13 00:00:00 and latest_time is 12/13/13
# 00:00:00.
#
[Fall_2013]
label = Fall Semester 2013
earliest_time = 1378278000
latest_time = 1386921600
# two time ranges that should appear in a sub menu instead of in the main
# menu. the order values here determine relative ordering within the
# submenu.
#
[yesterday]
label = Yesterday
earliest_time = -1d@d
latest_time = @d
order = 10
sub_menu = Other options
[day_before_yesterday]
label = Day before yesterday
header_label = from the day before yesterday
earliest_time = -2d@d
latest_time = -1d@d
order = 20
sub_menu = Other options
#
# The sub menu item that should contain the previous two time ranges. The
# order key here determines the submenu opener's placement within the main
# menu.
#
[other]
label = Other options
order = 202
#
# Disable the realtime panel in the time range picker
[settings]
show_realtime = false

Comments

times.conf

Enter your email address, and someone from the documentation team will respond to you:

Send me a copy of this feedback

Please provide your comments here. Ask a question or make a suggestion.

Feedback submitted, thanks!

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

Your Comment Has Been Posted Above

We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website.
Learn more (including how to update your settings) here »