Loupe 5.2 Released

Loupe 5.2 is now live for all Loupe Cloud-Hosted customers and available for download and installation for self-hosted customers. For a list of changes and defect fixes, see the Loupe 5.2 Release Notes

Enhanced Custom Session Properties

Loupe has supported custom name/value pairs on sessions since version 2. In Loupe 5.2, we’ve introduced a new display in the Web UI to handle more sophisticated data stored in these properties and make them more prominent in the web UI.

If you add a session property it will now show at the top of the Session view in its own block of properties separate from the large set of built-in properties. We’ve separated them based on feedback from customers that any property they added is more important and often a different category of information from the built-in properties. Putting them in their own group means you don’t have to expand all of the session details to see your custom properties.

Finding by Property

The session filter find for the session list will search property values to match the text you provide, so for example if you add a customer name property you can then search by customer name and not have to embed that information into a built-in field like environment or promotion level.

Hierarchal Properties

There are two ways to get properties to show in a tree structure: If you provide a JSON-formatted value, the value will be displayed as a formatted hierarchy of values. Alternately, if you use a dotted name for a value, all of the values under a top level will be merged together into a display.

Separate Storage Limits by Server Type

With the introduction of Loupe Monitor and its reliance on Elasticsearch to provide merged log data, a challenge was introduced if customers wanted to keep a distinct amount of data in Elasticsearch (by age and total size) from the amount of raw log data files they wanted. In version 5.2, we’ve introduced distinct age and size limits for Elasticsearch and file storage.

For example, if you want to keep 10TB and one year of raw log data but 1 TB and two weeks of lag data in Elasticsearch you can now configure limits to do exactly this. Loupe will automatically prune the log file storage and Elasticsearch storage to match these limits. We’ve also introduced a distinct limit for database storage which will have automatic pruning in a future version.

Other Improvements

We’ve rolled up a number of more minor changes to Loupe into this release, compared to 5.0 including:

• Repository Log File Size Pruning Performance: We’ve made this dramatically more efficient when you’re keeping a large number of log files.
• New Defaults and Refinements to Investigate Metrics: We’ve changed the default aggregation to the 95th percentile and done other minor changes to help rapid accurate assessment and comparison of data.

What’s Next?

The development team is deep into Loupe 6 with a focus on a significant upgrade to Loupe Desktop which didn’t get much attention for Loupe 5 and moving all of Loupe server to .NET 8. Of course, we’re also leaving room for enhancements requested by you - so let us know what you’d like to see!