Predefined situations descriptions and formulas (that run manually)
Situations that are run manually
- WebSphere® application server
- WebSphere application server portal
- WebSphere application server Process
- WebSphere application server ESB
- Lotus® Workplace server
- To start, stop, or edit any of these situations, see Accessing the situations.
- For information about situations that run automatically, see Predefined situations descriptions and formulas (that run automatically).
WASDBConnectionPoolThrdTimeout monitors the thread timeout count. This situation issues a Critical condition whenever the timeout count is greater than zero. Its formula is:
If
DB_Connection_Pools.Threads_Timed_Out is greater than 0
then
the situation WASDBConnectionPoolThreadTimeout is true.
WASContainerTransactionRollback monitors the rollback count of the WebSphere application server. This situation issues a Critical alert whenever the count becomes nonzero. Its formula is:
If
Container_Transactions.Global_Transactions_Rolled_Back is greater than 0
or
Container_Transactions.Local_Transactions_Rolled_Back is greater than 0
then
the situation WASContainerTransactionRollBack is true.
WASEJBCreateTimeHigh monitors the average time of a bean create call and issues a Critical alert when the time is longer than 2 seconds. Its formula is:
If
Enterprise_Java_Beans.Create_Average_Time is greater than 2000
then
WASEJBRemoveTimeHigh monitors the average time of a bean remove call and issues a Critical alert when the time is longer than 2 seconds. Its formula is:
If
Enterprise_Java_Beans.Remove_Average_Time is greater than 2000
then
WASEJBMethodResponseTimeHigh monitors the average response time on remote interface methods for all beans. This situation issues a Critical alert if the response time is longer than 2 seconds. Its formula is:
If
Enterprise_Java_Beans.Method_Average_Response_Time is greater than 2000
then
WASThreadFreeLow monitors the average free threads in the pool and issues a Critical alert if the number of threads is less than 200. Its formula is:
If
Thread_Pools.Average_Free_Threads is greater than or equal to 0
and
Thread_Pools.Average_Free_Threads is less than 200
and
Thread_Pools.Average_Active_Threads is greater than or equal to 0
then
WASDataSrcConWaitTimeHigh monitors the average time an application has to wait for a connection. This situation issues a Critical alert if the wait time is longer than 2 seconds. Its formula is:
If
Datasources_Connection_Average_Wait_Time is greater than 2000
then
WASReqSQLExecuteTimePercentHigh monitors the percentage of time the request spends executing a JDBC database. This situation issues a Critical alert if the percentage of time is higher than 80%. Its formula is:
If
Request_Analysis.SQL_Execute_Time_Percent is greater than 80
then
WASReqSQLQueryTimePercentHigh monitors the percentage of time the request spends querying a JDBC database. This situation issues a Critical Alert if the percentage of time is higher than 80%. Its formula is:
If
Request_Analysis.SQL_Query_Time_Percent is greater than 80
then
WASReqSQLUpdateTimePercentHigh monitors the percentage of time the request spends updating a JDBC database. This situation issues a Critical Alert if the percentage of time is higher than 80%. Its formula is:
If
Request_Analysis.SQL_Update_Time_Percent is greater than 80
then
WASDBConPAverageUsageTimeHigh monitors the average time that a connection in use is high. This situation issues a Critical alert if the average time the connection in use is longer than 2 seconds. Its formula is:
If
DB_Connection_Pools.Average_Usage_Time is greater than 2000
then
If
DB_Connection_Pools.Percent_Used is greater than 80
then
WASDBConPAvgWaitTimeHigh monitors the average time that a client has to wait for a connection. This situation issues a Critical alert when the time period is longer than 2 seconds. Its formula is:
If
DB_Connection_Pools.Average_Wait_Time is greater than 2000
then
WASJ2CCPAverageUsageTimeHigh monitors the average time that connections are in use (it measures from when the connection is allocated to when it is returned). This situation issues a Critical alert when the combined connection allocation and return time are longer than 2 seconds. Its formula is:
If
J2C_Connection_Pools.Average_Usage_Time is greater than 2000
then
WASJ2CCPAvgWaitTimeHigh monitors the average wait time until a connection is granted. This situation issues a Critical alert if the time period is longer than 2 seconds. Its formula is:
If
J2C_Connection_Pools.Average_Wait_Time is greater than 2000
then
WASCTGlbTransDurationHigh monitors the average duration of global transactions. This situation issues a Critical alert if the time period is longer than 2 seconds. Its formula is:
If
Container_Transactions.Global_Transaction_Duration is greater than 2000
then
WASCTLclTransDurationHigh monitors the average duration of local transactions. This situation issues a Critical alert if the time period is longer than 2 seconds. Its formula is:
If
Container_Transactions.Local_Transaction_Duration is greater than 2000
then
WASPortalPageResponseTime monitors the portal page response time and issues a Critical alert when the average request response time is higher than 2 seconds. The formula is:
If
Portal_Page_Summary.Average_Response_Time is greater than 2000
then
the situation WASPortalPageResponseTime is true.
WASPortletResponseTime monitors the portlet response time and issues a Critical alert when the average request response time is higher than 2 seconds. The formula is:
If
Portlet_Summary.Average_Response_Time is greater than 2000
then
the situation WASPortletResponseTime is true.
WASServletsJSPsError monitors the error count for servlets and JSPs invoked by a WebSphere application server application. This situation issues a Critical condition whenever the count becomes nonzero. Its formula is:
If
Servlets_JSPs.Error_Count is greater than 0
then
WASSrvlSessAvgActiveSessionHigh monitors the average number of concurrently active sessions. This situation issues a Critical alert if the average number of concurrently active sessions is greater than 100. Its formula is:
If
Servlet_Sessions.Average_Concurrently_Active_Sessions is greater than 100
then
the situation WASSrvlSessAvgActiveSessionHigh is true.
WASSrvlSessExtReadTimeHigh monitors the time it takes to read the session data from the persistent store. This situation issues a Critical alert if the time period is longer than 2 seconds. Its formula is:
If
Servlet_Sessions.External_Read_Time is greater than 2000
then
WASSrvlSessExtWriteTimeHigh monitors the time it takes to write session data to persistent store. This situation issues a Critical alert if the time period is longer than 2 seconds. Its formula is:
If
Servlet_Sessions.External_Write_Time is greater than 2000
then
WASThreadPoolPercentMaxed monitors the average usage time of all threads, and issues a Critical condition whenever that time exceeds 100%. The formula is:
If
Thread_Pools.Percent_of_Time_Pool_at_Max is greater than 100
then
the situation WASThreadPoolPercentMaxed is true.
WASWebApplicationError monitors the error log status of the WebSphere server and issues a Critical condition when an error occurs. Its formula is:
If
Web_Applications.Error_Count is greater than 0
then