<?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: Earliest and latest with pivot command in Reporting</title>
    <link>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188324#M4064</link>
    <description>&lt;P&gt;Hi Martin, thank you for replying. I'm trying to do subsearches with pivot using different time ranges&lt;/P&gt;</description>
    <pubDate>Wed, 20 Aug 2014 10:27:17 GMT</pubDate>
    <dc:creator>OL</dc:creator>
    <dc:date>2014-08-20T10:27:17Z</dc:date>
    <item>
      <title>Earliest and latest with pivot command</title>
      <link>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188322#M4062</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;Does anyone know if there is a way to add an earliest and latest with the pivot command?&lt;/P&gt;

&lt;P&gt;Adding earliest or earliest_time doesn't not work.&lt;/P&gt;

&lt;P&gt;Just to clarify, I don't want to use the timepicker here, I want to write a pivot command command in the same way I would write: "index=_internal earliest=-15m latest=now"&lt;/P&gt;

&lt;P&gt;Regards,&lt;BR /&gt;
Olivier&lt;/P&gt;</description>
      <pubDate>Wed, 20 Aug 2014 09:52:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188322#M4062</guid>
      <dc:creator>OL</dc:creator>
      <dc:date>2014-08-20T09:52:31Z</dc:date>
    </item>
    <item>
      <title>Re: Earliest and latest with pivot command</title>
      <link>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188323#M4063</link>
      <description>&lt;P&gt;I don't think so. What are you trying to achieve here?&lt;/P&gt;</description>
      <pubDate>Wed, 20 Aug 2014 10:03:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188323#M4063</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-08-20T10:03:21Z</dc:date>
    </item>
    <item>
      <title>Re: Earliest and latest with pivot command</title>
      <link>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188324#M4064</link>
      <description>&lt;P&gt;Hi Martin, thank you for replying. I'm trying to do subsearches with pivot using different time ranges&lt;/P&gt;</description>
      <pubDate>Wed, 20 Aug 2014 10:27:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188324#M4064</guid>
      <dc:creator>OL</dc:creator>
      <dc:date>2014-08-20T10:27:17Z</dc:date>
    </item>
    <item>
      <title>Re: Earliest and latest with pivot command</title>
      <link>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188325#M4065</link>
      <description>&lt;P&gt;I see. Assuming my feeling is correct and there is currently no way to specify the time range for a &lt;CODE&gt;pivot&lt;/CODE&gt; command inline, I see two ways around this. First, it might be possible to build your search using only one larger &lt;CODE&gt;pivot&lt;/CODE&gt; - that depends on what you're doing. Second, since you apparently already are writing searches manually rather than using the Pivot UI, you could consider falling back to regular search language.&lt;BR /&gt;
Personally I'd explore the first option, since there probably is a good reason you're using &lt;CODE&gt;pivot&lt;/CODE&gt; manually rather than traditional search language.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Aug 2014 11:07:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188325#M4065</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-08-20T11:07:52Z</dc:date>
    </item>
    <item>
      <title>Re: Earliest and latest with pivot command</title>
      <link>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188326#M4066</link>
      <description>&lt;P&gt;Use &lt;CODE&gt;_time &amp;gt; 1234567890&lt;/CODE&gt; or whatever as part of your filter. Or better and more efficient, don't use &lt;CODE&gt;pivot&lt;/CODE&gt;. Use &lt;CODE&gt;tstats&lt;/CODE&gt; and the &lt;CODE&gt;where&lt;/CODE&gt; clause of &lt;CODE&gt;tstats&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Aug 2014 12:55:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188326#M4066</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2014-08-20T12:55:19Z</dc:date>
    </item>
    <item>
      <title>Re: Earliest and latest with pivot command</title>
      <link>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188327#M4067</link>
      <description>&lt;P&gt;Indeed, there was a reason why I wanted to use pivot and it is take advantage of the acceleration of the data model, so indeed the second position isn't a possibility for me. About the first one, it will be quite tricky to achieve it also because there is lots of subsearches and "join type=left". But thank you for the tips.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Aug 2014 13:45:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188327#M4067</guid>
      <dc:creator>OL</dc:creator>
      <dc:date>2014-08-20T13:45:10Z</dc:date>
    </item>
    <item>
      <title>Re: Earliest and latest with pivot command</title>
      <link>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188328#M4068</link>
      <description>&lt;P&gt;Is it possible to use the eval function relative_time()?&lt;/P&gt;</description>
      <pubDate>Wed, 20 Aug 2014 13:48:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188328#M4068</guid>
      <dc:creator>Simon</dc:creator>
      <dc:date>2014-08-20T13:48:43Z</dc:date>
    </item>
    <item>
      <title>Re: Earliest and latest with pivot command</title>
      <link>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188329#M4069</link>
      <description>&lt;P&gt;Yeah, but probably not directly. You can however define an eval-based macro that does little more than call &lt;CODE&gt;relative_time()&lt;/CODE&gt;.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[relative_time(1)]
args = relative
definition = relative_time(time(), "$relative$")
iseval = 1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This is evaluated before the actual search starts.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Aug 2014 13:52:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188329#M4069</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-08-20T13:52:27Z</dc:date>
    </item>
    <item>
      <title>Re: Earliest and latest with pivot command</title>
      <link>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188330#M4070</link>
      <description>&lt;P&gt;Hey gkanapathy! Thank you for the answer. How would you use the _time in the pivot and tstats commands?&lt;/P&gt;

&lt;P&gt;I tried the "| pivot ... FILTER _time&amp;gt;1407684453" but no luck. This sounds promising. I start to understand why you say to not use pivot, btw, it takes ages to initialise.&lt;/P&gt;

&lt;P&gt;@Martin, nice one, didn't know you could do that with macros &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Aug 2014 15:33:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188330#M4070</guid>
      <dc:creator>OL</dc:creator>
      <dc:date>2014-08-20T15:33:48Z</dc:date>
    </item>
    <item>
      <title>Re: Earliest and latest with pivot command</title>
      <link>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188331#M4071</link>
      <description>&lt;P&gt;@gkanapathy, I managed to make it work with tstats. Thx a lot.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Aug 2014 16:17:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188331#M4071</guid>
      <dc:creator>OL</dc:creator>
      <dc:date>2014-08-20T16:17:42Z</dc:date>
    </item>
    <item>
      <title>Re: Earliest and latest with pivot command</title>
      <link>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188332#M4072</link>
      <description>&lt;P&gt;Nice idea, but you cannot use the "greater than" operator with pivot command filters, e.g. this does not work:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| pivot
...
filter _time &amp;gt; `relative_time("-5m")`
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Or did you have something else in mind?&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jan 2016 21:51:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Earliest-and-latest-with-pivot-command/m-p/188332#M4072</guid>
      <dc:creator>helge</dc:creator>
      <dc:date>2016-01-27T21:51:26Z</dc:date>
    </item>
  </channel>
</rss>

