DirectorySearch Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
Directory
Pradyumna
byPradyumna, February 8, 2014
Working fine but Esxi logs are growing
every check create a Login event and a logout event in the event table of the Esxi.
We get a lot of check (2 check per VM every 5min). That is generating millions of lines in the Esxi database which became very slow. We already reduce the event&task conservation time but not enough.
Does anyone know a way to limit the number of login to Esxi done by the check ?
Regards,
Pradyumna
every check create a Login event and a logout event in the event table of the Esxi.
We get a lot of check (2 check per VM every 5min). That is generating millions of lines in the Esxi database which became very slow. We already reduce the event&task conservation time but not enough.
Does anyone know a way to limit the number of login to Esxi done by the check ?
Regards,
Pradyumna
byPradyumna, January 29, 2014
Working fine but vCenter and Esxi logs are growing
every check create a Login event and a logout event in the event table of the vcenter/Esxi.
We get a lot of check (2 check per VM every 5min). That is generating millions of lines in the vcenter/Esxi database which became very slow. We already reduce the event&task conservation time but not enough.
Does anyone know a way to limite the number of login to vcenter done by the check ?
Regards,
Pradyumna
every check create a Login event and a logout event in the event table of the vcenter/Esxi.
We get a lot of check (2 check per VM every 5min). That is generating millions of lines in the vcenter/Esxi database which became very slow. We already reduce the event&task conservation time but not enough.
Does anyone know a way to limite the number of login to vcenter done by the check ?
Regards,
Pradyumna
Owner's reply
For issues like this better open an issue on GitHub. Well - you are right. Lot of logins. This is caused by the way the VMware Perl SDK is used. If a check starts you have to connect to VMware. Thats a login. Every time. So a lot of checks means a lot of logins. If you use a session file (which must be unique) you hav a persistent session per check. So less login but a lot of open sessions.
But this problem is imported from the original one )check_vmware_api.pl/check_esx3.pl). I am working on a solution but first I have to clean up the rest of the code.
Regards
Nartin
