Alert Category | Rule Description (criteria to trigger email) |
| CPU | when System CPU average usage is continuously greater than “N% (eg 60%)” since Last N minutes |
| Memory | when System Memory average usage is continuously greater than “N% (eg 60%)” since Last N hour |
| Low Disk Storage | When Disk Storage space is found to be less than “N% (eg 30%)” space free |
| SQL Server Log Scan | There are multiple conditioned that can be detected from SQL Server Logs. SQL Planner look for any messages starting from specific strings : |
| a) Error b) dead | |
| c) fail d) invalid | |
| e) Terminate f) Resolving – For Failover event | |
| if any of these strings were found in SQL server log since last “N Minute”, it triggers email. These conditions are very generic to various issues that SQL server raise and is categorised and kept in Log Error reporting page within SQL planner. | |
| Low Database (Data, Log File) Space | When Database data or Log file space is found to be less than “N% (eg 30%)” space free |
| Deadlock | Whenever Deadlock occurred |
| Blocked | When block on specific thread found for more than “N Seconds” |
| Server Down | When SQL Server instance is down or not reachable |
| SQL Server Agent Job Fails | When Any agent Job failed or did not completed successfully |
| Database Full Backup Missing | When selected database full backup was not performed since last “N days” |
| Database Differential Backup Missing | When selected database differential backup was not performed since last “N Hours” |
| Database Log Backup Missing | When selected database Log backup was not performed since last “N Hours” |
| Database not Online | When Selected database is not online – offline or single user mode – Under Development |
| SQL Server Failover | Whenever SQL server failover occurred |
| SQL Server Reboot | When there was any occurrence of SQL server restart |
| IO Taking longer than 15 sec | SQL Server database IO activity spend more than 15 second |
| Database State in Suspend, Recovery, Emergency, Offline , Recovery Pending | when Database State goes to in Suspend, Recovery, Emergency, Offline , Recovery Pending |
| SQL Planner Backup Job Status | When SQL Planner Backup Job fails or successfully completed |
| corrupt errors | When Database consistency reports corruption |
| Fatal Error | When SQL server Log has any information about Fatal related messages |
| Memory Pressure | When SQL server Log has any information about Memory Pressure related messages |
| Severe Error | When SQL server Log has any information about Severe related messages |
| Missing Log Block | When SQL server Log has any information about Missing log block chain in Always on database environment related messages |
| Operating System Error | When SQL server Log has any information about OS related Error messages |
| SQL Server Always On Missing Log Block | When log sequence during Always On DB continuous sync in AO environment is missed then MISSING LOG BLOCK IN ALWAYS ON DB alert is raised |
| SQL Server Always On DB Secondary Lag Delay | When log flow to secondary nodes takes longer time. |
| SQL Server Always On Status as – SUSPEND_FROM_USER ,SUSPEND_FROM_PARTNER, SUSPEND_FROM_RESTART, SUSPEND_FROM_REDO, SUSPEND_FROM_APPLY, SUSPEND_FROM_CAPTURE, SUSPEND_FROM_UNDO, SUSPEND_FROM_REVALIDATION, SUSPEND_FROM_XRF_UPDATE | When Always on Status changes because of following activities : A user manually suspended data movement, The database replica is suspended after a forced failover, The database replica was suspended before the database was restarted, An error occurred during the redo phase, An error occurred when writing the log to file, An error occurred while capturing log on the primary replica, An error occurred during the undo phase, Log change mismatch is detected on reconnection, Unable to find the common log point |