To view monitoring data for a component or service deployed in a server instance using the Application Server Admin Console, follow these steps. For more description on the attributes for each component or service, refer to the Monitoring chapter of the Administration Guide.
server (Admin Server)
.Monitoring data for the selected component or service displays below the View field. For a description of the monitorable properties, refer to the Monitoring chapter of the Administration Guide.
On this page, it is possible to view monitoring data for JVM, Server, Thread Pools, HTTP Service, and Transaction Service if monitoring is enabled for these components and services.
If you do see the application or component for which you wish to view monitoring, select the Configure Monitoring link to enable or disable monitoring for a component or service. To monitor applications, turn on the container in which they execute: for example, turn on the Web Container for Web applications and the EJB Container for EJB applications.
If monitoring data is not displayed for applications, it is most likely that the application does not exist or is not exercised. Applications monitoring data will be available only when the application exists, monitoring is enabled for the application, and the application is being exercised. Once the application is executed, it is registered in the monitoring registry and the monitoring data displays.
Use the Admin Console to monitor remote applications and instances. For this to occur, the remote instance must be running and the configuration set.
Monitoring data for the selected component will display below the selected component. For a description of the monitorable properties, refer to the Monitoring chapter of the Administration Guide.
If monitoring data is not displayed for resources, it is most likely that the resource does not exist or is not exercised. Resources monitoring data is available only when the resources exist, monitoring is enabled for the resource at a level of HIGH, and the resource is being exercised. For example, if you have created a JDBC connector service, but applications that use that connector service have not yet requested a connector from the service, that service has not yet been created, therefore, no service exists and no monitoring data is available. Once the JDBC application is executed and requests a connector from a service, the service is registered in the monitoring registry and monitoring data appears.
Monitoring data for the selected component or service displays below the View field. For a description of the monitorable properties, refer to the Monitoring chapter of the Administration Guide.
Equivalent asadmin
command: get --monitor
, for example, to view monitoring data for the JVM, use the following asadmin
command:
asadmin> get --monitor server.jvm.*
See Also: