Using the monitored-servers tool

The monitored-servers command line tool configures communication between the servers and the PingDataMetrics server, then adds external server definitions to the PingDataMetrics server based on the server’s administrative data.

Before a server is added to the PingDataMetrics server configuration, the system determines whether communication needs configuring. If so, the cn=Monitoring User root user account is created on the external server.

Running the tool with the add-servers subcommand creates an external server based on the information discovered about the remote server. It also uses the information located in the cn=admin data entry to discover other servers in the topology, which are also added to the configuration. The following examples use the monitored-servers tool.

Example

Run the monitored-servers tool with the add-servers subcommand. Specify connection information for the PingDataMetrics server, as well as connection information for any remote servers in use.

$ bin/monitored-servers add-servers \
--bindDN uid=admin,dc=example,dc=com \
--bindPassword password \
--monitoringUserBindPassword password \
--remoteServerHostname localhost \
--remoteServerPort 1389 \
--remoteServerBindPassword password

Example

Use the --dry-run option to generate output detailing the work that would be done in a live session without actually making changes to the server configuration.

$ bin/monitored-servers add-servers \
--bindDN uid=admin,dc=example,dc=com \
--bindPassword password \
--monitoringUserBindPassword password \
--remoteServerHostname localhost \
--remoteServerPort 1389 \
--remoteServerBindPassword password
--dry-run