Zabbix 7.0.6 not creating LLD items when item contains ÄäÖö etc.

[markosa]

Hi everyone. I've been banging my head to wall for a while.... I have zabbix agent (zabbix_agent2 Win64 (Zabbix) 6.0.26) running in windows machine, it returns LLD JSON like:
[{"{#TESTHOST}": "Test_\u00c4XX\u00c4", "{#TESTSITE}": "\u00c4XX\u00c4"}, {"{#TESTHOST}": "Test_AXXA", "{#TESTSITE}": "AXXA"}] and only AXXA is created(LLD creates host's and hostgroups). I've also tried so that json has [{"{#TESTHOST}": "Test_ÄXXÄ", "{#TESTSITE}": "ÄXXÄ"}, {"{#TESTHOST}": "Test_AXXA", "{#TESTSITE}": "AXXA"}] with same result, only AXXA is created.
JSON is generated in windows machine using python calls and data is returned to agent using either method:
sys.stdout.buffer.write(json.dumps(unique_data,ens ure_ascii=False).encode('utf8'))
sys.stdout.buffer.write(json.dumps(unique_data).en code('utf8'))
Based on selected output method I can receive that data to proxy(7.0.6) as shown above when using zabbix_get for discovery-item.

Anyone else seen this kind of behaviour? And possibly fixed it too....

[cyber]

You can use those õäöü-s in visible name, but not in hostname... Visible name will accept even emojis...
I guess those will not fit under "alphanumerics".. Just the usual "A-Z0-9 -._" It has always been like that...

Alphanumerics, spaces, dots, dashes and underscores are allowed. However, leading and trailing spaces are disallowed.

UTF-8 supoprt is specially mentioned for visible name.

https://www.zabbix.com/documentation/current/en/manual/config/hosts/host

[cyber]

You can use those õäöü-s in visible name, but not in hostname... Visible name will accept even emojis...
I guess those will not fit under "alphanumerics".. Just the usual "A-Z0-9 -._" It has always been like that...

Alphanumerics, spaces, dots, dashes and underscores are allowed. However, leading and trailing spaces are disallowed.

UTF-8 supoprt is specially mentioned for visible name.

https://www.zabbix.com/documentation/current/en/manual/config/hosts/host

[markosa]

Ah, crap. Yes, that was correct answer, tried to create host manually with that name and it failed. Hmmnnn... everything needs to be UTF8 but then it's not used. Too bad that LLD won't show that same error message as frontend does, or that would be written to some log instead of silently dropping...