Esta página lista todas as modificações nos templates padrões que são fornecidos com o Zabbix. É esperado que tais templates tenham sido modificados durante o processo de criação da nova versão e você poderá obte-los importando os arquivos ou modficando-os manualmente.
O item vmware.vm.cpu.ready
foi adicionado ao template Template Virt VMware Guest.
O item net.tcp.service[ntp]
foi modificado para net.udp.service[ntp]
no template Template App NTP Service.
O item de monitoração do cache de histórico de texto zabbix[wcache,index,pfree]
e a trigger correspondente foram removidos do template "Template App Zabbix Server".
O item de monitoração do cache de índices do histórico zabbix[wcache,index,pfree]
e a trigger correspondente foram adicionados ao template "Template App Zabbix Server".
New templates are available for monitoring some IBM, Dell, HP, Cisco UCS and Supermicro Aten hardware:
These templates are part of the default Zabbix dataset for new installations. If you are upgrading from previous versions, you can import these templates manually.
Naming style of groups and applications has been improved for some out-of-the-box templates.
Deprecated positional macros have been removed from item names in standard templates.
The default Zabbix server/proxy templates (Template App Zabbix Server, Template App Zabbix Proxy) have been changed.
While some items have been renamed, there are also some completely new items:
The following items are new and replace some old ones:
The trigger expressions using the replaced items have been updated accordingly.
Two new items have been added to Template_OS_Linux:
CPU guest time
- the time spent running a virtual CPU for guest operating systemsCPU guest nice time
- the time spent running a niced guest (virtual CPU for guest operating systems)The CPU utilization graph has been updated to include these two items.
Template App Apache Tomcat JMX has been updated:
New templates are available for remote monitoring of Zabbix server or proxy internal metrics from an external instance:
Note that in order to use a template for remote monitoring of multiple external instances, a separate host is required for each external instance monitoring.
Template VM VMware has been updated:
vmware.eventlog[{$URL},skip]
- now skipping old dataUpdate intervals have been changed from 5m to 3m for these LLD item prototypes:
Interface {#IFNAME}({#IFALIAS}): Inbound packets with errors
Interface {#IFNAME}({#IFALIAS}): Outbound packets with errors
in:
These update intervals have been changed to avoid creation of excess internal events caused by trigger state flapping.
The more correct OID of 'jnxOperatingCPU' (1.3.6.1.4.1.2636.3.1.13.1.8) is now used instead of 'jnxOperating5MinLoadAvg' (1.3.6.1.4.1.2636.3.1.13.1.21) in these LLD item and trigger prototypes:
{#SNMPVALUE}: CPU utilization
{#SNMPVALUE}: High CPU utilization
in:
A Cisco UCS server monitoring template - Template Server Cisco UCS SNMPv2 has been added.
It will be available in Configuration → Templates in new installations. If you are upgrading from previous versions, you can find this template in the templates
directory of the downloaded latest Zabbix version. Then, while in Configuration → Templates you can import it manually into Zabbix.
The counter for overall server health check has been fixed in the Template Server HP iLO SNMPv2 template.
The Template Net HP Comware HH3C SNMPv2 now contains the correct value mapping.
Low-level discovery rules have been split from the parent template Template Module HOST-RESOURCES-MIB SNMPv2 into separate linked templates:
Other changes:
Low-level discovery rules have been split into separate linked templates for the following template:
Template VM VMware has been updated: