Risks, Limitations & Assumptions

  • This application only supports mssql-cluster which is built upon the Windows failover cluster.

  • For Cluster object discovery and monitoring implementation, we are considering the object which has “Name” equals to Cluster Name in Get-ClusterResource response.

  • For ClusterGroup monitoring implementation, We are considering the object which has Name as Cluster Group in Get-ClusterGroup response

  • All the failover status metrics possible instance values are 0 - if there is no change in OwnerNode, 1 - If there is a change in OwnerNode, 2 - If no OwnerNode

  • Application can handle Critical/Recovery failure notifications for below two cases when user enables “App Failure Notifications” in configuration:

    • Connectivity Exception
    • Authentication Exception

  • Application will send any duplicate/repeat failure alert notification for every 6 hours.

  • If user enables agent monitoring templates on the Cluster/Node resource, he might see the duplicate metrics with different naming conventions.

  • While trying to fetch the node ip address we receive multiple node ips, which will include many local ips and actual ips (example : lets say actual node ip is 10.1.1.1 when trying to fetch the details we will receive two ips one associated with custer(192.168.0.0) and other is the actual ip). To identify the actual node ip address from the list of IP addresses received we are assuming that node ip address is part of the same subnet of cluster ip address. meaning if cluster ip is 10.1.1.1 then node ips will be 10.1.X.X.

  • We have provided the provision to give Cluster Ip Address OR HostName in configuration, but hostName provision will work only if the host name resolution works.

  • Classic gateway requires additional libraries to be packaged which are needed to execute the powershell script to achieve this integration approach.

  • This application supports only Classic Gateway and NextGen Gateway. Not supported with Cluster Gateway.

  • The Template Applied Time will only be displayed if the collector profile (Classic and NextGen Gateway) is version 18.1.0 or higher.

  • Component level thresholds can be configured on each resource level.

  • Optional configuration parameters can be defined.

  • Application upgrade is an automated process with version change.

  • If you select any of the MSSQL Type STANDALONE / CLUSTER in configuration page, by default all the RESOURCE TYPE’s are selected however the Discovery perform is based on MSSQL Type only.
    Example: if you select MSSQL Type as STANDALONE, the application will discover only two resource types which is MSSQL Node and MSSQL Server Instance even all the resource types is selected.

  • Validated the integration (MSSQL Type as VERITAS CLUSTER) with domain admin user only.

  • For the integration (MSSQL Type as VERITAS CLUSTER), we are considering cluster uid or cluster name for uniqueness. If there is any change with cluster uid or cluster name resources will be deleted and re-created.