Back to OP5 Monitor FAQ

How to Monitor Microsoft SQL clustered servers

Monitoring Microsoft clustered servers requires some extra configuration. This how-to describes how to configure OP5 Monitor to monitor drives and win32-services on clustered Windows servers.

Drives/partitions Copied

Since drives/partitions in Windows server clusters can fail over between the physical servers, the drives need to be checked/monitored via the virtual server names.

First, you need to add the virtual servers as new hosts in your configuration.

Second, add services to these new hosts. See example below:

Expand table

Services Copied

In a Windows server cluster, the Win32-services are named using the format ‘win-servicename$virtualhostname’. To monitor these services, the $-sign needs to be escaped in check_command_args. See example below:

Expand table