Client APIs

Application clients connect to the following addresses:

Internode RPC communication

Internode (server-to-server or node-to-node) communication, including xCluster, is managed using RPC calls on the following addresses:

To enable login to the machines running these servers, the SSH port 22 should be opened.

xCluster uses the YB-Master port 7100 for the initial communication, and then uses the YB-TServer port 9100 to get data changes. Note that YugabyteDB Anywhere obtains the replication lag information using Prometheus metrics from YB-TServer at port 9000. If this port is closed, the xCluster replication is not affected, but YugabyteDB Anywhere would not be able to display the replication lag.

Before installing YugabyteDB or YugabyteDB Anywhere, or upgrading the YugabyteDB software on YugabyteDB Anywhere, the YB Controller port 18018 must be open on all YugabyteDB nodes and be reachable from YugabyteDB Anywhere nodes:

Admin web server

Admin web server UI can be viewed at the following addresses:

Firewall rules

The following common ports are required for firewall rules:

** 54422 is a custom SSH port for universe nodes.

Prometheus monitoring

YugabyteDB servers expose time-series performance metrics in the Prometheus exposition format on multiple HTTP endpoints that have the following structure:

<target>/prometheus-metrics

You can access the Prometheus server on port 9090 of the YugabyteDB Anywhere node, and you can see the list of targets at the http://<yugaware-ip>:9090/targets. In particular, note port 9300 for node-level metrics:

Servers

Use the following targets to monitor YB-TServer and YB-Master server metrics:

APIs

Use the following YB-TServer targets for the various API metrics:

For information on using Prometheus with YugabyteDB, see Observability with Prometheus.