We have created a network map for both of our two cloud vendors to highlight any problems with their production VMs. Both maps use a host group of "virtual machines" and tags that are vendor specific.

The VMs for both vendors were discovered using LLD which has, unfortunately, assigned the VMs to a generic host group of "virtual machines". Zabbix will not allow us to retrospectively change the assigned host group or add an additional host group for these discovered VM hosts that would allow us to provide a more specific vendor grouping.

Although any problems that occur on one or more VMs display in the correct vendor's map, no doubt due to the use of specific vendor tags, any VMs in a maintenance window for a specific vendor incorrectly show in both vendor's maps. I expect the maintenance info is filtered only using the host group field in the map and it ignores the tags.

Consequently, when one vendor has VMs that are in a maintenance window, the number of VMs in maintenance is displayed in both vendor maps, despite being irrelevant for the other vendor. Refer to attached picture where Vendor 1 has 120 VMs in maintenance, but both vendor maps show the 120 VMs in maintenance. The vendor 2 map should not make any reference to hosts in maintenance.

Is it possible to:
1. Override the host groups that has been assigned by the LLD, so that the assigned host group can be replaced with an alternate host group - or another host group added?
2. In the maps, provide a user customised option to enable/disable the displaying of hosts in maintenance information?
3. Improve the maintenance functionality so that besides using host groups the maps also use the tags as a method of filtering the hosts in maintenance data to be displayed?