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 [2014/12/10 09:03]
martins-v when importing hosts/templates using the "delete missing" option, host/template macros not present in the imported XML file will be deleted too
manual:introduction:whatsnew240 [2018/12/13 06:31] (current)
martins-v fixing erroneous description
Line 17: Line 17:
 For the remaining node-based DM users, during an upgrade to Zabbix 2.4.0, each upgraded node will be switched to a standalone Zabbix server keeping all configuration and history information from the local node and from the child nodes as well. For the remaining node-based DM users, during an upgrade to Zabbix 2.4.0, each upgraded node will be switched to a standalone Zabbix server keeping all configuration and history information from the local node and from the child nodes as well.
  
-To maintain uniqueness of data from non-local nodes, all the fields will be prefixes ​with N<​nodeid>​_. If the length of the new value exceeds max field size, it will be trimmed. Highly unlikely, but if the new value already exists in the database, the situation will be caught by a check on duplicates. Global macros will be processed in a special way by adding N<​nodeid>​_ after the dollar sign, for example, {$N123_MACRO}.+To maintain uniqueness of data from non-local nodes, all the fields will be prefixed ​with N<​nodeid>​_. If the length of the new value exceeds max field size, it will be trimmed. Highly unlikely, but if the new value already exists in the database, the situation will be caught by a check on duplicates. Global macros will be processed in a special way by adding N<​nodeid>​_ after the dollar sign, for example, {$N123_MACRO}.
  
 ==== - Ad-hoc graphs for several items ==== ==== - Ad-hoc graphs for several items ====
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//​. ​This section has gained a larger filter offering ​the possibility to filter the exact set of items you want, and the items now also have checkboxes in the listing.+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.
  
 {{group_graphs.png|}} {{group_graphs.png|}}
Line 69: Line 71:
  
 Note that the old operators are no longer supported, so the new ones have to be used instead. Note also that the new **and**, **or**, **not** operators are case-sensitive and must be surrounded by spaces or parentheses. For more details, refer to the [[manual:​config:​triggers:​expression#​operators|trigger operator]] section. Note that the old operators are no longer supported, so the new ones have to be used instead. Note also that the new **and**, **or**, **not** operators are case-sensitive and must be surrounded by spaces or parentheses. For more details, refer to the [[manual:​config:​triggers:​expression#​operators|trigger operator]] section.
 +
 +In a related development,​ the support for newlines and tabs in trigger expressions has been added.
  
 ==== - Web monitoring improvements ==== ==== - Web monitoring improvements ====
Line 139: Line 143:
 For example, you would export a template, then update it by removing some items and triggers from it. However, when importing the same template back, the removed items and triggers would again be there since they are still on the original template. For this situation, Zabbix 2.4 offers a new //Delete missing// option for deleting resources that are not in the imported XML file. This option is implemented for host and template import. For example, you would export a template, then update it by removing some items and triggers from it. However, when importing the same template back, the removed items and triggers would again be there since they are still on the original template. For this situation, Zabbix 2.4 offers a new //Delete missing// option for deleting resources that are not in the imported XML file. This option is implemented for host and template import.
  
-Note that host/​template macros, if not present in the imported XML file will be deleted too.+Note that the host/​template macros not present in the imported XML file will be deleted too.
  
 Additionally,​ the //Add missing// option has been renamed to //Create new//, to avoid confusion with the new option. Additionally,​ the //Add missing// option has been renamed to //Create new//, to avoid confusion with the new option.
Line 237: Line 241:
 Maintenance periods can now be sorted by two new columns added to the list - //Active since// and //Active till//: Maintenance periods can now be sorted by two new columns added to the list - //Active since// and //Active till//:
  
-{{maintenance_periods_new.png?600|}}+{{maintenance_periods_new.png|}}
  
 === - Host menu changes === === - Host menu changes ===
Line 318: Line 322:
   * 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
   * 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//.
Line 328: Line 333:
   * 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.
 ==== - Macro improvements ==== ==== - Macro improvements ====
  
Line 380: 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 **