manual:introduction:whatsnew240

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:whatsnew240 [2016/04/11 12:00]
martins-v support for newlines and tabs in trigger expressions was added in 2.4
manual:introduction:whatsnew240 [2021/11/13 16:57] (current)
Line 25: Line 25:
 While offering quite a bit of flexibility,​ creating custom graphs was not particularly quick or easy to maintain, especially, if you wanted to compare a handful of items where their respective hosts were created and then deleted after a while. To address this issue it has now been made possible in Zabbix to create ad-hoc graphs for several items in a very quick way. While offering quite a bit of flexibility,​ creating custom graphs was not particularly quick or easy to maintain, especially, if you wanted to compare a handful of items where their respective hosts were created and then deleted after a while. To address this issue it has now been made possible in Zabbix to create ad-hoc graphs for several items in a very quick way.
  
-For that, similarly as for accessing simple graphs, you go to //​Monitoring// ​-> //Latest data//​. ​+For that, similarly as for accessing simple graphs, you go to //​Monitoring// ​→ //Latest data//​. ​
  
 The section no longer has the host and host group selection dropdowns. Instead, those two choices can be made within an expanded filter section, which can be used flexibly for displaying the exact set of items you want. Additonally,​ items now have checkboxes in the listing. The section no longer has the host and host group selection dropdowns. Instead, those two choices can be made within an expanded filter section, which can be used flexibly for displaying the exact set of items you want. Additonally,​ items now have checkboxes in the listing.
Line 177: Line 177:
 === - Responsible action shown in action log === === - Responsible action shown in action log ===
  
