Hi Nesrine,
This sounds like a quality controlled system or validated system. Dealing with those is one of the challenges in the IT world.
If possible, create VMware rules in the cluster that actually bind the VM to a host and document those with screenshots in your validation documents and configuration documents as well.
Further are the logfiles of VMware are a proofing tool that could be periodically reviewed.
To accomplish this via PRTG and since you deal with guest bound to host and only have a few that should match, you possibly could use the VMware REST API to check this.
Browse your VMware cluster API with https://your-server/apiexplorer/#!/VM_/get_vcenter_vm - respective API vCenter and VM. You can provide the filter values filter.hosts and filter.names.
Then use the PRTG REST sensor and query it with the determined API requests.
Did not test this, but this seems to me the best way to accomplish your specific task and make sure the guest does not leave the host.
Of course, you only specify one host and one guest per request, so you bind them together. If the guest is not found on the host you would get an error.
Test this and proof it with a VM that would roam on the cluster or move it forcefully to proof the sensor fires and document this in your validation documentation so the Oracle DBA / business application team has proof and good.
Hope this helps you,
Florian Rossmark
www.it-admins.com
Add comment