NCPA issue with MSSQL Cluster
Posted: Tue Feb 10, 2015 9:07 am
Hi,
We have been using NCPA to monitor basic KPIs like CPU/Memory/Disk Usage. Recently, we ran in to an issue with a MSSQL cluster. This cluster is configured with an active and a passive node. If the active node goes down, the passive takes over. When this happens though, the storage drives attached to the active node are seamlessly hotswapped to the passive. NCPA did not recognize this change when the active node failed over. The passive node was only reporting a C drive when it should have also had a few more storage drives attached. I am going to open a bug report at the NCPA git project, but I was wondering if anyone had suggestions for an alternative way to monitor our MSSQL cluster.
Thanks
We have been using NCPA to monitor basic KPIs like CPU/Memory/Disk Usage. Recently, we ran in to an issue with a MSSQL cluster. This cluster is configured with an active and a passive node. If the active node goes down, the passive takes over. When this happens though, the storage drives attached to the active node are seamlessly hotswapped to the passive. NCPA did not recognize this change when the active node failed over. The passive node was only reporting a C drive when it should have also had a few more storage drives attached. I am going to open a bug report at the NCPA git project, but I was wondering if anyone had suggestions for an alternative way to monitor our MSSQL cluster.
Thanks