<?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: UF first deployed in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/UF-first-deployed/m-p/263719#M10022</link>
    <description>&lt;P&gt;You can only go back as far as you are retaining internal events, but &lt;CODE&gt;index=_internal component=HttpPubSubConnection host=YOURSERVERNAME&lt;/CODE&gt; shows a basic event similar to this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;09-01-2016 12:44:34.840 -0400 INFO  HttpPubSubConnection - Running phone uri=/services/broker/phonehome/connection_10.xx.xx.xx_8089_10.xx.xx.xx_YOURSERVERNAME_0A5F9875-1BA5-4317-B4A5-248C0C43E52D
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;CODE&gt;connection_10.xx.xx.xx_8089_10.xx.xx.xx_YOURSERVERNAME&lt;/CODE&gt; will be the IP of the server (twice) and its name.&lt;/P&gt;

&lt;P&gt;Now this shows the earliest and latest event in your time range:  &lt;CODE&gt;index=_internal component=HttpPubSubConnection host=PVADFS03 | stats earliest(_time) AS Earliest, latest(_time) AS Latest | eval FirstEvent=strftime(Earliest,"%+") | eval LastEvent=strftime(Latest,"%+") | fields - Earliest Latest&lt;/CODE&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 01 Sep 2016 16:54:23 GMT</pubDate>
    <dc:creator>lycollicott</dc:creator>
    <dc:date>2016-09-01T16:54:23Z</dc:date>
    <item>
      <title>UF first deployed</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/UF-first-deployed/m-p/263718#M10021</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;Is it possible to see when a universal forwarder was first deployed or phonedhome?&lt;/P&gt;

&lt;P&gt;Thanks &lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2016 15:37:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/UF-first-deployed/m-p/263718#M10021</guid>
      <dc:creator>mansel_scheffel</dc:creator>
      <dc:date>2016-09-01T15:37:58Z</dc:date>
    </item>
    <item>
      <title>Re: UF first deployed</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/UF-first-deployed/m-p/263719#M10022</link>
      <description>&lt;P&gt;You can only go back as far as you are retaining internal events, but &lt;CODE&gt;index=_internal component=HttpPubSubConnection host=YOURSERVERNAME&lt;/CODE&gt; shows a basic event similar to this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;09-01-2016 12:44:34.840 -0400 INFO  HttpPubSubConnection - Running phone uri=/services/broker/phonehome/connection_10.xx.xx.xx_8089_10.xx.xx.xx_YOURSERVERNAME_0A5F9875-1BA5-4317-B4A5-248C0C43E52D
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;CODE&gt;connection_10.xx.xx.xx_8089_10.xx.xx.xx_YOURSERVERNAME&lt;/CODE&gt; will be the IP of the server (twice) and its name.&lt;/P&gt;

&lt;P&gt;Now this shows the earliest and latest event in your time range:  &lt;CODE&gt;index=_internal component=HttpPubSubConnection host=PVADFS03 | stats earliest(_time) AS Earliest, latest(_time) AS Latest | eval FirstEvent=strftime(Earliest,"%+") | eval LastEvent=strftime(Latest,"%+") | fields - Earliest Latest&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2016 16:54:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/UF-first-deployed/m-p/263719#M10022</guid>
      <dc:creator>lycollicott</dc:creator>
      <dc:date>2016-09-01T16:54:23Z</dc:date>
    </item>
    <item>
      <title>Re: UF first deployed</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/UF-first-deployed/m-p/263720#M10023</link>
      <description>&lt;P&gt;The answer is... &lt;EM&gt;"It Depends"&lt;/EM&gt;. &lt;/P&gt;

&lt;P&gt;So the next obvious question is "Why do you want to know?" Because that might get you a better answer than what follows...  Can you elaborate?&lt;/P&gt;

&lt;P&gt;There is data in the internal logs regarding the contact between the indexer and forwarder, but those logs roll and usually... that final rollout is to deletion. So it depends.&lt;/P&gt;

&lt;P&gt;If this is a new-ish (the _internal index is set to roll every 30 days) then you can take a look here:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal source=*metrics.log* "fwdtype=*"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;or if you are using a DS here: &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal source=*metrics.log* phonehome
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;These give you the data available to you (although not the search, there are countless resources for searching those bits...).&lt;/P&gt;

&lt;P&gt;the UF also has internal logs that most folks are forwarding to their indexer (but you fall under the same 30 day roll).  &lt;/P&gt;

&lt;P&gt;If you feel it's been phoning home since it was installed and you just want to know when... if it's never been upgraded you can check creation data of default config files in $SPLUNK_HOME/etc/system/default as those are dated at the last upgrade (or the initial install). mind you, this assumes you started it immediately, and that there isn't some overlying distribution system messing with the dates.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2016 17:05:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/UF-first-deployed/m-p/263720#M10023</guid>
      <dc:creator>rsennett_splunk</dc:creator>
      <dc:date>2016-09-01T17:05:21Z</dc:date>
    </item>
    <item>
      <title>Re: UF first deployed</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/UF-first-deployed/m-p/263721#M10024</link>
      <description>&lt;P&gt;Awesome, thanks! I am putting together a few panels to see various things relating to agents deployed. So was just curious about this.&lt;/P&gt;

&lt;P&gt;Is it possible to see a list of inactive UF's.. and why they are inactive? &lt;/P&gt;</description>
      <pubDate>Fri, 02 Sep 2016 13:19:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/UF-first-deployed/m-p/263721#M10024</guid>
      <dc:creator>mansel_scheffel</dc:creator>
      <dc:date>2016-09-02T13:19:35Z</dc:date>
    </item>
  </channel>
</rss>

