Using OverOps in Your Java System
In this article we'll focus on the software and frameworks that - when used together with the OverOps Java solution - will enable you to achieve the most from OverOps from a features and value standpoint. As you can see from the extensive lists below, OverOps works with many different technologies, so you'll likely find a technology you're already using.
OverOps Interaction with Other Java Agents
OverOps performs isolated machine code instrumentation, so that our Agent doesn't 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.
Other agents include, for example:
- Dynatrace OneAgent
- New Relic
There are currently two agents that aren't compatible with the OverOps Java Micro-Agent:
- Dynatrace AppMon Agent
- JRebel Agent
Application Performance Monitoring (APM) Tools
|New Relic||New Relic 3.38||Minimum supported version.|
Note that New Relic is not currently supported on Java versions 10 and 11 and on the AIX Unix operating system.
CI/CD Pipeline Integrations
|Jenkins||Jenkins 2.43 or later|
on Java 1.8 or later
|SonarQube||SonarQube version 7.9.1 or later||Available for OverOps version 4.48 or later|
The JaCoCo Maven plugin is not supported.
Our integrations are updated frequently so visit this page regularly and also follow our website integrations page.
Supported User Defined Functions
- Microsoft Teams digest
|Mule||A lightweight enterprise service bus and integration framework, Mule's platform is Java-based, but can broker interactions between other platforms such as .NET using web services or sockets.|
|JSP||Source-code highlighting is not supported.|
Web Servers/Application Servers
|Web Server/Application Server||Note|
|Jetty||A Java HTTP server and Java Servlet container.|
|Tomcat||Apache Tomcat implements several Java EE specifications including Java Servlet, JavaServer Pages, Java EL, and WebSocket.|
|JBoss/Wildfly - WildFly||An application server that implements the Java Platform, Enterprise Edition specification and runs on multiple platforms.|
|Websphere||This application server enables customers to connect Web site users with Java applications or servlets.|
|WebLogic||Oracle WebLogic Server is a Java EE application server.|
|Play Framework||An open-source web application framework.|
|Glassfish||An open-source application server project.|
Integrated Development Environments (IDEs)
|Eclipse||Eclipse contains a base workspace and an extensible plug-in system for customizing the environment.|
|NetBeans||NetBeans allows you to develop applications from a set of modular software components called modules. NetBeans runs on Windows, macOS, Linux, and Solaris.|
|IntelliJ||A Java IDE developed by JetBrains for developing computer software.|
When OverOps injects log links into your log files, the OverOps URLs are displayed within the Log View, allowing you to open new errors and exceptions in a new tab directly from the Log View.
Note that while all the loggers support log events, only some support log views.
|Logging Framework||Note||Log Event Supported Frameworks||Log View Supported Frameworks|
|Acl||Acl = org/apache/commons/logging/impl/SimpleLog||Supported|
|Akka logger||Akka = akka/event/EventStream||Supported|
|JBoss logger||jboss = org/jboss/logmanager/Logger||Supported|
|JUL||jul = java/util/logging/Logger||Supported|
|Logback||Logback = ch/qos/logback/classic/Logger||Supported||Supported|
|Log4j 1.x||Log4j = org/apache/log4j/Category||Supported||Supported|
|Log4j 2.x||log4j2 = org/apache/logging/log4j/core/Logger|
log4j2 = org/apache/logging/log4j/core/async/AsyncLogger
Note: The latest Log4J2 version 2.12 is currently not supported by the Agent.
|Slf4j-simple||sl4j = org/slf4j/impl/SimpleLogger||Supported|
|Tinylog||tinylog = org/pmw/tinylog/Logger||Supported|
The Cucumber framework converts the feature file into Java code at runtime by instrumenting it. This causes additional instrumentation from OverOps side, which creates job execution delays and affects performance. Therefore, this framework isn't supported in OverOps.
JProfiler is not supported by OverOps
Updated about 3 years ago