Getting Data In

ESX Syslog - vmkwarning

BlightMan
Explorer

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?

Tags (2)

BlightMan
Explorer

I actually found the way to do this just by reviewing the default entries in the ESX hosts' syslog.conf.

Rather than forwarding everything:
{star}.{star} @server.domain.com

I just do this:
local6.warning @server.domain.com

It works perfectly! I hope this is useful for other people.

0 Karma

kdenton
Path Finder

What about installing the universal forwarder on the ESX server and setting up a seperate stanza to monitor that file only.

This would require installing the Splunk Universal Forwarder instead of just setting the syslog daemon on the vmware server to forward to syslog.

-Kevin

0 Karma

lguinn2
Legend

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.

0 Karma

dwaddle
SplunkTrust
SplunkTrust

this should work on "classical" esx, but I don't think it'd be applicable on esxi. (I could be wrong there though)

0 Karma

dwaddle
SplunkTrust
SplunkTrust

You cannot stop the messages from being sent but you can filter them away once they arrive at Splunk using a rule to route it to the nullQueue. This answers post, http://splunk-base.splunk.com/answers/96/how-do-i-exclude-some-events-from-being-indexed-by-splunk, has details on exactly how to do that.

lguinn2
Legend

This is the best solution, as it does not violate any best practices of Splunk or VMware, that I know of, anyway.

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.

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
http://www.simonlong.co.uk/blog/2010/05/28/using-vma-as-your-esxi-syslog-server/

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...

SplunkTrust Application Period is Officially OPEN!

It's that time, folks! The application/nomination period for the 2026-2027 SplunkTrust is officially open. If ...