check_vmware_alarms | Review current handling of VMs without an exposed/visible resource pool #307
Labels
alarm
config
output/extended
Long Service Output (aka, "extended" or "detailed")
question
Further information is requested
resource pool
Milestone
Error from a triggered alarm today:
The problem was that a VM was visible to the service account monitoring the vSphere environment, but not the datastore housing the VM.
Previously this seemed like a reasonable scenario that could be fixed by removing the VM from view (e.g., adjust permissions) or exposing the datastore to the service account (depending on the needs of the specific site).
I wonder whether a flag should be offered to indicate that these VMs should be noted in extended output, but not trigger a state change?
The text was updated successfully, but these errors were encountered: