Monitor the health and availability of Windows Server failover clusters, including nodes, roles, resources, networks, and disks, in Dynatrace.
Find failed nodes, offline roles, and degraded networks before they cause downtime.
Windows Server failover clusters keep business-critical workloads available when a server fails. The Microsoft Windows Failover Cluster extension runs on one of the OneAgent-monitored nodes of each cluster and reports the state and status of the cluster and its components: nodes, resource groups (cluster roles), resources, cluster networks, network interfaces, and cluster disks.
The extension also reports cluster-level conditions, such as forced quorum states and backups in progress, and records each cluster's configuration as properties of the cluster entity.
This extension runs locally on a cluster node and doesn't offer remote monitoring. Typical extensions run as LOCAL SERVICE, but this one requires privileges elevated to LOCAL SYSTEM to read cluster data through PowerShell, unless you configure a dedicated monitoring account.
FailoverClusters PowerShell module, is installed on the node that runs the extension.LOCAL SYSTEM privileges. For details, see Activation and setup.LOCAL SYSTEM, the account has read access to the cluster. For details, see Monitoring configuration.Activate the extension on one of the nodes for each cluster. The extension collects data for the whole cluster, so activating it on more nodes of the same cluster results in duplicate metrics.
Choose one of the nodes in each cluster to run the extension.
Install OneAgent on that node.
Configure the Dynatrace OneAgent EEC to run this extension with elevated LOCAL SYSTEM account privileges. To do this, add the following line to the C:\ProgramData\dynatrace\oneagent\agent\config\extensionsuser.conf file on that node. If the file doesn't exist, create it.
elevated_privileges_extensions=[com.dynatrace.extension.failover-cluster:*]
elevated_privileges_extensions is a comma-separated list of extensions to run as LOCAL SYSTEM instead of the default LOCAL SERVICE, in the format <extensionName>:<extensionVersion>. The * wildcard applies the setting to all versions of the extension. If the line already exists, add the extension to its list.
Restart the Dynatrace Extensions Controller service so that the change takes effect.
net stop "Dynatrace Extensions Controller"net start "Dynatrace Extensions Controller"
If the extension was already running before you changed the file, also restart the OneAgent service, or disable and then re-enable the monitoring configuration.
In Dynatrace Hub, find the Microsoft Windows Failover Cluster extension and select Add to environment.
Create a monitoring configuration for that node.
Optional: Enter a username and password for a dedicated monitoring account. For details, see Monitoring configuration.
Open the Windows Failover Cluster Overview dashboard.
To monitor more clusters, repeat these steps on one of the nodes in each cluster.
| Field | Description |
|---|---|
Username | Optional. Domain and username of a Windows account used to collect cluster data, in the format |
Password | Optional. Password for the account in Username. |
Frequency | How often the extension collects data, in minutes, from 1 to 1440. The default is 1 minute. |
Debug | Turns on debug logging for the extension. |
When you leave Username and Password empty, the extension collects data as LOCAL SYSTEM, so no credentials are needed. This is the recommended option. It works only if you configured OneAgent to run the extension with elevated privileges, as described in Activation and setup. Otherwise, the extension runs as LOCAL SERVICE, which has no access to the cluster, and reports no metrics.
To collect data as a dedicated read-only account instead, grant it the following on the node that runs the extension:
Read-only access to the cluster.
Grant-ClusterAccess -User "DOMAIN\username" -ReadOnly
Read access to the ROOT\MSCluster WMI namespace, with the Enable Account and Remote Enable permissions.
The Allow log on locally user right, because the extension starts an interactive logon session for the account.
The account doesn't need local administrator rights.
This extension package contains:
The extension only reads data. On each run, it calls the following PowerShell commands:
Get-ClusterGet-ClusterNodeGet-ClusterGroupGet-ClusterResourceGet-ClusterNetworkGet-ClusterNetworkInterfaceGet-WmiObject -Namespace ROOT\MSCluster -Class MSCluster_DiskThese commands return data for the whole cluster, not just the local node, so running the extension on one of the nodes covers the entire cluster.
There is no charge to use the extension. You are only charged for the data that the extension ingests.
The Microsoft Windows Failover Cluster extension ingests custom metrics, which consume Davis data units (DDUs) (Dynatrace Classic license) or Metrics powered by Grail (DPS), according to your license model.
By default, this extension queries for data every minute. To estimate the number of metric datapoints produced by your extension configuration, use the following list, which gives you a number of metrics per feature set and a multiplier value depending on which entity the metric is split by. Add all of these up to get the number of datapoints produced every minute.
default 1 x number of Windows Failover Clusters + 1 x number of Nodes + 1 x number of Resource groups + 1 x number of Resources + 1 x number of Networks + 1 x number of Network Interfaces + 1 x number of DisksStatuses 1 x number of Nodes + 1 x number of Resource groups + 1 x number of Resources + 1 x number of Networks + 1 x number of Network Interfaces + 1 x number of DisksCluster metrics 3 x number of Windows Failover ClustersNode metrics 2 x number of NodesResource group metrics 4 x number of Resource groupsResource metrics 2 x number of ResourcesInterface metrics 2 x number of Network InterfacesThese formulas assume that the extension runs on one of the nodes for each cluster. Running it on more nodes of the same cluster ingests the same metrics again and increases consumption accordingly.
In the Dynatrace Platform Subscription, metric ingestion consumes Metrics powered by Grail according to the number of ingested metric data points.
To calculate the approximate yearly consumption, apply the following calculation: <metric data points per minute> * 60 minutes * 24 hours * 365 days.
For example, at 64 metric data points per minute: 64 * 60 * 24 * 365 = 33,638,400 metric data points per year.
In the classic licensing model, metric ingestion consumes Davis data units (DDUs) at the rate of .001 DDUs per metric data point. Multiply the annual data point formula by .001 to estimate annual DDU usage.
For example, at 64 metric data points per minute: 64 * 60 * 24 * 365 * 0.001 = 33,638.4 DDUs per year.
The DDU cost doesn't include any log events or custom events the extension triggers. For more information, see DDU events.
When activating your extension using a monitoring configuration, you can limit monitoring to one of the feature sets. To work properly, the extension has to collect at least one metric after the activation.
In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.
All metrics that aren't categorized into any feature set are considered to be the default and are always reported.
A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.
| Metric name | Metric key | Description |
|---|---|---|
| Resource core state | windows.cluster.resource.is_core_resource | If the resource is essential to the cluster and cannot be deleted. |
| Resource persistent state | windows.cluster.resource.persistent_state | Whether the resource should be brought online or left offline when the Cluster Service is started. |
| Metric name | Metric key | Description |
|---|---|---|
| Node power state | windows.cluster.node.power_state | Indicates the current power state of the ComputerSystem and its associated OperatingSystem: Unknown, Full Power, Power Save, Power Cycle, Power Off. |
| Node drain status | windows.cluster.node.drain_status | The current node drain status of a node: Not Initiated, In Progress, Completed, Failed. |
| Metric name | Metric key | Description |
|---|---|---|
| Windows failover cluster fix quorum | windows.cluster.fix_quorum | Specifies whether the cluster is in a fix quorum state or not. |
| Windows failover cluster prevent quorum | windows.cluster.prevent_quorum | Specifies whether the cluster is in a prevent quorum state or not. |
| Windows failover cluster backup in progress | windows.cluster.backup | Specifies whether a backup is in progress or not. |
| Metric name | Metric key | Description |
|---|---|---|
| Windows failover cluster properties | windows.cluster.properties | Static metric that registers properties for the cluster. |
| Node state | windows.cluster.node.state | The current state of a node: Uknown, Up, Down, Paused, Joining. |
| Resource group state | windows.cluster.group.state | The current state of the resource group: Unknown, Online, Offline, Failed, Partial Online, Pending. |
| Resource state | windows.cluster.resource.state | Current state of the resource: Unknown, Inherited, Initializing, Online, Offline, Failed, Pending, Online Pending, Offline Pending. |
| Network state | windows.cluster.network.state | Current state of a network: Unknown, Unavailable, Down, Partitioned, Up. |
| Network interface state | windows.cluster.network.interface.state | The current state of the network interface: Unknown, Unavailable, Failed, Unreachable, Up. |
| Disk size | windows.cluster.disk.size | Physical size of the disk. |
| Metric name | Metric key | Description |
|---|---|---|
| Resource group failover period | windows.cluster.group.failover_period | Number of hours during which a maximum number of failover attempts can occur. |
| Resource group failover threshold | windows.cluster.group.failover_threshold | Maximum number of failover attempts that can be made on a group within the failover period. |
| Resource group core state | windows.cluster.group.is_core_group | Indicates if the resource group is essential to the cluster and cannot be deleted. |
| Resource group persistent state | windows.cluster.group.persistent_state | Whether a group should be left offline or brought online when the Cluster Service starts or the group is moved to another node. |
| Metric name | Metric key | Description |
|---|---|---|
| Node status | windows.cluster.node.status | — |
| Resource group status | windows.cluster.group.status | Current status of the object: OK, Degraded, Stressed, Pred Fail, Error, NonRecover, Starting, Stopping, Service. |
| Resource status | windows.cluster.resource.status | Current status of the object: OK, Degraded, Stressed, Pred Fail, Error, NonRecover, Starting, Stopping, Service. |
| Network status | windows.cluster.network.status | Current status of the object: OK, Degraded, Stressed, Pred Fail, Error, NonRecover, Starting, Stopping, Service. |
| Network interface status | windows.cluster.network.interface.status | Current status of the object: OK, Degraded, Stressed, Pred Fail, Error, NonRecover, Starting, Stopping, Service. |
| Disk status | windows.cluster.disk.status | Current status of the object: OK, Degraded, Stressed, Pred Fail, Error, NonRecover, Starting, Stopping, Service. |
| Metric name | Metric key | Description |
|---|---|---|
| Network interface availability | windows.cluster.network.interface.availability | The availability and status of the interface. |
| Network interface power on hours | windows.cluster.network.interface.power_on_hours | Number of consecutive hours that the interface has been powered, since its last power cycle. |
OneAgent most likely isn't configured to run the extension with elevated privileges, so the extension runs as LOCAL SERVICE. This account doesn't have access to the cluster, so the PowerShell commands that the extension runs return no data. Add elevated_privileges_extensions=[com.dynatrace.extension.failover-cluster:*] to the extensionsuser.conf file on the node that runs the extension, and then restart the services as described in Activation and setup.
Although OneAgent typically runs as LocalSystem account, Python extensions run as LOCAL SERVICE. The LOCAL SERVICE account has the minimum privileges on the local computer, and by default it has no access to the cluster, so it can't run the FailoverClusters cmdlets or read the ROOT\MSCluster WMI namespace. Therefore, OneAgent needs to be explicitly instructed to run this extension with LOCAL SYSTEM privileges.
The account usually lacks access to the cluster. When the extension logs the account on, User Account Control filters administrator group membership out of the account's token, so local administrator rights alone don't grant cluster access. Run Grant-ClusterAccess -User "DOMAIN\username" -ReadOnly on the node that runs the extension. In a workgroup cluster, grant access to the local account of that node.
This happens when the extension is active on more than one node of the same cluster. Each of those nodes reports data for the whole cluster. Edit your monitoring configurations so that the extension runs on one of the nodes for each cluster.