manual:introduction:whatsnew300

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:whatsnew300 [2016/02/10 11:28]
martins-v changed order of entries according to higher significance
manual:introduction:whatsnew300 [2019/02/12 06:41] (current)
martins-v linking to template changes
Line 1: Line 1:
 ===== -#5 What's new in Zabbix 3.0.0 ===== ===== -#5 What's new in Zabbix 3.0.0 =====
- 
-<note warning>​Zabbix 3.0.0 is not released yet.</​note>​ 
  
 ==== - New web interface ==== ==== - New web interface ====
Line 232: Line 230:
  
 {{:​manual:​introduction:​dashboard_filter_by_trigger.png|}} {{:​manual:​introduction:​dashboard_filter_by_trigger.png|}}
 +
 +**Maps, screens, slide shows**
 +
 +Map, screen and slide show listings can now be filtered by name.
 +
 +{{:​manual:​introduction:​maps_filter.png?​600|}}
  
 **Triggers top 100** **Triggers top 100**
Line 247: Line 251:
 |Previous\\ version: ​ |{{:​manual:​introduction:​options_in_dropdown.png|}} ​ | |Previous\\ version: ​ |{{:​manual:​introduction:​options_in_dropdown.png|}} ​ |
 |Zabbix 3.0:  |{{:​manual:​introduction:​mass_update_buttons.png|}} ​ | |Zabbix 3.0:  |{{:​manual:​introduction:​mass_update_buttons.png|}} ​ |
 +
 +=== - Zeroes not displayed ===
 +
 +Zeroes are not displayed any more in lists for entities with no items. Whereas previously a (0) would be displayed next to the entity in a table column, now nothing is displayed.
 +
 +|Previous\\ version: ​ | {{:​manual:​introduction:​with_zeroes.png|}} |
 +|Zabbix 3.0:  | {{:​manual:​introduction:​without_zeroes.png|}} |
  
 === - User agent options in web monitoring === === - User agent options in web monitoring ===
Line 277: Line 288:
  
 It is now possible to import/​export the Clock screen element with a "Host time" option. It is now possible to import/​export the Clock screen element with a "Host time" option.
 +
 +=== - Value mapping improvements ===
 +
 +Value mapping setting "Host status"​ in //​Administration → General → Value mapping// has been updated and renamed to "Host availability"​. This value now supports 3 host states by default:
 +  *0 ⇒ not available
 +  *1 ⇒ available
 +  *2 ⇒ unknown
 +
 +and matches the value of [[manual/​config/​items/​itemtypes/​internal|internal check]] item ''​zabbix[host,<​type>,​available]''​. ​
 +
 === - Miscellaneous improvements === === - Miscellaneous improvements ===
  
