Loupe combines capabilities of a logging system, profiler, and application monitor. As indicated in the table below, there’s much more to Loupe than message logging:
| Data Type | Loupe Capabilities |
|---|---|
| Exceptions | + Unhandled exceptions including stack trace a type + Handled exceptions can be easily logged via Loupe API + User friendly exception display for handled and unhandled exceptions |
| Message Logging | + Records all .NET Trace, Debug, and Console messages + Integrates with DotNetLog, Log4Net, NLog and PostSharp out of the box + Easily integrated with other logging systems + Includes timestamp, thread information and source code reference for each message + Record Xml data along with your log messages |
| Configuration data | + User name, computer name, command line arguments + Time zone and culture (O/S, Process and UI) + Product and application name, description and version number + Name, location and version number on each loaded assembly + Operating system family, version and service pack + .NET framework version + Processor and O/S Architecture + Processor info, memory and screen size + Thread details for each managed thread that logs messages + Custom properties from app.config file such as CustID, etc |
| System events | + Assembly Load, AppDomain Unload, Process Exit + Network Address Changed, Network Availability Changed + Display Settings Changing/Changed + Power Mode Changed + Session Switch, Session Ending + Time Changed |
| Performance counters | + Memory (9 process + 3 system counters) + Processor (3 process + 1 system counters) + Disk (4 total + 8 counters per disk) + Network (5 counters per interface) |
| Custom Metrics | You can create any number of custom application-specific metrics you want to track. You can go beyond simple performance counters to record many attributes for each metric to help you understand the usage and performance of your application. |
Loupe data is stored in highly compressed files under the Common Application Data folder. You never need to worry about this folder because Loupe manages these files for you. Files are automatically deleted when they become too old, too large or if the amount of free space on the disk drops too far. If you use Loupe with multiple applications, you can set quota levels independently for each application.