Nodes

There are two kinds of Nodes in xMatters:

Node Types

Node Type

Description

Application Server

Receives events and converts them into notifications. Application Server Nodes may also contain Device Engines.

Notification Server

Contains Device Engines, solely responsible for delivering notifications and receiving responses from Devices.

Note: For deployments with multiple Nodes, the time zone for the operating system must be synchronized across all Application Server Nodes and web servers.

Failover

Depending on its licensing, an xMatters installation can include up to three Application Server Nodes. When multiple Application Servers Nodes share the database, they are considered to be in failover configuration. Note that Clusters do not affect failover; they are used strictly to specify message routing preferences.

Node failure detection

Every 10 seconds, each Application Server timestamps the database. At the same rate each application server examines the timestamps of other application. If the last timestamp of a node is more than 30 seconds old, that node is considered to have failed. The node that detects this assumes ownership of the processes of the failed node.

Undelivered Alerts

Alerts within the xMatters system are stored only in the database. If an Application Server Node fails, its Alerts remain in the database until the Application Server Node restarts, or another Node detects its failure.

Note: Whenever failover occurs, an email Alert is automatically sent to the recipient specified in the Health Monitor settings. For more information, see Global Configuration.