Child pages
  • Monitoring Microsoft clustered servers
Skip to end of metadata
Go to start of metadata

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

Since Drives/partitions in Windows server clusters can failover between the physical servers, the drives need to be checked/monitored via the virtual server names. First you add the virtual servers as new hosts in your configuration. Secondly add services to these new hosts. See example below:

service_description:Disk usage Q:
check_command:check_nt_disk
check_command_args:Q!88%!95%

Services

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:

service_description:SQL Server service
check_command:check_nt_service
check_command_args:MSSQLSERVER\$$virtualhost