Áú»¢¶Ä²©

This is the documentation page for an unsupported version of Áú»¢¶Ä²©.
Is this not what you were looking for? Switch to the current version or choose one from the drop-down menu.

5 Encoding of returned values

Áú»¢¶Ä²© server expects every returned text value in the UTF8 encoding. This is related to any type of checks: zabbix agent, ssh, telnet, etc.

Different monitored systems/devices and checks can return non-ASCII characters in the value. For such cases, almost all possible zabbix keys contain an additional item key parameter - <encoding>. This key parameter is optional but it should be specified if the returned value is not in the UTF8 encoding and it contains non-ASCII characters. Otherwise the result can be unexpected and unpredictable.

A description of behavior with different database back-ends in such cases follows.

MySQL

Si une valeur contient un caract¨¨re non-ASCII avec un encodage non UTF8, ce caract¨¨re et les suivants seront ignor¨¦s lorsque la base de donn¨¦es stockera cette valeur. Aucun message d'avertissement ne sera ¨¦crit dans zabbix_server.log.
Pertinent pour au moins MySQL version 5.1.61

PostgreSQL

Si une valeur contient un caract¨¨re non-ASCII avec un encodage non UTF8, une requ¨ºte SQL ¨¦chou¨¦e (PGRES_FATAL_ERROR:ERROR invalid byte sequence for encoding) et les donn¨¦es ne seront pas stock¨¦es. Un message d'avertissement appropri¨¦ sera ¨¦crit dans zabbix_server.log.
Pertinent pour au moins la version 9.1.3 de PostgreSQL.