Line 284: Line 305:
   * Spaces, tabulation and multiple lines can now be used in IP ranges in network discovery and action conditions (e.g., "​192.168.0.0/​24,​ 192.168.1.0/​24"​).   * Spaces, tabulation and multiple lines can now be used in IP ranges in network discovery and action conditions (e.g., "​192.168.0.0/​24,​ 192.168.1.0/​24"​).
   * The Dashboard //Last 20 issues// widget as well as "Host issues"​ and "Host group issues"​ screen elements now display all hosts from trigger expression.   * The Dashboard //Last 20 issues// widget as well as "Host issues"​ and "Host group issues"​ screen elements now display all hosts from trigger expression.
 +  * A table header has been added to the [[:​manual/​web_interface/​user_profile#​configuration|user media]] listing. Entries from the list can be deleted using the //Remove// link, rather than having to mark check-boxes and then click on //Delete selected//. Check-boxes have been removed.
 ==== - Daemon improvements ==== ==== - Daemon improvements ====
  
Line 292: Line 314:
 The automatic housekeeping procedures can now be disabled by setting the configuration file HousekeepingFrequency parameter to zero. The automatic housekeeping procedures can now be disabled by setting the configuration file HousekeepingFrequency parameter to zero.
  
-=== - Default configuration file improvements ​===+=== - Configuration parameters ​===
  
-Default configuration files have been changed to improve security and usability.+Default configuration ​[[:​manual/​appendix/​config|files]] have been changed to improve security and usability.
  
   * //DBUser// has been changed to **zabbix** for proxy and server   * //DBUser// has been changed to **zabbix** for proxy and server
Line 300: Line 322:
   * //​LogSlowQueries//​ has been increased from 0 to 3000 for proxy and server   * //​LogSlowQueries//​ has been increased from 0 to 3000 for proxy and server
   * //Timeout// has been increased from 3 to 4 seconds for proxy and server   * //Timeout// has been increased from 3 to 4 seconds for proxy and server
-  * Prohibited characters have been listed for //​UnsafeUserParamaters//​ 
   * Default value for //​MaxLinesPerSecond//​ has been decreased from 100 to 20 for agent   * Default value for //​MaxLinesPerSecond//​ has been decreased from 100 to 20 for agent
 +  * Prohibited characters have been listed for //​UnsafeUserParamaters//​
 +  * It is possible to disable automatic housekeeping by setting HousekeepingFrequency to 0
 +  * It is possible now to set //​DebugLevel//​=5 in server, proxy and agent configuration files. Previously it could be done using runtime control options only.
 +  * A new **LogType** configuration parameter has been added for server, proxy, agent and Windows agent. This parameter accepts the following values:
 +    * //file// (default) - write log messages to file configured by the LogFile parameter
 +    * //system// - write log messages to syslog (Unix-like systems) or eventlog (Windows)
 +    * //console// - write log messages to standard output (valid only when running in foreground mode)
 +    * See also important [[:​manual/​installation/​upgrade_notes_300#​changes_in_configuration_parameters_related_to_logging|upgrade notes]]
 +  * //​HistoryIndexCacheSize//​ parameter has been added for server and proxy
 +  * Several new parameters have been added that are related to [[:​manual/​introduction/​whatsnew300#​encryption_support|encryption]] support
 +
 === - Performance improvements === === - Performance improvements ===
  
Line 308: Line 340:
 The nodata() function calculation has been improved to limit the database requests to the range specified in nodata() function. The nodata() function calculation has been improved to limit the database requests to the range specified in nodata() function.
  
-When an active proxy connects to Zabbix server ​information about this proxy is retrieved ​from server configuration cache (in earlier versions ​it was retrieved ​directly from database). This improves performance and reduces database load. On the other hand, active proxy configuration change ​now has not an instant effect. It has to wait until server configuration cache is synchronized with database (can be enforced from commandline).+When an active proxy connects to Zabbix server, the server identifies ​this proxy using information ​from server configuration cache (in earlier versions directly from database). This improves performance and reduces database load. On the other hand, changing ​active proxy settings via frontend or API now does not have an instant effect. It has to wait until server configuration cache is updated from the database (can be enforced from commandline).
  
 The number of configuration cache locks done by pollers has been reduced. This should give slight performance improvement in peak situations. The number of configuration cache locks done by pollers has been reduced. This should give slight performance improvement in peak situations.
Line 339: Line 371:
 === - Logging IP addresses of incoming/​outgoing connections between Zabbix server and Zabbix proxy === === - Logging IP addresses of incoming/​outgoing connections between Zabbix server and Zabbix proxy ===
  
-The messages printed to the log files will now contain IP addresses of incoming/​outgoing connections between Zabbix server and Zabbix proxy. +The messages printed to the log files will now contain IP addresses of incoming/​outgoing connections between Zabbix server and Zabbix proxy. ​Please see the [[:​manual/​installation/​upgrade_notes_300#​logging_ip_addresses_of_incomingoutgoing_connections_between_zabbix_server_and_zabbix_proxy|upgrade notes]] for details.
- +
-=== - Setting DebugLevel=5 in daemon configuration file ===+
  
-It is possible now to set //​DebugLevel//​=5 in server, proxy and agent configuration files. Previously it could be done using runtime control options only. 
  
 === - Database recovery message on DebugLevel=2 === === - Database recovery message on DebugLevel=2 ===
  
-If database query fails the following message will be printed to log file: ''​database is down: reconnecting in 10 seconds''​. When database goes up ''​database connection re-established''​ will be printed. There were no such messages on //​DebugLevel//​=2 previously.+If database query fails the following message will be printed to the log file: ''​database is down: reconnecting in 10 seconds''​. When the database goes up ''​database connection re-established''​ will be printed. There were no such messages on //​DebugLevel//​=2 previously.
  
 === - Host availability improvements === === - Host availability improvements ===
Line 359: Line 388:
   * host is monitored by a proxy that appears to be offline (no updates received from the proxy during the maximum heartbeat interval - 1 hour),   * host is monitored by a proxy that appears to be offline (no updates received from the proxy during the maximum heartbeat interval - 1 hour),
   * host is disabled.   * host is disabled.
- 
  
 === - Support for multiple escalators === === - Support for multiple escalators ===
Line 375: Line 403:
 === - History cache improvements === === - History cache improvements ===
  
-History cache will better handle processing of large number of values (100 and more values per item) coming from low number of items (100 items or less).+History cache will better handle ​the processing of large number of values (100 and more values per item) coming from low number of items (100 items or less).
  
-The text based values (character, text, log types) are now stored in history cache and the history text cache is removed together with internal items used to monitor it. +Text-based values (character, text, log types) are now stored in history cache and the history text cache has been removed together with internal items used to monitor it. 
  
-History index cache was added to keep index of the history cache. A new ''​zabbix[wcache,​index,<​mode>​]''​ internal check was added to monitor history index cache usage. See [[manual:​config:​items:​itemtypes:​internal|Internal checks]] for details.+History index cache has been added to keep index of the history cache. A new ''​zabbix[wcache,​index,<​mode>​]''​ internal check was added to monitor history index cache usage. See [[manual:​config:​items:​itemtypes:​internal|Internal checks]] for details.
  
 === -  Action and action condition caching === === -  Action and action condition caching ===
Line 444: Line 472:
 Host-level macros such as {HOST.HOST},​ {HOST.NAME},​ {HOST.IP}, {HOST.DNS}, {HOST.CONN} and {HOST.PORT} along with user macros {$MACRO} are now available in the trigger URL. Host-level macros such as {HOST.HOST},​ {HOST.NAME},​ {HOST.IP}, {HOST.DNS}, {HOST.CONN} and {HOST.PORT} along with user macros {$MACRO} are now available in the trigger URL.
  
-==== - Commandline ​utilities ​improvements ====+==== - Commandline ​utility ​improvements ====
  
 ''​zabbix_get''​ exit code now is 0 (success) or 1 (error). In earlier versions it was 0 (success or error - cannot distinguish between them) or 141 (SIGPIPE). ''​zabbix_get''​ exit code now is 0 (success) or 1 (error). In earlier versions it was 0 (success or error - cannot distinguish between them) or 141 (SIGPIPE).
Line 468: Line 496:
  
 A new "HTTP response status code" value map has been added. A new "HTTP response status code" value map has been added.
 +
 +==== See also ====
 +
 +  * [[:​manual/​installation/​template_changes|Template changes]]