Compatibility

Contents

Introduction

Supported Environments and Versions

How OverOps Works with Other Agents

Related Articles

 

Introduction

OverOps is built for Java / Scala production environments and is compatible with the vast majority of deployments in that space. If your specific deployment isn’t supported, let us know and we’ll see what we can do in the future.

 

Supported Environments and Versions

 

We support:

We currently don’t support:

Server OS

Linux/Unix:

  • Ubuntu/Debian
  • CentOS / Fedora / RedHat 5.0+
  • Arch
  • SuSE
  • Gentoo
  • AIX
  • 32-bit Linux
  • Solaris
  • Windows Vista or newer (64-bit only)
  • Windows Server 2008 or newer
  • Windows XP or older
  • 32-bit Windows
  • macOS (10.6+)
 

Languages

All JVM-based languages:

  • Java 1.6+
  • Scala
  • Clojure
  • Groovy
  • JRuby
  • Jython
  • etc…

Non JVM-based languages:

  • Python
  • C
  • C++
  • C#
  • PHP
  • Ruby
  • etc…

Runtime

  • 64-bit Oracle (HotSpot)
  • 64-bit OpenJDK
  • 64-bit Azul Zulu
  • 64-bit IBM JVM (J9)
  • 32-bit Oracle/OpenJDK
  • JRockit
  • Azul Zing
  • .NET CLR
  • IBM JVM (J9) on Windows host

Logging frameworks

  • Logback
  • Log4j 1.x/2.x
  • Java Logger
  • Apache Commons Logging
  • JBoss logger
  • Akka logger
  • SLF4J-simple
  • Tinylog
 

Containers

  • Docker
  • Heroku
  • CloudFoundry
  • AWS ElasticBeanstalk
  • AWS Lambda
 

Configuration managements

  • Chef
  • Puppet
  • Ansible
  • SaltStack
 

Frameworks

  • Tomcat
  • Glassfish
  • JBoss / Wildfly
  • Play Framework
  • WebSphere
  • WebLogic
  • Mule
  • Spark
  • Hadoop
  • JSP
  • Akka
  • Nashorn
  • Rhino
  • Node.js
  • .NET

Web Browsers

  • Firefox
  • Google Chrome
 

 

How OverOps Works with Other Agents

OverOps performs isolated machine code instrumentation. That is, the OverOps agent does not interfere with the bytecode of other agents, and views all code, including the code of other agents, simply as system code. Moreover, the vast majority of monitoring performed by OverOps takes place in native code, at a level lower than most other Java agents. This means that for the most part OverOps is not even visible to other agents at the bytecode level. Since OverOps has a minimal CPU, memory, and network footprint on your server (more about that here), the performance of other agents will not be affected by its monitoring activity.

 

Related Articles

Performance and Overhead

Have more questions? Submit a request