This section contains the following topics:
To configure monitoring in the Admin Console:
For the developer profile, go to Configuration -> Monitoring
For the cluster and enterprise profiles, go to Configurations -> Configuration -> Monitoring
By default, monitoring is turned off for all components and services. To turn monitoring on, select LOW or HIGH from the combo box. To turn monitoring off, select OFF from the combo box.
For details on configuring monitoring, see the online help available with the Admin Console.
Use the get command to find out what services and components currently have monitoring enabled.
asadmin> get --user admin-user server.monitoring-service.module-monitoring-levels.* |
Returns:
server.monitoring-service.module-monitoring-levels. connector-connection-pool = OFF server.monitoring-service.module-monitoring-levels. connector-service = OFF server.monitoring-service.module-monitoring-levels.ejb-container = OFF server.monitoring-service.module-monitoring-levels.http-service = OFF server.monitoring-service.module-monitoring-levels.sip-service = OFF server.monitoring-service.module-monitoring-levels.jdbc-connection-pool = OFF server.monitoring-service.module-monitoring-levels.jms-service = OFF server.monitoring-service.module-monitoring-levels.jvm = OFF server.monitoring-service.module-monitoring-levels.orb = OFF server.monitoring-service.module-monitoring-levels.thread-pool = OFF server.monitoring-service.module-monitoring-levels.transaction-service = OFF server.monitoring-service.module-monitoring-levels.web-container = OFF |
Use the set command to enable monitoring.
For example, to enable monitoring for the HTTP service:
asadmin> set --user admin-user server.monitoring-service.module-monitoring-levels.http-service=LOW |
To disable monitoring, use the set command and specify OFF for the monitoring level.