Getting Started - What's New - Version 5.0.46
In This Topic
Review Loupe 5.0 Notes
Since this is an update release you should read Getting Started - What's New - Version 5.0 for a more complete picture of the new capabilities in 5.0.
New Features in This Release
Automatic Event Redaction (Monitor & Resolve)
When log messages are grouped together into events, common unique values are automatically redacted from the message to intelligently group common errors together. For example, timestamps, IP addresses, directory paths, file names, GUIDs, durations, and other numbers are removed and a token put in their place.
The original log message is still preserved and displayed when looking at the log viewer or detailed occurrence information; this only affects how messages are groupted together into events for the purposes of Loupe Monitor (for Alerts) and Resolve (for Issues).
When you upgrade to this version, this feature is enabled by default and will apply to new messages that come in. If you modify the list of manual redaction rules this will recalculate all of the event signatures and apply automatic redaction to the existing data.
Azure & Elasticsearch Integration for Standard Edition
Loupe Standard Edition now supports integration with several Azure systems previously only available in Enterprise Edition including:
- Azure Service Bus: Replaces using SQL Server for event queuing within the application. This is required to use Azure SQL instead of Microsoft SQL Server.
- Azure Storage: Replaces using the file system for storing log files. When paired with Azure Service Bus, this enables high scalable data uploads that don't tax the SQL Server for intaking session data from Agents.
- Elasticsearch: The built-in Lucene index that uses the file system can be replaced with an Elasticsearch 7 cluster for scalable full text search. This is required for Loupe Monitor.
Loupe Web UI
Inline Editing of Text Fields for Issues & Alerts
Most editable text fields for Loupe Monitor & Resolve (e.g. Issues, Alerts, etc.) can be modified inline instead of requiring you to click Edit and use a dialog to change the values.
Application Version Display
The Application Version display for an application now supports infinite scroll so you can move back through all of the versions in a long running application.
Monitor - Open Issues from an Alert
When reviewing alerts, you can open an Issue (which shows up in Resolve). When opening an issue, you can choose to simultaneously suppress the Alert from occurring again. This is useful for teams that share responsibility for both Monitor and Resolve for the same application - you can triage Alerts and indicate which ones are defects that should be resolved.
Loupe Server Administration
The Loupe Server Administration application has been upgraded to address new configuration options for Loupe Standard Edition (mentioned above) and supports lower resolution displays by scrolling the configuration content area.
Compatibility
Loupe 5.x is generally backwards compatible with 3.0 and later with the following notes:
- Agent: Requires Server version 4.0 and Desktop 4.0.
- Server: Fully backwards compatible with Agents 3.0 and later. Loupe Monitor requires a Loupe 5 Agent.
- Desktop: Compatible with Server versions 3.7.0 and later. Compatible with any version of Agent.
.NET 4.7.2 Required for Desktop and Server: Changes to Loupe Desktop and Loupe Server require .NET 4.7.2 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
Loupe Server
We're now sharing our internal defect tracking number as part of each resolved issue so you can associate these items with information provided by our support team. The number indicated is assigned by our work item tracking system, so gaps in sequence typically reflect other tracked items (like user stories, features, etc.) or defects that were introduced and resolved within the release.
- 1023: Monitor module - Switching Service while investigating doesn't update log tab.
- 1128: Monitor module - User can't favorite Application Environments in some cases.
- 1131: Resolve module - Changing application in application context doesn't update displayed issues.
- 1138: Monitor module - Creating a new Application Environment doesn't create application key automatically.
- 1150: Application Version editor Release Date dropdown isn't visible
- 1151: Resolve module - Application version statistics charts display compressed.
- 1152: Monitor module - Alert view doesn't show entire event.
- 1154: Monitor module - Issues Watching view can show empty when not empty.
- 1161: Monitor module - Alert Example Event doesn't respect CRLF by default.
- 1173: Search terms with spaces fails to find matching items.
- 1175: Application Users only show top 5 events in the Events tab.
- 1183: Resolve module - Event Cleanup dialog missing close button.
- 1187: Application User view uses oversize icon in header.
- 1191: Monitor module - Application Environment last contact timestamp doesn't update consistently.
- 1198: Log message display with JSON-formatted message details doesn't display formatted.
- 1201: Resolve module - displays new applications even if they aren't configured to be included in Resolve.
Loupe Desktop
- 1192: Live Sessions should sort by started date descending by default.
- 1193: Live Sessions doesn't respect timezone setting.
- 1210: Exception view doesn't show exception message on high DPI displays.
See Also