Skip to main content

Rebranding in HA Architecture

Objective​

To ensure consistent rebranding across all App servers in an HA setup by synchronizing the encrypted logo file generated in the Motadata ObserveOps (formerly known as AIOps) application.

Prerequisites​

  • Motadata ObserveOps HA architecture must be configured.
  • SSH access with sudo privileges on all App servers.
  • Ensure all App servers (Primary / Secondary / Failover) are up and reachable.
  • Identify the source server where the logo upload is performed.

Procedure​

Step 1: Upload Logo from UI​

Navigate to the following path in Motadata ObserveOps:

Menu → Settings → System Settings → Rebranding

Upload the required logo.

This action will generate an encrypted file at the following location:

/motadata/motadata/uploads

Step 2: Identify the Encrypted File​

Navigate to the uploads directory on the source server:

cd /motadata/motadata/uploads

List files to identify the latest uploaded encrypted file:

ls -ltrh

The most recent file will appear at the bottom of the list.

Step 3: Copy Encrypted File to Destination Server​

From the source server, transfer the encrypted file to the destination App server:

scp {encryptedfilename} motadata@{destination_server_ip}:/tmp/
info

The source server can be Primary or Secondary depending on where the logo was uploaded.

Step 4: Move File to Uploads Directory on Destination Server​

Login to the destination server and execute:

sudo cp /tmp/{encryptedfilename} /motadata/motadata/uploads/

Step 5: Repeat for All HA Nodes​

Repeat Step 3 and Step 4 for all remaining App servers (Secondary / Failover), ensuring the encrypted file is present in:

/motadata/motadata/uploads

on every server.

Expected Outcomes​

  • Rebranding logo is consistent across all App servers in HA setup.
  • No mismatch in UI branding during failover scenarios.
  • Encrypted logo file is synchronized across all nodes.
  • Rebranding works seamlessly irrespective of which server handles traffic.