IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
Predefined situations-descriptions and formulas (that run automatically)
- Overview
- WASAppDiscovered
- WASAppHealthBad
- WASAppHealthFair
- WASAppHealthGood
- WASError
- WASHighCPUPercentUsed
- WASHighGCTimePercent
- WASHighResponseTime
- WASNotConnected
- WASOutofHeapSpace
- WASAvgHeapSizeAfterGCHigh
- WASJ2CConnectionPoolUsageMaxed
- WASDBConnectionPoolUsageMaxed
Overview
The following predefined situations run automatically from the WebSphere Agent and support the following applications servers unless stated otherwise.
- WAS
- WAS portal
- WAS Process
- WAS ESB
- Lotus Workplace server
To start, stop or edit any of these situations see Access the situations.
For information about situations that run manually see Predefined situations descriptions and formulas (that run manually).
WASAppDiscovered
Monitor WebSphere applications deployed in the application server. Issue an Informational alert when a new application is discovered. The monitoring agent checks for new applications each time it connects to the data collector or when an application is deployed when the data collector is already active.
If Application_Monitoring_Configuration.Monitoring_Status equals 0 then the situation WASAppDiscovered is true
This situation does not support Lotus Workplace server.
The Take Action command Start_Baselining, associated with the WASAppDiscovered situation, enables automatation of baselining of newly discovered applications.
WASAppHealthBad
Monitor the overall application health. Issue a Critical alert when the application health is bad.
If Application_Health_Status.Web_Tier_Health equals 3 then the situation WASAppHealthBad is true
The Take Action command Set_Application_Monitoring, associated with WASAppHealthBad situation, increases the request monitoring rate for applications generated alert. Collect more detailed performance data. Collect the precise data about each application tier health level.
WASAppHealthFair
Monitor the overall application health. Issue a warning alert when application health is fair.
If Application_Health_Status.Application_Health equals 2 then the situation WASAppHealthFair is true.
The Take Action command Set_Application_Monitoring, associated with WASAppHealthFair situation, raises the request monitoring level for applications generated alert. This command enables you to collect detailed performance data that helps to pinpoint a bottleneck down to particular application tiers.
WASAppHealthGood
Monitor the overall application health. Issue an Informational alert when application health is good.
If Application_Health_Status.Application_Health equals 1 then the situation WASAppHealthGood is true.
The Take Action command Set_Application_Monitoring, associated with the WASAppHealthGood situation, lowers the request monitoring level, and reduces the monitoring workload.
WASError
Monitor the error severity for a single WAS. Issue a Critical condition whenever that severity is greater than 21.
If Log_Analysis.Severity is greater than 21 then the situation WASError is true.
WASHighCPUPercentUsed
Monitor the percentage of the CPU being consumed. Issue a Critical condition whenever that time exceeds 80%.
If Application_Server.CPU_Used_Percent is greater than 80 then the situation WASHighCPUPercentUsed is true.
WASHighGCTimePercent
Monitor the percentage of time being spent by the garage collector. Issue a Critical condition whenever that time exceeds 80%.
If Garbage_Collection_Analysis.Real_Time_Percent is greater than 80 then the situation WASHighGCTimePercent is true.
WASHighResponseTime
Monitor the average request response time. Issue a Critical condition whenever that time exceeds 2 seconds.
If Request_Times_and_Rates.Average_Request_Response_Time is greater than 2000 then the situation WASHighResponseTime is true.
WASNotConnected
Monitor the connection between the ITCAM for WebSphere data collector running in an application server and the ITCAM Agent for WebSphere Applications monitoring agent to ensure that the monitoring agent is connected. Issue a Critical condition whenever it is not.
If Application_Server_Status.Status equals 0 then the situation WASNotConnected is true.
WASOutofHeapSpace
Monitor the heap allocation status. Issue a Critical condition whenever heap space is exhausted.
If Allocation_Failure.Heap_Status equals 1 then the situation WASOutofHeapSpace is true.
This situation is not available when monitoring non-IBM Java Virtual Machines, including machines commonly used on HP-UX and Solaris platforms.
WASAvgHeapSizeAfterGCHigh
Monitor the average heap size free percentage after garbage collection. This situation issues a Critical alert if the average heap size free percentage after garbage collection is greater than 80%.
If Garbage_Collection_Cycle.Heap_Free_Percent_after_GC is greater than 80 then the situation WASAvgHeapSizeAfterGCHigh is true.
This situation does not support Lotus Workplace server.
WASJ2CConnectionPoolUsageMaxed
Monitor the J2C pool percentage usage. Issue a Warning alert if the pool usage is greater than or equal to 100%.
If J2C_Connection_Pools.Pool_Used_Percent is greater than or equal to 100% then the situation WASJ2CConnectionPoolUsageMaxed is true.
This situation does not support Lotus Workplace server.
WASDBConnectionPoolUsageMaxed
Monitor the JDBC pool usage. Issue a Critical alert if the pool usage is greater than or equal to 100%.
If DB_Connection_Pools.Percent_Used is greater than or equal to 100% then the situation WASDBConnectionPoolUsageMaxed is true.
This situation does not support Lotus Workplace server.
See also Attributes for ITCAM Agent for WebSphere Applications.
Parent topic:
Situations for ITCAM Agent for WebSphere Applications