<?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: Two different host names for the same host in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Two-different-host-names-for-the-same-host/m-p/69087#M13982</link>
    <description>&lt;P&gt;Thanks for the suggestions&lt;/P&gt;</description>
    <pubDate>Fri, 20 Sep 2013 14:26:16 GMT</pubDate>
    <dc:creator>hartfoml</dc:creator>
    <dc:date>2013-09-20T14:26:16Z</dc:date>
    <item>
      <title>Two different host names for the same host</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Two-different-host-names-for-the-same-host/m-p/69083#M13978</link>
      <description>&lt;P&gt;I have a Linux client with a UF reporting two different formats of host name.&lt;/P&gt;

&lt;P&gt;1) host.name.local.net&lt;BR /&gt;
2) host.name&lt;/P&gt;

&lt;P&gt;I looked in all input and output.conf and the server.conf and could only find the host=host.name.local.net&lt;/P&gt;

&lt;P&gt;I noticed that in only two types of events are the hostname different.&lt;BR /&gt;
source=/var/log/messages&lt;BR /&gt;
source=/var/log/cron&lt;/P&gt;

&lt;P&gt;two commands (ifconfig and sadc) are recorded in the messages log and both are failing to collect information due to permissions. these two are not the only two logs in the messages but are by far the dominant record.&lt;/P&gt;

&lt;P&gt;The other job or item with the wrong host name is &lt;CODE&gt;crond[21282]: (root) CMD (/usr/lib64/sa/sa1 1 1)&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;I don't know why these jobs are failing or why the host name is wrong.&lt;/P&gt;

&lt;P&gt;Any sugestions?&lt;/P&gt;</description>
      <pubDate>Fri, 20 Sep 2013 13:34:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Two-different-host-names-for-the-same-host/m-p/69083#M13978</guid>
      <dc:creator>hartfoml</dc:creator>
      <dc:date>2013-09-20T13:34:14Z</dc:date>
    </item>
    <item>
      <title>Re: Two different host names for the same host</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Two-different-host-names-for-the-same-host/m-p/69084#M13979</link>
      <description>&lt;P&gt;This can be related to the fact that data with the &lt;CODE&gt;syslog&lt;/CODE&gt; sourcetype will be parsed in a special way, where the &lt;CODE&gt;host&lt;/CODE&gt; value is extracted from each individual message, i.e. there is an index-time transform that overwrites the value from inputs.conf.&lt;/P&gt;

&lt;HR /&gt;

&lt;P&gt;UPDATE:&lt;/P&gt;

&lt;P&gt;As for 'fixing' it, you could either &lt;BR /&gt;
a) set another sourcetype for these inputs&lt;BR /&gt;
b) create a new TRANSFORM that will remove the .local from the host, and call that from props.conf.&lt;/P&gt;

&lt;P&gt;There are probably other good ways to deal with this, but it will depend on whether this a common or isolated problem&lt;/P&gt;

&lt;P&gt;/K&lt;/P&gt;</description>
      <pubDate>Fri, 20 Sep 2013 13:39:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Two-different-host-names-for-the-same-host/m-p/69084#M13979</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-09-20T13:39:48Z</dc:date>
    </item>
    <item>
      <title>Re: Two different host names for the same host</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Two-different-host-names-for-the-same-host/m-p/69085#M13980</link>
      <description>&lt;P&gt;this seems to be the right answer.  will you put it in as an answer so I can give you credit.  Also if you have any suggestions on how (if you wanted to) would you fixing this issue.&lt;/P&gt;

&lt;P&gt;Thanks for the speedy help!!!&lt;/P&gt;</description>
      <pubDate>Fri, 20 Sep 2013 13:50:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Two-different-host-names-for-the-same-host/m-p/69085#M13980</guid>
      <dc:creator>hartfoml</dc:creator>
      <dc:date>2013-09-20T13:50:30Z</dc:date>
    </item>
    <item>
      <title>Re: Two different host names for the same host</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Two-different-host-names-for-the-same-host/m-p/69086#M13981</link>
      <description>&lt;P&gt;you're welcome.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Sep 2013 14:10:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Two-different-host-names-for-the-same-host/m-p/69086#M13981</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-09-20T14:10:21Z</dc:date>
    </item>
    <item>
      <title>Re: Two different host names for the same host</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Two-different-host-names-for-the-same-host/m-p/69087#M13982</link>
      <description>&lt;P&gt;Thanks for the suggestions&lt;/P&gt;</description>
      <pubDate>Fri, 20 Sep 2013 14:26:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Two-different-host-names-for-the-same-host/m-p/69087#M13982</guid>
      <dc:creator>hartfoml</dc:creator>
      <dc:date>2013-09-20T14:26:16Z</dc:date>
    </item>
  </channel>
</rss>

