<?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: Universal Forwarder hardware specs in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-hardware-specs/m-p/483484#M82833</link>
    <description>&lt;P&gt;Hi @konstr,&lt;BR /&gt;
it's a very strange architecture to have HFs that send data to UFs, usually it's the opposite: UFs are installed on target servers, they tale logs and send them to HFs that forward to Indexers or Splunk Cloud.&lt;/P&gt;

&lt;P&gt;Anyway, yes, they should be enough.&lt;/P&gt;

&lt;P&gt;Ciao.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
    <pubDate>Tue, 28 Apr 2020 07:01:00 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2020-04-28T07:01:00Z</dc:date>
    <item>
      <title>Universal Forwarder hardware specs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-hardware-specs/m-p/483481#M82830</link>
      <description>&lt;P&gt;We are looking to deploy an Intermediary forwarding tier consisting of 3 Universal Forwarders going to Splunk Cloud.&lt;BR /&gt;
The 3 UFs will be receiving data from 3 Heavy forwarders which will load-balance data across the intermediary forwarding tier.&lt;/P&gt;

&lt;P&gt;The intermediary tier has to be there due to networking reasons that we cannot overcome which are not allowing the Heavy forwarders to forward to Splunk Cloud directly. &lt;/P&gt;

&lt;P&gt;What specs should we be looking for the UFs of the intermediary forwarding tier considering a license of 600GB/day? The license would be split through the 3 UFs but in case of failure, each UF should be spec'd to be able to forward the full load.&lt;/P&gt;

&lt;P&gt;Would something like 4 CPU cores and 8GB RAM be enough?&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2020 16:13:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-hardware-specs/m-p/483481#M82830</guid>
      <dc:creator>konstr</dc:creator>
      <dc:date>2020-04-27T16:13:54Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder hardware specs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-hardware-specs/m-p/483482#M82831</link>
      <description>&lt;P&gt;Hi @konstr,&lt;BR /&gt;
the intermediary forwarding tier consists of 3 Universal Forwarders or 3 Heavy Forwarders?&lt;BR /&gt;
Before you spoke of UFs and after of HFs!&lt;BR /&gt;
Anyway, it's better to use HFs.&lt;/P&gt;

&lt;P&gt;The HW reference of these HFs depends on the job they have to do: if they only have to concentrate logs, it's a very too light configuration, but it could run (eventually at least 8 CPUs) and you could also use UFs instead of HFs; if instead you have to filter and transforms logs, you have to give more resources to your HFs.&lt;/P&gt;

&lt;P&gt;Amyway, there isn't a clear definition of HW reference for HFs, if it isn't a problem, give the standard resources asked by Splunk for Stand Alone servers (12 CPUs and 12 GB RAM).&lt;BR /&gt;
Eventually use only two HFs but giving the correct resources!&lt;/P&gt;

&lt;P&gt;Ciao.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2020 16:29:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-hardware-specs/m-p/483482#M82831</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2020-04-27T16:29:05Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder hardware specs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-hardware-specs/m-p/483483#M82832</link>
      <description>&lt;P&gt;the intermediary forwarding tier will consist of 3 UFs receiving data from 3 HFs. So basically the UFs will just receive data and forward on to Splunk Cloud.&lt;/P&gt;

&lt;P&gt;Unfortunately we are not able to use the 3 HFs to send directly to Splunk Cloud due to networking reasons hence why we need the intermediary forwarding tier.&lt;/P&gt;

&lt;P&gt;Would you say that 4 cores and 8GB RAM for the UFs will not be enough?&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2020 16:34:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-hardware-specs/m-p/483483#M82832</guid>
      <dc:creator>konstr</dc:creator>
      <dc:date>2020-04-27T16:34:07Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder hardware specs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-hardware-specs/m-p/483484#M82833</link>
      <description>&lt;P&gt;Hi @konstr,&lt;BR /&gt;
it's a very strange architecture to have HFs that send data to UFs, usually it's the opposite: UFs are installed on target servers, they tale logs and send them to HFs that forward to Indexers or Splunk Cloud.&lt;/P&gt;

&lt;P&gt;Anyway, yes, they should be enough.&lt;/P&gt;

&lt;P&gt;Ciao.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Tue, 28 Apr 2020 07:01:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-hardware-specs/m-p/483484#M82833</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2020-04-28T07:01:00Z</dc:date>
    </item>
  </channel>
</rss>

