Software and Hardware Requirements


OverOps is designed for Java/Scala production environments and is compatible with most deployments in that space. If you don't see your deployment listed, please contact OverOps for assistance.

Deployment Model Hardware and Software Prerequisites

Depending on the deployment model you've chosen, there are several hardware and software components that you'll need to ensure are in place before beginning the deployment.

The following table highlights which logical components are required for each deployment type; you can view the hardware and software requirements for each deployment type in the sections below.

Hardware Requirements per Component

  • The Micro Agent doesn't require any additional hardware because it will be installed on your respective "application" server / container.
    • The Collector requires a server / container.
    • The Storage Server is bundled into the Analysis Server when using the On-Premise Model and doesn't require a separate server.

Agent Requirements

As explained above, the Agent doesn't require any additional hardware because it will be installed on your respective "application" server / container.

To learn more about which systems are supported for the Agent, see Supported Third-Party Software and Tools

Collector System Requirements


  • 4 Core Modern CPU
  • Minimum 8 GB RAM
  • Minimum 50 GB Disk Space / per application served


  • See Operating Systems
  • sudo privileges
  • Java
    • 1.6.0_20, 1.7, 1.8, 1.9
    • 10, 11 with OverOps Version 4.16 and newer only!

Network Requirements

Outbound HTTPS access (SaaS and Hybrid deployment only)

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


#Storage Server (for Hybrid Installations) Requirements


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


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-Premise Installation) 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)


  • 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.6.0_20 and higher, 1.7, 1.8, 1.9 (OpenJDK or Oracle JDK)
    • Version 1.10, 1.11 with Overops Version 4.16 and newer only!
  • wget and tar installed
  • Optional: MySQL Version 5.6 or higher
  • Optional: Postgres Version 9.5 or higher

Issue Running MySQL on a PDT Timezone

There's a known issue in MySQL 5.6 when running the MySQL Server on a PDT timezone.
Therefore, we strongly recommend running the server on a UTC timezone.

Postgres Considerations

We currently don't support the cleanup of our metrics information.

Requirements for Grafana

  • 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
  • TCP Ports 5000 - 5002 if internal H2 Database is used
  • TCP Port 6060 for remote Collector if used


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 6060 for remote Collector if used

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.

Supporting Third-Party Software and Tools

OverOps supports a wide range of supported third-party software and tools. This list changes often, so check back to see what's changed. See also OverOps Products End of Life Policy.

OverOps Interaction with Other Agents

OverOps performs an isolated machine code instrumentation. The OverOps agent does not interfere with the bytecode of other agents, and views all code, simply as system code. The vast majority of monitoring performed by OverOps takes place in the native code, at a lower level than most other Java agents. This means that OverOps is mostly seamless to other agents at the bytecode level. And, since OverOps has a minimal CPU, memory, and network footprint on your server, the performance of other agents is not affected by its monitoring activity.

For exceptions please see Non-Supported Frameworks and Tools.

Best Practice

See also our related best practice: OverOps Components.

Software and Hardware Requirements

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.