Zabbix Documentation 4.2

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:whatsnew420

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
Last revision Both sides next revision
manual:introduction:whatsnew420 [2019/03/27 13:46]
martins-v linking to lld config
manual:introduction:whatsnew420 [2019/04/03 12:28]
martins-v some rewording
Line 1: Line 1:
 ===== 5 What's new in Zabbix 4.2.0 ===== ===== 5 What's new in Zabbix 4.2.0 =====
- 
-<note important>​Zabbix 4.2.0 is not released yet.</​note>​ 
  
 This section introduces new and updated features of Zabbix 4.2. This section introduces new and updated features of Zabbix 4.2.
Line 146: Line 144:
   * Check for error in JSON (validation)   * Check for error in JSON (validation)
   * Discard unchanged with heartbeat (throttling)   * Discard unchanged with heartbeat (throttling)
 +  * Prometheus to JSON
  
 {{:​manual:​introduction:​lld_rule_preprocessing.png|}} {{:​manual:​introduction:​lld_rule_preprocessing.png|}}
Line 160: Line 159:
  
 For more details, see: [[:​manual/​discovery/​low_level_discovery#​custom_macros|Custom macros]] in low-level discovery rules. For more details, see: [[:​manual/​discovery/​low_level_discovery#​custom_macros|Custom macros]] in low-level discovery rules.
 +
 +==== Prometheus integration ====
 +
 +Prometheus integration offers the ability to monitor any object that exposes metrics in Prometheus line format, including Kubernetes, Docker, ​ GitLab, Ceph, Collectd, etcd, InfluxDB, InfluxDB Telegraf and others.
 +
 +Zabbix uses HTTP items to access Prometheus metrics and then uses preprocessing to query the metrics for specific values.
 +
 +See [[:​manual/​config/​items/​itemtypes/​prometheus|Prometheus checks]].
  
 ==== TimescaleDB support ==== ==== TimescaleDB support ====
Line 195: Line 202:
  
 See more on [[:​manual/​config/​event_correlation/​trigger/​event_tags|tags]]. See more on [[:​manual/​config/​event_correlation/​trigger/​event_tags|tags]].
-==== Remote monitoring of Zabbix stats ==== 
  
-It is now possible to make some internal metrics of Zabbix server and proxy accessible remotely by another Zabbix instance or a third party tool. This can be useful so that supporters/​service providers can monitor their client Zabbix servers/​proxies remotely or, in organizations where Zabbix is not the main monitoring tool, that Zabbix internal metrics can be monitored by a third party system in an umbrella-monitoring setup. ​ 
  
-Zabbix internal stats are exposed to a configurable set of addresses listed in the new '​StatsAllowedIP'​ [[:​manual/​appendix/​config/​zabbix_server|server]]/​[[:​manual/​appendix/​config/​zabbix_proxy|proxy]] parameter. Requests will be accepted only from these addresses. 
- 
-To configure querying of internal stats on another Zabbix instance, you may use two new items: 
- 
-  * ''​zabbix[stats,<​ip>,<​port>​]''​ internal item - for direct remote queries of Zabbix server/​proxy. <ip> and <​port>​ are used to identify the target instance. 
-  * ''​zabbix.stats[<​ip>,<​port>​]''​ agent item - for agent-based remote queries of Zabbix server/​proxy. <ip> and <​port>​ are used to identify the target instance. 
- 
-To make sure that the target instance allows querying it by the external instance, list the address of the external instance in the '​StatsAllowedIP'​ parameter on the target instance. ​ 
- 
-These items gather statistics in bulk and return a JSON which can be used as the master item for dependent items that get their data from. A selected set of internal metrics (i.e. not all) is returned by either of these two items. ​ 
- 
-There are also another two new items allowing to specifically remotely query internal queue stats: 
- 
-  * ''​zabbix[stats,<​ip>,<​port>,​queue,<​from>,<​to>​]''​ internal item - for direct internal queue queries to remote Zabbix server/​proxy 
-  * ''​zabbix.stats[<​ip>,<​port>,​queue,<​from>,<​to>​]''​ agent item - for agent-based internal queue queries to remote Zabbix server/​proxy 
- 
-For more details, see:  
-  * [[:​manual/​appendix/​items/​remote_stats|Remote monitoring of Zabbix stats]] 
-  * [[:​manual/​config/​items/​itemtypes/​internal|Internal items]] 
-  * [[:​manual/​config/​items/​itemtypes/​zabbix_agent|Zabbix agent items]] 
- 
-== New templates == 
-New templates are also available for remote Zabbix server or proxy internal metric monitoring: 
- 
-  * Template App Remote Zabbix server 
-  * Template App Remote Zabbix proxy 
- 
-Note that in order to use a template for remote monitoring of multiple external instances, a separate host is required for each external instance monitoring. 
  
 ==== More intuitive dashboard editing ==== ==== More intuitive dashboard editing ====
Line 248: Line 225:
  
 HTML format can be selected in the //Message format// option when configuring email as the media type in //​Administration//​ -> //Media types//. HTML format can be selected in the //Message format// option when configuring email as the media type in //​Administration//​ -> //Media types//.
 +
 +==== Testing media types ====
 +
 +It is now possible to test if a configured media type works. To do that in the media type list, click on //Test// in the last column.
 +
 +{{:​manual:​introduction:​media_type_test.png|}}
 +
 +A testing window will open where you can enter a //Send to// recipient address and send a test message subject and body by clicking on //​Test//​. ​
 +
 +{{:​manual:​introduction:​media_type_test2.png?​600|}}
 +
 +Test success or failure message will be displayed in the same window.
  
 ==== Regular expression-based matching in auto-registration conditions ==== ==== Regular expression-based matching in auto-registration conditions ====
Line 333: Line 322:
  
 See also: [[:​manual/​appendix/​config/​zabbix_server|StartLLDProcessors]] parameter See also: [[:​manual/​appendix/​config/​zabbix_server|StartLLDProcessors]] parameter
 +
 +=== Sender uses all ServerActive addresses ===
 +
 +Zabbix sender now uses all addresses defined in the agent ServerActive configuration parameter for sending data, instead of the first entry only. If sending to one address fails, the sender tries sending to the other addresses. If sending of batch data fails to one address, other batches are not sent to this address. ​
  
 ==== See also ==== ==== See also ====
  
   * [[:​manual/​installation/​template_changes|Template changes]]   * [[:​manual/​installation/​template_changes|Template changes]]