manual:introduction:whatsnew340
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
manual:introduction:whatsnew340 [2017/09/13 06:24] martins-v linking to what's new for 3.4.2 about problem ack messages |
manual:introduction:whatsnew340 [2021/11/13 16:58] (current) |
||
|---|---|---|---|
| Line 12: | Line 12: | ||
| There are also completely new widgets: | There are also completely new widgets: | ||
| - | * //Problems// - this widget replaces the //Last 20 issues// widget from previous versions and displays problems similarly to the //Monitoring// -> //Problems// section | + | * //Problems// - this widget replaces the //Last 20 issues// widget from previous versions and displays problems similarly to the //Monitoring// → //Problems// section |
| * //Map navigation tree// - this widget allows to build a hierarchy of existing maps. See more [[:manual/introduction/whatsnew340#map_navigation_tree|details]]. | * //Map navigation tree// - this widget allows to build a hierarchy of existing maps. See more [[:manual/introduction/whatsnew340#map_navigation_tree|details]]. | ||
| The dashboard filtering functionality has been removed as a dashboard-wide setting. Instead, the filtering can be applied to individual widgets such as //Host status//, //System status//, etc. | The dashboard filtering functionality has been removed as a dashboard-wide setting. Instead, the filtering can be applied to individual widgets such as //Host status//, //System status//, etc. | ||
| + | |||
| + | New function "//Open the action menu//" {{manual:web_interface:dashboard_action_menu2.png|}} has been added for modifying and accessing administration settings of a dashboard. It includes "//Sharing//" option to edit sharing preferences for the dashboard (e.g. share dashboards with other users and provide read only or write permission) as well as //Create new//, //Clone// and //Display// options. See [[:manual/web_interface/frontend_sections/monitoring/dashboard#viewing_and_editing_a_dashboard|viewing and editing a dashboard]] and [[:manual/config/visualisation/maps/map#sharing|sharing]] for more information. | ||
| For more details, see: | For more details, see: | ||
| Line 276: | Line 278: | ||
| * Server-proxy data exchange protocol was optimized to reduce the number of connections made to send historical (host availability, item history, discovery and auto registration) data from proxy to server. However server will also accept historical data from 3.2 (and older) proxies, keeping partial backwards compatibility. | * Server-proxy data exchange protocol was optimized to reduce the number of connections made to send historical (host availability, item history, discovery and auto registration) data from proxy to server. However server will also accept historical data from 3.2 (and older) proxies, keeping partial backwards compatibility. | ||
| * The default data storage period for internal, discovery and agent auto-registration events has been decreased from 365 days to 1 day. | * The default data storage period for internal, discovery and agent auto-registration events has been decreased from 365 days to 1 day. | ||
| - | * Maximum error message length has been increased from 128 to 2048 symbols for trigger and alert errors. This should reduce the possibility of error message being trimmed. Error messages can be viewed in //Configuration// -> //Hosts// -> //Triggers// for triggers and in //Reports// -> //Action log// for alerts, when rolling the mouse over the error icon. | + | * Maximum error message length has been increased from 128 to 2048 symbols for trigger and alert errors. This should reduce the possibility of error message being trimmed. Error messages can be viewed in //Configuration// → //Hosts// → //Triggers// for triggers and in //Reports// → //Action log// for alerts, when rolling the mouse over the error icon. |
| * Semaphore and shared memory management has been reworked to eliminate the possibility of IPC-related conflicts in between Zabbix daemons and between Zabbix and other applications. | * Semaphore and shared memory management has been reworked to eliminate the possibility of IPC-related conflicts in between Zabbix daemons and between Zabbix and other applications. | ||
| * Cache locking time during configuration synchronization has been reduced. | * Cache locking time during configuration synchronization has been reduced. | ||
| Line 336: | Line 338: | ||
| {{:manual:introduction:frontend_return_code_error.png|}} | {{:manual:introduction:frontend_return_code_error.png|}} | ||
| + | |||
| + | ==== See also ==== | ||
| + | |||
| + | * [[:manual/installation/template_changes|Template changes]] | ||