<?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: Which is more efficient - filldown or streamstats in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Which-is-more-efficient-filldown-or-streamstats/m-p/269740#M2552</link>
    <description>&lt;P&gt;Run both searches on your system searching your events over the same time range and check the job inspector for each search and you will get the answer which one will perform best for you in your environment.&lt;/P&gt;</description>
    <pubDate>Thu, 10 Dec 2015 20:14:09 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2015-12-10T20:14:09Z</dc:date>
    <item>
      <title>Which is more efficient - filldown or streamstats</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Which-is-more-efficient-filldown-or-streamstats/m-p/269739#M2551</link>
      <description>&lt;PRE&gt;&lt;CODE&gt;... | sort _time | filldown l_lat l_lon by UID | table _time UID w_tbys w_tbyr l_lat l_lon 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;or&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;... | sort _time | streamstats last(l_lat) as lastLat last(l_lon) as lastLon by UID | table _time UID w_tbys w_tbyr l_lat lastLat l_lon lastLon
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 10 Dec 2015 20:08:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Which-is-more-efficient-filldown-or-streamstats/m-p/269739#M2551</guid>
      <dc:creator>simpkins1958</dc:creator>
      <dc:date>2015-12-10T20:08:41Z</dc:date>
    </item>
    <item>
      <title>Re: Which is more efficient - filldown or streamstats</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Which-is-more-efficient-filldown-or-streamstats/m-p/269740#M2552</link>
      <description>&lt;P&gt;Run both searches on your system searching your events over the same time range and check the job inspector for each search and you will get the answer which one will perform best for you in your environment.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Dec 2015 20:14:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Which-is-more-efficient-filldown-or-streamstats/m-p/269740#M2552</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2015-12-10T20:14:09Z</dc:date>
    </item>
    <item>
      <title>Re: Which is more efficient - filldown or streamstats</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Which-is-more-efficient-filldown-or-streamstats/m-p/269741#M2553</link>
      <description>&lt;P&gt;What @MuS said (he beat me to it).&lt;/P&gt;</description>
      <pubDate>Thu, 10 Dec 2015 20:25:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Which-is-more-efficient-filldown-or-streamstats/m-p/269741#M2553</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-12-10T20:25:48Z</dc:date>
    </item>
    <item>
      <title>Re: Which is more efficient - filldown or streamstats</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Which-is-more-efficient-filldown-or-streamstats/m-p/269742#M2554</link>
      <description>&lt;P&gt;filldown does &lt;STRONG&gt;not&lt;/STRONG&gt; support "by" argument so if you need "by" arguments ,   filldown is not an right option for you . check here &lt;A href="https://docs.splunk.com/Documentation/Splunk/7.2.4/SearchReference/Filldown"&gt;https://docs.splunk.com/Documentation/Splunk/7.2.4/SearchReference/Filldown&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Sat, 23 Feb 2019 09:49:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Which-is-more-efficient-filldown-or-streamstats/m-p/269742#M2554</guid>
      <dc:creator>RR5027153</dc:creator>
      <dc:date>2019-02-23T09:49:43Z</dc:date>
    </item>
  </channel>
</rss>

