manual:introduction:whatsnew440

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:whatsnew440 [2020/02/04 08:51]
marinagen
manual:introduction:whatsnew440 [2021/11/13 16:59] (current)
Line 70: Line 70:
 It is now possible to configure ways of displaying operational data for current problems, i.e. the latest item values as opposed to the item values at the time of the problem. It is now possible to configure ways of displaying operational data for current problems, i.e. the latest item values as opposed to the item values at the time of the problem.
  
-Operational data display can be configured in the filter of //​Monitoring// ​-> //​Problems//​ or in the configuration of the respective [[:​manual/​web_interface/​frontend_sections/​monitoring/​dashboard/​widgets#​problems|dashboard widget]], by selecting one of the three options:+Operational data display can be configured in the filter of //​Monitoring// ​→ //​Problems//​ or in the configuration of the respective [[:​manual/​web_interface/​frontend_sections/​monitoring/​dashboard/​widgets#​problems|dashboard widget]], by selecting one of the three options:
  
   * //None// - no operational data is displayed   * //None// - no operational data is displayed
Line 155: Line 155:
 Previously all communications during agent autoregistration were performed unencrypted. In the new version a secure way of autoregistration is possible by configuring PSK-based authentication with encrypted connections. Previously all communications during agent autoregistration were performed unencrypted. In the new version a secure way of autoregistration is possible by configuring PSK-based authentication with encrypted connections.
  
-The level of encryption is configured globally in //​Administration// ​-> //​[[:​manual/​web_interface/​frontend_sections/​administration/​general|General]]//,​ in the new Autoregistration section accessible through the dropdown to the right. It is possible to select no encryption, TLS encryption with PSK authentication or both (so that some hosts may register without encryption while others through encryption):​+The level of encryption is configured globally in //​Administration// ​→ //​[[:​manual/​web_interface/​frontend_sections/​administration/​general|General]]//,​ in the new Autoregistration section accessible through the dropdown to the right. It is possible to select no encryption, TLS encryption with PSK authentication or both (so that some hosts may register without encryption while others through encryption):​
  
 {{:​manual:​introduction:​adm_gen_autoreg.png|}} {{:​manual:​introduction:​adm_gen_autoreg.png|}}
Line 165: Line 165:
 ==== Autoregistration with DNS name ==== ==== Autoregistration with DNS name ====
  
-It is now possible to specify that the host should be autoregistered with the DNS name as the default agent interface. To do that, the DNS name should be specified/​returned as the value of either '​HostInterface'​ or '​HostInterfaceItem'​ configuration parameters. Note that if the value of one of the two parameters changes, the autoregistered host interface is updated. So it is possible to update the default interface to another DNS name or an IP address. For the changes to take effect though, the agent has to be restarted. '​HostInterface'​ or '​HostInterfaceItem'​ configuration parameters are supported since Zabbix 4.4.+It is now possible to specify that the host should be autoregistered with the DNS name as the default agent interface. To do that, the DNS name should be specified/​returned as the value of either '​HostInterface'​ or '​HostInterfaceItem' ​[[:​manual/​appendix/​config/​zabbix_agentd|configuration parameters]]. Note that if the value of one of the two parameters changes, the autoregistered host interface is updated. So it is possible to update the default interface to another DNS name or an IP address. For the changes to take effect though, the agent has to be restarted. '​HostInterface'​ or '​HostInterfaceItem'​ configuration parameters are supported since Zabbix 4.4.
  
 ==== Longer host names allowed in discovery ==== ==== Longer host names allowed in discovery ====
Line 256: Line 256:
 You can get these templates: You can get these templates:
  
-  * In //​Configuration// ​-> //​Templates//​ in new installations;​ +  * In //​Configuration// ​→ //​Templates//​ in new installations;​ 
-  * If you are upgrading from previous versions, you can download the latest templates from the [[https://​git.zabbix.com/​projects/​ZBX/​repos/​zabbix/​browse/​templates?​at=refs%2Fheads%2Frelease%2F4.4|Zabbix Git repository]]. Then, while in //​Configuration// ​-> //​Templates//​ you can import them manually into Zabbix. If templates with the same names already exist, the //Delete missing// options should be checked when importing to achieve a clean import. This way the old items that are no longer in the updated template will be removed (note that it will mean losing history of these old items).+  * If you are upgrading from previous versions, you can download the latest templates from the [[https://​git.zabbix.com/​projects/​ZBX/​repos/​zabbix/​browse/​templates?​at=refs%2Fheads%2Frelease%2F4.4|Zabbix Git repository]]. Then, while in //​Configuration// ​→ //​Templates//​ you can import them manually into Zabbix. If templates with the same names already exist, the //Delete missing// options should be checked when importing to achieve a clean import. This way the old items that are no longer in the updated template will be removed (note that it will mean losing history of these old items).
  
 ==== Internal knowledge base ==== ==== Internal knowledge base ====
Line 454: Line 454:
   * Host, template and trigger mass update forms (tags)   * Host, template and trigger mass update forms (tags)
   * Low-level discovery rule configuration form (LLD macros)   * Low-level discovery rule configuration form (LLD macros)
-  * //​Administration// ​-> //​General// ​-> //Macros//+  * //​Administration// ​→ //​General// ​→ //Macros//
   * Item, item prototype and LLD rule configuration forms (test item preprocessing)   * Item, item prototype and LLD rule configuration forms (test item preprocessing)
  
Line 461: Line 461:
 Proxy information has been split into a separate column in several places in the frontend: Proxy information has been split into a separate column in several places in the frontend:
  
-  * the host list in //​Configuration// ​-> //Hosts// +  * the host list in //​Configuration// ​→ //Hosts// 
-  * the discovery rule list in //​Configuration// ​-> //​Discovery//​ +  * the discovery rule list in //​Configuration// ​→ //​Discovery//​ 
-  * //​Administration// ​-> //Queue// (with //Details// selected in the dropdown)+  * //​Administration// ​→ //Queue// (with //Details// selected in the dropdown)
  
 So, for example, if previously host names of the hosts monitored by a proxy were prefixed with the proxy name, now the proxy name is listed in a separate column. So, for example, if previously host names of the hosts monitored by a proxy were prefixed with the proxy name, now the proxy name is listed in a separate column.