success. 有关导出数据的详细信息，请参见导出协议页面。For precise details on what information is exported, see the export protocol page. 请注意，如果在收到数据后，在服务器导出数据之前删除了主机/监控项，主机/监控项可能没有元数据（例如：主机组，主机名，监控项 名称）。Note that host/item can availability, history data, discovery data and auto registration 请求. 1 Server-proxy data exchange protocol Overview Server - proxy data exchange is based on JSON format. Request and response messages 有关详细信息，请参阅被动和主动代理检查页面。 2 Zabbix agent protocol Please refer to Passive and active agent checks page for more information. 3 Zabbix sender 协议 有关详细信息，请参阅Trapper items页面。 3 Zabbix sender protocol Please refer to Trapper

success. 有关导出数据的详细信息，请参见导出协议页面。For precise details on what information is exported, see the export protocol page. 请注意，如果在收到数据后，在服务器导出数据之前删除了主机/监控项，主机/监控项可能没有元数据（例如：主机组，主机名，监控项 名称）。Note that host/item can availability, history data, discovery data and auto registration 请求. 1 Server-proxy data exchange protocol Overview Server - proxy data exchange is based on JSON format. Request and response messages exhaust memory (potentially) Zabbix protocol is limited to accept only 128MB in one connection. Implementation Here are code snippets showing how to add Zabbix protocol header to the data you want to send

success. 有关导出数据的详细信息，请参见导出协议页面。For precise details on what information is exported, see the export protocol page. 请注意，如果在收到数据后，在服务器导出数据之前删除了主机/监控项，主机/监控项可能没有元数据（例如：主机组，主机名，监控项 名称）。Note that host/item can availability, history data, discovery data and auto registration 请求. 1 Server-proxy data exchange protocol Overview Server - proxy data exchange is based on JSON format. Request and response messages message length, if it is compressed or not, if it is a large packet or not. Zabbix communications protocol has 1GB packet size limit per connection. The limit of 1GB is applied to both the received packet

success. 有关导出数据的详细信息，请参见导出协议页面。For precise details on what information is exported, see the export protocol page. 请注意，如果在收到数据后，在服务器导出数据之前删除了主机/监控项，主机/监控项可能没有元数据（例如：主机组，主机名，监控项 名称）。Note that host/item can availability, history data, discovery data and auto registration 请求. 1 Server-proxy data exchange protocol Overview Server - proxy data exchange is based on JSON format. Request and response messages 有关详细信息，请参阅被动和主动代理检查页面。 2 Zabbix agent protocol Please refer to Passive and active agent checks page for more information. 3 Zabbix sender 协议 有关详细信息，请参阅Trapper items页面。 3 Zabbix sender protocol Please refer to Trapper

DBTLSCipher13 - the list of encryption ciphers that the client permits for connections using TLS 1.3 protocol (MySQL) TLS connection is made using a cipher from the provided list. (PostgreSQL) Setting this TO 'zbx_srv'@'%'; mysql> SET DEFAULT ROLE 'zbx_web_role' TO 'zbx_web'@'%'; Note, that the X.509 protocol is not used to check identity, but the user is configured to use only encrypted connections. See ssl_key_file = 'server.key' ssl_ciphers = 'HIGH:MEDIUM:+3DES:!aNULL' ssl_prefer_server_ciphers = on ssl_min_protocol_version = 'TLSv1.3' ... For access control adjust /var/lib/pgsql/13/data/pg_hba.conf: 25 ...

been introduced allowing data polling using the HTTP/HTTPS protocol. Trapping is also possible using Zabbix sender or Zabbix sender protocol. For more details see HTTP agent item type. New templates connectivity environments. For more details on the protocols, see: • Server-proxy data exchange protocol • Active agent checks Data without session token will be accepted without validation for duplicate domain name or IP address was allowed in the first parameter and there was no support for HTTPS protocol. Additionally, Unicode is now supported in the hostnames of these items (Punycode support was added)

domain name or IP address was allowed in the first parameter and there was no support for HTTPS protocol. Additionally, Unicode is now supported in the hostnames of these items (Punycode support was added) the clock, etc), used in the dashboard. Zabbix API - Zabbix API allows you to use the JSON RPC protocol to create, update and fetch Zabbix objects (like hosts, items, graphs and others) or perform any (server, proxy, agent, zabbix_sender and zabbix_get utilities) using Transport Layer Security (TLS) protocol. network discovery - automated discovery of network devices. low-level discovery - automated

ssl_key_file = 'server.key' ssl_ciphers = 'HIGH:MEDIUM:+3DES:!aNULL' ssl_prefer_server_ciphers = on ssl_min_protocol_version = 'TLSv1.3' ... 对于用户访问控制，请调整 /var/lib/pgsql/13/data/pg_hba.conf： ... ### require hostssl "parent_taskid": 20, "hostid": 10084 } ] } 2 Zabbix Agent 协议 有关详细信息，请参阅被动和主动代理检查页面。 3 Zabbix agent 2 protocol Overview This section provides information on: • Agent2 -> Server : active checks request • 003534" } 3 Zabbix sender 协议 有关详细信息，请参阅Trapper items页面。 409 4 Zabbix agent 2 plugin protocol Zabbix agent 2 protocol is based on code, size and data model. Code Type Size Comments Byte 4 Payload type

item values and trends (previously only the visible host name was exported). Note that the export protocol has changed with host name information now an object, rather than a string/array. Value types Value types are now included in the real-time export of item values and trends. See the export protocol for more details. New templates New official templates are available for monitoring: Linux The the clock, etc), used in the dashboard. Zabbix API - Zabbix API allows you to use the JSON RPC protocol to create, update and fetch Zabbix objects (like hosts, items, graphs and others) or perform any

0.16 Databases Support for MariaDB 10.6.X has been added. Handling large proxy configuration Protocol has been improved to support Zabbix proxy configuration of size up to 16 GB. Additionally performance improved by freeing uncompressed data as fast as possible and compressing before connection. See also protocol header information. Items • Zabbix agent 2 items proc.num, proc.cpu.utilization, proc.mem have the clock, etc.), used in the dashboard. Zabbix API - Zabbix API allows you to use the JSON RPC protocol to create, update and fetch Zabbix objects (like hosts, items, graphs and others) or perform any