parameter. The vmware.vm.discovery item now also returns data on virtual machine network interfaces. This data can be used to configure custom host interfaces. The vmware.vm.net.if.discovery item now frontend, go to http:// (for access from the host’s browser bridged mode should be enabled in the VM network settings). Note: If the appliance fails to start up in Hyper-V, you may want to press Ctrl+Alt+F2 working properly. Note that the event log item could already be present on the hypervisor if the Template VM VMware template has been linked during the host creation. 2. On the VMware Hypervisor host, create

frontend, go to http:// (for access from the host’s browser bridged mode should be enabled in the VM network settings). Note: If the appliance fails to start up in Hyper-V, you may want to press Ctrl+Alt+F2 working properly. Note that the event log item could already be present on the hypervisor if the Template VM VMware template has been linked during the host creation. 2. On the VMware Hypervisor host create number or percentage of inodes. vfs.fs.size The disk space in bytes or in percentage from total. vm.memory.size The memory size in bytes or in percentage from total. Virtual memory web.page.get Get

improvements ** New host prototype API ** A host prototype API has been implemented with the development of VM support for low-level discovery rules and can be used to manage host prototypes. It comes with the more VMware collectors than monitored services in your Zabbix server/proxy configuration. • vmware.vm.perfcounter and vmware.hv.perfcounter items were added to allow custom hypervisor and virtual machine second in Template Virt VMware Guest. The affected items are vmware.vm.vfs.dev.read[{$URL},{HOST.HOST},{#DISKNAME},bps] and vmware.vm.vfs.dev.write[{$URL},{HOST.HOST},{#DISKNAME},bps]. Template changes

Zabbix. Updated items • vmware.vm.discovery item, used for virtual machine discovery, now returns additional fields {#VM.DNS}, {#VM.GUESTFAMILY}, {#VM.GUESTFULLNAME}, {#VM.IP}; • vmware.hv.discovery item vmware.vm.cpu.latency[,] • vmware.vm.cpu.readiness[,,] • vmware.vm.cpu.swapwait[,,] • vmware.vm.cpu.usage.perf[,] • vmware.vm.guest.memory • vmware.vm.guest.osuptime[,] • vmware.vm.memory.size.consumed[,] • vmware.vm.memory.usage[,] • vmware.vm.net.if.usage[,,] • vmware.vm.storage.readoio[

more VMware collectors than monitored services in your Zabbix server/proxy configuration. • vmware.vm.perfcounter and vmware.hv.perfcounter items were added to allow custom hypervisor and virtual machine second in Template Virt VMware Guest. The affected items are vmware.vm.vfs.dev.read[{$URL},{HOST.HOST},{#DISKNAME},bps] and vmware.vm.vfs.dev.write[{$URL},{HOST.HOST},{#DISKNAME},bps]. Template changes Template OS AIX. Both items were also added to ”Performance” application. Template changes in 2.4.7 Item vm.memory.size[total] moved from ”Filesystems” to ”Memory” application in Template OS Windows. 8 Upgrade

without getting double alerts. vm.memory.size[available] item on AIX now returns the sum of free and cached memory. Before Zabbix 3.0 only the free memory size was returned. vm.memory.size[available] item sysfs, if sysfs access fails then try reading directly from memory. 3.3 Windows monitoring A new vm.vmemory.size key has been added to monitor virtual memory statistics on Windows. 4 Trigger functions latest version or by performing the change manually. Template changes in 3.0.0 A new item vmware.vm.cpu.ready was added to template Template Virt VMware Guest. Item net.tcp.service[ntp] was changed

dvswitch.fetchports.get[]; • Virtual machines: vmware.vm.state[], vmware.vm.tools[], vmware.vm.snapshot.get[], vmware.vm.consolidationneeded[], vmware.vm.attribute[]; • Hypervisors: vmware.hv.connectionstate[] new mode options have been added to both items: packets, dropped, errors, broadcast. The item vmware.vm.discovery[], used for virtual machine discovery, now returns additional discovery fields, including vmware.vm.alarms.get[]. • Collecting tag information from different VMware components: vmware.cluster.tags.get[], vmware.datastore.tags.get[], vmware.dc.tags.get[], vmware.hv.tags.get[], vmware.vm.tags

Old naming: vfs.fs.free[*], vfs.fs.total[*], vfs.fs.used[*], vfs.fs.pfree[*], vfs.fs.pused[*] vm.memory.size[] 173 Key Memory size in bytes or in percentage from total. Integer - for See a more detailed description of vm.memory.size parameters. Old naming: vm.memory.buffers, vm.memory.cached, vm.memory.free, vm.memory.shared, vm.memory.total web.page.get[host,,] - returns the status of the first physical disk. This key is supported since Zabbix 2.2.0. vm.vmemory.size[] 184 Key Virtual memory size in bytes or in percentage from total. Integer

级别，以区分不 同的容器。 简单检查 vmware.eventlog 监控项现在支持在第三个参数中按严重性进行可选过滤。 vmware.vm.discovery 监控项现在也返回有关虚拟机网络接口的数据。这些数据可用于配置自定义主机接口。 vmware.vm.net.if.discovery 监控项现在也返回网络接口地址的数组。 以下监控项已添加新的 options 参数： • icmpping name 和 fields 元素已更新，以反映 Plain text 小部件被 Item history 小部件替换的更改。 7.0.1 的变化 新模板 • 通过 HTTP 监控 Azure VM Scale Set，HTTP 方式监控 Azure 的模板集补充。 • 通过 JMX 监控 Jira 数据中心：用于监控 Jira 数据中心健康状况的模板。 已更新模板 模板 Zabbix server 在工作的 VMWare Hypervisor 主机上，检查事件日志项 vmware.eventlog[,] 是否存在并且工作正常。请注意，如 果在主机创建期间已链接 Template VM VMWare 模板，则事件日志项可能已经存在于管理程序上。 2. 在 VMWare Hypervisor 主机上创建一个 “日志” 类型的依赖项 并将事件日志项设置为其主项。 在依赖项的 “预处理”