<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Search Time Range in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Search-Time-Range/m-p/303983#M91437</link>
    <description>&lt;P&gt;It is possible that you don't see a difference because you may not have any data that would be different. The relative time modifiers is discussed in the documents here: &lt;A href="https://docs.splunk.com/Documentation/Splunk/6.5.2/SearchReference/SearchTimeModifiers#How_to_specify_relative_time_modifiers"&gt;https://docs.splunk.com/Documentation/Splunk/6.5.2/SearchReference/SearchTimeModifiers#How_to_specify_relative_time_modifiers&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;But for your specific question... Let's say you're running a search and it is right now to the sub-second exactly: 12:51:39.135&lt;/P&gt;

&lt;P&gt;earliest=-15m would mean the earliest time for your time range is exactly 15 minutes ago, or 12:36:39.135&lt;/P&gt;

&lt;P&gt;earliest=-15m@s means take the current time, subtract 15 minutes, and then round down to the nearest second, or in other words: 12:36:39.000&lt;/P&gt;

&lt;P&gt;Unless you're dealing with high volumes of data that comes from devices that log down to subsecond precision it's unlikely that you would see differences between these two examples. But relative time modifiers locking down in general is a pretty handy thing to be familiar with.&lt;/P&gt;</description>
    <pubDate>Wed, 15 Feb 2017 03:56:31 GMT</pubDate>
    <dc:creator>acharlieh</dc:creator>
    <dc:date>2017-02-15T03:56:31Z</dc:date>
    <item>
      <title>Search Time Range</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-Time-Range/m-p/303982#M91436</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have a simple question, what is the difference between &lt;EM&gt;earliest=-15m&lt;/EM&gt; with &lt;EM&gt;earliest=-15m@s&lt;/EM&gt;?&lt;/P&gt;

&lt;P&gt;I could not find any diff when run my search. Any help is appreciated. Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 15 Feb 2017 03:45:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-Time-Range/m-p/303982#M91436</guid>
      <dc:creator>dellytaniasetia</dc:creator>
      <dc:date>2017-02-15T03:45:58Z</dc:date>
    </item>
    <item>
      <title>Re: Search Time Range</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-Time-Range/m-p/303983#M91437</link>
      <description>&lt;P&gt;It is possible that you don't see a difference because you may not have any data that would be different. The relative time modifiers is discussed in the documents here: &lt;A href="https://docs.splunk.com/Documentation/Splunk/6.5.2/SearchReference/SearchTimeModifiers#How_to_specify_relative_time_modifiers"&gt;https://docs.splunk.com/Documentation/Splunk/6.5.2/SearchReference/SearchTimeModifiers#How_to_specify_relative_time_modifiers&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;But for your specific question... Let's say you're running a search and it is right now to the sub-second exactly: 12:51:39.135&lt;/P&gt;

&lt;P&gt;earliest=-15m would mean the earliest time for your time range is exactly 15 minutes ago, or 12:36:39.135&lt;/P&gt;

&lt;P&gt;earliest=-15m@s means take the current time, subtract 15 minutes, and then round down to the nearest second, or in other words: 12:36:39.000&lt;/P&gt;

&lt;P&gt;Unless you're dealing with high volumes of data that comes from devices that log down to subsecond precision it's unlikely that you would see differences between these two examples. But relative time modifiers locking down in general is a pretty handy thing to be familiar with.&lt;/P&gt;</description>
      <pubDate>Wed, 15 Feb 2017 03:56:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-Time-Range/m-p/303983#M91437</guid>
      <dc:creator>acharlieh</dc:creator>
      <dc:date>2017-02-15T03:56:31Z</dc:date>
    </item>
  </channel>
</rss>

