Application Health workspace

The workspace displays the information about the real-time health status of applications monitored by the monitoring agent.

The health status information is collected from the following sources.
  • Request Metrics - performance data that measures request execution time collected from the ITCAM instrumentation points in the application code.
  • Resource Metrics - pool usage and container performance statistics collected from the corresponding PMI modules or MBeans.
  • GC Metrics - metrics on 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 - metrics collected about the JVM process and the whole system execution, such as CPU used percentage, paging rate, etc.
Additionally, the monitoring agent uses thresholds, called 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 provides performance data and status of application execution in servlets/JSPs or portal containers as well as corresponding thread pools servicing these containers.
  • Application Tier provides application execution metrics of EJB containers and custom requests.
  • Backend Tier provides 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, which shows 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. The Navigator will 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, which shows the report of the application name, status, and health indicator for client, application, and backend tiers health status.
Note: Due to the runtime MBeans configuration, the monitoring agent can only find composition units of business-level applications that associate with either web or EJB modules.

Accessing the Application Health Summary workspace

To access this workspace, complete the following steps:

  1. Within the Navigator, expand Windows Systems, Linux® Systems, z/OS Systems or UNIX Systems, as appropriate for the node you are monitoring.
  2. Within the node list, expand the entry that corresponds to the note you want to select.
  3. Within that node list of monitored applications, expand the list of WebSphere® agents.
  4. Within the list of available agents, expand the WebSphere Application Server entry of your choice.
  5. Within that server list of available WebSphere Application Server workspaces, click the Application Health entry.