Supported Versions
This application is validated on Windows Server 2019 and Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64) for both MSSQL failover instance & availability group clusters.

Multi-node failover cluster Instance

SQL Server clustering describes a collection of two or more physical servers (nodes), connected via LAN, each of which host a SQL server instance and have the same access to shared storage. Clustering SQL servers provides high availability and protection from disasters when a server hosting the SQL Server instance fails.

Always on failover cluster instances

SQL Server Always On Failover Cluster Instances (FCIs) use Windows Server Failover Clustering (WSFC) to provide high availability at the server instance level. An FCI is a single instance of SQL Server that is installed across WSFC nodes to provide high availability for the entire installation of SQL Server.

Always On availability group

Always On availability groups feature a high availability and disaster recovery solution that provides an alternative to database mirroring, and maximizes the availability of a set of user databases for an enterprise. This supports a failover environment for a discrete set of user databases, known as availability databases.

The availability group supports a set of read-write primary databases and one to eight sets of corresponding secondary databases. Optionally, secondary databases can be made available for read-only access and/or some backup operations. Availability group fails over at the level of an availability replica. Failovers are not caused by database issues such as a database becoming suspect due to a loss of a data file, deletion of a database, or corruption of a transaction log.

Pre-requisites

  • The application would require classic gateway 13.0.0 and above.

  • There is no version dependency for cluster gateway.

  • Powershell cmdlets have the following prerequisites:

    • Windows domain User should be able to do powershell remoting
      Enable-PSRemoting -Force
    • Windows domain user should be added to “Remote Management users” group net localgroup “Remote Management Users” /add < user >
    • Windows domain user should be added to “Performance monitor users” group net localgroup “Performance monitor users” /add < user >
  • Granting Remote DCOM Rights

    • To grant users DCOM rights, log on to each monitored system and complete the following procedure:
      • Go to command prompt and enter dcomcnfg
      • Navigate to component services > computers > My computer and then right click and select Properties. Then go to the COM Security tab.
      • Under Access Permissions, go to edit limits and add the domain non-admin user and enable both local and remote access then click OK.
      • In Launch and Activation permissions, go to edit limits, add the domain non-admin user and check all boxes , and click OK.
  • Granting Remote WMI Rights

    • To give the user remote WMI rights, log on to each system to be monitored and complete the following procedure:
      • Go to “computer management” and select “WMI Control” under ‘Services and Applications’.
      • Right-click WMI control and go to properties. Then select the Security tab.
      • Select root and click Security.
      • Add the domain non-admin user, and check the boxes for execute methods, enable account, remote enable, and reas security.
      • Click Advanced, select added non-admin domain user and click edit. Then for “Applies” to select “namespace and sub namespaces” in the dropdown.
      • Click OK 3 times .
  • For monitoring services like windows cluster service and other mssql services (sql server, sql agent , sql browser etc.), windows domain users have to be a part of “Local Administrators group” as we are using win32_Service class for fetching the details.

  • Windows domain user should be granted read-only access to cluster
    Grant-ClusterAccess -User <domain\user> -Readonly

SQL authorization permissions:

  • For monitoring some metrics, we are using JDBC. For JDBC connections we are supporting mixed authentication (both NLTM and SQL server authentication)
  • The minimum privileges for SQL auth are:
    • server role: public - This server role is available by default
    • securables: We need to enable some securables for connecting to SQL instances,connecting to all databases, and also some read-only permissions like below:

 - CONNECT ANY DATABASE
      GRANT CONNECT ANY DATABASE to < user >
 - CONNECT SQL
      GRANT CONNECT SQL to < user >
 - SELECT ALL USER SECURABLES
      GRANT SELECT ALL USER SECURABLES to < user >
 - VIEW ANY DATABASE
      GRANT VIEW ANY DATABASE to < user >
 - VIEW ANY DEFINITION
      GRANT VIEW ANY DEFINITION to < user >
 - VIEW SERVER STATE
      GRANT VIEW SERVER STATE to < user >

Hierarchy of MSSQL Cluster resources

  • MSSQL Windows Failover Cluster
        - MSSQL Windows Failover Cluster Node
        - MSSQL Windows Failover Cluster Role
        - MSSQL Windows Failover Cluster Storage Disk
        - MSSQL Server Instance

