Hi,
we're monitoring our vSphere 5.1 environment with Nagios. Most of the checks (cpu, memory, hardware, etc.) are performed against the hosts and not through the vCenter. The checks use a local user "monagent" that has been created on each ESXi host.
Unfortunately these checks are filling up the Events list of the ESXi in our vCenter. Is there a way to suppress these entries?
#####################################################################################
User monagent@ logged out (login time: , number of API invocations: , user agent: )
info
13.12.2012 09:27:13
esxihost.domain.local
monagent
User monagent@IPAdress logged in as
info
13.12.2012 09:27:12
esxihost.domain.local
monagent
User monagent@ logged out (login time: , number of API invocations: , user agent: )
info
13.12.2012 09:27:03
esxihost.domain.local
monagent
User monagent@IPAdress logged in as
info
13.12.2012 09:27:03
esxihost.domain.local
monagent
User monagent@ logged out (login time: , number of API invocations: , user agent: )
info
13.12.2012 09:20:51
esxihost.domain.local
monagent
User monagent@IPAdress logged in as
info
13.12.2012 09:20:50
esxihost.domain.local
monagent
#####################################################################################
Any help appreciated...
Anyone having any idea?
Hi, i have the same problem than you... I'm searching some workaround...
I switched to a workaround today.
All Nagios checks are now running through the vCenter, only the hardware is beiing checked directly on the ESXi.
No increased load measurable on the vCenter (20 hosts) yet.
I have the same issue ...
once enable the shell and run shell command
I have the same issue with HP image of ESXi 5.1.0 U1, but only on DL380G8! Five servers are DL380G7, with same image, but without these messages!
I think that this is more for HP to answer...
I turn off ESXi Shell & SSH in every ESXI managed by vCenter, the issue still remain.
If running 5.1 Update 1, you could try to adjust the hostd logging a bit....
New Component-Based Logging For Hostd In ESXi 5.1 Update 1 | VMware vSphere Blog - VMware Blogs
/Rubeck