ONES Distributed Collector

ONES Distributed Collector enables seamless, large-scale fabric expansion without compromising visibility or control 🔍⚙️

A single ONES controller can manage up to 1,024 devices 🧠. For larger deployments—2,000, 4,000 devices, or beyond—ONES Distributed Collector allows you to scale horizontally by deploying multiple collectors 📡📡, all reporting into a single, unified ONES UI dashboard 🖥️✨

This architecture delivers:

• 🚀 Massive scalability without architectural complexity

• 👁️ Centralized visibility through one consistent UI

• ⚡ Distributed data collection for performance and reliability

• 🧩 Simplified operations even as the fabric grows

In short, regardless of how large your network becomes, ONES provides one unified UI 🖥️ with multiple distributed controllers 🔗—ensuring enterprise-grade scale with operational simplicity 🌐💡

Scenarios

1. Running UI on One Server Among the ONES Instances

2. Running UI on a Separate Server Besides the ONES Instances

1. Running UI on One Server Among the ONES Instances

Infra:

1. Host the UI component on one of the ONES instances (VM-1)

2. Run collector and other related services on all ONES instances (VM-1, VM-2, VM-3)

Steps

1. Install ONES on All Instances Install ONES on all required instances (e.g., vm-1, vm-2, vm-3).

2. Provide the Common UI IP During Installation When prompted for the Rule Engine Alert configuration, provide the IP address of the instance where the UI will be hosted:

   Enter the ONES App URL for Rule-Engine Alert [https://<host-ip or domain>]: https://X.X.X.X

3. Stop UI on All Instances Run the following command on all instances:

   docker-compose stop ui

4. Update rule-service Configuration On all instances except vm-1 (UI host), update the docker-compose.yml file:

   rule-service: 
     container_name: ones-rule-service 
     image: avizdock/ones-rule-service:v4.1.0 
     restart: always 
     ports:
       - "9000:8080"

5. Start rule-service On each collector instance (e.g., vm-2 and vm-3), start the rule-service:

   docker-compose up -d rule-service

6. Configure and Start UI on vm-1 On vm-1, update the UI section in docker-compose.yml:

   ui:
     environment:
       JWT_SECRET: aviz-2019
       SALT: 8
       PORT: 443
       PGUSER: postgres,postgres
       PGHOST: "10.4.5.236,10.4.5.227" //Replace these IPs with VM2 and VM-3 IPs
       PGPASSWORD: 3e8d98e9636e421f4ecab93,3e8d98e9636e421f4ecab93
       PGPORT: 5432,5432
       PGDATABASE: collector,collector
       HTTP_PORT: 443
       isFmEnabled: "true"
       CERT_PRIVATE_KEY_FILE_NAME: server.pem
       CERT_FILE_NAME: server.crt.pem
       USER_VALILDATION_MODE: ONES-APP
       ONE_DL_MODE: onprem
       RULE_ENGINE_URL: http://rule-service:8080

7. Start the UI service:

   docker-compose up -d ui

2. Running UI on a Separate Server Besides the ONES Instances

Infra:

1. Host the UI component on a seperate server (e.g., VM-1)

2. Run collector and other related services on other ONES instances (VM-2, VM-3)

Steps

1. Install ONES on All Instances (Including UI Server) Install ONES on vm-1 (UI), vm-2, and vm-3.

2. Provide the Common UI IP During Installation When prompted for the Rule Engine Alert configuration, provide the UI server IP:

   Enter the ONES App URL for Rule-Engine Alert [https://<host-ip or domain>]: https://X.X.X.X

3. Stop UI on All Instances

   docker-compose stop ui

4. Update rule-service Configuration (Collectors Only) On collector VMs (vm-2, vm-3), update the docker-compose.yml:

   rule-service:
     container_name: ones-rule-service
     image: avizdock/ones-rule-service:4.1.0
     restart: always
     ports:
       - "9000:8080"

5. Start rule-service on Collectors

   docker-compose up -d rule-service

6. Stop All Services on UI Server (vm-1)

   docker-compose down

7. Update and Start UI and pty-server on vm-1 Update the UI section in docker-compose.yml:

   ui:
     environment:
       JWT_SECRET: aviz-2019
       SALT: 8
       PORT: 443
       PGUSER: postgres,postgres
       PGHOST: "10.4.5.236,10.4.5.227"
       PGPASSWORD: 3e8d98e9636e421f4ecab93,3e8d98e922210ce9c0789d1f4ecab93
       PGPORT: 5432,5432
       PGDATABASE: collector,collector
       HTTP_PORT: 443
       isFmEnabled: "true"
       CERT_PRIVATE_KEY_FILE_NAME: server.pem
       CERT_FILE_NAME: server.crt.pem
       USER_VALILDATION_MODE: ONES-APP
       ONE_DL_MODE: onprem
       RULE_ENGINE_URL: http://rule-service:8080
       INTEGRATIONS_URL: http://api-server:8080

8. Start the UI and pty-server services:

   docker-compose up -d ui pty-server