Self-Monitoring the Controller

You can use the system account to self-monitor the Controller. When your system experiences noticeable performance issues with the Controller, you can log in to the system account to access and review the memory utilization trend for the last few hours.

Note: Only the internal Java Agent bundled in the path: <Controller_home>/appserver/jetty/appagent/javaagent.jar with the controller, the application is supported for self-monitoring. Using a custom Java Agent from a different path is not supported for self-monitoring.

You require to configure JMX using the Machine Agent to self-monitor the Controller.

Configure JMX Using a Machine Agent

Note: By default, the JMX module is enabled in the Jetty server of the Controller.

To configure JMX on the Controller using a Machine Agent, complete the following:

  1. Log in to the server where you have deployed the Controller.

  2. If the Machine Agent and Controller are in different servers, enable the JMX remote module using the following command:

    CODE 
    java -jar start.jar --add-to-start=jmx-remote
  3. (Optional) Verify the thread pool using JConsole. In Java Monitoring & Management Console, complete the following:
    1. Select the process where you have enabled JMX.
    2. Select the MBeans and navigate to com.appdynamics.serverthreadpools .It displays the configured thread pool.
  4. Configure the Machine Agent to report JMX metrics of the com.appdynamics.serverthreadpools domain in the Controlller.
  5. Restart the Controller.