<?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: Query to return all forwarder versions and the last time that they sent data? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Query-to-return-all-forwarder-versions-and-the-last-time-that/m-p/239601#M46574</link>
    <description>&lt;P&gt;Curious about your use of &lt;CODE&gt;dedup&lt;/CODE&gt; and &lt;CODE&gt;table&lt;/CODE&gt; vs &lt;CODE&gt;stats&lt;/CODE&gt;. With this snippet replacing that section of your search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; | stats latest(version) as version latest(arch) as arch latest(os) as os latest(build) as build by hostname
 | rex field=hostname "(?&amp;lt;hostname&amp;gt;[^\.]+)"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;... the search takes about 15% less time for me. Not a huge savings, for sure, but still.&lt;/P&gt;

&lt;P&gt;Any advantage to using &lt;CODE&gt;depup&lt;/CODE&gt; + &lt;CODE&gt;table&lt;/CODE&gt;?&lt;/P&gt;</description>
    <pubDate>Thu, 05 May 2016 16:59:55 GMT</pubDate>
    <dc:creator>twinspop</dc:creator>
    <dc:date>2016-05-05T16:59:55Z</dc:date>
    <item>
      <title>Query to return all forwarder versions and the last time that they sent data?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Query-to-return-all-forwarder-versions-and-the-last-time-that/m-p/239599#M46572</link>
      <description>&lt;P&gt;Please provide a query that will show me the version of my forwarders and when they last shipped me data.&lt;/P&gt;</description>
      <pubDate>Thu, 05 May 2016 16:07:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Query-to-return-all-forwarder-versions-and-the-last-time-that/m-p/239599#M46572</guid>
      <dc:creator>the_wolverine</dc:creator>
      <dc:date>2016-05-05T16:07:44Z</dc:date>
    </item>
    <item>
      <title>Re: Query to return all forwarder versions and the last time that they sent data?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Query-to-return-all-forwarder-versions-and-the-last-time-that/m-p/239600#M46573</link>
      <description>&lt;PRE&gt;&lt;CODE&gt;index=_internal sourcetype=splunkd group=tcpin_connections version=* os=* arch=* build=* hostname=* source=*metrics.log 
| stats latest(version) as version,latest(arch) as arch,latest(os) as os,latest(build) as build by hostname
| join hostname [ | metadata type=hosts index=* 
| eval last_seen_hours=(now()-lastTime)/60/60 
| table host, last_seen_hours 
| rex field=host "(?&amp;lt;hostname&amp;gt;[^\.]+)" | fields - host ]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This removes the domain component of hostname to ensure a match between metrics and metadata host value.&lt;/P&gt;</description>
      <pubDate>Thu, 05 May 2016 16:10:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Query-to-return-all-forwarder-versions-and-the-last-time-that/m-p/239600#M46573</guid>
      <dc:creator>the_wolverine</dc:creator>
      <dc:date>2016-05-05T16:10:20Z</dc:date>
    </item>
    <item>
      <title>Re: Query to return all forwarder versions and the last time that they sent data?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Query-to-return-all-forwarder-versions-and-the-last-time-that/m-p/239601#M46574</link>
      <description>&lt;P&gt;Curious about your use of &lt;CODE&gt;dedup&lt;/CODE&gt; and &lt;CODE&gt;table&lt;/CODE&gt; vs &lt;CODE&gt;stats&lt;/CODE&gt;. With this snippet replacing that section of your search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; | stats latest(version) as version latest(arch) as arch latest(os) as os latest(build) as build by hostname
 | rex field=hostname "(?&amp;lt;hostname&amp;gt;[^\.]+)"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;... the search takes about 15% less time for me. Not a huge savings, for sure, but still.&lt;/P&gt;

&lt;P&gt;Any advantage to using &lt;CODE&gt;depup&lt;/CODE&gt; + &lt;CODE&gt;table&lt;/CODE&gt;?&lt;/P&gt;</description>
      <pubDate>Thu, 05 May 2016 16:59:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Query-to-return-all-forwarder-versions-and-the-last-time-that/m-p/239601#M46574</guid>
      <dc:creator>twinspop</dc:creator>
      <dc:date>2016-05-05T16:59:55Z</dc:date>
    </item>
    <item>
      <title>Re: Query to return all forwarder versions and the last time that they sent data?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Query-to-return-all-forwarder-versions-and-the-last-time-that/m-p/239602#M46575</link>
      <description>&lt;P&gt;Yep thanks for the reminder.  I normally use stats and have updated the query. I came up with the query this morning and post it on answers as a future reference for myself and others.&lt;/P&gt;</description>
      <pubDate>Thu, 05 May 2016 18:07:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Query-to-return-all-forwarder-versions-and-the-last-time-that/m-p/239602#M46575</guid>
      <dc:creator>the_wolverine</dc:creator>
      <dc:date>2016-05-05T18:07:23Z</dc:date>
    </item>
  </channel>
</rss>

