. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1849 12 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1850 on Select next to the item key field). Preprocessing Advanced root-cause handling for unsupported item state Error handling in case of a failure to retrieve an item value (and thus it becoming unsupported) where the process failed. All errors had to be handled using one and the same option for error handling - either to discard the value, set a specified value or set a specified error message. 13 It is

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1790 12 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1791 use native SNMP bulk requests (GetBulkRequest-PDUs), available in SNMP versions 2/3. A GetBulk request in SNMP executes multiple GetNext requests and returns the result in a single response. Previously independently. Using the new SNMP walk[OID1,OID2,...] item, it becomes possible to collect data in one request and parse the response as needed, without additional requests to devices. For example, walk[1.3

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1805 14 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1806 values: 0 - numeric float, 1 - character, 2 - log, 3 - numeric unsigned, 4 - text. • Time period handling of the fmttime macro function has become more flexible. Webhook integrations New integrations are you can import them manually into Zabbix. 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

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1376 15 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1376 CSV file data into JSON format. 12 See also: CSV to JSON preprocessing Custom error handling Custom error handling is now also available for the following preprocessing steps: * Check for error in JSON in JSON’ and ’Check for error in XML’ preprocessing steps. In a typical use case of custom error handling, data can be skipped if an error message is found. More options for LLD rule preprocessing More

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1542 12 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1543 TCP queue. 20 What’s new in Zabbix 5.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 Zabbix agents can perform passive and active checks. In a passive check the agent responds to a data request. Zabbix server (or proxy) asks for data, for example, CPU load, and Zabbix agent sends back the

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1658 12 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1659 → Templates you can import them manually into Zabbix. Handling of NaN values in Prometheus preprocessing There is a new behavior for handling (skipping) NaN values. So, if a dataset consists of valid of actions • ha manager - process for managing high availability • history poller - process for handling calculated and internal checks requiring a database connection • history syncer - history DB writer

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1719 14 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1720 exported and imported in the YAML format, which is easy to read and edit. Custom handling for item errors Custom handling for item errors has been introduced in the new version on the basis of an individual Zabbix agents can perform passive and active checks. In a passive check the agent responds to a data request. Zabbix server (or proxy) asks for data, for example, CPU load, and Zabbix agent sends back the

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1257 14 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1258 returns +999°C when it is off, the normal range being -100°C up to +100°C. Validation and custom error handling allows to discard these noise values or replace them with some default value or simply replace Item value preprocessing. Custom error handling Previously an item would become unsupported if any of the preprocessing steps failed. Now a custom error handling option has been added to the following

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1669 12 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1670 (in the list of proxies or the proxy editing form) It is also now possible for passive proxies to request configuration from the server using the config_cache_reload proxy runtime control command. Separate discovery of devices • escalator - process for escalation of actions • history poller - process for handling calculated checks requiring a database connection • history syncer - history DB writer • housekeeper

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 14 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 instruction. 创建 text 类型的映射可以发送如下请求到 Elasticsearch：To create mapping for text type send the following request to Elastic- search: curl -X PUT \ http://your-elasticsearch.here:9200/text \ -H 'content-type:application/json' : false, "type" : "text" } } } } }' 对于创建 “字符” 和 “日志” 类型的历史数据映射，需要执行类似的请求，请求内容需要进行相应的修改。Similar request is required to be executed for Character and Log history values mapping creation with corresponding