A new Loupe Agent for Java has been published along with enhancements to Loupe Desktop and Loupe Server to identify Java sessions and customize displays of session properties for Java.
To get started with your Java app, see Developer's Guide - Java -Using Loupe with Java.
The Loupe Agent for Java is open sourced at GitHub: Loupe-Java.
The Loupe Server Web UI now offers filtering the various Event views by Environment and Promotion Level where applicable, making it easy to see just the errors being reported by computers in a particular environment or promotion level.
Loupe Desktop & Server now support improved scalability with lower network bandwidth by pausing sending session summary information from the Server to the Desktop when the Live Sessions view isn't active. When there are large numbers of Agents reporting to the Server this can dramatically reduce bandwidth between the Server and Desktops and reduce latency when bandwidth is restricted.
Loupe Server now uses a reusable memory buffer system to reduce memory necessary to handle large numbers of Agents.
When a Server Repository is selected in Loupe Desktop the summary information for the most recent 25,000 sessions. When the server has a large number of sessions (typically millions) this initial load can be slow due to database query performance limitations. The database schema has been changed and additional indexes added to significantly improve the scalability and performance of this initial load operation.
The Properties available on an Application User are now displayed in both Loupe Server and Loupe Desktop. Properties can be added by any application when providing an ApplicationUser at runtime and are merged with the property values previously recorded for that user on the server (repository-wide).
When clients have more than 50-100 applications the performance of several views becomes unacceptable even with a fast database server. Changes to how summary metrics and views are composed significantly improve the performance of these views.
Internal changes to how pages of events are calculated for the various Event views (Review, Latest, Top and Suppressed) significantly improves the performance of those views with large repositories.
The database changes in this release can take significant time to perform in the SQL Server Database. Upgrades may take 15-30 minutes for larger repositories and should not be interrupted.
For details on how to upgrade your on-premises Loupe Server installation see Loupe Server Administration - Upgrading to a New Version.
Loupe 4.x is generally backwards compatible with 3.0 with the following notes:
Loupe 4.8 resolved the following issues.