Available in:

• 4.0.18rc1 32a1e56b
• 4.4.6rc1 7a62e6d0
• 5.0.0alpha2 66579c21

We have run into this and I wonder whether this check is not too strict. The warning in "System information" is

Incorrect default charset for Zabbix database: "utf8mb4" instead "UTF8".

This conversion is even the example of mismatch to be fixed in documention:

https://www.zabbix.com/documentation/current/manual/appendix/install/db_charset_coll

But utf8mb4 shall be superset of MySQL's UTF8 (alias for utf8mb3), with same storage requirements and is broadly recommended as a default charset:

https://www.eversql.com/mysql-utf8-vs-utf8mb4-whats-the-difference-between-utf8-and-utf8mb4/

https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-utf8mb4.html

The conversion recommended in the documentation is also potentially problematic. On the other hand, conversion from UTF8 to utf8mb4 should be without any issues at all (see dev.mysql.com link above).

Also:

In MySQL utf8 is currently an alias for utf8mb3 which is deprecated and will be removed in a future MySQL release. At that point utf8 will become a reference to utf8mb4.

So regardless of this alias, you can consciously set yourself an utf8mb4 encoding.

From: https://stackoverflow.com/a/52337457/12118546

Maybe this would be reason to reopen this or start a new issue?

CC @sasha, @mabele

Today Zabbix works with UTF-8 up to 3-byte characters. I think supporting up to 4-byte characters will require some modifications.

Thank you for prompt reply, Andris. I see that there are possible problems so we should do the change to utf8.

Seeing that utf8mb3 support will be removed in MySQL, I voted for ZBXNEXT-3706 and its duplicate ZBXNEXT-3238. Searching JIRA for emoji and utf8mb4, you can see more issues, so it is possible there are more of these duplicates.

Thanks, Roman Pavelka, for pointing to related ZBXNEXT's