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/25 12:15]
martins-v adding info about the preprocessing manager process
manual:introduction:whatsnew340 [2019/02/12 06:42] (current)
martins-v linking to template changes
Line 16: 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 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 273: 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 285: Line 291:
 === - Preprocessing manager === === - 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.+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 292: 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 330: Line 338:
  
 {{:​manual:​introduction:​frontend_return_code_error.png|}} {{:​manual:​introduction:​frontend_return_code_error.png|}}
 +
 +==== See also ====
 +
 +  * [[:​manual/​installation/​template_changes|Template changes]]