<?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: ESX Syslog - vmkwarning in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/ESX-Syslog-vmkwarning/m-p/97633#M20356</link>
    <description>&lt;P&gt;Correct - will NOT work on ESXi, and is NOT a recommended practice for ESX, either.  I am not sure it will even work on ESX; the Linux kernel that sits beneath ESX has been heavily modified and may not have the components that Splunk needs.  Besides, ESX is not a supported OS for the Splunk forwarder(s), so not a good practice even if it works.&lt;/P&gt;</description>
    <pubDate>Thu, 27 Oct 2011 22:07:03 GMT</pubDate>
    <dc:creator>lguinn2</dc:creator>
    <dc:date>2011-10-27T22:07:03Z</dc:date>
    <item>
      <title>ESX Syslog - vmkwarning</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/ESX-Syslog-vmkwarning/m-p/97629#M20352</link>
      <description>&lt;P&gt;I've set up Splunk Free to receive syslogs from my ESX hosts. This is all working perfectly. But is there some way to only send the contents of the vmkwarning file? Or can Splunk filter out anything that's not from vmkwarning?&lt;/P&gt;</description>
      <pubDate>Tue, 25 Oct 2011 15:56:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/ESX-Syslog-vmkwarning/m-p/97629#M20352</guid>
      <dc:creator>BlightMan</dc:creator>
      <dc:date>2011-10-25T15:56:01Z</dc:date>
    </item>
    <item>
      <title>Re: ESX Syslog - vmkwarning</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/ESX-Syslog-vmkwarning/m-p/97630#M20353</link>
      <description>&lt;P&gt;You cannot stop the messages from being &lt;STRONG&gt;sent&lt;/STRONG&gt; but you can filter them away once they arrive at Splunk using a rule to route it to the &lt;CODE&gt;nullQueue&lt;/CODE&gt;.  This answers post, &lt;A href="http://splunk-base.splunk.com/answers/96/how-do-i-exclude-some-events-from-being-indexed-by-splunk"&gt;http://splunk-base.splunk.com/answers/96/how-do-i-exclude-some-events-from-being-indexed-by-splunk&lt;/A&gt;, has details on exactly how to do that.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Oct 2011 18:24:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/ESX-Syslog-vmkwarning/m-p/97630#M20353</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2011-10-25T18:24:24Z</dc:date>
    </item>
    <item>
      <title>Re: ESX Syslog - vmkwarning</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/ESX-Syslog-vmkwarning/m-p/97631#M20354</link>
      <description>&lt;P&gt;What about installing the universal forwarder on the ESX server and setting up a seperate stanza to monitor that file only.  &lt;/P&gt;

&lt;P&gt;This would require installing the Splunk Universal Forwarder instead of just setting the syslog daemon on the vmware server to forward to syslog.&lt;/P&gt;

&lt;P&gt;-Kevin&lt;/P&gt;</description>
      <pubDate>Wed, 26 Oct 2011 15:15:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/ESX-Syslog-vmkwarning/m-p/97631#M20354</guid>
      <dc:creator>kdenton</dc:creator>
      <dc:date>2011-10-26T15:15:56Z</dc:date>
    </item>
    <item>
      <title>Re: ESX Syslog - vmkwarning</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/ESX-Syslog-vmkwarning/m-p/97632#M20355</link>
      <description>&lt;P&gt;this should work on "classical" esx, but I don't think it'd be applicable on esxi.  (I could be wrong there though)&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2011 21:56:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/ESX-Syslog-vmkwarning/m-p/97632#M20355</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2011-10-27T21:56:47Z</dc:date>
    </item>
    <item>
      <title>Re: ESX Syslog - vmkwarning</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/ESX-Syslog-vmkwarning/m-p/97633#M20356</link>
      <description>&lt;P&gt;Correct - will NOT work on ESXi, and is NOT a recommended practice for ESX, either.  I am not sure it will even work on ESX; the Linux kernel that sits beneath ESX has been heavily modified and may not have the components that Splunk needs.  Besides, ESX is not a supported OS for the Splunk forwarder(s), so not a good practice even if it works.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2011 22:07:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/ESX-Syslog-vmkwarning/m-p/97633#M20356</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2011-10-27T22:07:03Z</dc:date>
    </item>
    <item>
      <title>Re: ESX Syslog - vmkwarning</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/ESX-Syslog-vmkwarning/m-p/97634#M20357</link>
      <description>&lt;P&gt;This is the best solution, as it does not violate any best practices of Splunk or VMware, that I know of, anyway.&lt;/P&gt;

&lt;P&gt;FWIW, I don't think that the ESX syslogs are chatty.  So it's not a big deal to do the filtering to the null queue on the Splunk indexer.&lt;/P&gt;

&lt;P&gt;As a final option, you might install the vMA and use it a a syslog server.  I believe that you can use the vMA to control the logging level.  And you can probably install a fowarder on the vMA.  Look in the VMware manuals, and/or this article&lt;BR /&gt;
&lt;A href="http://www.simonlong.co.uk/blog/2010/05/28/using-vma-as-your-esxi-syslog-server/"&gt;http://www.simonlong.co.uk/blog/2010/05/28/using-vma-as-your-esxi-syslog-server/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2011 22:22:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/ESX-Syslog-vmkwarning/m-p/97634#M20357</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2011-10-27T22:22:10Z</dc:date>
    </item>
    <item>
      <title>Re: ESX Syslog - vmkwarning</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/ESX-Syslog-vmkwarning/m-p/97635#M20358</link>
      <description>&lt;P&gt;I actually found the way to do this just by reviewing the default entries in the ESX hosts' syslog.conf.&lt;/P&gt;

&lt;P&gt;Rather than forwarding everything:&lt;BR /&gt;
{star}.{star} @server.domain.com&lt;/P&gt;

&lt;P&gt;I just do this:&lt;BR /&gt;
local6.warning   @server.domain.com&lt;/P&gt;

&lt;P&gt;It works perfectly! I hope this is useful for other people.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Nov 2011 14:26:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/ESX-Syslog-vmkwarning/m-p/97635#M20358</guid>
      <dc:creator>BlightMan</dc:creator>
      <dc:date>2011-11-15T14:26:34Z</dc:date>
    </item>
  </channel>
</rss>

