OverOps Installation Prerequisites


This article details the prerequisites you'll need to install OverOps on your end, including the required hardware, software, network configurations and more.

Micro-Agent Requirements

The Micro-Agent is the component that's installed alongside an environment and monitors your applications. There are no hardware requirements for the OverOps Micro-Agent because it's installed on your respective "application" server / container.

However, depending on whether you're installing a Java Agent or a .NET Agent, you'll need to refer to the supported operating systems and other supported third-party software the Micro-Agent will be running on.

Agent Network Requirements

  • Outbound TCP on Port 6060 (configurable) for connections to the Collector

Collector System Requirements

The Collector is the endpoint to which Micro-Agents report, and is usually installed on a separate machine or on the same machine as the OverOps Server. The following are the hardware and software requirements for the Collector:

Hardware Requirements

  • 4 Core Modern CPU
  • Minimum 8 GB RAM
  • Minimum 50 GB Disk Space / per application served
  • At least 32768 files (ulimit -n)

Software Requirements

  • Operating system:
    • Linux - see Software Requirements below for details
    • Windows
    • Windows Vista and newer
    • Windows Server 2008 and newer
  • Sufficient permissions to install 3rd party software are required
  • Java 1.8 to 1.11 (supported versions are Java SE 8 to 11 and OpenJDK 8 to 11) - The Collector machine must have Java installed on it for all types of Micro-Agents (Java supported versions were updated in release 4.46)

Network Requirements

Inbound TCP for Collector

  • Port 6060 (default)

Outbound HTTPS access (SaaS and On-Premises Data deployments only)

The following hosts must be whitelisted. This may also be done by using a proxy.

  • backend.takipi.com
  • prod1-sparktale.s3.amazonaws.com
  • prod1-frontend-sparktale.s3.amazonaws.com

Variable Store/Storage Server (for On-Premises Data Installations) Requirements

Hardware Requirements

  • 2 Core Modern CPU
  • Minimum 8 GB RAM
  • Minimum 250 GB Disk Space

Software Requirements

  • Linux 64-bit only operating systems
  • Java 8, Java 9
  • Sufficient permissions to install 3rd party software are required

Network Requirements

Inbound TCP/HTTP(S) ports:

  • 8080 used for HTTP access
  • 8443 used for HTTPS access
    These ports can be changed using the settings.yml file.

OverOps Server (On-Premises Installation) Requirements

For On-Premises installations you'll need a server for the backend instance (for example, Tomcat) which is the hardware identified below. You'll also need a database that's installed on a separate server.

On-Premises Hardware Requirements

  • Modern 8 core 64bit CPU
  • Minimum 32 GB RAM
  • Minimum 1 TB Disk Space
  • At least 16384 processes (ulimit -u)
  • At least 32768 files (ulimit -n)
  • Minimum 1TB Disk Space for DB

On-Premises Software Requirements

  • Operating System: Modern Linux (minimum kernel: 3.10): For example RedHat 6.5 or above, CentOs, Debian, Ubuntu, and many different Linux distribution (or distros)
  • Java Development Kit (JDK) version 1.8
  • wget and tar installed
  • Optional: MySQL
  • Optional: Postgres
  • Optional: Oracle

Known Database Limitations

  • MySQL only supported when running on UTC Timezone
  • Oracle only supported when running on UTC Timezone
  • Postgres Considerations: We currently don't support the cleanup of our metrics information.

Grafana Requirements

  • TCP Port 3000 must be available
  • No other running instances of Grafana on the machine

Network Requirements for Containers that are not Docker

  • HTTP Port 8080 to access Dashboard and Storage
  • TCP Port 4567 for key value - Storage Server (Variable Store)
  • TCP Port for the Collector - we use 6060 as the default (however it's configurable)

Note that the Docker-compose file will require execute permissions.

Network Requirements for Docker Containers

  • HTTP Port 8080 to access Dashboard
  • HTTP Port 9090 to access Dashboard
  • TCP Port for the Collector - we use 6060 as the default (however it's configurable)


Choosing an Optimal Docker Configuration

Choose an optimal Docker configuration for the Linux and the environment workload, since production requires a more robust Docker configuration.

Refer to the recommendations in the Docker blog here for more information.

Supported Browsers

Firefox*Using Firefox in private browsing mode is not currently supported.
SafariVersion 12.1 and newer

Supported Databases (On-Premises Installations Only)

MySQLVersions 5.5, 5.6 and 5.7
PostgresVersion 11+Currently only UTC timezone is supported
OracleVersion 11g release 2 (
Version 12g
Currently only UTC timezone is supported

Reliability Dashboards (On-Premises Installations Only)

Hosted in your Grafana environment

Bundled Grafana6.7.3 from release 4.52
5.3.4 in earlier releases
Grafana version bundled with the OverOps solution OOB
Grafana5.3.4 and above
Boom Table Plugin

Automation Frameworks

Mgmt ToolNote
AWS ElasticBeanstalk

Best Practice

To learn more about how to best implement OverOps in your solution, see our related best practice article: OverOps Components for details.