Zabbix Documentation 4.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: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 [2019/10/31 11:04]
martins-v csv to json preprocessing
manual:introduction:whatsnew440 [2020/05/13 12:02] (current)
martins-v adding internal link
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 177: Line 177:
 It is now possible to convert CSV file data into JSON format. It is now possible to convert CSV file data into JSON format.
  
-{{:​manual:​introduction:​csv_to_json.png?600|}} +{{:​manual:​introduction:​csv_to_json0.png|}}
- +
-This option is available for [[:​manual/​config/​items/​item#​item_value_preprocessing|items]],​ item prototypes and [[:​manual/​discovery/​low_level_discovery#​discovery_rule|low-level discovery rules]].+
  
 +See also: [[:​manual/​appendix/​preprocessing/​csv_to_json|CSV to JSON preprocessing]]
 === Custom error handling === === Custom error handling ===
  
Line 194: Line 193:
 === More options for LLD rule preprocessing === === More options for LLD rule preprocessing ===
  
-New preprocessing options have been added to [[:​manual/​discovery/​low_level_discovery#​preprocessing|low-level discovery rules]]:+More preprocessing options have been added to [[:​manual/​discovery/​low_level_discovery#​preprocessing|low-level discovery rules]]:
  
   * XML Xpath   * XML Xpath
-  * CSV to JSON+  * CSV to JSON (new in 4.4)
   * Check for error in XML   * Check for error in XML
  
Line 203: Line 202:
  
 Host names are now included in the [[:​manual/​appendix/​install/​real_time_export|real-time export]] of events, item values and trends (previously only the visible host name was exported). Note that the [[:​manual/​appendix/​protocols/​real_time_export|export protocol]] has changed with host name information now an object, rather than a string/​array. Host names are now included in the [[:​manual/​appendix/​install/​real_time_export|real-time export]] of events, item values and trends (previously only the visible host name was exported). Note that the [[:​manual/​appendix/​protocols/​real_time_export|export protocol]] has changed with host name information now an object, rather than a string/​array.
 +
 +==== Value types included in real-time export ====
 +
 +Value types are now included in the [[:​manual/​appendix/​install/​real_time_export|real-time export]] of item values and trends. See the [[:​manual/​appendix/​protocols/​real_time_export|export protocol]] for more details.
  
 ==== New templates ==== ==== New templates ====
Line 244: Line 247:
 === MySQL/​MariaDB === === MySQL/​MariaDB ===
  
-  * //Template DB MySQL// - see [[:​manual/​config/​templates_out_of_the_box/​requirements/​mysql#​steps|requirements for operating]] this template.+  * //Template DB MySQL by Zabbix agent// - see [[:​manual/​config/​templates_out_of_the_box/​requirements/​mysql#​steps|requirements for operating]] this template. 
  
 === PostgreSQL === === PostgreSQL ===
Line 253: Line 257:
  
   * In //​Configuration//​ -> //​Templates//​ in new installations;​   * In //​Configuration//​ -> //​Templates//​ in new installations;​
-  * If you are upgrading from previous versions, you can download ​these templates from Zabbix ​[[https://​git.zabbix.com/​projects/​ZBX/​repos/​zabbix/​browse/​templates|Git repository]] ​or find them in the ''​templates''​ directory of the downloaded latest Zabbix version. 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 285: Line 289:
 === Media type export === === Media type export ===
  
-Media types now can be [[:​manual/​xml_export_import/​media|exported]] and imported ​for easier sharing.+For easier sharing of media types, including the new webhooks, media types can now be [[:​manual/​xml_export_import/​media|exported]] and imported.
  
 The export files support the new human-readable format (see below) implemented for host/​template export. The export files support the new human-readable format (see below) implemented for host/​template export.
Line 420: Line 424:
  
 {{:​manual:​introduction:​graph_prototype_new.png?​600|}} {{:​manual:​introduction:​graph_prototype_new.png?​600|}}
 +
 +=== Cannot support audio notification notice ===
 +
 +“Cannot support notification audio for this device.” message will be displayed when [[:​manual/​web_interface/​user_profile/​sound|notification sounds]] on the device cannot be played. ​
  
 === Monospaced fonts in trigger expression/​command fields === === Monospaced fonts in trigger expression/​command fields ===