-The action log (displayed in the //​Administration// ​-> //Audit// section and in the //History of actions// screen element) would previously display various details about action operations (such as notifications sent, commands executed), however, the name of the responsible action was not displayed. ​+The action log (displayed in the //​Administration// ​→ //Audit// section and in the //History of actions// screen element) would previously display various details about action operations (such as notifications sent, commands executed), however, the name of the responsible action was not displayed. ​
  
 Now the Action log/Action log screen element have gained a new **Action** column showing the name of the responsible action as well. Now the Action log/Action log screen element have gained a new **Action** column showing the name of the responsible action as well.
Line 184: Line 184:
  
 Other improvements include: Other improvements include:
-  * renaming page titles in //​Administration ​-> Audit//:+  * renaming page titles in //​Administration ​→ Audit//:
     * '​Actions'​ to '​Action log'     * '​Actions'​ to '​Action log'
     * '​Logs'​ to 'Audit log'     * '​Logs'​ to 'Audit log'
Line 211: Line 211:
 === - Option to see problems only in trigger status page === === - Option to see problems only in trigger status page ===
  
-Filtering options in //​Monitoring ​-> Triggers// previously allowed to either show all triggers regardless of status, or to show problem triggers, which included those that have recently switched to OK. +Filtering options in //​Monitoring ​→ Triggers// previously allowed to either show all triggers regardless of status, or to show problem triggers, which included those that have recently switched to OK. 
  
 The second option meant that if many triggers were switching to OK simultaneously,​ it became difficult to spot triggers that still remained in problem status. To deal with this situation, a third specific filtering option is now available showing only those triggers that still remain in problem status - this option now is called //​Problem//​. The second option meant that if many triggers were switching to OK simultaneously,​ it became difficult to spot triggers that still remained in problem status. To deal with this situation, a third specific filtering option is now available showing only those triggers that still remain in problem status - this option now is called //​Problem//​.
Line 221: Line 221:
 === - More options for trigger filtering === === - More options for trigger filtering ===
  
-Filtering in //​Monitoring ​-> Triggers// has gained a couple of new options:+Filtering in //​Monitoring ​→ Triggers// has gained a couple of new options:
  
   * //Filter by application// ​   * //Filter by application// ​
Line 230: Line 230:
 Additionally,​ the fairly large trigger filter now features in two frontend sections: Additionally,​ the fairly large trigger filter now features in two frontend sections:
  
-  * //​Monitoring// ​-> //​Triggers//​ +  * //​Monitoring// ​→ //​Triggers//​ 
-  * //​Monitoring// ​-> //​Overview//​ (with //​Triggers//​ selected in the Type dropdown)+  * //​Monitoring// ​→ //​Overview//​ (with //​Triggers//​ selected in the Type dropdown)
  
-Note that in //​Monitoring// ​-> //​Overview//,​ with //Data// selected in the Type dropdown, a small filter is displayed offering the possibility to filter data by application (an option, which was introduced in 2.2 version as an additional dropdown in the title bar).+Note that in //​Monitoring// ​→ //​Overview//,​ with //Data// selected in the Type dropdown, a small filter is displayed offering the possibility to filter data by application (an option, which was introduced in 2.2 version as an additional dropdown in the title bar).
  
 {{overview_new.png|}} {{overview_new.png|}}
Line 259: Line 259:
 == Synchronized in maps == == Synchronized in maps ==
  
-The menu available for hosts in //​Monitoring ​-> Maps// has been synchronized with other host menus to display the same selection of links.+The menu available for hosts in //​Monitoring ​→ Maps// has been synchronized with other host menus to display the same selection of links.
  
 The host menu is accessible by clicking on a host in several frontend sections. See more details about the [[manual:​web_interface:​frontend_sections:​monitoring:​dashboard#​host_menu|host menu]]. The host menu is accessible by clicking on a host in several frontend sections. See more details about the [[manual:​web_interface:​frontend_sections:​monitoring:​dashboard#​host_menu|host menu]].
Line 278: Line 278:
 === - Changing uploaded image type disallowed === === - Changing uploaded image type disallowed ===
  
-The type of uploaded images previously could be freely changed from //Icon// to //​Background//​ in the Images section of //​Administration// ​-> //​General//​. ​+The type of uploaded images previously could be freely changed from //Icon// to //​Background//​ in the Images section of //​Administration// ​→ //​General//​. ​
  
 That could be potentially dangerous since an icon, used in a network map, could be changed to //​background//​ thus making the map unsaveable in the future. To avoid this situation, the option of changing image type has been removed and the image upload form has been separated into two forms - one for icon and one for background upload. ​ That could be potentially dangerous since an icon, used in a network map, could be changed to //​background//​ thus making the map unsaveable in the future. To avoid this situation, the option of changing image type has been removed and the image upload form has been separated into two forms - one for icon and one for background upload. ​
Line 309: Line 309:
 {{templates_clickable.png|}} {{templates_clickable.png|}}
  
-  * Host groups listed in the //Web monitoring//​ widget of the frontend have been made clickable. The link leads to //​Monitoring// ​-> //Web// with scenarios of the respective host group selected.+  * Host groups listed in the //Web monitoring//​ widget of the frontend have been made clickable. The link leads to //​Monitoring// ​→ //Web// with scenarios of the respective host group selected.
  
 {{webmon_groups_clickable.png|}} {{webmon_groups_clickable.png|}}
Line 318: Line 318:
 |{{event_hostlist_new.png?​400|}}|In Zabbix 2.4.0.| |{{event_hostlist_new.png?​400|}}|In Zabbix 2.4.0.|
  
-  * //​Monitoring ​-> Latest data// filter option //Show items without data// is now enabled by default +  * //​Monitoring ​→ Latest data// filter option //Show items without data// is now enabled by default 
-  * //Cancel// button has been added to //​Monitoring ​-> Dashboard// filter+  * //Cancel// button has been added to //​Monitoring ​→ Dashboard// filter
   * In the user list, disabled groups in the //Group// column are now displayed in red   * In the user list, disabled groups in the //Group// column are now displayed in red
   * In the user group list, //Status// column has been moved to the end   * In the user group list, //Status// column has been moved to the end
-  * The value of ''​Max count of elements to show inside table cell''​ from //​Administration// ​-> //​General// ​-> //GUI// now also applies to templates listed in the host list, users listed in the user group list and user groups listed in the user list+  * The value of ''​Max count of elements to show inside table cell''​ from //​Administration// ​→ //​General// ​→ //GUI// now also applies to templates listed in the host list, users listed in the user group list and user groups listed in the user list
   * When a trigger belongs to many hosts, hosts are now displayed in alphabetical order   * When a trigger belongs to many hosts, hosts are now displayed in alphabetical order
-  * For numeric items with disabled history ('​history'​ and '​trends'​ set to 0), the //Graph// link is hidden from view in //​Monitoring//​ → //Latest data//. If history and trends are set to '​0'​ globally in //​Administration// ​-> //​General// ​-> //​Housekeeping//,​ then all //​Graph/​History//​ links are hidden in //Latest data//. +  * For numeric items with disabled history ('​history'​ and '​trends'​ set to 0), the //Graph// link is hidden from view in //​Monitoring//​ → //Latest data//. If history and trends are set to '​0'​ globally in //​Administration// ​→ //​General// ​→ //​Housekeeping//,​ then all //​Graph/​History//​ links are hidden in //Latest data//. 
-  * Hyperlinks in the first column of //​Inventory// ​-> //​Overview//​ now are displayed properly as links, not plain text.+  * Hyperlinks in the first column of //​Inventory// ​→ //​Overview//​ now are displayed properly as links, not plain text.
   * If evaluation for nodata() function fails due to lack of data on the server, a more informative message is displayed. Previous vague message of //​Evaluation failed for function...//​ has been expanded to include //item does not have enough data after server start or item creation//.   * If evaluation for nodata() function fails due to lack of data on the server, a more informative message is displayed. Previous vague message of //​Evaluation failed for function...//​ has been expanded to include //item does not have enough data after server start or item creation//.
   * //​Auto-login//​ and //​Auto-logout//​ controls have been removed from '​guest'​ user profile, as unnecessary.   * //​Auto-login//​ and //​Auto-logout//​ controls have been removed from '​guest'​ user profile, as unnecessary.
Line 331: Line 331:
   * A forward slash (/) in global regular expressions is treated literally, rather than a delimiter. This way it is possible to save expressions containing a slash, whereas previously it would produce an error.   * A forward slash (/) in global regular expressions is treated literally, rather than a delimiter. This way it is possible to save expressions containing a slash, whereas previously it would produce an error.
   * Proxy name is now displayed as host prefix in the item [[manual:​web_interface:​frontend_sections:​administration:​queue|queue details]] page.   * Proxy name is now displayed as host prefix in the item [[manual:​web_interface:​frontend_sections:​administration:​queue|queue details]] page.
-  * The trigger filter will no longer be reset when selecting all hosts on the //​Monitoring// ​-> //Events// page.+  * The trigger filter will no longer be reset when selecting all hosts on the //​Monitoring// ​→ //Events// page.
   * IT services in pop-up windows are now sorted by name.   * IT services in pop-up windows are now sorted by name.
   * IT service dependencies in the configuration window are now sorted by name.   * IT service dependencies in the configuration window are now sorted by name.
Line 386: Line 386:
 ** Handling automatically discovered hosts ** ** Handling automatically discovered hosts **
  
-Hosts created ​by a network discovery rule will be deleted ​automatically if a discovered entity is not in the rule's IP range anymore. Hosts are deleted ​immediately.+Hosts discovered ​by a network discovery rule will be removed ​automatically ​from //​Monitoring//​ → //​Discovery// ​if a discovered entity is not in the rule's IP range any more. Hosts are removed ​immediately.
  
 ** More details about unsupported agent items ** ** More details about unsupported agent items **
Line 392: Line 392:
 Zabbix agents now provide detailed information on why items become not supported, instead of the generic "Not supported by Zabbix Agent"​. This was achieved by extending the passive agent and active agent protocols (see [[manual:​appendix:​items:​activepassive|protocol documentation]]). However, new agents are compatible with older server and proxy, except the error message for passive agents will not be visible in the frontend. Querying values with ''​zabbix_get'',​ testing with ''​zabbix_agentd -p''​ and ''​zabbix_agentd -t''​ now also provides a detailed error message. Zabbix agents now provide detailed information on why items become not supported, instead of the generic "Not supported by Zabbix Agent"​. This was achieved by extending the passive agent and active agent protocols (see [[manual:​appendix:​items:​activepassive|protocol documentation]]). However, new agents are compatible with older server and proxy, except the error message for passive agents will not be visible in the frontend. Querying values with ''​zabbix_get'',​ testing with ''​zabbix_agentd -p''​ and ''​zabbix_agentd -t''​ now also provides a detailed error message.
  
-As a result, in //​Configuration// ​-> //​Hosts// ​-> //Items// of the frontend, when rolling the mouse over the error icon, you may expect to see more specific messages about why an item went unsuported.+As a result, in //​Configuration// ​→ //​Hosts// ​→ //Items// of the frontend, when rolling the mouse over the error icon, you may expect to see more specific messages about why an item went unsuported.
  
 |{{not_supported.png|}} ​ |{{not_supported_new2.png}}\\ {{not_supported_new1.png|}}\\ {{not_supported_new3.png|}}\\ ...  | |{{not_supported.png|}} ​ |{{not_supported_new2.png}}\\ {{not_supported_new1.png|}}\\ {{not_supported_new3.png|}}\\ ...  |