About searching with time
You can use time to narrow your search and to group events in your search by time.
How timestamps are used
- Correlate events by time
- Create the timeline histogram in Splunk Web
- Set time ranges for searches
Splunk software adds timestamps to events at index time. Timestamp values are assigned automatically by using information that the software finds in the raw event data. See How timestamp assignment works in Getting Data In.
Splunk software sometimes represents time in UNIX time. Time represented this way appears as a series of numbers, for example
1518632124. You can use any UNIX time converter to convert the UNIX time to either GMT or your local time.
The _time field
_time field is in UNIX time. In Splunk Web, the
_time field appears in a human readable format in the UI. However, the values in the
_time field are stored in UNIX time.
Specify narrow time ranges
When you start a new search, the default time range is Last 24 hours. This range helps to avoid running searches with overly-broad time ranges that waste system resources and produce more results than you really need.
Whether you are running a new search, a report, or creating a dashboard, it is important to narrow the time range to only the dates or times that you really need.
Time is also crucial for determining what went wrong. You often know when something happened, if not exactly what happened. By looking at events that happened around the same time that something went wrong, can help correlate results and find the root cause of the problem.
Select time ranges to apply to your search
This documentation applies to the following versions of Splunk Cloud Platform™: 7.0.13, 8.2.2107, 8.0.2007, 8.1.2009, 8.1.2012, 8.1.2101, 8.1.2103, 8.2.2104, 8.2.2105 (latest FedRAMP release), 8.2.2106, 8.1.2011, 8.0.2006