The Alert Types screen displays all of the available alerts in WISdom. Alert association with Resources and alert configuration happens in Profiles.
- Use the drop-down menus to further filter the list by Profile and/or Alert Category.
Alert Types
This card displays the available alerts in a table format with sortable columns, as follows:
- The Name column displays the name of the alert.
- The Description column displays a snippet of the description text for the alert.
- The Profiles column displays the number of profiles that use the alert.
- Click the icon to see a pop-up with the profile names.
- The Alert Categories column displays the number of categories the alert is a member of.
- Not all alerts have categories.
- Click the icon to see a pop-up with the category names.
Note: Click on column headings to sort the list in ascending or descending order. The table is also searchable using the magnifying glass icon at the top-right corner of the card. Click on the action icon (three dots) at the end of the row or click the Name or Description field to display the Alert Type Details flyout.
Alert Type Details Flyout
This flyout displays more details for the selected alert and is made up of Three cards:
The Alert Name card displays the name of the alert in the title bar along with Default Severity, Evaluation Frequency, Alert Categories, and Description.
The Recommendations card displays recommendations for addressing the alert.
The Tolerance/Rules card displays the Alerting Logic and Tolerance Settings available for the alert as well as the Rules applied to the alert.
Editing Alerts
Alert definitions can be modified using the [Edit] button located at the bottom right, next to the [Close] button. This edit function allows users to update various aspects of the alert, including its default Severity, assigned Categories, Description, and Recommendations. Users can also modify existing Tolerance settings to better fit their environment and add custom Tolerance settings as needed.
Rules Tab
See Alert Rules for more details.
The Rules tab in the flyout includes editing capabilities accessible via the action icon on the right side of each rule. The available options are as follows:
- View Rule: Opens a flyout with detailed rule information.
- Edit Rule: Allows for rule editing directly within the flyout, eliminating the need to navigate to the Alert Rules section.
- Enable Rule: Easily enable a rule that is currently in a disabled state.
- Delete Rule: Provides a straightforward way to remove a rule, completely deleting it from both the alert and the Alert Rules.
Alert Types Reference List
This page lists all built-in alert types available in WISdom, along with a concise description and alert category for each. Use this as a quick reference when building Profiles or reviewing which alerts apply to your environment.
New Alerts and Custom Alerts
Newly added alerts may not be included in the list. While Custom alerts are not listed here. To view all alerts, including any custom alerts configured for your environment, navigate to Admin Console > Monitoring > Alert Types.
For details on configuring alerts in a Profile, see Profiles. For information on creating exception rules for individual alerts, see Alert Rules.
| Alert Name | Description | Alert Categories |
|---|---|---|
| Azure SQL Database High CPU Usage | Monitors CPU utilization on an Azure SQL Database and triggers when usage exceeds defined thresholds, indicating potential performance bottlenecks or resource contention. | — |
| CPU High Processor Queue Length | Monitors the number of threads waiting in the processor queue. A sustained high queue length (greater than 2 per CPU core) indicates CPU bottlenecks and degraded SQL Server performance. | CPU, Performance |
| CPU Pressure with High Context Switches | Monitors CPU utilization alongside context switches per second to identify performance bottlenecks caused by thread management issues or CPU scheduling problems. | CPU, Performance |
| Daily Dump Files | Monitors the creation of SQL Server dump files over time and triggers when the quantity exceeds defined thresholds. Differs from SQL Stack Dump File Generated in that it tracks volume over time rather than individual events. Recommended only as a temporary noise-reduction measure while resolving an underlying issue. | — |
| High CPU Privileged Time | Monitors the percentage of processor time spent in kernel mode. Elevated privileged time (greater than 25%) may signal system-level bottlenecks affecting SQL Server performance. | CPU, Performance |
| High CPU Utilization | Monitors CPU utilization across all processors on the Windows Server hosting SQL Server and triggers when usage exceeds defined thresholds, indicating potential performance bottlenecks or resource contention. | CPU, Performance |
| High Disk Latency | Measures the average time required to complete a disk read or write operation. High values indicate slow disk performance due to contention, latency, or hardware bottlenecks that can negatively impact SQL Server response times. | — |
| High Number of Deadlocks | Monitors the frequency of deadlocks occurring in SQL Server instances and triggers when the number exceeds defined thresholds, indicating concurrency issues that may impact performance and application stability. | Database Contention |
| High Number of SQL Blocked Processes | Triggers when multiple SQL Server processes are blocked for an extended period, indicating potential deadlocks, resource contention, or long-running transactions that are preventing other processes from completing. | Database Contention |
| High tempdb Version Store Size | Monitors the size of the tempdb version store used for row versioning in snapshot isolation and online index operations. Triggers when the version store grows excessively, risking tempdb space exhaustion and query failures. | Availability |
| Identity Column Value Overflow Warning | Monitors the percentage of the maximum value used by the identity column of each table and triggers when usage exceeds the configured threshold. | Capacity Planning |
| Large SQL Server Error Log | Monitors SQL Server error log file size and triggers when it exceeds predefined thresholds. Large error logs can indicate excessive logging, system issues, or poor log management that may impact server performance and storage. | Capacity Planning |
| Long Running Sleeping Transaction | Monitors transactions in a SLEEPING state that exceed a specified duration threshold. Inactive but open transactions can hold locks, block other processes, and consume system resources unnecessarily. | Performance |
| Long-Running Blocking Chain | Detects queries that have been blocked for an extended period, potentially causing performance degradation and application timeouts. Monitors blocking chains to identify both blocking and blocked sessions and the resources involved. | Blocking |
| Low Database File Free Space | Triggers when a database data file (.mdf, .ndf) or log file (.ldf) has low available space and auto-growth is disabled. Without available space, new transactions may fail, causing application errors and data insertion or transaction log failures. | — |
| Low Disk Space | Monitors available disk space on volumes and triggers when free space falls below defined thresholds, helping prevent system crashes and database outages. | Capacity Planning |
| Low Disk Space (Critical) | Monitors available disk space on volumes and triggers at a critical threshold when free space falls below defined levels, helping prevent system crashes and database outages. | Capacity Planning |
| No Recent Log Backup | Monitors transaction log backup history for databases in FULL or BULK_LOGGED recovery models. Triggers when a log backup has not occurred within the defined interval, which can lead to excessive log file growth and data loss exposure. | Availability |
| Oracle Connection Status Failed | Triggers when SQL Server is unable to establish or maintain connectivity with a linked Oracle database, impacting cross-database operations and data integration processes. | Availability |
| OS Paging is High | Monitors system memory usage and page file activity. Triggers when the Pages/sec counter exceeds defined thresholds, indicating operating system memory pressure that could impact SQL Server performance. | Performance, OS Memory |
| SQL Availability Group Database Health Status | Monitors the health and synchronization status of databases participating in Always On Availability Groups. Triggers when a database deviates from the expected synchronization or health state, which may indicate data movement issues, network problems, or storage constraints. | Availability Groups |
| SQL Availability Group Failover | Triggers when a failover event has occurred or is in progress within an Availability Group, requiring immediate verification of successful role transition, application connectivity, and data synchronization status. | Availability Groups |
| SQL Availability Group Latency is High | Monitors synchronization health between primary and secondary replicas. Triggers when secondary replicas fall behind in receiving or applying transaction logs, indicating potential data loss risk if a failover occurs. | Availability Groups, Latency |
| SQL Availability Group Linked Server Mismatch | Detects differences in linked server configurations between Availability Group replicas that can cause application connectivity issues and data access failures during failover events. | Availability Groups |
| SQL Availability Group Long Recovery Time | Monitors the recovery time objective (RTO) for Availability Group synchronization and triggers when the estimated failover recovery time exceeds critical thresholds, indicating data synchronization delays between replicas. | Availability Groups |
| SQL Availability Group Node Job Mismatch | Detects when SQL Server Agent jobs are not synchronized across Availability Group nodes, potentially causing job execution failures or duplicate runs during failover events. | Availability Groups |
| SQL Availability Group Node Login Mismatch | Detects mismatched SQL Server logins and permissions across Availability Group nodes, which can cause application connectivity issues during failover. | Availability Groups |
| SQL Availability Group Unhealthy | Monitors the health state of Always On Availability Groups by tracking synchronization status, replica availability, and failover readiness. Triggers when any availability group reports a non-healthy state. | Availability Groups |
| SQL Database is in an Abnormal State | Monitors database health status and triggers when a database enters states such as RECOVERING, RECOVERY_PENDING, SUSPECT, or EMERGENCY, which can prevent database access and indicate corruption or missing files. | Availability |
| SQL Database is Offline | Monitors for databases that are unavailable to users and applications, whether due to administrative action, resource constraints, or failed recovery attempts. | Availability |
| SQL High Latch Waits | Monitors excessive latch wait times in SQL Server, indicating internal resource contention. Triggers when average latch wait time exceeds defined thresholds, suggesting memory pressure or synchronization bottlenecks that degrade performance. | Performance |
| SQL Instance Low Disk Space | Monitors disk space availability across the entire SQL Server instance and triggers when cumulative free disk space falls below critical thresholds, risking transaction log growth failures and instance-wide downtime. | Capacity Planning |
| SQL Pending Memory Grants | Monitors the number of processes waiting to acquire workspace memory. Triggers when queries are queued due to insufficient memory grants, which can cause performance degradation and query timeouts. | Performance, Database Memory |
| SQL Replication Agent Failed | Triggers when any replication agent (Snapshot, Log Reader, or Distribution Agent) fails to execute successfully, indicating potential synchronization issues between publisher and subscriber databases. | Availability, Replication |
| SQL Replication High Latency | Monitors the delay between source (Publisher) and destination (Subscriber) servers in SQL Server replication. Triggers when replication lag exceeds the defined threshold, which may indicate performance or network issues causing the subscriber to fall out of date. | Replication, Latency |
| SQL Server Agent Alert Fired | Triggers when a SQL Server Agent Alert fires, providing visibility into agent-level events configured directly in SQL Server. | — |
| SQL Server Agent Job Failed | Triggers when a SQL Server Agent Job fails, indicating that a scheduled task did not complete successfully. | — |
| SQL Server Agent Offline | Monitors the operational status of the SQL Server Agent service. Triggers when the service stops running, potentially impacting automated database operations, maintenance plans, and scheduled backups. | Availability |
| SQL Server Database File With Suspect Pages Detected | Monitors for corrupt database pages and triggers when suspect pages are detected in a database data or log file, indicating a potential data integrity issue that requires investigation. | — |
| SQL Server Database Suspect Pages Fixing Increase | Triggers when previously flagged corrupt pages have been fixed, providing confirmation that a data integrity issue has been resolved. | — |
| SQL Server Not Responding | Monitors SQL Server service responsiveness and triggers when the instance becomes unresponsive to client connections, query requests, or management operations, which may indicate severe resource constraints, deadlocks, or memory pressure. | Availability |
| SQL Server Offline or Unresponsive | Monitors SQL Server service availability and triggers when the service stops unexpectedly or fails to respond within 60 seconds, potentially indicating service failure or system-wide issues. | Availability |
| SQL Stack Dump File Generated | Monitors for the creation of SQL Server dump files (.mdmp) generated when SQL Server encounters critical errors or crashes. Early detection enables prompt investigation of the underlying cause. | Stack Dump |
| SQL System Database Offline | Monitors the operational status of critical SQL Server system databases (master, model, msdb, tempdb) and triggers when any system database becomes inaccessible or transitions to an offline state. | Availability |
| Unknown SQL Server Connection Error | A catch-all alert for errors WISdom encounters when connecting to SQL Server that are not related to permissions or connectivity. | Availability |
| WISdom Data Collector Authentication Failed | Triggers when the WISdom collector service cannot connect to a monitored SQL Server instance due to authentication or permission issues, impacting monitoring capabilities and data collection. | — |