IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
Application Health Status attributes
The Application Health Status attributes provide information for real-time and historical application health status.
The attributes within this group are used to build the Application Health Summary workspace.
The combined application health level. Valid values are Unknown, Good, Fair, and Bad.
The unique identifier that is assigned automatically when the application is first configured and is preserved during the whole application life cycle. Format is positive integer.
The name of the application to which the request belongs. Format is alphanumeric string, with a maximum of 256 characters.
The status of the monitored application (only supported for Tomcat, and Oracle). Valid values are Standby, Discovered, Unknown, Starting, Running, Stopping, Stopped, and Failed.
The health level of the application tier. Valid values are Unknown, Good, Fair, and Bad. Application tier health indicator is determined from EJB or custom request delays collected on the interval and compared against thresholds configured for application requests.
The health level of the backend tier. Backend tier health indicator is determined from JDBC, JCA, JNDI, JMS delays collected on the interval and compared against thresholds configured for application requests. Valid values are Unknown, Good, Fair, and Bad.
The health level of the client tier. Valid values are Unknown, Good, Fair, and Bad. Client tier health indicator is determined from servlet/JSP or portal delays collected on the interval and compared against thresholds configured for application requests.
The completion level of the requests during the interval. Valid values are Unknown, Good, Fair, and Bad. Determined from request data as the percentage of number of failed requests to the total number of application requests on the interval.
The availability indicator of custom requests. Valid values are Unknown, Good, Fair, and Bad.
The health level of the EJB container. Valid values are Unknown, Good, Fair, and Bad. Determined from EJB delay types collected during the interval and compared against application thresholds.
The length (in seconds) of the sampling interval. Format is positive integer.
The overall health status of JCA resources used by applications. Valid values are Unknown, Good, Fair, and Bad. Determined from JCA delay types collected during the interval and compared against application thresholds.
The overall health status of JDBC resources used by applications. Valid values are Unknown, Good, Fair, and Bad. Determined from JDBC delay types collected during the interval and compared against application thresholds.
The overall health status of Java Naming and Directory Interface (JNDI) resources used by applications. Valid values are Unknown, Good, Fair, and Bad. Determined from JNDI delay types collected during the interval and compared against application thresholds.
The overall health status of JMS resources used by applications. Valid values are Unknown, Good, Fair, and Bad. Determined from JMS delay types collected during the interval and compared against application thresholds.
The name of the system on which the server is running. Format is alphanumeric string, with a maximum of 256 characters.
The name of the server subnode. Format is alphanumeric string, with a maximum of 128 characters.
The health level of the portal container. Valid values are Unknown, Good, Fair, and Bad. Determined from portal delay types collected during the interval and compared against application thresholds.
The health level of the response time for the requests. Valid values are Unknown, Good, Fair, and Bad. Determined from application requests response times collected during the interval and compared against application thresholds.
The date and time the Tivoli Enterprise Management Agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string:
Format of the 12-character timestamp
Character String Meaning MM Month DD Day YY Year HH Hour MM Minute SS Second
Example: 09/13/06 18:32:03 indicates the data was collected on September 13, 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.
The name of the application server. Format is alphanumeric string, with a maximum of 256 characters.
The health level of the Web container. Valid values are Unknown, Good, Fair, and Bad.
Additional information:
Parent topic:
Attributes for ITCAM Agent for J2EE