<?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 hostname in inputs.conf in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/hostname-in-inputs-conf/m-p/14632#M88349</link>
    <description>&lt;P&gt;Is there anyway I could verify if there is any variable which could be used to extract hostname for inputs.conf? instead of explicitly mentioning hostname, I need to push the input.conf file to a set of systems...&lt;/P&gt;</description>
    <pubDate>Wed, 02 Jun 2010 06:56:31 GMT</pubDate>
    <dc:creator>heterodyned</dc:creator>
    <dc:date>2010-06-02T06:56:31Z</dc:date>
    <item>
      <title>hostname in inputs.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/hostname-in-inputs-conf/m-p/14632#M88349</link>
      <description>&lt;P&gt;Is there anyway I could verify if there is any variable which could be used to extract hostname for inputs.conf? instead of explicitly mentioning hostname, I need to push the input.conf file to a set of systems...&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jun 2010 06:56:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/hostname-in-inputs-conf/m-p/14632#M88349</guid>
      <dc:creator>heterodyned</dc:creator>
      <dc:date>2010-06-02T06:56:31Z</dc:date>
    </item>
    <item>
      <title>Re: hostname in inputs.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/hostname-in-inputs-conf/m-p/14633#M88350</link>
      <description>&lt;P&gt;Well. In a standard install, the first time Splunk is run, it executes &lt;CODE&gt;hostname&lt;/CODE&gt; and puts the result into &lt;CODE&gt;$SPLUNK_HOME/etc/system/local/inputs.conf&lt;/CODE&gt; as the default hostname. That is what will be used for all inputs from this local machine unless otherwise specified or overridden. If that doesn't work for you then, at least as of 4.1.2, you'll have to figure out a way to regenerate the value in that file separately from any Splunk functionality.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jun 2010 16:57:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/hostname-in-inputs-conf/m-p/14633#M88350</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-06-02T16:57:29Z</dc:date>
    </item>
    <item>
      <title>Re: hostname in inputs.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/hostname-in-inputs-conf/m-p/14634#M88351</link>
      <description>&lt;P&gt;By default it is taking the IP of that system, although the fqdn is ssomething like : abcd.xyz.com, is there anyway I should be overwriting the hostname, like some default variable..&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jun 2010 05:06:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/hostname-in-inputs-conf/m-p/14634#M88351</guid>
      <dc:creator>heterodyned</dc:creator>
      <dc:date>2010-06-03T05:06:06Z</dc:date>
    </item>
    <item>
      <title>Re: hostname in inputs.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/hostname-in-inputs-conf/m-p/14635#M88352</link>
      <description>&lt;P&gt;hostname is defined in the $SPLUNKHOME/etc/system/local/inputs.conf. If you want to push out a standard inputs.conf to multiple splunk instances you have a few options:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Use a deployment server, creating a new app with your inputs.conf to be shipped out. A little bit up front setup time, but easy to manage many hosts. &lt;A href="http://www.splunk.com/base/Documentation/latest/Admin/Aboutdeploymentserver" rel="nofollow"&gt;http://www.splunk.com/base/Documentation/latest/Admin/Aboutdeploymentserver&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;If you want to manually (or via script) do this, simply place the inputs.conf into $SPLUNKHOME/etc/apps/search/local. The inputs.conf at this location does not define the hostname, so you don't have to worry about overwriting it by accident or setting it yourself.&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Take a look at the configuration file reference in the documentation, this should make a lot more sense then. &lt;A href="http://www.splunk.com/base/Documentation/latest/Admin/Wheretofindtheconfigurationfiles" rel="nofollow"&gt;http://www.splunk.com/base/Documentation/latest/Admin/Wheretofindtheconfigurationfiles&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jun 2010 20:07:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/hostname-in-inputs-conf/m-p/14635#M88352</guid>
      <dc:creator>ftk</dc:creator>
      <dc:date>2010-06-16T20:07:48Z</dc:date>
    </item>
    <item>
      <title>Re: hostname in inputs.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/hostname-in-inputs-conf/m-p/14636#M88353</link>
      <description>&lt;P&gt;thank you so much, i think this is what i was looking for, i am going to be working to use this feature for scaling the updated conf files...&lt;/P&gt;</description>
      <pubDate>Sun, 27 Jun 2010 18:45:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/hostname-in-inputs-conf/m-p/14636#M88353</guid>
      <dc:creator>heterodyned</dc:creator>
      <dc:date>2010-06-27T18:45:35Z</dc:date>
    </item>
  </channel>
</rss>

