State
Monitoring in the Visual Administrator
Use
The J2EE Engine Monitoring service provides a runtime control for displaying the monitored data. The monitored resources and their attributes are displayed in a tree view in the left-hand pane of the Monitoring → MonitorTree tab of the Visual Administrator. When you choose a monitored object from the tree, this displays general information and the monitored data in the right-hand pane.
For more information about the monitored data, see Monitored Data.
Monitoring resources using the Monitoring service of the Visual Administrator is especially useful for monitoring test and development systems.
For the alert monitoring of productive application servers it is recommended that you use a CCMS central monitoring system (CEN). In addition to a variety of monitoring functions, you can monitor whole system landscapes via CCMS. For more information see State Monitoring of the J2EE Engine Using CCMS.
Features
Monitoring Tree
●
Applications – reports information
about the state of the applications running on J2EE Engine that have
implemented the monitoring functionality. For more information about how to
activate monitoring in your application, see
Monitoring
in the Development Manual.
● Kernel – reports information about the state of the J2EE Engine managers registered for monitoring
● Performance – J2EE Engine performance measurements
● Services – reports information about the state J2EE Engine services registered for monitoring
● System – displays information about the system properties. For more information, see System Properties.
Color Changing Thresholds
The J2EE Engine Visual Administrator provides a type of alert monitoring. That is, according to the thresholds defined in the configuration the performance monitors have a color status:
Only performance monitors have the
alert functionality of changing their color according to the defined
thresholds. The other monitor types are marked only with a white icon (
).
Color Description
Image |
Description |
|
The data is at the normal level (OK). No attention is needed. |
|
A warning point. Shows that the values have moved to the next alert level and some problems may occur soon. Some attention is needed. |
|
An error point. The data values have moved to the error level. Special measures must be taken. |
|
This icon has two meanings. The first one is to indicate that the monitor is a non-performance one. The second is to show that the monitor is not working. If the monitor is a performance monitor and it is marked with this icon, it is not working. If it is a non-performance monitor, it always has this icon, therefore you have to check whether the particular monitor contains data. If there is no data, the monitor is not working. |
Once the defined values of each threshold are reached, the colored icon in the tree structure changes. Simultaneously, the color of the parent nodes is changed, that is, if one resource reaches a critical value and its icon is changed to red, all its parent nodes will also change their icons to red.
The levels are defined in the monitor-configuration.xml, which is used to specify the
monitored data. For more information, see
monitor-configuration.dtd.
General Info
● Name – the name of the monitored resource
● Description – a description of the resource, if any
● Type – the monitor type. The available types are:
○ Performance monitors – availability, integer, long, frequency, quality-rate, and duration monitor
○ Non-performance monitors – text, state, table, version, and configuration monitor
● Configuration group – the name of the configuration group with which the monitor participates
● Creation date – the resource creation date and time
● Last change date – the date and time the resource was last changed
Monitored Data
Displays the value of the monitored attribute. Furthermore, additional information is displayed according to the monitor type, for example, for the IntegerMonitorthe minimum and the maximum values are displayed.
History
A History option is provided to each monitor that keeps a track on the past values of each monitor and provides averaged history values aggregated in several time intervals. For more information, see Understanding the Data History.
Configuration
The Configuration option provides you to make changes to the
general configuration for each monitor, as well as to additional data
depending on the type monitor that was selected. The changes are stored in the
database. A 
Restore option is
provided on the toolbar for restoring the default configuration of the whole
monitoring tree. These option is also available for each monitor to restore
only its default configuration.
For more information, see Customizing the Configuration of a Monitor.
Data Refresh
The data retrieved from the resources is stored in a monitoring tree. The Monitoring runtime is automatically refreshed each minute with the newest data available in the monitoring tree. However, you can use the Refresh option from the toolbar to refresh the Monitoring runtime with the latest data stored in the monitoring tree.
An Update context menu is available on each polled-by-resource monitor in the Monitoring runtime. Use it to obtain at any time the latest data for this monitor from the resource.
Moreover, each table monitor has a show table in a frame context menu, which displays the table in a separate dialog, not in the right-hand pane. This dialog shows the current state of the table. This way, if you have a bigger table, you can stretch it screen-wide without being constrained by the right-hand pane. What is important here is the fact that displayed in a separate dialog the table is not refreshed each minute.
See also: