Skip to main content

Installation Guide for Single-Box Standalone Deployment

Overview​

This installation guide provides step-by-step instructions for installing Motadata ObserveOps (formerly known as AIOps) in a Single-Box Standalone deployment.
You can follow the steps for Linux or Windows, based on your environment.

Minimum System Requirements for Motadata ObserveOps (formerly known as AIOps) Server​

Before installing and running Motadata ObserveOps (formerly known as AIOps), please ensure that your server meets the minimum system requirements of 12 vCPU, 12 GB of RAM, and 500 GB of disk storage for Observability edition to ensure optimal performance and functionality.

Prerequisites​

Before starting the installation, ensure the following prerequisites are met:

  • Configure servers based on the sizing requirements of the chosen component.
  • Download the Motadata ObserveOps (formerly known as AIOps) installation ISO.
  • Network Port should be open in Network Firewall and respective servers as defined below:

Network Port Specifications​

Port NamePort NumberPort TypeDirectionPort To Be Opened AtPurpose
Motadata Manager9440, 9441TCPBidirectionalApplication ServerFacilitates communication with Motadata Manager
Motadata Application9433, 9455, 9456, 9457, 9471, 9472, 9473, 9474, 9475, 9477TCPBidirectionalMotadata ApplicationEstablishes communication for Motadata Application with MotaStore. This port needs to be opened only when the application and database reside on different servers.
Event Publisher9444 to 9448TCPBidirectionalApplication ServerFacilitates communication between MotaAgent and the Application Server. Typically, 9444 and 9445 ports are mandatory, but multiple ports may need to be open to support load balancing when a significant number of agents are used.
Event Subscriber9449 to 9453TCPBidirectionalApplication ServerFacilitates communication between MotaAgent and the Application Server. Typically, 9449 and 9450 ports are mandatory, but multiple ports may need to be open to support load balancing when a significant number of agents are used.
MotaStore9464, 6060, 6061TCPBidirectionalDatabase ServerFacilitates remote troubleshooting of MotaStore. These ports need to be opened only when troubleshooting is required for MotaStore.
TCP Log Listener5140TCPBidirectionalApplication Server or CollectorUsed to ingest logs into Motadata in an encrypted format for secure data transfer. Ensure this port is open on the collector if logs need to be ingested at the collector level.
UDP Log Listener514UDPInboundApplication Server or CollectorUsed to ingest logs into Motadata. Ensure this port is open on the collector if logs need to be ingested at the collector level.
Flow Listener (netflow)2055UDPInboundApplication Server or CollectorUsed to ingest flow data into Motadata. Ensure this port is open on the collector if flow data needs to be ingested at the collector level.
Flow Listener (sflow)6343UDPInboundApplication Server or CollectorUsed to ingest flow data into Motadata. Ensure this port is open on the collector if flow data needs to be ingested at the collector level.
Trap Listener (v1/v2)1620UDPInboundApplication ServerUsed to ingest trap into Motadata.
Trap Listener (v3)1630UDPInboundApplication ServerUsed to ingest trap into Motadata.
Event Processor9443TCPBiredirectionalApplication ServerProcesses event messages, offloading the processing load from the application server.
Web UI443HTTPSBidirectionalApplication ServerEnables user interface access from the browser.
Upgrade/Restore8080HTTPSBidirectionalApplication ServerUsed for upgrading Motadata artifacts from the UI
Important

Motadata ObserveOps (formerly known as AIOps) (APP, DB, Collector) – Antivirus Whitelist Guidelines

Motadata does not recommend applying Antivirus on Application (APP), Datastore (DB) or Collector components. However, in cases where client compliance mandates Antivirus installation, please carefully follow the guidelines below.

General Considerations

  1. Resource Utilization: Installing antivirus on Motadata components will significantly add resource overhead which may lead to abnormal monitoring activity. Consider increasing resources to compensate this overhead.

  2. VM Snapshot: Before applying Antivirus, take a VM snapshot of all components: APP, DB, and Collector.

  3. Monitoring: Keep the environment under observation after applying the Antivirus with the below prerequisites configured.

Folders & Files to Whitelist

Whitelist the following directory and executables from real-time and scheduled Antivirus scans:

Directory Path: \Motadata

Executables (whitelist all matching 'motadata-*'):

  • motadata-agent.exe
  • motadata-manager.exe
  • motadata-upgrade.exe
  • motadata-manager_m.exe
  • motadata-log-agent.exe
  • motadata-metric-agent.exe
  • motadatadb
  • nfacctd
  • sfacctd
  • datastorebroker
  • aiopsengine
  • gopluginengine

Also, make sure to exclude all listed directory and executables from both real-time scanning and scheduled scans and ensure security agents/firewalls allow continuous communication over the specified ports. Then, apply these rules for both on-premises deployments and remote/endpoint devices running Motadata Agents.

Installation Steps​

  1. Create a virtual machine (VM).
  2. Map the downloaded ISO to the VM datastore.
  3. Boot the VM from the ISO to initiate the installation process.
info

You would need to establish an SSH connection with the server. Use motadata as the username and password when prompted and continue with the installation.

  1. Obtain sudo permissions by running the following command:

    sudo su

  2. Navigate to the opt folder using the following command:

    cd /opt

  3. Check for the existence of the installation script (post-install.sh) using the following command:

    ls

  4. Run the installation script:

    ./post-install.sh

    After you run the installation script, you will be asked to select the Deployment Type out of the following:

    1. Single-Box
    2. Distributed
    3. Collector

  5. Select the Deployment Type 1. Single-Box and then follow the steps further as demonstrated below.

  6. Select the Deployment Architecture as 1. Standalone from the following options:

    1. Standalone
    2. High-Availability
    3. Disaster-Recovery

  7. Change the root password by providing and confirming a new password.

  8. Configure the static IP address, default gateway, and DNS servers. You can change the default DNS servers as per your requirement.

  9. Configure the hostname.

  10. Configure the timezone by selecting the region and timezone where you are installing the Motadata ObserveOps (formerly known as AIOps) Master.

  11. Once the installation process is complete, Motadata ObserveOps (formerly known as AIOps) application is accessible using the link specified below:

       https://[IP]

where [IP] is the static IP you configured.

  1. Detach the ISO from the virtual machine to complete the installation.
info

Use admin as the username and password for first-time login. You can change these default credentials using the configuration options listed on Configuring your Motadata ObserveOps (formerly known as AIOps) Profile