Pre-requisites for Monitoring the eG Manager

The eG agent should be configured to connect to the JRE used by the eG manager to pull out metrics of interest. To enable the eG agent to connect to the JRE, by default, JMX support has been enabled for the eG manager’s JRE. JMX enables external programs like the eG agent to connect to the JRE of an application and pull out metrics in real-time.

By default, the eG manager's JMX has been enabled without authentication or security (SSL). In this case therefore, no additional configuration is required to enable the eG agent to communicate with the manager's JRE via JMX.

High-security environments on the other hand, may prefer one of the following secure JMX configurations:

  • JMX with authentication, but without security (SSL)

  • JMX without authentication, but with security (SSL)

  • JMX with authentication and security (SSL)

To know how to configure JMX with authentication only, refer to the Configuring the eG Manager's JMX with Authentication topic . To know how to configure JMX with security only, refer to the Configuring the eG Manager's JMX with Security (SSL) topic . To enable both authentication and SSL for JMX, follow the steps discussed in both the topics cited above.