<?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: Questions on a Splunk Forwarder in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Questions-on-a-Splunk-Forwarder/m-p/164835#M33429</link>
    <description>&lt;P&gt;Hi crt89,&lt;/P&gt;

&lt;P&gt;basically you can say, that the impact of the universal forwarder is very low. You can see maybe some CPU and IO peak during initial load of old logs. But during daily business the load should stay at a low one numbered percent.&lt;/P&gt;

&lt;P&gt;The load will increase, the more file will be observed by the UF.&lt;/P&gt;

&lt;P&gt;Regarding the minimum requirements, here is a basic rule - if you depend on near real-time events use fast CPU's and high IO disks. If you don't ... well, I run an UF on an ARMv5te 1.2Ghz mini server with an old 2.5" USB2 disk attached and it runs fine.&lt;/P&gt;

&lt;P&gt;To sum this up: it really depends on your use case, if you need special fast CPU and high IO disks or not.&lt;/P&gt;

&lt;P&gt;You can also check &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.1/Installation/Systemrequirements"&gt;the system requirement docs&lt;/A&gt; and get some CPU info's for the UF.&lt;/P&gt;

&lt;P&gt;hope this helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
    <pubDate>Thu, 15 May 2014 05:40:02 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2014-05-15T05:40:02Z</dc:date>
    <item>
      <title>Questions on a Splunk Forwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Questions-on-a-Splunk-Forwarder/m-p/164834#M33428</link>
      <description>&lt;P&gt;Good day Splunkers,&lt;/P&gt;

&lt;P&gt;Would like to ask some questions on the universal forwarder.&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;What is the minimum CPU usage? Given that we configured the forwarder as default with a minimum of 3 log files being monitored and forwarded.&lt;/LI&gt;
&lt;LI&gt;What is its disk I/O requirements?&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Thu, 15 May 2014 02:53:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Questions-on-a-Splunk-Forwarder/m-p/164834#M33428</guid>
      <dc:creator>crt89</dc:creator>
      <dc:date>2014-05-15T02:53:57Z</dc:date>
    </item>
    <item>
      <title>Re: Questions on a Splunk Forwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Questions-on-a-Splunk-Forwarder/m-p/164835#M33429</link>
      <description>&lt;P&gt;Hi crt89,&lt;/P&gt;

&lt;P&gt;basically you can say, that the impact of the universal forwarder is very low. You can see maybe some CPU and IO peak during initial load of old logs. But during daily business the load should stay at a low one numbered percent.&lt;/P&gt;

&lt;P&gt;The load will increase, the more file will be observed by the UF.&lt;/P&gt;

&lt;P&gt;Regarding the minimum requirements, here is a basic rule - if you depend on near real-time events use fast CPU's and high IO disks. If you don't ... well, I run an UF on an ARMv5te 1.2Ghz mini server with an old 2.5" USB2 disk attached and it runs fine.&lt;/P&gt;

&lt;P&gt;To sum this up: it really depends on your use case, if you need special fast CPU and high IO disks or not.&lt;/P&gt;

&lt;P&gt;You can also check &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.1/Installation/Systemrequirements"&gt;the system requirement docs&lt;/A&gt; and get some CPU info's for the UF.&lt;/P&gt;

&lt;P&gt;hope this helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Thu, 15 May 2014 05:40:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Questions-on-a-Splunk-Forwarder/m-p/164835#M33429</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2014-05-15T05:40:02Z</dc:date>
    </item>
  </channel>
</rss>

