Failover to a standby server in the SolarWinds Platform
This SolarWinds Platform topic applies only to the following products:
Hybrid Cloud Observability Essentials — Hybrid Cloud Observability Advanced
DPAIM — IPAM — LA — NAM — NCM — NPM — NTA — SAM — SCM — SRM — UDT — VMAN — VNQM — WPM
Use this alert action in conjunction with SolarWinds High Availability. You can use alerts to refine your monitoring and force a failover when specific conditions exist.
For example, if you want to force a failover to your secondary server when the primary server's CPU load is more than 85% for more than 20 minutes, create an alert that monitors the primary server and choose the Failover Action in the trigger action. You can then use the Failover Action as the reset action to set the primary server as active server.
An HA pool must be set up to configure this action.
When editing or adding an alert, click Add Action in the Trigger or Reset Action section of the Alert Wizard.
- Select the Failover Action, and then click Configure Action.
- Select the pool you want to use to failover to the backup server.
Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. This schedule only applies to the alert action you are editing.
This is often used to prevent an action from occurring during specific windows.
Select how frequently this action occurs for each triggered alert in Execution Settings.
Click Add Action.
The action is added to the trigger or reset action list, and you can test the action using the Simulate button. When the trigger or reset conditions of the alert are met, the HA pool you selected fails over to the secondary server.