Documentation
Table of Contents
23 Co nowego w Zabbix 6.0.18
Items
docker.container_stats
The docker.container_stats item on Zabbix agent 2 now also returns a pids_stats property with the current number of processes/threads on the container.
Cleaner configuration export
YAML files generated during Zabbix entity configuration export no longer contain empty lines between entities in an array, which makes such files shorter and more convenient to work with. See Configuration export/import section for updated export examples.
UTF-8 BOM in configuration import
Configuration import now supports files with a UTF-8 byte-order mark (BOM).
Cosmos DB monitoring
The template Azure by HTTP now also works with Azure Cosmos DB for MongoDB.
You can get this template:
- In Configuration → Templates in new installations.
- If you are upgrading from previous versions, you can download this template from Zabbix Git repository or find it in the zabbix/templates directory of the downloaded latest Zabbix version. Then, while in Configuration → Templates you can import it manually into Zabbix.
Proxy history housekeeping
The limitation on the amount of outdated information deleted from the proxy database per proxy history housekeeping cycle has been removed.
Previously the housekeeper deleted only no more than 4 times the HousekeepingFrequency hours of outdated information. For example, if HousekeepingFrequency was set to "1", no more than 4 hours of outdated information (starting from the oldest entry) was deleted. In cases when a proxy would constantly receive data older than set in ProxyOfflineBuffer, this could result in excessive data accumulation.
Now this limitation has been removed, providing a more effective proxy history housekeeping solution.
A new template Google Cloud Platform by HTTP (GCP by HTTP) is available.
Default values for Zabbix agent 2
Zabbix agent 2 plugins now allow to define default values for connecting to monitoring targets in the configuration file. If no value is specified in an item key or a named session, the plugin will use the value defined in the corresponding default parameter. New parameters have the structure Plugins.<PluginName>.Default.<Parameter> - for example, Plugins.MongoDB.Default.Uri=tcp://localhost:27017. See for more info: