<?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 in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder/m-p/19364#M2746</link>
    <description>&lt;P&gt;Usually, &lt;CODE&gt;host=&lt;/CODE&gt; is set to FQDN in the &lt;CODE&gt;[defaults]&lt;/CODE&gt; stanza of &lt;CODE&gt;$SPLUNK_HOME/etc/system/local/inputs.conf&lt;/CODE&gt;.  If this value is set incorrectly, Splunk could be assigning the wrong &lt;CODE&gt;host&lt;/CODE&gt; value for your data.&lt;/P&gt;

&lt;P&gt;This is an instance where &lt;CODE&gt;btool&lt;/CODE&gt; can help.  On your forwarders, run this command:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;splunk cmd btool --debug inputs list
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And look for your various inputs and see what &lt;CODE&gt;host=&lt;/CODE&gt; is set to for them.&lt;/P&gt;</description>
    <pubDate>Mon, 30 May 2011 16:06:46 GMT</pubDate>
    <dc:creator>dwaddle</dc:creator>
    <dc:date>2011-05-30T16:06:46Z</dc:date>
    <item>
      <title>Universal Forwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder/m-p/19363#M2745</link>
      <description>&lt;P&gt;I have multiple LAMP servers that I am looking to monitor with Splunk. I got my server setup last Friday and setup the Universal forwarder on a couple of VM's that i am using for testing. The problem is that these hosts do not show up on my server.&lt;/P&gt;

&lt;P&gt;I am running the configs from the *nix module on my forwarder test systems and was expecting them to show up when I was viewing the os index. Unfortunately, I only see a single host.&lt;/P&gt;

&lt;P&gt;I have verified that the forwarder is connecting to the server. A quick view of tcpdump output shows that information is being sent, but I am not sure what the server is doing with it; as the UI only shows the index server host and no others.&lt;/P&gt;

&lt;P&gt;Am I missing something basic here?&lt;/P&gt;</description>
      <pubDate>Mon, 30 May 2011 15:56:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder/m-p/19363#M2745</guid>
      <dc:creator>slopresto</dc:creator>
      <dc:date>2011-05-30T15:56:33Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder/m-p/19364#M2746</link>
      <description>&lt;P&gt;Usually, &lt;CODE&gt;host=&lt;/CODE&gt; is set to FQDN in the &lt;CODE&gt;[defaults]&lt;/CODE&gt; stanza of &lt;CODE&gt;$SPLUNK_HOME/etc/system/local/inputs.conf&lt;/CODE&gt;.  If this value is set incorrectly, Splunk could be assigning the wrong &lt;CODE&gt;host&lt;/CODE&gt; value for your data.&lt;/P&gt;

&lt;P&gt;This is an instance where &lt;CODE&gt;btool&lt;/CODE&gt; can help.  On your forwarders, run this command:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;splunk cmd btool --debug inputs list
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And look for your various inputs and see what &lt;CODE&gt;host=&lt;/CODE&gt; is set to for them.&lt;/P&gt;</description>
      <pubDate>Mon, 30 May 2011 16:06:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder/m-p/19364#M2746</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2011-05-30T16:06:46Z</dc:date>
    </item>
  </channel>
</rss>

