<?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 CPU usage  using the lightforwarder in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/CPU-usage-using-the-lightforwarder/m-p/24386#M3841</link>
    <description>&lt;P&gt;I am using the light forwarder on AIX and running into high CPU usage (80-90% of a CPU).&lt;BR /&gt;
We tracked it down to using ellipse in the monitor line in inputs.conf.&lt;BR /&gt;
(even a "*" uses too much CPU).&lt;BR /&gt;
We are using the ellipse so that we can deploy the same inputs.conf to several machines, each with a different directory path.&lt;/P&gt;

&lt;P&gt;If we tighten it down to a single directory/file, things run great.&lt;/P&gt;

&lt;P&gt;My question is:&lt;BR /&gt;
Is there any way to have splunk traverse the directory tree less often (once a day or even less frequent), but still read files it already knows about in near real time?&lt;/P&gt;

&lt;P&gt;I did not see anything in the doc about a setting like that.&lt;/P&gt;</description>
    <pubDate>Tue, 07 Jun 2011 21:03:28 GMT</pubDate>
    <dc:creator>kkalmbach</dc:creator>
    <dc:date>2011-06-07T21:03:28Z</dc:date>
    <item>
      <title>CPU usage  using the lightforwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/CPU-usage-using-the-lightforwarder/m-p/24386#M3841</link>
      <description>&lt;P&gt;I am using the light forwarder on AIX and running into high CPU usage (80-90% of a CPU).&lt;BR /&gt;
We tracked it down to using ellipse in the monitor line in inputs.conf.&lt;BR /&gt;
(even a "*" uses too much CPU).&lt;BR /&gt;
We are using the ellipse so that we can deploy the same inputs.conf to several machines, each with a different directory path.&lt;/P&gt;

&lt;P&gt;If we tighten it down to a single directory/file, things run great.&lt;/P&gt;

&lt;P&gt;My question is:&lt;BR /&gt;
Is there any way to have splunk traverse the directory tree less often (once a day or even less frequent), but still read files it already knows about in near real time?&lt;/P&gt;

&lt;P&gt;I did not see anything in the doc about a setting like that.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2011 21:03:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/CPU-usage-using-the-lightforwarder/m-p/24386#M3841</guid>
      <dc:creator>kkalmbach</dc:creator>
      <dc:date>2011-06-07T21:03:28Z</dc:date>
    </item>
    <item>
      <title>Re: CPU usage  using the lightforwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/CPU-usage-using-the-lightforwarder/m-p/24387#M3842</link>
      <description>&lt;P&gt;You should open a bug on this issue.  You'd have to write your own script to look for new files.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jun 2011 21:26:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/CPU-usage-using-the-lightforwarder/m-p/24387#M3842</guid>
      <dc:creator>mw</dc:creator>
      <dc:date>2011-06-07T21:26:53Z</dc:date>
    </item>
  </channel>
</rss>

