Zabbix Documentation 3.4

3.04.04.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:introduction:whatsnew340

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:whatsnew340 [2017/08/22 08:24]
martins-v {EVENT.VALUE} and {EVENT.STATUS} changes
manual:introduction:whatsnew340 [2019/02/12 06:42] (current)
martins-v linking to template changes
Line 1: Line 1:
 ===== 5 What's new in Zabbix 3.4.0 ===== ===== 5 What's new in Zabbix 3.4.0 =====
- 
-<note warning>​Zabbix 3.4.0 is not released yet.</​note>​ 
  
 ==== - New dashboards ==== ==== - New dashboards ====
Line 18: Line 16:
  
 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 51: Line 51:
 Note that executing remote commands through proxies is disabled by default. In secure environments (encryption,​ SSH tunneling, etc), remote commands on a proxy can be enabled by setting the EnableRemoteCommands [[:​manual/​appendix/​config/​zabbix_proxy|parameter]] to '​1'​. IPMI, SSH and Telnet scripts are executed even if remote commands are disabled. Note that executing remote commands through proxies is disabled by default. In secure environments (encryption,​ SSH tunneling, etc), remote commands on a proxy can be enabled by setting the EnableRemoteCommands [[:​manual/​appendix/​config/​zabbix_proxy|parameter]] to '​1'​. IPMI, SSH and Telnet scripts are executed even if remote commands are disabled.
  
-==== - Dependent ​items ====+==== - Bulk metrics and dependent ​items ====
  
-There are situations when one item gathers multiple metrics at a time or it makes more sense to collect related metrics simultaneously,​ for example:+There are situations when one item gathers multiple metrics at a time or it even makes more sense to collect related metrics simultaneously,​ for example:
  
   * CPU utilization of individual cores   * CPU utilization of individual cores
   * Incoming/​outgoing/​total network traffic   * Incoming/​outgoing/​total network traffic
  
-To allow for this, Zabbix ​now supports dependent items. Dependent items have a master item, which collects all metrics in one query. Dependent items use the master item data to collect their data. A new value for the master item automatically populates the values of the dependent items.+To allow for bulk metric collection and simultaneous use in several related items, Zabbix supports dependent items. Dependent items use the master item to collect their data simultaneously,​ in one query. A new value for the master item automatically populates the values of the dependent items
 + 
 +Zabbix preprocessing options can be used to extract the part that is needed for the dependent item from the master item data.
  
 See also: [[:​manual/​config/​items/​itemtypes/​dependent_items|Dependent items]] See also: [[:​manual/​config/​items/​itemtypes/​dependent_items|Dependent items]]
Line 88: Line 90:
 Remote commands can also be executed upon problem acknowledgement. Remote commands can also be executed upon problem acknowledgement.
  
