<?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 Universal Forwader - Cap CPU, memory, Disk usage in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Universal-Forwader-Cap-CPU-memory-Disk-usage/m-p/77518#M932</link>
    <description>&lt;P&gt;Hi everyone,&lt;BR /&gt;
Thank you for your time. My question is sample:&lt;BR /&gt;
is it possible to cap this three parameters:&lt;BR /&gt;
 - CPU&lt;BR /&gt;
 - RAM&lt;BR /&gt;
 - DISK&lt;BR /&gt;
On a Universal Forwarder, installed like a agent for monitoring file and fschange. I think that UF don't write on Disk, just on RAM. is it true ?&lt;BR /&gt;
I know that is possible to cap bitrate in output.conf and EventQueue, but for CPU and RAM footprinting of process itself, not Queue ?&lt;/P&gt;

&lt;P&gt;Thank you and have a nice day.&lt;BR /&gt;
Nicolas.&lt;/P&gt;</description>
    <pubDate>Thu, 27 Jun 2013 09:48:23 GMT</pubDate>
    <dc:creator>nhurtaud</dc:creator>
    <dc:date>2013-06-27T09:48:23Z</dc:date>
    <item>
      <title>Universal Forwader - Cap CPU, memory, Disk usage</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Universal-Forwader-Cap-CPU-memory-Disk-usage/m-p/77518#M932</link>
      <description>&lt;P&gt;Hi everyone,&lt;BR /&gt;
Thank you for your time. My question is sample:&lt;BR /&gt;
is it possible to cap this three parameters:&lt;BR /&gt;
 - CPU&lt;BR /&gt;
 - RAM&lt;BR /&gt;
 - DISK&lt;BR /&gt;
On a Universal Forwarder, installed like a agent for monitoring file and fschange. I think that UF don't write on Disk, just on RAM. is it true ?&lt;BR /&gt;
I know that is possible to cap bitrate in output.conf and EventQueue, but for CPU and RAM footprinting of process itself, not Queue ?&lt;/P&gt;

&lt;P&gt;Thank you and have a nice day.&lt;BR /&gt;
Nicolas.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2013 09:48:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Universal-Forwader-Cap-CPU-memory-Disk-usage/m-p/77518#M932</guid>
      <dc:creator>nhurtaud</dc:creator>
      <dc:date>2013-06-27T09:48:23Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwader - Cap CPU, memory, Disk usage</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Universal-Forwader-Cap-CPU-memory-Disk-usage/m-p/77519#M933</link>
      <description>&lt;P&gt;This must be accomplished outside the Splunk application(s). Use OS level controls, so as ulimit settings on *Nix systems, or things like Cgroups in RHEL based systems.&lt;/P&gt;</description>
      <pubDate>Thu, 15 May 2014 14:25:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Universal-Forwader-Cap-CPU-memory-Disk-usage/m-p/77519#M933</guid>
      <dc:creator>jtrucks</dc:creator>
      <dc:date>2014-05-15T14:25:09Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwader - Cap CPU, memory, Disk usage</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Universal-Forwader-Cap-CPU-memory-Disk-usage/m-p/77520#M934</link>
      <description>&lt;P&gt;OK.&lt;BR /&gt;
Thank you for your answer.&lt;BR /&gt;
But, I regret not having the opportunity to cap CPU and RAM footprint.&lt;BR /&gt;
Customers are worried.&lt;BR /&gt;
Is it possible to gives some ideas for roadmap ?&lt;/P&gt;

&lt;P&gt;Nicolas.&lt;/P&gt;</description>
      <pubDate>Fri, 30 May 2014 15:46:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Universal-Forwader-Cap-CPU-memory-Disk-usage/m-p/77520#M934</guid>
      <dc:creator>nhurtaud</dc:creator>
      <dc:date>2014-05-30T15:46:03Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwader - Cap CPU, memory, Disk usage</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Universal-Forwader-Cap-CPU-memory-Disk-usage/m-p/77521#M935</link>
      <description>&lt;P&gt;I second this.  Worries are abound.  We just had a DNS server crash and splunk-regmon was using almost 4GB of virtual memory.....&lt;/P&gt;</description>
      <pubDate>Mon, 14 Dec 2015 14:57:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Universal-Forwader-Cap-CPU-memory-Disk-usage/m-p/77521#M935</guid>
      <dc:creator>kranzrm</dc:creator>
      <dc:date>2015-12-14T14:57:47Z</dc:date>
    </item>
  </channel>
</rss>

