8 Template changes
This page lists all changes to the stock templates that are shipped with Zabbix. It is suggested to modify these templates in existing installations - depending on the changes, it can be done either by:
- importing the latest official version (while in Configuration →
Templates you can import the updated template manually from the
templatesdirectory of the downloaded latest Zabbix version); - performing the change manually.
Changes in 4.2.0
Zabbix server template
- New low-level discovery manager and worker processes have been added
- The new
zabbix[lld_queue]item has been added to monitor low-level discovery queue - More descriptions for triggers related to caching parameters have been added (e.g. "Consider increasing HistoryCacheSize in the zabbix_server.conf configuration file" for the More than 75% used in the history cache trigger, etc.).
Zabbix proxy template
Description of the More than 75% used in the configuration cache trigger has been fixed to refer to the zabbix_proxy.conf file (instead of zabbix_server.conf).
More descriptions for triggers related to caching parameters have been added (e.g. "Consider increasing HistoryCacheSize in the zabbix_proxy.conf configuration file" for More than 75% used in the history cache trigger, etc.).
Zabbix agent template
Minor naming inconsistency in items and triggers has been fixed in Template App Zabbix Agent (e.g. Version of zabbix_agent(d) running → Version of Zabbix agent running)
Changes in 4.2.1
SNMP interface templates
Update intervals have been changed from 5m to 3m for these LLD item prototypes:
Interface {#IFNAME}({#IFALIAS}): Inbound packets with errorsInterface {#IFNAME}({#IFALIAS}): Outbound packets with errors
in:
- Template Module Interfaces Simple SNMPv1
- Template Module Interfaces Simple SNMPv2
- Template Module Interfaces SNMPv1
- Template Module Interfaces SNMPv2
- Template Module Interfaces Windows SNMPv2
These update intervals have been changed to avoid creation of excess internal events caused by trigger state flapping.
Changes in 4.2.7
Juniper template
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:
- Template Net Juniper SNMPv2
Changes in 4.2.8
New Cisco UCS server template
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.
HP iLO template
The counter for overall server health check has been fixed in the Template Server HP iLO SNMPv2 template.
HP Comware template
The Template Net HP Comware HH3C SNMPv2 now contains the correct value mapping.