Getting Started - What's New - Version 4.10
In This Topic
New Features in This Release
Loupe Desktop Session Search/Filter on Details
The free-text session search and filter now checks the individual Details field of each log message as well as the caption/description/exception information.
Loupe Server Session Lists Performance & Filter Improvements
The Latest Session and application-level Session displays now remember the last filter options set during the current user session. This means if a user drills into a session from a sessions view and navigates around, then returns to that session view it will remember the most recent filters they set. This improves several user flows where users are moving in and out of the same session list during an investigation. The API methods that support these views have been optimized with new database indexes to significantly reduce database load and improve response time.
Loupe Server Docker Compatibility
It's now possible to containerize Loupe Server as a Windows container. Loupe Server now supports configuration from environment variables using Loupe__Server__[Section]__[Property]. Note this is two underscores (_) in a row as a delimiter, matching the behavior of .NET Core. To containerize, you will need to contact Gibraltar Software for a license key file for portable licensing.
Compatibility
Loupe 4.x is generally backwards compatible with 3.0 with the following notes:
- Agent: Requires Server version 4.0 and Desktop 4.0 due to new data types introduced in this version.
- Server: Fully backwards compatible with Agents 3.0 and later. Older Loupe Desktop clients will not be able to use AddIns.
- Desktop: Compatible with Server versions 3.7.0 and later. Compatible with any version of Agent.
- Extensions must be modified: Any Loupe Addin developed for an Loupe 3.* will need to be updated to use the new Loupe Extension types and repackaged. Confirmation information has been moved so each extension will need to be reconfigured once it is installed. See Loupe Extensions - Getting Started for more information.
.NET 4.5 Required for Desktop and Server: Changes to Loupe Desktop and Loupe Server require .NET 4.5 to be installed. There is no change to the Agent - it still works with .NET 2.0 SP1 and later.
Defects Fixed in This Release
This update to Loupe 4.10 fixes the following issues
Server
- Fixed: Loupe Desktop Live Stream sessions may be slow to display the set of sessions or disconnect from the server when there are many live sessions.
- Fixed: Loupe Server fails to provide the list of recently viewed sessions to Loupe Desktop.
- Fixed: Loupe Server Service may use excessive memory when a Loupe Desktop is connected to Live Stream over a slow connection.
Desktop
- Fixed: Live Sessions display may generate a null reference exception when there are no sessions available and a user clicks on and off of the live sessions display.
- Fixed: Repository View may generate a null reference exception when a view is closed while currently displayed if a filter is enabled.
Defects Fixed in Update 2
This update to Loupe 4.10 fixes the following issues
Server
- Fixed: Double-clicking session row in session usage attempts to display an issue instead of session.
- Fixed: Live Stream can fail due to network stream corruption under stress due to incorrect buffer reuse.
- Fixed: Rebuilding full text index on repositories with a very large number of events can use excessive memory.
Desktop
- Fixed: Live Log Viewer text search doesn't inspect details or exception information.
- Fixed: Viewing a partial session from the local data fails to load log messages.
Defects Fixed in Update 1
This update to Loupe 4.10 fixes the following issues.
Server
- Fixed: Loupe Server Service uses excessive memory performing repository maintenance on large repositories with slow(er) disks/network access.
- Fixed: Loupe Server Service uses excessive memory when rebuilding the full text index for repositories with large numbers of events.
- Fixed: Live Stream uses excessive memory if an agent reconnects while a live log view is active.
- Fixed: Live Stream can fail to respond to connection attempts if one or more desktops are not responding
- Fixed: Live Stream may fail to transfer data or disconnect on a server with many sessions and multiple logs being viewed simultaneously.
- Fixed: Repository initialization is slow when using Azure Service Bus, possibly preventing site from coming online.
Desktop
- Fixed: Loupe Live Log Viewer disconnects when log messages extend 1-2 bytes beyond the end of a TCP packet.
Agent
- Fixed: Null Reference Exception when subscribing to Log.ResolveApplicationUser before initializing the Loupe Agent.
- Fixed: Server AutoSendOnError does not work unless the Log.MessageAlert event is subscribed to.
- Fixed: Loupe Live Log Viewer may not display the last few messages during a burst of messages until a new message is received.
Defects Fixed in 4.10
Loupe 4.10 resolved the following issues.
Server
- Fixed: ARM processor type is not understood, preventing logs from Android and iOS from being categorized and stored correctly.
- Fixed: Notification Filters for Environment and Promotion Level are not saved.
- Fixed: Issues fail to display if the sum of all occurrences exceeds 2.14 billion (Int32 maximum value)
- Fixed: Live Stream updates stop if a connected Loupe Desktop can't keep up.
- Fixed: Live Stream can deadlock if an agent disconnects while connecting, preventing new agent connections.
- Fixed: Loupe Server Service tries to repeatedly initialize if background tasks are disabled.
- Fixed: Loupe Server Admin can't edit an Active Directory entry after it is created.
- Fixed: Latest Sessions display leaves wait cursor up if query results complete out-of-order (typically due to filter changes)
- Fixed: Exception display doesn't include source file & line number in all cases.
- Fixed: .NET Core Getting Started help is incorrect for .NET Core 3.
Desktop
- Fixed: Loupe Live Log Viewer attempts to update the display too frequently viewed through remote desktop/screen sharing.
- Fixed: Log Events display in Repository view does not adjust timestamps to selected time zone.
See Also
Server Administration
Using Loupe Server