Zabbix Documentation 4.0

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


manual:installation:upgrade_notes_400

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:installation:upgrade_notes_400 [2018/11/21 10:01]
martins-v explaining the logic behind {TRIGGER.NAME} -> {EVENT.NAME} macro changes a bitt better
manual:installation:upgrade_notes_400 [2019/07/12 08:51] (current)
martins-v some rewording
Line 14: Line 14:
   * libpthread - the POSIX Threads library is now mandatory when compiling Zabbix server and Zabbix proxy. It is required for process-shared mutexes and read-write locks. If mutexes are available, but cannot be process shared then Zabbix will fall back to using semaphores as before the upgrade.   * libpthread - the POSIX Threads library is now mandatory when compiling Zabbix server and Zabbix proxy. It is required for process-shared mutexes and read-write locks. If mutexes are available, but cannot be process shared then Zabbix will fall back to using semaphores as before the upgrade.
   * zlib - the compression library is now mandatory when compiling Zabbix server and Zabbix proxy.   * zlib - the compression library is now mandatory when compiling Zabbix server and Zabbix proxy.
 +
 +=== Compression for server-proxy communication ===
 +
 +Communication between Zabbix server and Zabbix proxies is now using compression to reduce network load and increase performance on low bandwidth network links.
 +
 +Note that the [[:​manual/​appendix/​protocols/​header_datalen|header]] of Zabbix requests/​responses has been changed as part of this development.
 +
 +<note warning>​If you are using network security devices like [[https://​en.wikipedia.org/​wiki/​Intrusion_detection_system|IDS/​IPS]] or [[https://​en.wikipedia.org/​wiki/​Next-generation_firewall|NGFW]] in your network and you are using Zabbix proxies, please make sure your application definitions are up to date for the new Zabbix proxy protocol prior to upgrading to 4.0.x as there have been reports on these devices dropping the traffic when encountering the compression in the network stream. Please contact your security vendor for more information on how to obtain updated definitions or possible workarounds if you run into this problem.</​note>​
  
 === Server parameter for passive proxies mandatory === === Server parameter for passive proxies mandatory ===
Line 59: Line 67:
   UPDATE users SET passwd=""​ WHERE passwd=md5('​zabbix'​)   UPDATE users SET passwd=""​ WHERE passwd=md5('​zabbix'​)
  
 +== API related changes ==
 +
 +HTTP basic-authentication specific code was removed from API, therefore the ''​password''​ field is now mandatory for the API ''​user.login''​ action.
 ==== Informational ==== ==== Informational ====
  
Line 79: Line 90:
 === Timestamp correction === === Timestamp correction ===
  
-Zabbix server will no longer ​correct ​timestamps in cases when Zabbix proxy time differs from Zabbix server time.+Zabbix server will no longer ​adjust value timestamps in cases when Zabbix proxy/active agent/​sender ​time differs from Zabbix server time.
  
 === Time triggers processed by history syncers === === Time triggers processed by history syncers ===
Line 122: Line 133:
 Since problem names are no longer generated in runtime based on the current trigger name, and instead are being generated at the time of event, there are corresponding macro changes: Since problem names are no longer generated in runtime based on the current trigger name, and instead are being generated at the time of event, there are corresponding macro changes:
  
-  * In all default messages - {TRIGGER.NAME} has been replaced by {EVENT.NAME}.+  * In all default messages - {TRIGGER.NAME} has been replaced by {EVENT.NAME};
   * In all trigger-based actions - {TRIGGER.NAME} will be replaced by {EVENT.NAME} when upgrading.   * In all trigger-based actions - {TRIGGER.NAME} will be replaced by {EVENT.NAME} when upgrading.
-  + 
 +See also: [[:​manual/​installation/​known_issues#​known_issues_for_400_-_401|known issues]]
 === Working with problems === === Working with problems ===
  
Line 177: Line 189:
  
 Dashboard API is also affected: some of [[manual:​api:​reference:​dashboard:​object|Dashboard widget property types]] are now renamed. ​ Dashboard API is also affected: some of [[manual:​api:​reference:​dashboard:​object|Dashboard widget property types]] are now renamed. ​
 +
 +=== Host column always displayed ===
 +
 +The host column is now always displayed even if only one host is selected in:
 +
 +  * //​Monitoring//​ -> //Latest data//
 +  * //​Monitoring//​ -> //Web//
 +  * //Reports// -> //​Availability//​
 +
 +This results in a wider page than previously with one host data. For more information,​ see the [[:​manual/​introduction/​whatsnew400#​host_column_always_displayed|What'​s new]] section.
  
 === JMX monitoring error message === === JMX monitoring error message ===
Line 191: Line 213:
 |//​Previously:// ​    ​|''​History buffer is full. Sleeping for 1 second.'' ​ | |//​Previously:// ​    ​|''​History buffer is full. Sleeping for 1 second.'' ​ |
 |//In Zabbix 4.0:// ​ |''​History cache is full. Sleeping for 1 second.'' ​ | |//In Zabbix 4.0:// ​ |''​History cache is full. Sleeping for 1 second.'' ​ |
 +
 +==== See also ====
 +
 +  * [[:​manual/​installation/​template_changes|Template changes]]