Failsafe Conditions have an assigned default severity and associated tags, and will affect your environment's Environmental Health Score (EHO). Failsafe Conditions fall into the following two categories:
- Connection Status
Instance Status Failsafe Conditions are met when an instance goes Offline or Online. The Offline condition for an instance is met if a server crashes or becomes unavailable. The Online condition is met once that instance becomes available again. Failsafe Error Conditions are met when there's an error detected in a SQL Sentry monitoring service or related monitoring process.
Note: The Log to Database action and the Send Email action are configured by default for all Failsafe Conditions. You can be alerted when an instance goes offline, or when the SQL Sentry monitoring service experiences an error and is unable to perform its work.
Configure Actions for Failsafe Conditions
Configure actions in response to Instance Status Failsafe Conditions being met at these levels: shared groups (Global), site, computer group, computer, and instance. Configure actions in response to Failsafe Error Conditions being met at the global level (shared groups) or at the site level.
To add a Failsafe Condition, complete the following steps:
1. Open the Navigator pane (View > Navigator), and then select the desired node where you want to configure an action. 2. Open the Conditions Pane (View > Conditions) and then select Failsafe Conditions from the dropdown menu.
3. Select Add in the Conditions pane to open the Actions Selector. Expand the applicable object and condition. Use the checkbox(es) to select which actions should be taken in response to this condition being met, and then select OK.
Additional Information: For more information about actions that can be taken when a condition is met, see the Actions topic.
The following is a complete list of all Failsafe Conditions.
Amazon RDS for SQL Server
|Offline||Amazon RDS is offline or otherwise inaccessible.|
|Online||Amazon RDS is online and accessible.|
|Offline||Analysis Services is offline or otherwise inaccessible.|
|Online||Analysis Service is online and accessible.|
Analytics Platform System
|Offline||Analytics Platform System is offline or otherwise inaccessible.|
|Online||Analytics Platform System is online and accessible.|
Azure SQL Data Warehouse
|Offline||Azure SQL Data Warehouse is offline or otherwise inaccessible.|
|Online||Azure SQL Data Warehouse is online and accessible.|
Azure SQL Database
|Offline||Azure SQL Database is offline or otherwise inaccessible.|
|Online||Azure SQL Database is online and accessible.|
Note: Depending on your product version, the condition names and descriptions may reference SQL Sentry or SentryOne for the monitoring service and database.
|Device Connection Status Monitor: Error||An error was encountered by the Device Connection Status Monitor, the process responsible for monitoring device connections.|
|Event History Monitor: Error||An error was encountered by the Event History Monitor, the process responsible for historical data collection from various sources.|
|Job Monitor: Error||An error was encountered by the Job Monitor, the process responsible for collecting data for running SQL Server Agent Jobs.|
|Message Processor: Message Action Throttled||The Message Processor reached its max messages per interval threshold, and at least one message was throttled. Subsequent messages are sent to the Actions Log. For more information, see SQL Sentry Monitoring Service > Settings.|
|Monitoring Service: Action Failed||The SQL Sentry Monitoring Service attempted to execute an action, but the action failed. For example, the Send Email Action can fail if the SMTP Server is unavailable.|
|Monitoring Service: Performance Collection Failed||The Performance Monitor encountered an error while collecting data for a specific performance counter.|
|Monitoring Service: Repository Error||An error occurred while writing data to the SQL Sentry database.|
|Monitoring Service: Send Heartbeat Error||The Monitoring Service encountered a critical error while sending a heartbeat to the SQL Sentry database.|
|Monitoring Service: SQL Sentry Database Offline||The SQL Sentry database is offline or otherwise inaccessible.|
|Monitoring Service: SQL Sentry Database Online||The SQL Sentry database is online and accessible.|
|Monitoring Service: Synchronization Error||The SQL Sentry Monitoring Service encountered a critical error while synchronizing settings from the SQL Sentry database with its configuration management thread.|
|Performance Analysis Data Writer: Error||The Performance Analysis data writer encountered an error|
|Performance Monitor: Error||An error was encountered by the Performance Monitor, the process responsible for collecting performance data.|
|Reporting Services Monitor: Error||An error is encountered by the Reporting Services Monitor, the process responsible for collecting data for SSRS reports.|
|vCenter Collector: Error||The vCenter collector encountered an error.|
|Windows Task Scheduler Monitor: Error||An error was encountered by the Task Scheduler Monitor, the process responsible for collecting data for Windows Tasks.|
Note: Make use of Condition Settings when configuring alerts for conditions. Condition filters are available which can help fine tune exactly when a condition is considered met.
|SQL Server Availability Group|
|The SQL Availability Group failed over.|
|SQL Availability Replica Healthy||The SQL Availability Replica is healthy.|
|SQL Availability Replica Unhealthy||The SQL Availability Replica is unhealthy.|
|SQL Server Agent: Offline||SQL Server Agent is offline or otherwise inaccessible.|
|SQL Server Agent: Online||SQL Server Agent is online and accessible.|
|SQL Server Cluster Failover||The SQL Server cluster failed over.|
|SQL Server Instance: Offline||SQL Server is offline or otherwise inaccessible.|
|SQL Server Instance: Online||SQL Server is online and accessible.|
|Offline||Trintri VMstore is offline or otherwise inaccessible.|
|Online||Trintri VMstore is online and accessible.|
|Offline||vCenter is offline or otherwise inaccessible.|
|Online||vCenter is online and accessible.|
|Offline||VMware host is offline or otherwise inaccessible.|
|Online||VMware host is online and accessible.|
|Offline||Windows is offline and other inaccessible.|
|Online||Windows is online and accessible.|
|Offline||Windows instance is offline or otherwise inaccessible.|
|Online||Windows instance is online and accessible.|