Details
-
Problem report
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
2.2.20
-
None
-
VMware ESXi 5.5, vCenter 5.5 (only check this version but other VMware version maybe same)
-
Team C
-
Sprint 18, Sprint 19, Sprint 20, Sprint 21, Sprint 22
-
3
Description
I noticed that vmware.eventlog item can only get latest 10 logs in one collection process.
If more than 10 event logs are outputted during the check interval of VMwareCollector (VMwareFrequency), over 10 event logs will not be monitored in Zabbix history data.
Are there planning to fix this issue?
VMware EventHistoryCollector object has SetCollectorPageSize method.
By using this method, EventHistoryCollector returns more than 10 event logs.(1000 is limit as VMware specification)
e.g. (set 100)
curl -X POST -s -k -b vmware_soap_session=${session_id} -H "Soapaction:urn:vim25/4.1" -H "Content-Type:text/xml; charset=utf-8" -d "\
<?xml version=\"1.0\" encoding=\"UTF-8\"?>\
<SOAP-ENV:Envelope xmlns:ns0=\"urn:vim25\"\
xmlns:ns1=\"http://schemas.xmlsoap.org/soap/envelope/\"\
xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\
xmlns:SOAP-ENV=\"http://schemas.xmlsoap.org/soap/envelope/\">\
<SOAP-ENV:Header/>\
<ns1:Body>\
<ns0:SetCollectorPageSize>\
<ns0:_this type=\"EventHistoryCollector\">${history_collector_session_name(session[xxx-xxx-xx..]yy-yy-...)}</ns0:_this>\
<ns0:maxCount>100</ns0:maxCount>\
</ns0:SetCollectorPageSize>\
</ns1:Body>\
</SOAP-ENV:Envelope>" https://esxi-server/sdk
By this change, load and data size may increase, but the possibility of lost logs will be low.
please consider.
best regards