Default Monitoring Configurations

Mssql-cluster has default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. You can customize these default monitoring configurations as per your business use cases by cloning respective global templates and global Device Management Policies. OpsRamp recommends performing the below activity before installing the application to avoid noise alerts and data.

  1. Default Global Device Management Policies

    OpsRamp has a Global Device Management Policy for each Native Type of MS SQL Cluster. You can find those Device Management Policies at Setup -> Resources -> Device Management Policies, search with suggested names in global scope. Each Device Management Policy follows below naming convention:

    {appName nativeType - version}

    Ex: mssql-cluster MSSQL Windows Failover Cluster - 1 (i.e, appName = mssql-cluster, nativeType =MSSQL Windows Failover Cluster, version = 1)

  2. Default Global Templates

    OpsRamp has a Global Template for each Native Type of MSSQL Windows Failover Cluster. You can find those templates at Setup -> Monitoring -> Templates, search with suggested names in global scope. Each template follows below naming convention:

    {appName nativeType 'Template' - version}

    Ex: mssql-cluster MSSQL Windows Failover Cluster Template - 1 (i.e, appName = mssql-cluster , nativeType = MSSQL Windows Failover Cluster, version = 1)

  3. Default Global Monitors

    OpsRamp has a Global Monitors for each Native Type which has monitoring support. You can find those monitors at Setup -> Monitoring -> Monitors, search with suggested names in global scope. Each Monitors follows below naming convention:

    {monitorKey appName nativeType - version}

    Ex: MSSQL Windows Failover Cluster Monitor mssql-cluster MSSQL Windows Failover Cluster 1 (i.e, monitorKey = MSSQL Windows Failover Cluster Monitor, appName = mssql-cluster , nativeType = MSSQL Windows Failover Cluster , version= 1)

Configure and install the integration

  1. From All Clients, select a client.
  2. Go to Setup > Integrations and Apps.
  3. Click Manage Apps.
    Notes:
    • If there are already installed applications, it will redirect to the INSTALLED APPS page, where all the installed applications are displayed.
    • If there are no installed applications, it will navigate to the ADD APP page.
MS SQL Configure
  1. Click + ADD on the INSTALLED APP page. The AVAILABLE INTEGRATIONS AND APPS page displays all the available applications along with the newly created application with the version.
    Note: You can even search for the application using the search option available. Also you can use the All Categories option to search.
MS SQL Configure
  1. Click ADD in the MS SQL Cluster application.
  2. In the Configurations page, click + ADD. The Add Configuration page appears.
  3. Enter the below mentioned BASIC INFORMATION:
FunctionalityDescription
NameEnter the name for the configuration.
IP Address/Host NameIP address of the target.
PortPort
Example: By default 443 is the port value
MSSQL Cluster TypeSelect the cluster type from the drop-down list.
Note: By default FailoverClusterInstance is selected.
Windows Cluster CredentialsSelect the windows cluster credentials from the drop-down list.
Note: Click + Add to create a credential.
SQL Server CredentialsSelect the SQL Server credentials from the drop-down list.
Note: Click + Add to create a credential.

Notes:

  • By default the Is Secure and SQL Server Authentication Mode checkbox is selected.
  • App Failure Notifications: if turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.
  1. Select the below mentioned Custom Attribute:
FunctionalityDescription
Custom AttributeSelect the custom attribute from the drop down list box.
ValueSelect the value from the drop down list box.

Note: The custom attribute that you add here will be assigned to all the resources that are created by the integration. You can add a maximum of five custom attributes (key and value pair).

  1. In the RESOURCE TYPE section, select:
    • ALL: All the existing and future resources will be discovered.
    • SELECT: You can select one or multiple resources to be discovered.
  2. In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:
    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly
  3. Click ADD.
MS SQL Configure
  1. Now the configuration is saved and displayed on the configurations page after you save it.
    Note: From the same page, you may Edit and Remove the created configuration.
  2. Click Next.
  3. In the Installation page, select an existing registered profile, and click FINISH.
MS SQL Configure

The application is now installed and displayed on the INSTALLED INTEGRATION page. Use the search field to find the installed application.

