Zabbix Documentation 2.4

3.04.05.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.24.4Guidelines

User Tools

Site Tools


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 [2015/01/27 13:02]
martins-v mentioning explicitly the removal of host/host group selection dropdowns
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 71: 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 384: 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 **