How does eG Enterprise Monitor Solace Cluster?

eG Enterprise monitors the Solace Cluster using an eG external agent that is deployed on a remote host. The external agent can be deployed on any remote host in the environment. To pull out the metrics pertaining to its health, node connectivity, and availability of the cluster, the eG agent should be configured to access Solace Element Management Protocol (SEMP) API. To know how to configure the eG agent to work with the SEMP API, the following pre-requisites should be fulfilled.

• Determine the correct port using which the target Solace Cluster has to be managed in the eG admin interface. If the target appliance is SSL enabled, then the default port would be 443, if it is not SSL-enabled the port will be 80. Likewise, if the target software event broker is SSL enabled, then use 1943 as the default port, and 8080 if it is not SSL-enabled.

• By default, the eG agent executes SEMP APIs on the target component to collect the required metrics. For the eG agent to execute the SEMP API, a user with read only privilege is required with the respective user credentials. If such a user does not pre-exist, then, you need to manually create a user account with the aforesaid privileges on every cluster node that requires monitoring. To know how to create such a user, refer to Creating a New User for Monitoring Solace PubSub+ Event Broker