必须将字符集设置为 UTF-8。否则，来自 Zabbix 的文本信息将被 IBM DB2 服 务器解析为非 UTF-8 字符集，并在 Zabbix 与数据库之间互相转换。数据库将存储有问题的非 ASCII 字符。 Note: It is important to set UTF-8 locale for Zabbix server, Zabbix proxy and the web server converted on the way from Zabbix to the database and back. The database will store corrupted non-ASCII characters. Zabbix 前端使用了 SQL 中的 OFFSET 和 LIMIT 语句。为了 SQL 正常工作，IBM DB2 服务器必须设置环境变量 DB2_COMPATIBILITY_VECTOR ssh, telnet 等等。 不同的监视系统/设备和检查的返回值中可能有非 ascii 字符。对于这种情况，几乎所有的 zabbix keys 都包含一个额外的 item key 参数 * * * *。这个关键参数是可选的，但是如果返回的值不是 UTF8 编码，并且它包含非 ascii 字符，则应该指定它。否则，结果可 能是出乎意料的和不可预测的。 在这种情况下，对不同数据库后台的行为描述如下。

sinh, sqrt, tan, truncate Operator functions between, in Prediction functions - String functions ascii, bitlength, bytelength, char, concat, insert, left, length, ltrim, mid, repeat, replace, right, rtrim 3*365*24*3600* (250+80+#tags*100) = ~30GB+#tags*100B disk space2. Note: 1 More when having non-ASCII event names, tags and values. 2 The size approximations are based on MySQL and might be different versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names. net.if.in[if,] 211 Key Incoming traffic statistics on

3*365*24*3600* (250+80+#tags*100) = ~30GB+#tags*100B disk space2. Note: 1 More when having non-ASCII event names, tags and values. 2 The size approximations are based on MySQL and might be different Windows versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names. net.if.in[if,] On Windows, the item gets values from 64-bit Windows versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names. perf_counter[counter,] 223 Item key Value of any Windows

3*365*24*3600* (250+80+#tags*100) = ~30GB+#tags*100B disk space2. Note: 1 More when having non-ASCII event names, tags and values. 2 The size approximations are based on MySQL and might be different Windows versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names. net.if.in[if,] Incoming traffic statistics on network Windows versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names. perf_counter[counter,] Value of any Windows performance

3*365*24*3600* (250+80+#tags*100) = ~30GB+#tags*100B disk space2. Note: 1 More when having non-ASCII event names, tags and values. 2 The size approximations are based on MySQL and might be different Windows versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names. net.if.in The incoming traffic statistics on a network interface. Windows versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names. perf_counter[counter,]
The value of any Windows performance

3*365*24*3600* (250+80+#tags*100) = ~30GB+#tags*100B disk space2. Note: 1 More when having non-ASCII event names, tags and values. 2 The size approximations are based on MySQL and might be different Windows versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names. net.if.in The incoming traffic statistics on a network interface. Windows versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names. perf_counter[counter,]
The value of any Windows performance

3*365*24*3600* (250+80+#tags*100) = ~30GB+#tags*100B disk space2. Note: 1 More when having non-ASCII event names, tags and values. 2 The size approximations are based on MySQL and might be different versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names. net.if.in[if,] 188 Key Incoming traffic statistics on versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names. perf_counter[counter,] 235 Key Value of any Windows

Discovery of systemd services • Zabbix agent items (new item keys) JMX MBean discovery with non-ASCII characters There is now a new item for JMX MBean discovery that does not generate low-level discovery limitations associated with LLD macro name generation (for example, hyphens, square brackets and non-ASCII characters): jmx.get[,] The jmx.discovery[] item from previous versions 3*365*24*3600* (250+80+#tags*100) = ~30GB+#tags*100B disk space2. Note: 1 More when having non-ASCII event names, tags and values. 2 The size approximations are based on MySQL and might be different

were not configured properly text containing non-ASCII characters was saved in the database incorrectly. In such situations after upgrade non-ASCII characters will be displayed in Zabbix incorrectly misconfigured for Zabbix server and for web server running Zabbix frontend and the number of non-ASCII characters was too low to cause ”Value too long...” errors. Please check the database contents before versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names. net.if.in[if,] 125 Key Incoming traffic statistics on

using a screenreader Miscellaneous • The allowed character limit has been raised from 63 to 255 ASCII characters for fields containing DNS names. The affected forms are host configuration and passive 3*365*24*3600* (250+80+#tags*100) = ~30GB+#tags*100B disk space2. Note: 1 More when having non-ASCII event names, tags and values. 2 The size approximations are based on MySQL and might be different versions (for example, Server 2008) might require the latest updates installed to support non-ASCII characters in interface names. net.if.in[if,] 181 Key Incoming traffic statistics on