<?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 Deploy limits.conf for Splunk Universal Forwarder? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Deploy-limits-conf-for-Splunk-Universal-Forwarder/m-p/436587#M20937</link>
    <description>&lt;P&gt;We are trying to deploy limits.conf to all of our endpoints to here:&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;C:\Program Files\SplunkUniversalForwarder\etc\apps\local&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;The problem is, I don't see an app for SplunkUniversalForwarder on our Deployment Server... It's not in /etc/apps or /etc/deployment-apps&lt;/EM&gt;&lt;/STRONG&gt; &lt;/P&gt;

&lt;P&gt;Do I need to create a "SplunkUniversalForwarder" app in the deployment-apps directory on the Deployment Server where our other deployed apps reside, and just create the local folder with the inputs.conf I want to use in there and deploy it like any other app?&lt;/P&gt;

&lt;P&gt;I would have thought if the SplunkUniversalForwarder app is on the local machines, there would already be an app for it somewher eon the deployment server...&lt;/P&gt;</description>
    <pubDate>Wed, 01 May 2019 20:31:19 GMT</pubDate>
    <dc:creator>jcleary47</dc:creator>
    <dc:date>2019-05-01T20:31:19Z</dc:date>
    <item>
      <title>Deploy limits.conf for Splunk Universal Forwarder?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Deploy-limits-conf-for-Splunk-Universal-Forwarder/m-p/436587#M20937</link>
      <description>&lt;P&gt;We are trying to deploy limits.conf to all of our endpoints to here:&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;C:\Program Files\SplunkUniversalForwarder\etc\apps\local&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;The problem is, I don't see an app for SplunkUniversalForwarder on our Deployment Server... It's not in /etc/apps or /etc/deployment-apps&lt;/EM&gt;&lt;/STRONG&gt; &lt;/P&gt;

&lt;P&gt;Do I need to create a "SplunkUniversalForwarder" app in the deployment-apps directory on the Deployment Server where our other deployed apps reside, and just create the local folder with the inputs.conf I want to use in there and deploy it like any other app?&lt;/P&gt;

&lt;P&gt;I would have thought if the SplunkUniversalForwarder app is on the local machines, there would already be an app for it somewher eon the deployment server...&lt;/P&gt;</description>
      <pubDate>Wed, 01 May 2019 20:31:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Deploy-limits-conf-for-Splunk-Universal-Forwarder/m-p/436587#M20937</guid>
      <dc:creator>jcleary47</dc:creator>
      <dc:date>2019-05-01T20:31:19Z</dc:date>
    </item>
    <item>
      <title>Re: Deploy limits.conf for Splunk Universal Forwarder?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Deploy-limits-conf-for-Splunk-Universal-Forwarder/m-p/436588#M20938</link>
      <description>&lt;P&gt;The best way to handle this is&lt;BR /&gt;
1. Create a specific app  eg:  &lt;CODE&gt;MY_LIMITS_APP&lt;/CODE&gt;  and create &lt;CODE&gt;local/limits.conf&lt;/CODE&gt; within this app&lt;BR /&gt;
2. put the stanza and value you need in  &lt;CODE&gt;MY_LIMITS_APP/local/limits.conf&lt;/CODE&gt;&lt;BR /&gt;
3. Update your serverclass to push &lt;CODE&gt;MY_LIMITS_APP&lt;/CODE&gt; to your Universal Forwarders&lt;/P&gt;

&lt;P&gt;Everything should be good and you can control all your limits via this app afterwards and is modular&lt;/P&gt;

&lt;P&gt;PS: In case if something is not working, run a btool in your UF to see if the limits.conf stanza from your app is being picked up&lt;BR /&gt;
&lt;CODE&gt;$SPLUNK_HOME/bin/splunk cmd btool limits list --debug&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 01 May 2019 20:48:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Deploy-limits-conf-for-Splunk-Universal-Forwarder/m-p/436588#M20938</guid>
      <dc:creator>koshyk</dc:creator>
      <dc:date>2019-05-01T20:48:58Z</dc:date>
    </item>
    <item>
      <title>Re: Deploy limits.conf for Splunk Universal Forwarder?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Deploy-limits-conf-for-Splunk-Universal-Forwarder/m-p/436589#M20939</link>
      <description>&lt;P&gt;Just so I understand, and to clarify - the limits.conf file I want to deploy is supposed to (according to Splunk Support) go into this directory on all of our endpoints:&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;C:\Program Files\SplunkUniversalForwarder\etc\apps\local\limits.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;If I create a new app with the limits.conf that I want to use, won't it only apply to data going through the forwarder for that app I create?&lt;/P&gt;

&lt;P&gt;I was under the impression to create this: &lt;BR /&gt;
&lt;STRONG&gt;C:\Program Files\SplunkUniversalForwarder\etc\apps\local\limits.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;I would have to have an app on the deployment server called SplunkUniversalForwarder to get it to deploy to that location.&lt;/P&gt;

&lt;P&gt;But it sounds like you are saying the SplunkUniversalForwarder will use the limits.conf value from any app that is on the endpoint that has one in it's local folder?&lt;/P&gt;</description>
      <pubDate>Wed, 01 May 2019 20:56:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Deploy-limits-conf-for-Splunk-Universal-Forwarder/m-p/436589#M20939</guid>
      <dc:creator>jcleary47</dc:creator>
      <dc:date>2019-05-01T20:56:23Z</dc:date>
    </item>
    <item>
      <title>Re: Deploy limits.conf for Splunk Universal Forwarder?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Deploy-limits-conf-for-Splunk-Universal-Forwarder/m-p/436590#M20940</link>
      <description>&lt;P&gt;-- But it sounds like you are saying the SplunkUniversalForwarder will use the &lt;CODE&gt;limits.conf&lt;/CODE&gt; value from any app that is on the endpoint that has one in its local folder?&lt;/P&gt;

&lt;P&gt;Absolutely - and you can't control from the deployment server the &lt;CODE&gt;C:\Program Files\SplunkUniversalForwarder\etc\apps\local\limits.conf&lt;/CODE&gt; file and therefore you should follow the solution prescribed by @koshyk ; -)&lt;/P&gt;</description>
      <pubDate>Wed, 01 May 2019 21:34:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Deploy-limits-conf-for-Splunk-Universal-Forwarder/m-p/436590#M20940</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2019-05-01T21:34:31Z</dc:date>
    </item>
    <item>
      <title>Re: Deploy limits.conf for Splunk Universal Forwarder?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Deploy-limits-conf-for-Splunk-Universal-Forwarder/m-p/436591#M20941</link>
      <description>&lt;P&gt;It is much simpler than you think.  Just create your own app, put the limits.conf in your app and in serverclass, put the wildcard whitelist in deployment-server for of  your APP to all UF clients and should go perfectly. and You then have full control and naming standards for your organisation&lt;/P&gt;</description>
      <pubDate>Thu, 02 May 2019 18:41:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Deploy-limits-conf-for-Splunk-Universal-Forwarder/m-p/436591#M20941</guid>
      <dc:creator>koshyk</dc:creator>
      <dc:date>2019-05-02T18:41:06Z</dc:date>
    </item>
  </channel>
</rss>