Modify the Configuration

View the MS SQL Cluster details

The MS SQL Cluster integration is displayed in the Infrastructure > Resources > Cluster. You can navigate to the Attributes tab to view the discovery details and Metrics tab to view the metric details for MS SQL Cluster.

MS SQL Configure

View resource metrics

To confirm MS SQL Cluster monitoring, review the following:

  • Metric graphs: A graph is plotted for each metric that is enabled in the configuration.
  • Alerts: Alerts are generated for metrics that are configured as defined for integration.
MS SQL Configure

Resource Type Filter Keys

MSSQL Cluster application resources are filtered and discovered based on below keys:

Resource TypeSupported Input Keys
All TypesresourceName
hostName
aliasName
dnsName
ipAddress
macAddress
os
make
model
serialNumber
MSSQL Windows Failover ClusterConfigured Nodes Count
Owner Node
MSSQL Server InstancePort

Supported Alert Custom Macros

Customize the alert subject and description with below macros then it will generate alerts based on customisation. Supported macros keys:

                                ${resource.name}

                                ${resource.ip}

                                ${resource.mac}

                                ${resource.aliasname}

                                ${resource.os}

                                ${resource.type}

                                ${resource.dnsname}

                                ${resource.alternateip}

                                ${resource.make}

                                ${resource.model}

                                ${resource.serialnumber}

                                ${resource.systemId}

                                ${Custome Attributes in the resource}

                                ${parent.resource.name}

Supported metrics

