The memory usage alarm in vCenter Server was not being triggered, even though it was properly configured and enabled.
vCenter logs showed no relevant exceptions or backend service issues. Other alarms were functioning normally, isolating the problem to this specific alarm configuration.
vCenter 7.0
vCenter 8.0
A configuration inconsistency or corruption was identified in the alarm definition, likely introduced after the alarm was manually reset to a green state sometime back.
The memory usage alarm was reconfigured using default parameters.
Once recreated with the default settings, the alarm began triggering correctly.
Alarm definition was verified to be enabled.
Attempts to disable and re-enable the alarm did not resolve the issue.