IBM Tivoli Composite Application Manager for Application Diagnostics, Version 220.127.116.11
Application Health workspace
Real-time health status of applications monitored by the Tivoli Enterprise Monitoring Agent. Collected from the following sources...
Request Metrics Request execution time collected from ITCAM instrumentation points in the application code. Resource Metrics Pool usage and container performance statistics collected from PMI modules or MBeans. GC Metrics Garbage collection frequency and performance collected from parsing of the GC verbose log file when it is enabled for the application server JVM. OS metrics JVM process and system execution, such as CPU used percentage, paging rate, etc.
The monitoring agent uses thresholds, Application Health Indicators, to determine the quality of the application service. For request response times, thresholds are assigned automatically during baselining. You can also manually customize the thresholds.
There are three monitored application tiers evaluated for health status.
Client Tier Performance data and status of application execution in servlets/JSPs or portal containers as well as corresponding thread pools servicing these containers. Application Tier Application execution metrics of EJB containers and custom requests. Backend Tier Application execution in JDBC, JCA, JMS, JNDI API calls.
This workspace displays data provided by the Application Health Status attributes.
By default, the predefined workspace has the following views:
Situation Event console view Show the event console with activity associated with the Application Health Summary Navigator item and any other workspaces in the group, as well as linked workspaces. Navigator Display an event icon overlaid on the Application Health Summary node when a situation becomes true. The report is useful when multiple alerts are raised as you can see them all in a single filtered view. Application Health Summary report Show the report of the application name, status, and health indicator for client, application, and backend tiers health status.
Due to the runtime MBeans configuration, the Tivoli Enterprise Monitoring Agent (TEMA) can only find composition units of business-level applications that associate with either web or EJB modules.
Access the Application Health Summary workspace
To access this workspace:
Within the Navigator...
Systems | node | WebSphere agents | WebSphere Application server | Application Health
Parent topic:Workspaces for ITCAM Agent for WebSphere Applications