manual:introduction:whatsnew400

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:introduction:whatsnew400 [2021/01/27 19:24]
127.0.0.1 external edit
manual:introduction:whatsnew400 [2021/11/13 16:59] (current)
Line 53: Line 53:
   * Template Server Cisco UCS SNMPv2   * Template Server Cisco UCS SNMPv2
  
-These templates are part of the default Zabbix dataset for new installations. If you are upgrading from previous versions, you can download the latest templates from the [[https://​git.zabbix.com/​projects/​ZBX/​repos/​zabbix/​browse/​templates|Zabbix Git repository]]. Then, while in //​Configuration// ​-> //​Templates//​ you can import them manually into Zabbix. If templates with the same names already exist, the //Delete missing// options should be checked when importing to achieve a clean import. This way the old items that are no longer in the updated template will be removed (note that it will mean losing history of these old items).+These templates are part of the default Zabbix dataset for new installations. If you are upgrading from previous versions, you can download the latest templates from the [[https://​git.zabbix.com/​projects/​ZBX/​repos/​zabbix/​browse/​templates|Zabbix Git repository]]. Then, while in //​Configuration// ​→ //​Templates//​ you can import them manually into Zabbix. If templates with the same names already exist, the //Delete missing// options should be checked when importing to achieve a clean import. This way the old items that are no longer in the updated template will be removed (note that it will mean losing history of these old items).
  
 ==== Item prototypes can depend on regular items ==== ==== Item prototypes can depend on regular items ====
Line 98: Line 98:
  
 ^New naming^Old naming^Affected location^Function^ ^New naming^Old naming^Affected location^Function^
-|//Show suppressed problems// ​ |//Show hosts in maintenance// ​ |Filter option in //​Monitoring// ​-> //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​problems|Problems]]// ​ |Display problems which would otherwise be suppressed (not shown) because of host maintenance. ​  | +|//Show suppressed problems// ​ |//Show hosts in maintenance// ​ |Filter option in //​Monitoring// ​→ //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​problems|Problems]]// ​ |Display problems which would otherwise be suppressed (not shown) because of host maintenance. ​  | 
-|:::​|:::​|Filter option in //​Monitoring// ​-> //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​overview|Overview]]//​ ('​Triggers'​ as //​Type//​) ​ |:::|+|:::​|:::​|Filter option in //​Monitoring// ​→ //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​overview|Overview]]//​ ('​Triggers'​ as //​Type//​) ​ |:::|
 |:::​|:::​|Configuration option in dashboard widgets:\\ //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​dashboard/​widgets#​problem_hosts|Problem hosts]]//\\ //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​dashboard/​widgets#​problems|Problems]]//​\\ //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​dashboard/​widgets#​problems_by_severity|Problems by severity]]//​\\ ​   |:::| |:::​|:::​|Configuration option in dashboard widgets:\\ //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​dashboard/​widgets#​problem_hosts|Problem hosts]]//\\ //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​dashboard/​widgets#​problems|Problems]]//​\\ //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​dashboard/​widgets#​problems_by_severity|Problems by severity]]//​\\ ​   |:::|
-|//Show suppressed problems// ​ |-  |New filter option in //​Monitoring// ​-> //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​overview|Overview]]//​ ('​Data'​ as //​Type//​) ​ |:::|+|//Show suppressed problems// ​ |-  |New filter option in //​Monitoring// ​→ //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​overview|Overview]]//​ ('​Data'​ as //​Type//​) ​ |:::|
 |:::​|:::​|New option in map [[:​manual/​config/​visualization/​maps/​map#​creating_a_map|configuration]] ​ |:::| |:::​|:::​|New option in map [[:​manual/​config/​visualization/​maps/​map#​creating_a_map|configuration]] ​ |:::|
 |:::​|:::​|New option in global [[:​manual/​web_interface/​user_profile/​global_notifications|notifications]] ​ |:::| |:::​|:::​|New option in global [[:​manual/​web_interface/​user_profile/​global_notifications|notifications]] ​ |:::|
Line 176: Line 176:
  
   * The problem severity displayed is now event-level severity and will change if updated in the following locations:   * The problem severity displayed is now event-level severity and will change if updated in the following locations:
-    * //​Monitoring// ​-> //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​problems|Problems]]//​ (and the corresponding dashboard widgets and screen elements) +    * //​Monitoring// ​→ //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​problems|Problems]]//​ (and the corresponding dashboard widgets and screen elements) 
-    * //​Monitoring// ​-> //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​overview|Overview]]//​ (and the corresponding dashboard widgets and screen elements)+    * //​Monitoring// ​→ //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​overview|Overview]]//​ (and the corresponding dashboard widgets and screen elements)
     * //Host group issues// and //Host issues// screen elements     * //Host group issues// and //Host issues// screen elements
-  * The content of what is displayed in the Actions column of //​Monitoring// ​-> //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​problems|Problems]]//​ has been expanded. Previously it only had textual information about the course of actions. Now all information is symbolic (icons) and, besides actions, also displays information on such activities as commenting and changing problem severity. When you roll the mouse over the icons, popups are displayed with more details about each activity.+  * The content of what is displayed in the Actions column of //​Monitoring// ​→ //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​problems|Problems]]//​ has been expanded. Previously it only had textual information about the course of actions. Now all information is symbolic (icons) and, besides actions, also displays information on such activities as commenting and changing problem severity. When you roll the mouse over the icons, popups are displayed with more details about each activity.
   * Previously in [[:​manual/​web_interface/​frontend_sections/​monitoring/​problems#​viewing_details|event details]] there were separate blocks for acknowledgments,​ message and remote command actions. Now all activities on the problem are displayed in one block and symbolic icons are used for each stage of the problem life cycle, including entries for problem generation and resolution times.   * Previously in [[:​manual/​web_interface/​frontend_sections/​monitoring/​problems#​viewing_details|event details]] there were separate blocks for acknowledgments,​ message and remote command actions. Now all activities on the problem are displayed in one block and symbolic icons are used for each stage of the problem life cycle, including entries for problem generation and resolution times.
-  * Acknowledgment operations in actions have been renamed to [[:​manual/​config/​notifications/​action/​acknowledgement_operations|Update operations]] +  * Acknowledgment operations in actions have been renamed to [[:​manual/​config/​notifications/​action/​acknowledgment_operations|Update operations]] 
-  * Event acknowledgment is now always enabled (the on/off checkbox in //​Administration// ​-> //General (GUI option in dropdown)// has been removed)+  * Event acknowledgment is now always enabled (the on/off checkbox in //​Administration// ​→ //General (GUI option in dropdown)// has been removed)
   * [[:​manual/​appendix/​macros/​supported_by_location|Macros]] have been updated:   * [[:​manual/​appendix/​macros/​supported_by_location|Macros]] have been updated:
     * {ACK.DATE} renamed to {EVENT.UPDATE.DATE}     * {ACK.DATE} renamed to {EVENT.UPDATE.DATE}
Line 213: Line 213:
 The following locations benefit from the redesign: The following locations benefit from the redesign:
  
-  * //​Monitoring// ​-> //​Dashboard//​ (graph widget) +  * //​Monitoring// ​→ //​Dashboard//​ (graph widget) 
-  * //​Monitoring// ​-> //​Problems//​ (with //History// selected in the filter) +  * //​Monitoring// ​→ //​Problems//​ (with //History// selected in the filter) 
-  * //​Monitoring// ​-> //Web// (in scenario details) +  * //​Monitoring// ​→ //Web// (in scenario details) 
-  * //​Monitoring// ​-> //Latest data// (item graph, item history, ad-hoc graph, templated screens) +  * //​Monitoring// ​→ //Latest data// (item graph, item history, ad-hoc graph, templated screens) 
-  * //​Monitoring// ​-> //​Graphs//​ +  * //​Monitoring// ​→ //​Graphs//​ 
-  * //​Monitoring// ​-> //​Screens//​ +  * //​Monitoring// ​→ //​Screens//​ 
-  * //​Monitoring// ​-> //Screens// (slideshows) +  * //​Monitoring// ​→ //Screens// (slideshows) 
-  * //​Reports// ​-> //​Availability report// +  * //​Reports// ​→ //​Availability report// 
-  * //​Reports// ​-> //Triggers top 100// +  * //​Reports// ​→ //Triggers top 100// 
-  * //​Reports// ​-> //Audit// +  * //​Reports// ​→ //Audit// 
-  * //​Reports// ​-> //Action log//+  * //​Reports// ​→ //Action log//
  
 See also: [[:​manual/​config/​visualization/​graphs/​simple#​time_period_selector|Time period selector]] See also: [[:​manual/​config/​visualization/​graphs/​simple#​time_period_selector|Time period selector]]
Line 237: Line 237:
 ==== Compact view of problems ==== ==== Compact view of problems ====
  
-A //Compact view// mode has been added in //​Monitoring// ​-> //​Problems//​ allowing to maximize the amount of problems that can be seen at the same time:+A //Compact view// mode has been added in //​Monitoring// ​→ //​Problems//​ allowing to maximize the amount of problems that can be seen at the same time:
  
 {{:​manual:​introduction:​compact_view.png?​600|}} {{:​manual:​introduction:​compact_view.png?​600|}}
Line 252: Line 252:
 With //​Monitoring//​ → //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​problems|Problems]]//​ becoming the go-to section when needing to see the current problems, it has been decided to remove the //​Triggers//​ section from the Monitoring menu. With //​Monitoring//​ → //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​problems|Problems]]//​ becoming the go-to section when needing to see the current problems, it has been decided to remove the //​Triggers//​ section from the Monitoring menu.
  
-Note that trigger status as such can now be viewed in //​Configuration// ​-> //​Hosts// ​-> //​[[:​manual/​web_interface/​frontend_sections/​configuration/​hosts/​triggers|Triggers]]//​ (in the new //Value// column), while trigger descriptions can be accessed from the //Trigger// context menu and are opened in a popup window.+Note that trigger status as such can now be viewed in //​Configuration// ​→ //​Hosts// ​→ //​[[:​manual/​web_interface/​frontend_sections/​configuration/​hosts/​triggers|Triggers]]//​ (in the new //Value// column), while trigger descriptions can be accessed from the //Trigger// context menu and are opened in a popup window.
  
 {{:​manual:​introduction:​triger_dependencies.png}} {{:​manual:​introduction:​triger_dependencies.png}}
Line 268: Line 268:
 In the new version, any unit can be prevented from being converted by using a ''​!''​ prefix, for example ''​!B''​. To better illustrate how this conversion works with and without the blacklisting,​ see the following examples of values and units: In the new version, any unit can be prevented from being converted by using a ''​!''​ prefix, for example ''​!B''​. To better illustrate how this conversion works with and without the blacklisting,​ see the following examples of values and units:
  
-  1024 !B -> 1024 B +  1024 !B → 1024 B 
-  1024 B -> 1 KB +  1024 B → 1 KB 
-  61 !s -> 61 s +  61 !s → 61 s 
-  61 s -> 1m 1s +  61 s → 1m 1s 
-  0 !uptime ​-> 0 uptime +  0 !uptime ​→ 0 uptime 
-  0 uptime ​-> 00:00:00 +  0 uptime ​→ 00:00:00 
-  0 !! -> 0 ! +  0 !! → 0 ! 
-  0 ! -> 0+  0 ! → 0
  
 Even though the previous unit blacklist also still works, it is now deprecated, so the correct way to prevent conversion for these units is now ''​!ms'',​ ''​!rpm'',​ ''​!RPM'',​ ''​!%''​ Even though the previous unit blacklist also still works, it is now deprecated, so the correct way to prevent conversion for these units is now ''​!ms'',​ ''​!rpm'',​ ''​!RPM'',​ ''​!%''​
Line 299: Line 299:
 {{:​manual:​introduction:​user_group_new.png?​600|}} {{:​manual:​introduction:​user_group_new.png?​600|}}
  
-This change applies to the "//​User groups//"​ form in //​Administration// ​-> //User groups//.+This change applies to the "//​User groups//"​ form in //​Administration// ​→ //User groups//.
  
 ==== Compression for server-proxy communication ==== ==== Compression for server-proxy communication ====
Line 305: Line 305:
 All communications between Zabbix server and all proxies, and vice versa are now unconditionally compressed. Compression lowers the bandwidth requirements and improves data transfer speed. All communications between Zabbix server and all proxies, and vice versa are now unconditionally compressed. Compression lowers the bandwidth requirements and improves data transfer speed.
  
-The //​Administration// ​-> //Proxies// form is extended with an additional column named "//​Compression//"​. ​+The //​Administration// ​→ //Proxies// form is extended with an additional column named "//​Compression//"​. ​
  
 {{:​manual:​introduction:​proxies_compression_new.png|}} ​ {{:​manual:​introduction:​proxies_compression_new.png|}} ​
Line 431: Line 431:
   * The order in which tags are displayed with the problem can be defined, as a comma-separated list (in the new //Tag display priority// field)   * The order in which tags are displayed with the problem can be defined, as a comma-separated list (in the new //Tag display priority// field)
  
-These changes apply to the filter in //​Monitoring// ​-> //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​problems|Problems]]//​ and to the //​Problems//​ dashboard [[:​manual/​web_interface/​frontend_sections/​monitoring/​dashboard/​widgets#​problems|widget]].+These changes apply to the filter in //​Monitoring// ​→ //​[[:​manual/​web_interface/​frontend_sections/​monitoring/​problems|Problems]]//​ and to the //​Problems//​ dashboard [[:​manual/​web_interface/​frontend_sections/​monitoring/​dashboard/​widgets#​problems|widget]].
  
-Similar changes are made to the filter in //​Configuration ​-> Hosts-> //​[[:​manual/​web_interface/​frontend_sections/​configuration/​hosts/​triggers|Triggers]]////​ excluding //Show tags//, //Tag name// and //Tag display priority// fields.+Similar changes are made to the filter in //​Configuration ​→ Hosts→ //​[[:​manual/​web_interface/​frontend_sections/​configuration/​hosts/​triggers|Triggers]]////​ excluding //Show tags//, //Tag name// and //Tag display priority// fields.
  
 == Host list == == Host list ==
Line 494: Line 494:
 {{:​manual:​introduction:​general_trigger_display2.png|}} {{:​manual:​introduction:​general_trigger_display2.png|}}
  
-A new //Use custom event status colors// option has been added in //​Administration// ​-> //​General// ​-> //Trigger displaying options//. This option allows to turn on the customization of colors for acknowledged/​unacknowledged problems.+A new //Use custom event status colors// option has been added in //​Administration// ​→ //​General// ​→ //Trigger displaying options//. This option allows to turn on the customization of colors for acknowledged/​unacknowledged problems.
  
 === Changes in "Host mass update"​ form === === Changes in "Host mass update"​ form ===
Line 508: Line 508:
 Trigger severity active blocks are now styled in severity colors while inactive blocks have the same color as table background color. Trigger severity active blocks are now styled in severity colors while inactive blocks have the same color as table background color.
  
-This change applies to the "//​Media//"​ tab in //​Administration// ​-> //​Users// ​-> //User properties//​ form and [[manual:​web_interface:​user_profile|User profile configuration]] form.+This change applies to the "//​Media//"​ tab in //​Administration// ​→ //​Users// ​→ //User properties//​ form and [[manual:​web_interface:​user_profile|User profile configuration]] form.
  
 === Twin boxes replaced with auto-select === === Twin boxes replaced with auto-select ===
Line 518: Line 518:
  
 This change applies to the following configuration forms: This change applies to the following configuration forms:
-  * //​Configuration// ​-> //​Hosts// ​-> //​Create/​Edit host and Configuration//;​ +  * //​Configuration// ​→ //​Hosts// ​→ //​Create/​Edit host and Configuration//;​ 
-  * //​Configuration// ​-> //Host groups// ​-> //​Create/​Edit host group//; +  * //​Configuration// ​→ //Host groups// ​→ //​Create/​Edit host group//; 
-  * //​Configuration// ​-> //​Maintenance// ​-> //​Create/​Edit maintenance period// ​-> //Hosts & Groups// tab; +  * //​Configuration// ​→ //​Maintenance// ​→ //​Create/​Edit maintenance period// ​→ //Hosts & Groups// tab; 
-  * //​Configuration// ​-> //​Templates// ​-> //​Create/​Edit template//;​ +  * //​Configuration// ​→ //​Templates// ​→ //​Create/​Edit template//;​ 
-  * //​Administration// ​-> //User groups// ​-> //​Create/​Edit user group //; +  * //​Administration// ​→ //User groups// ​→ //​Create/​Edit user group //; 
-  * //​Administration// ​-> //​Proxies// ​-> //​Create/​Edit proxy//.+  * //​Administration// ​→ //​Proxies// ​→ //​Create/​Edit proxy//.
  
 === Improved widget configuration === === Improved widget configuration ===
Line 598: Line 598:
 Green background has been removed: Green background has been removed:
  
-  * for resolved problems in the severity column in //​Monitoring// ​-> //​Problems/​Triggers//​ and the corresponding dashboard widget+  * for resolved problems in the severity column in //​Monitoring// ​→ //​Problems/​Triggers//​ and the corresponding dashboard widget
  
 |In Zabbix 4.0.0\\ {{:​manual:​introduction:​resolved_now.png|}} ​ | |In Zabbix 4.0.0\\ {{:​manual:​introduction:​resolved_now.png|}} ​ |
 |Before Zabbix 4.0.0\\ {{:​manual:​introduction:​resolved_before.png|}} ​ | |Before Zabbix 4.0.0\\ {{:​manual:​introduction:​resolved_before.png|}} ​ |
  
-  * for devices that are up in //​Monitoring// ​-> //​Discovery//​+  * for devices that are up in //​Monitoring// ​→ //​Discovery//​
  
 == Discovery status details == == Discovery status details ==
  
-Discovery status details in //​Monitoring// ​-> //​Discovery//​ are now displayed as text inside the cell, instead of a pop-up that's visible upon mouse over.+Discovery status details in //​Monitoring// ​→ //​Discovery//​ are now displayed as text inside the cell, instead of a pop-up that's visible upon mouse over.
  
 |In Zabbix 4.0.0  |Before Zabbix 4.0.0  | |In Zabbix 4.0.0  |Before Zabbix 4.0.0  |
Line 622: Line 622:
 The host column is now always displayed even if only one host is selected in: The host column is now always displayed even if only one host is selected in:
  
-  * //​Monitoring// ​-> //Latest data// +  * //​Monitoring// ​→ //Latest data// 
-  * //​Monitoring// ​-> //Web// +  * //​Monitoring// ​→ //Web// 
-  * //​Reports// ​-> //​Availability//​+  * //​Reports// ​→ //​Availability//​
  
 {{:​manual:​introduction:​host_column_on.png|}} {{:​manual:​introduction:​host_column_on.png|}}
Line 634: Line 634:
  
   * The allowed character limit has been raised from 63 to 255 ASCII characters for fields containing DNS names. The affected forms are host configuration and passive proxy configuration.   * The allowed character limit has been raised from 63 to 255 ASCII characters for fields containing DNS names. The affected forms are host configuration and passive proxy configuration.
-  * When importing maps (//​Monitoring// ​-> //​Maps// ​-> //Import// button) the //Create new// option for importing images is now checked by default:+  * When importing maps (//​Monitoring// ​→ //​Maps// ​→ //Import// button) the //Create new// option for importing images is now checked by default:
  
 {{:​manual:​introduction:​map_import_images.png|}} {{:​manual:​introduction:​map_import_images.png|}}