Release 4.45 from OverOps features our new .NET Micro-Agent, whose details are listed below, and our new In-app Installation Guide for trial accounts, as well as a major improvements and updates in the Backend.
The OverOps .NET Micro-Agent monitors .NET applications by attaching to a running application or environment, detecting errors and problems, thereby providing you with a comprehensive view of your application's performance.
The .NET Micro-Agent supports both .NET Framework and .NET Core, installs as a standalone on your laptop and works with Azure- Server, PC, and cloud - Azure AppService - through NuGet. The Micro-Agent can also be installed with a remote machine (using NuGet or MSI).
The .NET Micro-Agent can be currently used for pre-production environments only.
- Redis for On-Premises Deployments: The Redis Session Manager for Tomcat is an off-the-shelf product that allows you to store sessions of Apache Tomcat in Redis. This product is already implemented in our SaaS solution automatically; however, in this release we’ve developed a feature that adds a similar mechanism to On-Premises to enable the user to use cache in multiple Tomcats, i.e, to share the cache between multiple sessions. Customers who use this solution will need to ensure that Redis is already installed on their end and then to connect to it. The solution should be used in an On-Premises environment using a configuration of a number of backends and either an external Redisson server or a local installation on one of the backends.See Redis for On-Premises for details.
- Kerberos Support: In this release we’ve added support for the Kerberos authentication protocol for On-Premises deployments. See Kerberos for On-Premises for details.
- Improved warnings about previously installed Grafana instances for On-Premises deployments
- With this release, OverOps deprecated the use of an internal database layer (Dynalite) which will no longer be in use in the OverOps system. This change is introduced as part of our data access optimization process. This change is relevant for customers using MySQL, Postgres and Oracle databases. Customers that currently use the H2 database and will upgrade will still use the existing data access layer (only when installing a fresh installation will customers using H2 enjoy the new database optimized mode).
OverOps recommends that the default H2 database only be used for POC purposes and not for production environments.
In this release, we’ve implemented a major improvement in the way our product reports and processes an event’s statistical information through the entire hit flow - from our Micro-Agent, to the Collector to the Backend. This optimization will improve resource utilization and performance. To use this feature, you’ll need to make sure that the Collector and Backend are on this latest version.
- Added the top 5 event details as a custom field to the PagerDuty alert information.
- Updated and improved Jira tickets for Resurfaced events, which now include a description of the server/application/deployment fields and have a clearer indication that these are resurfaced events.
- Added the code_last_modified date field to integrations: To enable integrations to have all the information possible at their disposal, we’ve added the code_last_modified date field, which shows when the code was modified compared to the time of the event.
- The default my.server.properties file has been updated to include examples of most frequent configuration options used
- Separated the SAML metadata.xml to an external file instead of in my.server.properties
- To improve the user’s experience with the ARC screen, we optimized the way method sources are loaded asynchronously into the page.
- Increased the character limitation for View names from 50 characters to 100 (particularly relevant for routing UDFs that create routing views with long deployment names).
- Updated the way in which the “Last Seen/First Seen” value is displayed when there are no statistics.
- Updated the validation message in the UDF upload dialog
- Updated the Method Summary fields so that the class version is only shown when the source file exists
- Routing UDFs: To prevent situations where some of the default routing UDFs (such as deployments, apps, and tiers routing) are disabled by mistake, these UDFs can now run in ‘Silent’ mode (set by default) so that they don't require an alert channel to be enabled.
- Added an API endpoint that sets the jira_issue_url field
- Optimized Jira API request handling
- Added an Installation guide for basic OverOps installation for trial accounts that contains both Java and .NET installation (for pre-production environments) flows.
Updated 9 months ago