Table of Contents
10 What's new in Zabbix 2.0.5
10.1 Frontend improvements
- Frontend overall performance was improved by optimising performance checks
- SQL query count was reduced and performance improved in IT services and most pages that access trigger information
- Graphs in web monitoring will use new flicker-free refresh method now
- Error messages for screen row and column span validation were improved
- Reduced the amount of persistent connections and to Oracle backend and changed to suggested Oracle access functions
10.1.1 New translations
- Bulgarian
10.1.2 Completed translations
The following translations are 100% completed for this release:
- American English
- Brazilian Portuguese
- French
- German
- Greek
- Japanese
- Portuguese (Portugal)
- Russian
- Ukrainian
10.1.3 Updated translations
- American English
- Brazilian Portuguese
- Dutch
- Finnish
- French
- German
- Greek
- Hungarian
- Japanese
- Latvian
- Polish
- Portuguese (Portugal)
- Russian
- Slovak
- Spanish
- Swedish
- Turkish
- Ukrainian
10.2 Daemon improvements
- Source IP setting for SNMP checks was not supported with all Net-SNMP versions. Since Zabbix 2.0.5 this setting should work in all cases.
- Performance for Oracle as the Zabbix backend database was improved by prefetching 2MB of data in SELECT statements.
- Zabbix Windows agent now supports Windows 8 and Windows Server 2012 in the system.uname item.
- Zabbix Windows agent now supports non-ASCII interface names on Windows Vista/Server 2008 and later.
- User macros and global regular expressions now are supported in SNMP trap item key parameters.
- Zabbix agent user parameter output previously was limited to 64KB. It can now return up to 512KB of data. Additionally, peak memory usage of agent in cases when the output size is smaller may be reduced by up to 60KB.
10.2.1 Improved SNMP performance
- Performance of the SNMP normalize function was improved.
- Previously, each dynamic index was obtained individually when requested. On systems with thousands of dynamic indexes Zabbix pollers were 100% busy for more than 10 minutes until the cache was built up. Now the first dynamic index request will cause all indexes in the same SNMP table to be looked up and processed in one go. This greatly speeds up the cache building and reduces the SNMP query count. Note that all entries are looked up even if only some would be used later.
10.2.2 Increased cache size limits
The limit for Zabbix server and proxy configuration parameters CacheSize, HistoryCacheSize and HistoryTextCacheSize, as well as server parameter TrendCacheSize, was increased from 1GB to 2GB.
10.3 Miscellaneous improvements
Zabbix sender now supports ServerActive parameter from the agent daemon configuration file. The first IP address is used.