Version 4.42 Release Notes and Multi-Environment Collector (MEC) Follow

Version 4.42 was released on August 14th, 2019. The following are the notable changes to the product. For all the details, please see our documentation.


This release includes new features as well as significant improvements, including the launching of our Multi-Environment Collector (MEC), a new integration with New Relic, full support for Oracle, improvements to the ARC screen, and some pretty cool updates to the Alerts and Settings features.


This release features the addition of the OverOps Multi-Environment Collector (MEC), which enables you to onboard new applications and functional groups in an easy and repeatable way. MEC creates a centralized management solution that ensures easy installation and addition of new applications and environments. Refer to this article to learn more.
Note that MEC is an addition to our existing installation, and doesn't affect the current installation.


  • OverOps has integrated the New Relic application performance monitoring (APM) software into our system. In this integration, links are inserted directly into the log files so that deep, code-level context can be surfaced and accessed during the troubleshooting process using a single click. To learn more, check out the New Relic Integration integration article.
  • Oracle Support: In this release, OverOps has added full support for the Oracle database in On-Premises deployments.
  • Extended the validity of the API token to 5 years (instead of the current 1 year).

Alert Dashboard Updates

  • Updated the UI and flow of adding a new alert in the Alerts dashboard. See Alerts Management for details.
  • Updated the UI and flow of viewing and managing active (existing) alerts in the Alerts dashboard. See Alerts Management for details.

ARC Screen Improvements

  • In rare cases where an error occurs while trying to open an ARC screen, we have added the ability for the user to report those errors directly to OverOps, helping us to review them and improve the product experience.
    In cases where our backend is not able to access our reporting interface (due to Internet connectivity issues), the report will be saved locally on the backend (/logs/tomcat/tale-fail.log).