<?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: Forwarder Raw Heartbeat Data in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Raw-Heartbeat-Data/m-p/61709#M12316</link>
    <description>&lt;P&gt;I had the same question. I erased all the configuration apps and inputs.conf from the universal forwarder and found out that this pattern kept going. Still believe is a heartbeat.&lt;/P&gt;</description>
    <pubDate>Thu, 27 Sep 2012 18:41:10 GMT</pubDate>
    <dc:creator>rodrigocon</dc:creator>
    <dc:date>2012-09-27T18:41:10Z</dc:date>
    <item>
      <title>Forwarder Raw Heartbeat Data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Raw-Heartbeat-Data/m-p/61706#M12313</link>
      <description>&lt;P&gt;Greetz,&lt;/P&gt;

&lt;P&gt;Please can someone tell me if these events every minute are raw universal forwarder heartbeat data?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;»  5/28/12
8:10:28.000 PM  

\x16\x3\x00\x00D\x1\x00\x00@\x3\x00O\xC3\xC0\x94r\xBB\xB9m\x9C&amp;lt;[\xA9\xFC\xE4\x9C(\xAC\x108\xB5\x85؅\xEDP$\xF8\xB0\x1Bx/\xBC\x00\x00\x18\x009\x008\x005\x003\x002\x00/\x00\x16\x00\x13\x00\x00\x5\x00\x4\x00\xFF\x2\x1\x00

host=collector   Options|  
sourcetype=ds:ad   Options|  
source=tcp:50000   Options
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 28 May 2012 18:19:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Raw-Heartbeat-Data/m-p/61706#M12313</guid>
      <dc:creator>ephemeric</dc:creator>
      <dc:date>2012-05-28T18:19:51Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarder Raw Heartbeat Data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Raw-Heartbeat-Data/m-p/61707#M12314</link>
      <description>&lt;P&gt;That (looks) like a normal tcp receiver that is being fed data from a forwarder in &lt;CODE&gt;splunktcp&lt;/CODE&gt; (cooked) format.&lt;/P&gt;</description>
      <pubDate>Mon, 28 May 2012 18:34:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Raw-Heartbeat-Data/m-p/61707#M12314</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2012-05-28T18:34:16Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarder Raw Heartbeat Data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Raw-Heartbeat-Data/m-p/61708#M12315</link>
      <description>&lt;P&gt;No it's not. This was in actual fact connection data from the deployment client to a raw TCP input and the forwarder has been configured to "sendCookedData = false".&lt;/P&gt;</description>
      <pubDate>Thu, 31 May 2012 16:47:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Raw-Heartbeat-Data/m-p/61708#M12315</guid>
      <dc:creator>ephemeric</dc:creator>
      <dc:date>2012-05-31T16:47:42Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarder Raw Heartbeat Data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Raw-Heartbeat-Data/m-p/61709#M12316</link>
      <description>&lt;P&gt;I had the same question. I erased all the configuration apps and inputs.conf from the universal forwarder and found out that this pattern kept going. Still believe is a heartbeat.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Sep 2012 18:41:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Raw-Heartbeat-Data/m-p/61709#M12316</guid>
      <dc:creator>rodrigocon</dc:creator>
      <dc:date>2012-09-27T18:41:10Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarder Raw Heartbeat Data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Raw-Heartbeat-Data/m-p/61710#M12317</link>
      <description>&lt;P&gt;This was the problem.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Sep 2012 19:01:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Raw-Heartbeat-Data/m-p/61710#M12317</guid>
      <dc:creator>ephemeric</dc:creator>
      <dc:date>2012-09-27T19:01:30Z</dc:date>
    </item>
    <item>
      <title>Re: Forwarder Raw Heartbeat Data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Raw-Heartbeat-Data/m-p/61711#M12318</link>
      <description>&lt;P&gt;No it's not. This was in actual fact connection data from the deployment client to a raw TCP input and the forwarder has been configured to "sendCookedData = false".&lt;/P&gt;</description>
      <pubDate>Thu, 27 Sep 2012 19:02:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Forwarder-Raw-Heartbeat-Data/m-p/61711#M12318</guid>
      <dc:creator>ephemeric</dc:creator>
      <dc:date>2012-09-27T19:02:00Z</dc:date>
    </item>
  </channel>
</rss>

