Zabbix Documentation 4.0

3.04.04.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

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 [2019/02/12 06:37]
martins-v linking to template changes
manual:installation:upgrade_notes_400 [2019/07/19 08:13] (current)
martins-v some rewording
Line 32: Line 32:
  
 As a consequence,​ Zabbix agents that are older than version 1.4 are no longer supported. Also, messages from self-written senders will be rejected if the header is absent. Whereas previously Zabbix trappers would accept messages without headers as well as messages with headers, now they will only accept messages with protocol header. As a consequence,​ Zabbix agents that are older than version 1.4 are no longer supported. Also, messages from self-written senders will be rejected if the header is absent. Whereas previously Zabbix trappers would accept messages without headers as well as messages with headers, now they will only accept messages with protocol header.
 +
 +Requests from an older Zabbix get version to the new agent will fail. Note that in this case the following error message is displayed:
 +
 +  Check access restrictions in Zabbix agent configuration
  
 === Loadable modules === === Loadable modules ===
Line 67: Line 71:
   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 87: Line 94:
 === Timestamp correction === === Timestamp correction ===
  
-Zabbix server will no longer ​correct ​timestamps in cases when Zabbix proxy time differs from Zabbix server time. The same applies to timestamps of an active agent check or Zabbix sender.+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 186: Line 193:
  
 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 201: Line 218:
 |//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 ===+==== See also ====
  
   * [[:​manual/​installation/​template_changes|Template changes]]   * [[:​manual/​installation/​template_changes|Template changes]]