-See also: [[:​manual/​config/​notifications/​action/​acknowledgement_operations|Acknowledgement operations]]+See also:  
 + 
 +  * [[:​manual/​config/​notifications/​action/​acknowledgement_operations|Acknowledgement operations]] 
 +  * [[:​manual/​introduction/​whatsnew342#​acknowledgement_message_recipient_option|What'​s new in 3.4.2]]
  
 === - Improved default messages === === - Improved default messages ===
Line 96: Line 101:
 {{:​manual:​introduction:​new_default_message.png|}} {{:​manual:​introduction:​new_default_message.png|}}
  
-  * {TRIGGER.STATUS} macro has been removed, because it no longer can be relied upon if event correlation is used - a problem may be resolved with correlation,​ while the trigger may still show a problem+  * {TRIGGER.STATUS} macro has been removed, because it no longer can be relied upon if event correlation is used - a problem may be resolved with correlation,​ while the trigger may still show a problem ​([[:​manual/​installation/​upgrade_notes_340#​macro_changes|changed]] {EVENT.VALUE} and {EVENT.STATUS} macros can be used instead)
   * Host is indicated using the {HOST.NAME} macro   * Host is indicated using the {HOST.NAME} macro
   * Problem notifications have been made more distinct from recovery notifications in the message subject   * Problem notifications have been made more distinct from recovery notifications in the message subject
Line 108: Line 113:
 {{:​manual:​introduction:​item_preprocessing.png|}} {{:​manual:​introduction:​item_preprocessing.png|}}
  
-=== New preprocessing options ===+=== New preprocessing options ===
  
 Several new options for value preprocessing have been added: Several new options for value preprocessing have been added:
Line 142: Line 147:
 Previously variable values in web monitoring were passed to the scenario steps unchanged. Any URL-encoding of the values could only be accomplished manually. ​ Previously variable values in web monitoring were passed to the scenario steps unchanged. Any URL-encoding of the values could only be accomplished manually. ​
  
-=== Automatic URL-encoding ===+=== Automatic URL-encoding ===
  
 GET and POST variable values entered in web scenario steps are now automatically URL-encoded. Encoding is applied no matter what type of data is used (text, macro, scenario-level variable or any combination of those). Encoding is performed before executing the step (data is saved unencoded in the database). GET and POST variable values entered in web scenario steps are now automatically URL-encoded. Encoding is applied no matter what type of data is used (text, macro, scenario-level variable or any combination of those). Encoding is performed before executing the step (data is saved unencoded in the database).
  
-=== Flexible URL-encoding for variables ===+=== Flexible URL-encoding for variables ===
  
 Values of scenario or step-level variables (macros) can be flexibly URL-encoded/​decoded,​ depending on the chosen post variable settings in web scenario steps. For example: Values of scenario or step-level variables (macros) can be flexibly URL-encoded/​decoded,​ depending on the chosen post variable settings in web scenario steps. For example:
Line 154: Line 159:
 |In 3.4      |{user}\\ {user}\\ {{user}.urlencode()}\\ {{user}.urldecode()} ​ |Variable value is automatically URL-encoded in //Form mode// for post variables.\\ Variable value is passed as is in //Raw mode// for post variables.\\ Variable value is manually URL-encoded in //Raw mode// for post variables.\\ Variable value is manually URL-decoded in //Raw mode// for post variables. ​ | |In 3.4      |{user}\\ {user}\\ {{user}.urlencode()}\\ {{user}.urldecode()} ​ |Variable value is automatically URL-encoded in //Form mode// for post variables.\\ Variable value is passed as is in //Raw mode// for post variables.\\ Variable value is manually URL-encoded in //Raw mode// for post variables.\\ Variable value is manually URL-decoded in //Raw mode// for post variables. ​ |
  
-=== Unicode support in domain names ===+=== Unicode support in domain names ===
  
 Specifying domain names in Unicode characters is now supported in web scenario steps. Unicode characters are automatically punycode-converted to ASCII when executing a web scenario step. Specifying domain names in Unicode characters is now supported in web scenario steps. Unicode characters are automatically punycode-converted to ASCII when executing a web scenario step.
Line 172: Line 177:
   * Ability to add shapes and lines    * Ability to add shapes and lines 
  
-=== Permission changes ===+=== Permission changes ===
  
 Maps are no longer hidden if the user does not have read permission to all map elements. Instead, the map is shown, providing the user has read access to at least one element. The elements that the user does not have read permission to are displayed with a grey icon and without any textual information on it (except for triggers which do have labels). Maps are no longer hidden if the user does not have read permission to all map elements. Instead, the map is shown, providing the user has read access to at least one element. The elements that the user does not have read permission to are displayed with a grey icon and without any textual information on it (except for triggers which do have labels).
Line 180: Line 185:
 See also: [[:​manual/​config/​visualisation/​maps/​map#​access_based_on_permissions|Network map configuration]] See also: [[:​manual/​config/​visualisation/​maps/​map#​access_based_on_permissions|Network map configuration]]
  
-=== Multiple trigger support ===+=== Multiple trigger support ===
  
 When creating a trigger-type map element, it is now possible to select multiple triggers for this element instead of one as before. When creating a trigger-type map element, it is now possible to select multiple triggers for this element instead of one as before.
Line 192: Line 197:
 See also: [[:​manual/​config/​visualisation/​maps/​map#​creating_a_map|Network map configuration]] See also: [[:​manual/​config/​visualisation/​maps/​map#​creating_a_map|Network map configuration]]
  
-=== Moving elements ===+=== Moving elements ===
  
 Drag-and-drop support has been introduced to map elements. Several selected elements can be moved to another place in the map by clicking on one of the selected elements, holding down the mouse button and moving the cursor to the desired location. Drag-and-drop support has been introduced to map elements. Several selected elements can be moved to another place in the map by clicking on one of the selected elements, holding down the mouse button and moving the cursor to the desired location.
  
-=== Copying and pasting elements ===+=== Copying and pasting elements ===
  
 Map elements, when selected, can now be [[:​manual/​config/​visualisation/​maps/​map#​copying_and_pasting_elements|copied and pasted]] within the same map: Map elements, when selected, can now be [[:​manual/​config/​visualisation/​maps/​map#​copying_and_pasting_elements|copied and pasted]] within the same map:
Line 204: Line 209:
 Several selected elements can now also be dragged and dropped in another place all together. Several selected elements can now also be dragged and dropped in another place all together.
  
-=== Adding shapes and lines ===+=== Adding shapes and lines ===
  
 Rectangle and ellipse shapes can now be [[:​manual/​config/​visualisation/​maps/​map#​adding_shapes|added]] in network maps. These shapes are a visual representation. For example, a rectangle shape can be used as a background to group some hosts. Shapes are not map elements and cannot be linked. Text can be added in the shapes. Rectangle and ellipse shapes can now be [[:​manual/​config/​visualisation/​maps/​map#​adding_shapes|added]] in network maps. These shapes are a visual representation. For example, a rectangle shape can be used as a background to group some hosts. Shapes are not map elements and cannot be linked. Text can be added in the shapes.
Line 213: Line 218:
  
 {{:​manual:​introduction:​map_line_new.png}} {{:​manual:​introduction:​map_line_new.png}}
 +
 ==== - Support of macros and time suffixes in time periods ==== ==== - Support of macros and time suffixes in time periods ====
  
Line 272: 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 ​or 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.
 +  * To allow internal checks to be processed prior to other items, internal check items are now enqueued at the beginning of the preprocessing queue. ​
  
 === - IPMI polling === === - IPMI polling ===
Line 281: Line 288:
  
 Since Zabbix 3.4, a new IPMI manager process has been added to schedule IPMI checks by IPMI pollers. Now a host is always polled by the same IPMI poller, reducing the number of open connections to BMC controllers. With those changes it's safe to increase the number of IPMI pollers without worrying about BMC controller overloading. The IPMI manager process is automatically started when at least one IPMI poller is started. Since Zabbix 3.4, a new IPMI manager process has been added to schedule IPMI checks by IPMI pollers. Now a host is always polled by the same IPMI poller, reducing the number of open connections to BMC controllers. With those changes it's safe to increase the number of IPMI pollers without worrying about BMC controller overloading. The IPMI manager process is automatically started when at least one IPMI poller is started.
 +
 +=== - Preprocessing manager ===
 +
 +A new ''​preprocessing manager''​ process has been added along with workers that perform the preprocessing steps. All values (with or without preprocessing) from different data gatherers pass through the preprocessing manager before being added to the history cache. Socket-based IPC communication is introduced between data gatherers (pollers, trappers, etc) and the preprocessing process.
  
 === - Configuration parameters === === - Configuration parameters ===
Line 287: Line 298:
  
 A ''​SocketDir''​ configuration parameter has been added to Zabbix server and proxy configurations. This parameter points to the directory where internal Zabbix socket files are stored (/tmp by default). Server and proxy uses different socket file names so it's safe to use the same '​SocketDir'​ for server and proxy running on the same system. However, running multiple servers or proxies in the same system will require different '​SocketDir'​ configurations. A ''​SocketDir''​ configuration parameter has been added to Zabbix server and proxy configurations. This parameter points to the directory where internal Zabbix socket files are stored (/tmp by default). Server and proxy uses different socket file names so it's safe to use the same '​SocketDir'​ for server and proxy running on the same system. However, running multiple servers or proxies in the same system will require different '​SocketDir'​ configurations.
 +
 +A ''​StartPreprocessors''​ configuration parameter has been added to Zabbix server configuration. As a preprocessing manager process is introduced in this version, the '​StartPreprocessors'​ parameter determines how many item value preprocessing workers are started by Zabbix server.
  
 ''​EnableRemoteCommands''​ and ''​LogRemoteCommands''​ parameters have been added to the proxy configuration file, as remote commands are now supported through proxies as well. Both are disabled by default. ''​EnableRemoteCommands''​ and ''​LogRemoteCommands''​ parameters have been added to the proxy configuration file, as remote commands are now supported through proxies as well. Both are disabled by default.
Line 305: Line 318:
  
 A new **zabbix[host,​discovery,​interfaces]** internal [[:​manual/​config/​items/​itemtypes/​internal|item]] has been added to return all host interfaces configured in Zabbix frontend. This item can be used in [[:​manual/​discovery/​low_level_discovery/​host_interfaces|low-level discovery]]. A new **zabbix[host,​discovery,​interfaces]** internal [[:​manual/​config/​items/​itemtypes/​internal|item]] has been added to return all host interfaces configured in Zabbix frontend. This item can be used in [[:​manual/​discovery/​low_level_discovery/​host_interfaces|low-level discovery]].
 +
 +A new **zabbix[preprocessing_queue]** internal [[:​manual/​config/​items/​itemtypes/​internal|item]] has been added to count the values enqueued in the preprocessing queue.
  
 ==== - Macro changes ==== ==== - Macro changes ====
Line 323: Line 338:
  
 {{:​manual:​introduction:​frontend_return_code_error.png|}} {{:​manual:​introduction:​frontend_return_code_error.png|}}
 +
 +==== See also ====
 +
 +  * [[:​manual/​installation/​template_changes|Template changes]]