VMware plugin: How to identify VM name in alerts instead of vCenter (Zabbix 7.4)

[tibiki]

Hi everyone,

I'm using the VMware plugin to monitor vCenter Server with Zabbix 7.4. Sometimes I see alarms like "VMware: Virtual machine CPU usage," but the host appears as the vCenter server itself. Is there a way to display the actual VM name in the alert, instead of just seeing the vCenter as the host? I want to easily identify which VM triggered the alarm.

Thanks in advance!
Regards,

[zekaleka]

yes, im interested in solution too.
Little bit different scenario for me, but equivalent.
VMSnapshot alarm-701, vm-id-10889.
Reather i would like to see VMSnapshot alarm-701, vm-Name

[mpetes]

I have the same problem with Slack notifications. Anyone find some solution for this?
I get this:
Problem: VMware: Virtual machine CPU usage
Problem started at 09:20:49 on 2025.11.04
Problem name: VMware: Virtual machine CPU usage
Host: Selska-vCentat00
Severity: Warning
Operational data: 5.5152113
Original problem ID: 11571187

[mintamanta]

Hi all, I was facing this issue. Main problem, that I could not find these problems even in history, only in Action log. Go to Templates -> Vmware ->Discovery -> Get alarms: VMware alarm discovery -> Trigger prototypes.
Set VMware: {#VMWARE.ALARMS.NAME} to "Create enabled" "No". In this case you DISABLE all VMware alarm related triggers. Personally I don't need any. If you don't want DISABLE all related trigger you should define FILTER values.

Regards, Mintamanta.

[zekaleka]

Hi all, I was facing this issue. Main problem, that I could not find these problems even in history, only in Action log. Go to Templates -> Vmware ->Discovery -> Get alarms: VMware alarm discovery -> Trigger prototypes.
Set VMware: {#VMWARE.ALARMS.NAME} to "Create enabled" "No". In this case you DISABLE all VMware alarm related triggers. Personally I don't need any. If you don't want DISABLE all related trigger you should define FILTER values.

Regards, Mintamanta.

It's naughty to provide solution by disabling monitoring at monitoring forum
But yes, problem still persist, and I can't find solution how to make VM name visible in operational-data / Problem field. (tried #VM.NAME but it didn't helped)


Let's hope for 2026.! Maybe someone will guide us