Out of Semaphores | Each transaction requires a semaphore to begin processing. Extended periods of semaphore unavailability will result in performance degradation and outages | Num free semaphores |
Excessive browser time | The calculated browser network time is very high | Client browser time |
Excessive client network time | The calculated client network time is very high | Client network time |
Excessive server response time | The average server response time has significantly slowed | Server response time |
Available DB connections exhausted | All database connections are in use, any new transactions will wait for DB availability. This typically indicates a critical problem and usually arises from poor SQL performance | Available DB connections |
Unable to access instance | The ServiceNow instance is completely unavailable | Log error count |
Very high rate of increase in errors detected | The error rate suddenly increased |
|
High rate of increase in errors detected |
|
|
Extremely slow worker queue | The worker queue processed has significantly degraded | Worker Queue |
Slow worker queue |
|
|
Extremely low app server memory | The ServiceNow application servers are running dangerously low on memory. This typically results from high concurrency and not enough application nodes, a long running transaction requiring a high amount of memory, or a memory leak | Percent free memory of Max |
Very low app server memory |
|
|
Low app server memory |
|
|
Stuck Outbound Email Queue | Email is not sending or the queue is growing much faster than it can be depleted. Typically this alert if the job processing email crashes, the SMTP gateway is unavailable, or an abnormally high number of emails were created | Email Queue (send-ready) |
Unusually high number of ignored inbound emails | A high number of inbound emails are being ignored | Email Queue (received-ignored) |
Outbound Email Queue fails to send consistently | Email is not sending. Typically this alert if the job processing email crashes, the SMTP gateway is unavailable, or another network problem | Email Queue (send-failed) |
Excessive number of ECC Queue in processing mode | The ECC queue has a significant number of processing items | ECC Queue (processing) |
High number of ECC Queue errors | A high number of ECC queue errors occurred | ECC Queue (error) |
High number of Import Set Run errors | A high number of import set run errors occurred. This may indicate that an import set did not properly execute | Import Set Run Queue (complete_with_errors) |
High number of Import Sets running | There is a high number of concurrent import sets running that may impact performance | Import Set Run Queue (running) |
Excessive number of Progress Workers currently running | Excessive number of Progress Workers are running | Progress Worker Queue (running) |
High number of System Event Queue errors | A high number of system event queue errors occurred | System Event Queue (error) |
High number of System Event Queue unprocessed | A high number of system event queue items are unprocessed |
|
Extremely high rate of increase in SQL Response Time | The overall SQL performance is degrading at a high rate. This may be an early warning for a database performance bottleneck | SQL response time (1 min) |
Alarmingly high SQL Response Time |
|
|
Very high rate of increase in SQL Response Time |
|
|
High rate of increase in SQL Response Time |
|
|
Extremely high rate of increase in SQL Inserts | There is a high number of SQL insert statements into the database. This typically will result from an import, integration, or scheduled job that is inserting a large amount of data. This may indicate the beginning of a performance issue | SQL inserts (1 min) |
Alarmingly high number of SQL Inserts |
|
|
Very high rate of increase in SQL Inserts |
|
|
High rate of increase in SQL Inserts |
|
|
Extremely high rate of increase in SQL Updates | There is a high number of SQL update statements into the database. This typically will result from an import, integration, or scheduled job that is updating a large amount of data. This may indicate the beginning of a performance issue | SQL updates (1 min) |
Alarmingly high number of SQL Updates |
|
|
Very high rate of increase in SQL Updates |
|
|
High rate of increase in SQL Updates |
|
|
Extremely high rate of increase in SQL Deletes | There is a high number of SQL update statements into the database. This typically will result from an import, integration, or scheduled job that is updating a large amount of data. This may indicate the beginning of a performance issue | SQL deletes (1 min) |
Alarmingly high number of SQL Deletes |
|
|
Very high rate of increase in SQL Deletes |
|
|
High rate of increase in SQL Deletes |
|
|
Extremely high rate of increase in Active User Sessions | High increases in the rate of Active User Sessions indicate a sudden spike in transaction concurrency by user traffic. This may reflect misconfigurations or security events such as a Denial of Service attack | Active sessions |
Alarmingly high Active User Sessions |
|
|
Very high rate of increase in Active User Sessions |
|
|
High rate of increase in Active User Sessions |
|
|
Extremely high rate of increase in Logged in User Sessions | A high rate in the number of users are logged into the system. These may be an early indication of a problem or security issue occuring | Logged in sessions |
Alarmingly high Logged in User Sessions |
|
|
Very high rate of increase in Logged in User Sessions |
|
|
High rate of increase in Logged in User Sessions |
|
|
Extremely high rate of increase in SQL Insert Response Time | The SQL insert performance is rapidly slowing down. This may be an early warning sign of an upcoming performance problem | SQL insert response |
Alarmingly high number of SQL Insert Response Time |
|
|
Very high rate of increase in SQL Insert Response Time |
|
|
High rate of increase in SQL Insert Response Time |
|
|
Extremely high rate of increase in SQL Update Response Time | The SQL update performance is rapidly slowing down. This may be an early warning sign of an upcoming performance problem | SQL update response |
Alarmingly high number of SQL Update Response Time |
|
|
Very high rate of increase in SQL Update Response Time |
|
|
High rate of increase in SQL Update Response Time |
|
|
Extremely high rate of increase in SQL Delete Response Time | The SQL delete performance is rapidly slowing down. This may be an early warning sign of an upcoming performance problem | SQL delete response |
Alarmingly high number of SQL Delete Response Time |
|
|
Very high rate of increase in SQL Delete Response Time |
|
|
High rate of increase in SQL Delete Response Time |
|
|