doc.overops.com

Software and Hardware Requirements

Introduction

OverOps is designed for Java/Scala and .NET 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 Components

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.

Deployment Models

Deployment Models

Determining the Hardware Requirements per Component

Depending on the deployment model you choose, there are certain hardware requirements you'll need to make sure are in place before beginning with the following issues to consider:

  • For the Collector you'll need a server / container
  • If you're using an On-Premises model, the required Storage Server is bundled into the OverOps Analysis Server and doesn't require a separate server
  • The OverOps Micro Agent doesn't require any additional hardware because it will be installed on your respective "application" server / container

Requirements Overview

In this article we'll go into detail as to which requirements you'll need for the OverOps components, depending again on the deployment model you're using.

Agent Requirements

For the OverOps Agent, there are no hardware requirements (because the the Agent will be 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 Agent will be running on:

Java Agent Supported Third-Party Software and Tools
.NET Agent Supported Third-Party Software and Tools

Agent Network Requirements

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

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, refer to the Additional Supported Third-Party Software and Tools article.

Collector System Requirements

The Collector is usually installed on a separate machine or on the same machine as the OverOps Server, As such, the requirements for the Collector are the same as those for the server.

Hardware Requirements

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

Software Requirements

Important

The Collector machine must have Java installed on it for all types of Agents - both Java and .NET.

Network Requirements

Inbound TCP for remote collector

  • Port 6060 (default)

Outbound HTTPS access (SaaS and Hybrid deployment 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

Storage Server (for Hybrid 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
  • requires sudo privileges

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

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)

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.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

Known Database Limitations

  • 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. herefore, we strongly recommend running the server on a 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
  • TCP Ports 5000 - 5002 if internal H2 Database is used
  • TCP Port 6060 for remote Collector if used

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 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 additional supported third-party software and tools. This list changes often, so check back to see what's changed. You may also want to check out the OverOps Products End of Life Policy.

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.