Configure SolarWinds Platform High Availability settings
This SolarWinds Platform topic applies only to the following products:
Hybrid Cloud Observability Essentials — Hybrid Cloud Observability Advanced
DPAIM — EOC — IPAM — LA — NAM — NCM — NPM — NTA — SAM — SCM — SRM — UDT — VMAN — VNQM — WPM
Click Settings > My Deployment, and then click High Availability Settings in the top right of the High Availability Deployment Summary to access these options.
By default, SolarWinds Platform High Availability (HA) is enabled and an email is sent when a failover occurs. You can change the default interval and modify your default email settings.
Reset to default
Click to reset all settings to defaults.
Default interval to consider a member as down in a pool
Define how long the active pool member can be down before a failover occurs. Provide the interval in seconds.
Keep the secondary server disabled...
Define how long the secondary server should stay disabled after a failover to prevent continuous failover. Provide the interval in minutes.
Email me when server status is changed
Choose to receive email messages when a failover occurs. This is enabled by default and uses the default email settings to send notifications. HA notifications do not depend on the SolarWinds alerting service or the SolarWinds Platform database, so you still receive HA alerts when the service or database is down.
Email me when facility status is changed
Receive email messages when the status of a low-level component changes, such as the percent used of the CPU or RAM.
Facilities are used to gauge the health of the system and may trigger a failover condition. For example, the computer may restart and failover if the CPU stays over 100% for a significant amount of time.
When you enable this setting, the default email address might start getting a huge number of email messages.
Email me when resource status is changed
Receive email messages when a SolarWinds Platform component changes, such as the polling or job engines.
Resources are generally SolarWinds-specific processes or services monitored by HA that can trigger a failover condition. For example, if the job engine is down and does not restart successfully, the active server fails over to the standby server.
When you enable this setting, the default email address might start getting a huge number of messages.