Mastering Windows Server 2016 Hyper-V

(Romina) #1

Figure 7.10 Enabling monitoring of a service


Monitoring can also be enabled using the Add-ClusterVMMonitoredItem cmdlet and -
VirtualMachine, with the -Service parameters, as in this example:


PS C:\ > Add‐ClusterVMMonitoredItem ‐VirtualMachine savdaltst01 ‐Service
spooler


After two service failures, an event ID 1250 is logged in the system log. At this point,
the VM will be restarted, initially on the same host. On subsequent failures, however,
it will restart on another node in the cluster. This process can be seen in a video
located at http://youtu.be/H1EghdniZ1I.


This is a rudimentary capability, but it may help in some scenarios. As mentioned in
the previous chapter, for a complete monitoring solution, leverage System Center
Operations Manager, which can run monitoring with deep OS and application
knowledge that can be used to generate alerts. Those alerts can be used to trigger
automated actions for remediation or simply to generate incidents in a ticketing
system.

Free download pdf