---
title: Using the monitored-servers tool
description: 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.
component: pingdirectory
version: 9.3
page_id: pingdirectory:pingdatametrics_server_administration_guide:pd_met_use_monitored_servers_tool
canonical_url: https://docs.pingidentity.com/pingdirectory/9.3/pingdatametrics_server_administration_guide/pd_met_use_monitored_servers_tool.html
revdate: September 13, 2023
section_ids:
  example: Example
  example-2: Example
---

# 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.

```shell
$ 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.

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