manual:installation:upgrade_notes_520

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Previous revision
manual:installation:upgrade_notes_520 [2020/01/30 15:26]
manual:installation:upgrade_notes_520 [2020/10/26 09:49] (current)
marinagen [ZBXNEXT-6148] better formatting
Line 1: Line 1:
 +==== 10 Upgrade notes for 5.2.0 ====
  
 +​<note important>​Zabbix 5.2.0 is not released yet.</​note>​
 +
 +==== Critical ====
 +
 +=== Minimum required PHP version ===
 +
 +The minimum required PHP version has been upped from 7.2.0 to 7.2.5.
 +
 +==== Informational ====
 +
 +==== User roles ====
 +It is now possible to define [[:​manual/​web_interface/​frontend_sections/​administration/​user_roles|user roles]] for granular control on what parts of UI, which API methods, and which functionality (such as the ability to acknowledge problems) are available to end-users. ​
 +
 +Defining a user role is now mandatory. By default, Zabbix is configured with four user roles, which are automatically assigned to the corresponding user types during upgrade: ​
 +^Role^Description^
 +|Admin role  | The same permissions as for Zabbix Admin user type. Access to Monitoring and Configuration sections. |
 +|Guest role  | The same permissions as for Guest users (user type: Users). Access to the Monitoring section only, without rights to perform any actions. Access to API is disabled. |
 +| Super admin role | Unlimited permissions. This role cannot be deleted or modified because at least one Super Admin with a full set of rights must exist. |
 +| User role        | The same permissions as for Zabbix User user type. Access to the Monitoring section only. By default, all available actions are enabled and users with role User have access to some API methods (item.get, dashboard.get,​ etc.) if they have sufficient permissions to a host or a UI element. | 
 +
 +It is possible to delete or modify these roles, except of the Super Admin role, or create additional roles with custom sets of permissions. ​
 +
 +<note warning> For users of type User read-only access to hosts is now sufficient to perform actions such as event acknowledgement,​ etc. 
 +
 +List of actions that users are allowed to perform is defined by the //User role// settings. By default, //User role// allows the following actions: ​
 +  * Create and edit dashboards and screens
 +  * Create and edit maps
 +  * Acknowledge problems
 +  * Close problems
 +  * Change severity
 +  * Add problem comments
 +  * Execute scripts
 +
 +To restrict users from performing all or some of the actions, go to //​Administration -> User roles//, select the role //User role// and unmark required checkboxes in the section //Access to actions//. Press the Update button to save new settings. </​note>​
 +
 +=== Time zone definition ===
 +
 +The frontend time zone, previously set by the '​date.timezone'​ setting of php.ini, now can be set globally in the frontend and adjusted for individual users. ​
 +
 +During the upgrade the time zone setting will default to %%"​%%System%%"​%% ensuring that everything works for users the same as before. With the //System// option, the web server time zone is used for the frontend (including the value of '​date.timezone'​ of php.ini, if set), while Zabbix server uses the time zone of the machine it is running on.
 +
 +See also: [[:​manual/​web_interface/​time_zone|Time zones]]
 +
 +=== Refreshing unsupported items ===
 +
 +A separate setting for refreshing unsupported items has been removed from //​Administration//​ -> //General// -> //Other//. Instead, the item update interval is now used for each unsupported item. This has been done to remove a potential performance bottleneck in the scenario when a lot of items turn unsupported and the global refresh interval has been set to a short value.
 +
 +=== Template screens converted to dashboards ===
 +
 +Host screens configured on the template level, or "​template screens",​ have been [[:​manual/​introduction/​whatsnew520#​template_screens_converted_to_dashboards|converted]] to template dashboards. The conversion of template screens will take place as soon as you launch the upgraded Zabbix server. As a result, the template screen elements will become the widgets of template dashboards. ​
 +
 +Each template screen will be converted to a template dashboard preserving the name and the configuration and location of screen elements (now widgets).
 +
 +However, it is not guaranteed that all screen elements will find their place on the converted dashboards, since screens can have a significantly larger width and height comparing to dashboards. In such cases Zabbix will discard the out-of-range screen elements, after trying to accommodate as many screen elements as possible by manipulating the size of newly created widgets.
 +
 +Please make sure to back up your templates before the upgrade to 5.2.
 +
 +Note that when importing an older template containing template screens into Zabbix 5.2 or later, the same screen-to-dashboard conversion principles will be applied.
 +=== Session stored in cookie ===
 +
 +Zabbix session is now stored in a user cookie.