Resource TypeMetric NamesDisplay NameUnitDescription
MSSQL Windows Failover Clustermssql_cluster_node_stateMSSQL Windows Failover Cluster Node StateState of all nodes of the cluster such as up or down. Possible values 0-DOWN, 1-UP.
mssql_cluster_online_nodes_countMSSQL Windows Failover Cluster Online nodes countcountCount of nodes which are in Online state.
mssql_cluster_node_healthMSSQL Windows Failover Cluster Node Health%Cluster health - percentage of online nodes.
MSSQL Windows Failover Cluster Nodemssql_cluster_node_service_statusMSSQL Windows Cluster Node Service StatusState of each node's windows os service named cluster service which is responsible for windows failover cluster. Possible values 0-STOPPED, 1-RUNNING,2-Start Pending, 3-Stop Pending, 4-Continue Pending, 5-Pause Pending, 6-Paused, 7-Unknown.
mssql_cluster_node_system_os_UptimeMSSQL Windows Cluster Node System OS UptimemTime lapsed since last reboot in minutes
mssql_cluster_node_system_cpu_LoadMSSQL Windows Cluster Node System CPU LoadMonitors the system's last 1min, 5min and 15min load. It sends per cpu core load average.
mssql_cluster_node_system_cpu_UtilizationMSSQL Windows Cluster Node System CPU Utilization%The percentage of elapsed time that the processor spends to execute a non-Idle thread(This doesn't includes CPU steal time).
mssql_cluster_node_system_memory_UsedspaceMSSQL Windows Cluster Node System Memory Used SpaceGBPhysical and virtual memory usage in GB.
mssql_cluster_node_system_cpu_IdleTimeMSSQL Windows Cluster Node System CPU IdleTime%Monitors cpu time in percentage spent in various program spaces. User - The processor time spent running user space processes. System - The amount of time that the CPU spent running the kernel. IOWait - The time the CPU spends idle while waiting for an I/O operation to complete. Idle - The time the processor spends idle. Steal - The time virtual CPU has spent waiting for the hypervisor to service another virtual CPU running on a different virtual machine. Kernal Time Total Time.
mssql_cluster_node_system_network_interface_InTrafficMSSQL Windows Cluster Node System Network In TrafficKbpsMonitors In traffic of each interface for windows Devices.
mssql_cluster_node_system_network_interface_OutTrafficMSSQL Windows Cluster Node System Network Out TrafficKbpsMonitors Out traffic of each interface for windows Devices.
mssql_cluster_node_system_network_interface_InPacketsMSSQL Windows Cluster Node System Network In packetspackets/secMonitors in Packets of each interface for windows Devices.
mssql_cluster_node_system_network_interface_OutPacketsMSSQL Windows Cluster Node System Network out packetspackets/secMonitors Out packets of each interface for windows Devices.
mssql_cluster_node_system_network_interface_InErrorsMSSQL Windows Cluster Node System Network In ErrorsErrors per SecMonitors network in errors of each interface for windows Devices.
mssql_cluster_node_system_network_interface_OutErrorsMSSQL Windows Cluster Node System Network Out ErrorsErrors per SecMonitors network out errors of each interface for windows Devices.
mssql_cluster_node_system_network_interface_InDiscordsMSSQL Windows Cluster Node System Network In discardspsecMonitors Network in discards of each interface for windows Devices.
mssql_cluster_node_system_network_interface_OutDiscordsMSSQL Windows Cluster Node System Network Out discardspsecMonitors Network Out discards of each interface for windows Devices.
mssql_cluster_node_sqlservices_stateMSSQL Windows Cluster Node SQL services running stateMonitors sql services state. Possible values 0-STOPPED, 1-RUNNING, 2-Start Pending, 3-Stop Pending, 4-Continue Pending, 5-Pause Pending, 6-Paused, 7-Unknown.
mssql_cluster_node_sqlprocesses_cpuUsageMSSQL Windows Cluster Node SQL processes CPU usage in SecondssMonitors sql processes cpu usage in seconds.
mssql_cluster_node_sqlprocesses_handlesMSSQL Windows Cluster Node SQL processes number of handlescountMonitors sql processes handles count.
mssql_cluster_node_system_memory_UtilizationMSSQL Windows Cluster Node System Memory Utilization%Physical and virtual memory usage in percentage.
MSSQL Windows Failover Cluster Rolemssql_cluster_group_running_statusMSSQL Windows Cluster Group Running StatusState of cluster group of the failover cluster. Possible values 0-OFFLINE, 1-ONLINE 2-Initializing, 3-Failed, 4-Pending, 5-OnlinePending, 6-OfflinePending, 7-Unknown.
mssql_cluster_group_failover_statusMSSQL Windows Cluster Group Failover StatusAny other node immediately becomes owner node whenever the owner node hosting all of the cluster services goes down. This metric indicates whether the present node was the owner node during the last failover. Possible instance values, 0-if there is no change in OwnerNode, 1-If there is a change in OwnerNode, 2-If no OwnerNode.
mssql_cluster_group_listener_statusMSSQL Windows cluster group listener statusMonitors MSSQL cluster group listeners status. Possible values 0-OFFLINE, 1-ONLINE 2-Initializing, 3-Failed, 4-Pending, 5-OnlinePending, 6-OfflinePending, 7-Unknown.
mssql_cluster_AG_instance_statusMSSQL Windows cluster availability group instance statusMonitors MSSQL availability group cluster instance status. Possible values 0-OFFLINE,1-ONLINE 2-Initializing, 3-Failed, 4-Pending, 5-OnlinePending, 6-OfflinePending, 7-Unknown. This metric is applicable only for AAG clusters.
MSSQL Windows Failover Cluster Storage Diskmssql_cluster_disk_AvailabilityStatusMSSQL Windows System Disk availability statusMonitors system disk availability status. Possible values 0-OFFLINE, 1-ONLINE, 2-Initializing, 3-Failed, 4-Pending, 5-OnlinePending, 6-OfflinePending, 7-Unknown.
mssql_cluster_disk_FailoverStatusMSSQL Windows System Disk Failover statusWhen the storage disc host owner node fails, any other node immediately takes over as owner node. This measurement indicates whether the present node was the owner node during the last failover. Possible instance values, 0-if there is no change in OwnerNode, 1-If there is a change in OwnerNode, 2-If no OwnerNode.
mssql_cluster_disk_UsedspaceMSSQL Windows System Disk UsedSpaceGBMonitors disk used space in GB.
mssql_cluster_disk_UtilizationMSSQL Windows System Disk Utilization%Monitors disk utilization in percentage.
mssql_cluster_disk_FreespaceMSSQL Windows System Disk FreeSpaceGBMonitors the Free Space usage in GB.
MSSQL Server Instancemssql_cluster_instance_RunningStatusMSSQL Cluster Instance Running StatusMonitors MSSQL failover cluster instance running status. Possible values 0-OFFLINE, 1-ONLINE 2-Initializing, 3-Failed, 4-Pending, 5-OnlinePending, 6-OfflinePending, 7-Unknown.
mssql_cluster_instance_FailoverStatusMSSQL Cluster Instance Failover StatusMonitors MSSQL cluster instance failover status. Possible instance values, 0-if there is no change in OwnerNode, 1-If there is a change in OwnerNode, 2-If no OwnerNode. This metric is applicable only for FCI clusters.
mssql_cluster_avgLockWaitTimeMSSQL Cluster Average Lock Wait TimemsThe average amount of wait time (milliseconds) for each lock request that resulted in a wait.
mssql_cluster_bufferCacheHitRatioMSSQL Cluster Buffer Cache Hit Ration%Percentage of pages that were found in the buffer pool without having to incur a read from disk.
mssql_cluster_sqlCacheMemoryMSSQL Cluster Cache MemoryKBTotal amount of dynamic memory the server is using for the dynamic SQL cache.
mssql_cluster_datafileSizeMSSQL Cluster Data File SizeKBThe cumulative size of all the data files in the database.
mssql_cluster_databasesCountMSSQL Cluster Databases CountcountShow the count of total number of databases.
mssql_cluster_fullScansMSSQL Cluster SQL Server Full ScanspsecNumber of unrestricted full scans. These can either be base tables or full index scans.
mssql_cluster_databasepageReadsMSSQL Cluster Databases Page ReadsrpsNumber of physical database page reads issued.
mssql_cluster_databasepageWritesMSSQL Cluster Database Page WriteswpsNumber of physical database page writes issued.
mssql_cluster_serverUptimeMSSQL Cluster Server UptimeDaysMonitors the uptime (in days) of the database server.
mssql_cluster_totalServerMemoryMSSQL Cluster Total Server MemoryKBTotal amount of dynamic memory the server is currently consuming
mssql_cluster_databaseTransactionsMSSQL Cluster Database TransactionspsecThe number of transactions started for the database.
mssql_cluster_databaseStatusMSSQL Cluster Database Status0 = ONLINE, 1 = RESTORING, 2 = RECOVERING SQL Server 2008 and later, 3 = RECOVERY_PENDING SQL Server 2008 and later, 4 = SUSPECT, 5 = EMERGENCY SQL Server 2008 and later, 6 = OFFLINE SQL Server 2008 and later, 7 = COPYING Azure SQL Database Active Geo-Replication, 10 = OFFLINE_SECONDARY Azure SQL Database Active Geo-Replication.
mssql_cluster_databaseActiveUsersMSSQL Cluster Database Active UserscountMonitors the number of active user transactions per database.
mssql_cluster_datafilesFreeSpaceMSSQL Cluster Data Files Free Space%Monitors datafiles free space regardless of auto-growth.
mssql_cluster_databaseFreeSpaceMSSQL Cluster Database Free Space%Monitors Database Freespace in Percentage
mssql_cluster_dbLogCacheHitRatioMSSQL Cluster DB Log Cache Hit Ratio%Monitors MSSQL database log cache-hit ratio.
mssql_cluster_dbLogfilesFreeSpaceMSSQL Cluster DB Logfiles Free Space%Monitors MSSQL database LogFiles free space.
mssql_cluster_minsSinceLastLogBackupMSSQL Cluster Mins since Last Log BackupmMonitors Database transaction log backup in minutes.
mssql_cluster_minsSinceLastLogFullBackupMSSQL Cluster Mins since Last Log Full BackupmMonitors Database Backup status in Minutes since Last Full Backup.
mssql_cluster_fileGroupFreespaceWithAvailableDiskMSSQL Cluster File Group Free Space with Available Disk%Monitor MSSQL DB Filegroup Freespace with Available Disk.
mssql_cluster_dbFileGroupFreespaceMSSQL Cluster DB File Group Free Space%Monitors MSSQL DB Filegroup Freespace.
mssql_cluster_longRunningQueriesLast5minCountMSSQL Cluster Long Running Queries Last 5min CountcountMonitors MSSQL Database Long Running queries count Last 5 minutes.
mssql_cluster_serverIOBusyMSSQL Cluster Server IO Busy%Monitors MSSQL DB Server IO Busy.
mssql_cluster_dbWorkspaceMemoryMSSQL Cluster DB Workspace Memory%Monitors MSSQL Database Workspace Memory in Percentage.
mssql_cluster_dbInstanceCpuUtilizationMSSQL Cluster DB Instance CPU Utilization%Monitors MSSQL Database Instance CPU Utilization in percentage.
mssql_cluster_logfileFreespaceWithAvailableDiskMSSQL Cluster Logfile Free Space with Available Disk%Monitors MSSQL DB Log File Freespace with Available Disk in percentage.
mssql_cluster_instanceFreeConnectionsMSSQL Cluster Instance Free Connections%Monitors MSSQL Database Instance Free Connections in percentage.
mssql_cluster_daysSinceLastFullBackupMSSQL Cluster Days since Last Full BackupDaysMSSQL DB Backup Days Since Last Full Backup.
mssql_cluster_daysSinceLastLogBackupMSSQL Cluster Days since Last Log BackupDaysMSSQL DB Backup Days Since Last Log Backup.
mssql_cluster_daysSinceLastDifferentialBackupMSSQL Cluster Days since Last Differential BackupDaysMSSQL DB Backup Days Since Last Differential Backup.
mssql_cluster_alwaysOnDBAvailabilitySyncHealthMSSQL Cluster AlwaysOn DB Avalability Sync HealthMSSQL AlwaysOn DataBase Availability Synchronization Health, below are the possible states: 0 : NOT_HEALTHY, 1 : PARTIALLY_HEALTHY, 2 : HEALTHY. This metric is applicable only for AAG clusters.
mssql_cluster_alwaysOnAGSyncHealthMSSQL Cluster AlwaysOn AG Sync HealthMSSQL AlwaysOn Availability Group Synchronization Health, below are the possible values: 0 : NOT_HEALTHY, 1 : PARTIALLY_HEALTHY, 2 : HEALTHY. This metric is applicable only for AAG clusters.
mssql_cluster_alwaysOnListenerStateMSSQL Cluster AlwaysOn Listener StateMSSQL AlwaysOn Listener State, below are the possible values: 0 : OFFLINE, 1 : ONLINE, 2 : ONLINE_PENDING, 3 : FAILED. This metric is applicable only for AAG clusters.
mssql_cluster_cpuBusyMSSQL Cluster CPU BusymicrosecMSSQL CPU Busy
mssql_cluster_cpuIdleMSSQL Cluster CPU IdlemicrosecMSSQL CPU IDLE
mssql_cluster_cpuIOBusyMSSQL Cluster CPU IO BusymicrosecMSSQL CPU IoBusy
mssql_cluster_alwayson_database_replicaStateMSSQL Cluster AlwaysOn DataBase Replica StateIt monitor the MSSQL Always On Database Replica synchronization state along with role description.Below are the possible states: PRIMARY_NOT SYNCHRONIZING - 0 PRIMARY_SYNCHRONIZING - 1 PRIMARY_SYNCHRONIZED - 2 PRIMARY_REVERTING - 3 PRIMARY_INITIALIZING - 4 SECONDARY_NOT SYNCHRONIZING - 5 SECONDARY_SYNCHRONIZING - 6 SECONDARY_SYNCHRONIZED - 7 SECONDARY_REVERTING - 8 SECONDARY_INITIALIZING - 9 This metric is applicable only for AAG clusters.

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 not send any duplicate/repeat failure alert notification until the already existing critical alert is recovered.
  • If user enables agent monitoring templates on the Cluster/Node resource, he might see the duplicate metrics with different naming conventions
  • In order to determine the actual node IP address from the list of received IPs, we are assuming that the node IP address is a part of the same subnet as the cluster IP address. For example, let’s say the actual node IP is 10.1.1.1 when trying to fetch the details, we will receive two IPs, one associated with the cluster (192.168.0.0) and the other is the actual IP. i.e., if the cluster IP is 10.1.1, the 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.
    Note: Not supported with Cluster Gateway. No support of showing activity log and applied time.
  • 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.