Version 4.48 is released and available for installation Follow


Version 4.48 was released on February 19th, 2020. The following are the notable changes to the product. For all the details, please see our documentation.


On-Premises Installation

In this version, we’ve added the option of installing the On-Premises component - the CR server - using two Linux package managers: RPM Package Manager (RPM) or Deb Package Manager.
The RPM is intended for RedHat and Centos Linux operating systems, while the Deb Package Manager is intended for Debian and Ubuntu Linux operating systems.

To learn more about these installers, check out the articles Install a CR Server Using the RPM Installer and Install a CR Server Using the Deb Installer. For instructions on how to install, go to the article Install a Collector and Java Micro-Agent Using RPM or Deb.

In addition, we’ve implemented the Systemd Linux Service Manager, a suite of basic building blocks for a Linux system. Also added options to run the On-Premises installation by a specific user/group, and to configure the storage/temp/logs directories. See Systemd Linux Service Manager and [Customizing the Directory Path for On-Premises Installations Customizing the directory path for on-premises installations for details.


  • Updated the flow of generating a new installation key in the Event Explorer - the user is now redirected to Settings/Manage Environments where he or she can create the new key. When the new environment is created successfully, the user is redirected to the OverOps app home with the new environment selected (see Generate an Installation Key.
  • Fixes and improvements to the Sync Jira UDF:
    • Added the ability to choose a “Status” or “Resolution” Jira field (using the resolutionOrStatus field
    • Added the ability to optionally sync “Hidden”, “Resolved” or both
    • Bug fixes

Backend (On-Premises)

  • As part of troubleshooting cases where the Collector’s state becomes unresponsive due to existing data processing issues, OverOps has implemented a method for wiping the Collector’s data without losing the Collector configuration. See Wiping a Collector's Data (On-Premises Linux Collector) for details.
  • Added Tomcat-access logs and additional log files (to learn more about the log locations, see Viewing On-Premises Logs)
  • Implemented additional performance optimizations


  • In the Env View, the section that displays the Java process now includes the Micro-Agent version as well.
  • Linux installation - When the user specifies the Collector port, this selection is now reflected in the agent properties ( file) that are downloaded with the Collector.
  • Added the Jira issue ID to the 'View Jira Issue' tooltip
  • Bug fixes:
    • Catalina.log recycling
    • Fixed an issue where an owner appeared twice in the team members when opening a new environment
    • Automatic refresh of method source code in the ARC screen when the source code is ready

Java Micro Agent

  • Added an API command option to disable the OverOps Micro agent on a group of applications/group of servers at any point if required. Note that this option is currently supported only for the Java Micro-Agent (not .NET). This capability is currently not supported on the Java 10, 11 (Neo) Agent.
  • Java 10, 11 (Neo) Agent: Implemented additional performance optimizations
  • Secure encrypted communication between the OverOps Collector and Micro-Agent is now supported on AIX in addition to Windows and Linux.
  • Added support for Java 8 u 232
  • Bug fixes:
    • Fixed an issue in the Collector that prevented processing events from many Micro-Agents, and also reduced the input/output usage of the Collector
    • Fixed an issue that caused an incorrect line number in decompiled source code
    • Improved the Micro-Agents’ footprint on the disk upon shutdown
    • Fixed an issue with presenting corrupted variable state. This doesn’t fix tales that are already open but will apply to any new tale that’s opened. The fix requires a restart of the Backend only (not the Collector or Micro-Agent)

.NET Micro-Agent

  • Added support for .NET Core 3.0 to the supported versions of .NET
  • Starting from this release, the .NET Micro-Agent is fully incorporated into the OverOps release process, sharing the same version number and download links.
  • Implemented improvements and bug fixes in the .NET decompilation process, such as limiting the number of threads.
  • When using an IIS web application, the application pool name is detected automatically and applied to the name of the application; see Naming the .NET Application for details.


  • Jira integration: For both New and Resurfaced Jira Alerts, added the following fields, and improved visibility:
    • Error
    • Location
    • First seen
    • Stack-trace preview
  • Added support for the SonarQube plugin integration; see SonarQube Integration for details.