Currently real-time export JSON files for events items and trends include information about host (or hosts) visible name. It is proposed to add host name too.
For this purposes old JSON tag "host" will be used. It is proposed to use JSON object consisting from visible and technical name of the host under this tag.

{
	"host": {
		"host":"My host name",
		"name":"My visible name"
	},
	"groups": ["Zabbix servers"],
	"applications": ["Zabbix server"],
	"itemid": 23662,
	"name": "Zabbix value cache operating mode",
	"clock": 1568788342,
	"ns": 272565946,
	"value": 0
}

For events, where array of hosts can be used proposed to use old tag "hosts" with array of JSON objects consisting from visible and technical name of the hosts

{
	"clock": 1568709760,
	"ns": 579504018,
	"value": 1,
	"eventid": 27,
	"name": "Trigger name",
	"hosts": [{
			"host": "My host name 1",
			"name": "My visible name 1"
		},
		{
			"host": "My host name 2",
			"name": "My visible name 2"
		}
	],
	"groups": ["Zabbix servers"],
	"tags": []
}

Server changes

• function DCexport_history - add json object with ZBX_PROTO_TAG_HOST with item->host.name and item->host.host instead of string with the same tag
• function DCexport_trends - add json object with ZBX_PROTO_TAG_HOST with item->host.name and item->host.host instead of string with the same tag
• function zbx_export_events - add json object with host->host and host->name instead of string into array with tag ZBX_PROTO_TAG_HOSTS
• patch from ZBXNEXT-4831 should be applied

Documentation changes

• What's new
• Real-time export protocol must be extended with new fields
• Upgrade notes

Dear palivoda, is it an invitation to comment?

<palivoda>: Feel free.

I was asking this in PR, but the answer wasn't very optimistic. It is proposed above to change types of existing keys "host" and "hosts" from string and array of strings to object and array of objects. This will very likely break existing integrations (if there are any), existing user code will not be able to find host names in the same places. And unlike ZBXNEXT-5416, no one forces Zabbix to do this breaking change. Why can't you just leave existing keys alone and introduce new ones ("Hosts" or "hosts+" or whatever) with extra information? You can declare old keys deprecated and remove them in the next major release, but this will at least give users some time to adapt.

Fixed in:

• 4.4.0rc1 (master) 64d5130f51e

Updated documentation:

• Real-time export protocol
• Upgrade notes
• What's new