Install Pulse on Multiple Nodes (Docker/Podman-Based)

Use this page when deploying Pulse across multiple nodes to support larger environments, improve workload distribution, or provide high availability for data services.

• Pulse can scale horizontally as the number of monitored clusters and nodes increases. In multi-node deployments, selected Pulse services can run on dedicated hosts to distribute resource consumption and improve overall performance.
• In addition, MongoDB (ad-db) and Elasticsearch (ad-elastic) can be deployed in clustered configurations to provide data replication and high availability.

When to Use This Procedure

Follow this procedure when:

• Installing Pulse on multiple nodes.
• Deploying standalone Pulse services on dedicated hosts.
• Configuring a highly available Pulse environment.

If you are installing Pulse on a single node, follow the instructions in Install Pulse on Single Node (Docker/Podman-Based).

Components That Can Run in Standalone Mode

The following Pulse components can be deployed on separate nodes:

• ad-db
• ad-tsdb
• ad-logsearch
• ad-fs-elastic
• ad-pulse-ui (formerly ad-graphql)
• ad-ldap

Before You Begin

• Complete the Pulse installation on the primary node before installing components on secondary nodes.
• For details, see Install Pulse on Single Node (Docker/Podman-Based).

Configure Secondary Nodes

Perform the following steps on each node where standalone Pulse components will be installed.

1. Generate an Encrypted MongoDB URI.

Generate an encrypted string for the MongoDB connection URI.

xxxxxxxxxx

accelo admin encrypt

When prompted, provide the MongoDB URI in the following format:

xxxxxxxxxx

mongodb://accel:<MONGO_PASSWORD>@<PULSE_MASTER_HOST>:27017

Copy the encrypted output returned by the command.

2. Configure Environment Variables

Add the following environment variables to /etc/profile.d/ad.sh.

xxxxxxxxxx

export MONGO_URI="<encrypted_mongo_uri>"

export MONGO_ENCRYPTED=true

export PULSE_SA_NODE=true

Replace <encrypted_mongo_uri> with the encrypted value generated in the previous step.

3. Load the Environment Variables

Apply the configuration changes.

xxxxxxxxxx

source /etc/profile.d/ad.sh

Next Steps

• Install and configure the required standalone Pulse components on the node.
• Repeat this procedure for each additional node participating in the Pulse deployment.