To view monitoring data in the Admin Console

For more information on the attributes for each component or service, refer to About Statistics for Monitored Components and Services.

1. Access the Monitoring page. To do this:

   1. In the tree component, expand the Standalone Instances node.

   2. Select a stand-alone server instance, for example server (Admin Server), from the list.

   3. Select the Monitor page.

   4. Select the Monitor tab on the Monitor page.

2. From the View list, select a component or service that has been deployed onto the server instance and for which monitoring is enabled.

   Monitoring data for the selected component or service displays below the View field. For a description of the monitorable properties, refer to About Statistics for Monitored Components and Services.

   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. A diagram showing how these components and services are organized is shown in About the Tree Structure of Monitorable Objects.

3. If you do not see the component or service you wish to monitor in this list, select the Configure Monitoring link to enable and disable monitoring for selected components and services.

   Select OFF to disable monitoring for a component or service. Select LOW or HIGH to enable monitoring for a component or service.

   For more information on enabling and disabling monitoring, refer to To configure monitoring levels using the Admin Console or To configure monitoring using the asadmin tool.

4. Select the Applications tab of the Monitor page to view monitoring data for application components that are deployed onto the server instance and for which monitoring is enabled. Select the application from the Application list. Select the specific component from the Component list.

   If no monitoring data appears for the application or component, 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, select Low or High for the Web Container for web applications and/or the EJB Container for EJB applications.

   If no monitoring data is displayed for applications, it is most likely that the application does not exist or is not exercised. Applications monitoring data is 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 displays below the selected component. For a description of the monitorable properties, refer to About Statistics for Monitored Components and Services. A diagram showing how these components and services are organized for applications can be viewed in About the Tree Structure of Monitorable Objects.

5. Select the Resources page to view monitoring data for resources that are deployed onto the server instance and for which monitoring has been enabled. Select the resource from the View list.

   If the resource for which you wish to view monitoring data does not appear, select the Configure Monitoring link to enable or disable monitoring for a resource.

   If no monitoring data is 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 About Statistics for Monitored Components and Services. A diagram showing how these components and services are organized for resources can be viewed in About the Tree Structure of Monitorable Objects.

6. Select the Transactions page to freeze the transaction subsystem in order to roll back transactions and determine the transactions that are in process at the time of the freeze.

7. To enable monitoring for the Transaction Service, select the Configure Monitoring link and make sure that Transaction Service is set to LOW.

   To freeze the Transaction Service in order to roll back transactions, select Freeze. To rollback a transaction, select the checkbox beside the transaction and click Rollback.

Equivalent asadmin command

get --monitor

For example, to view monitoring data for the JVM, use the following asadmin command:

asadmin> get --user adminuser --monitor server.jvm.*