Loupe - Log - Monitor - Resolve
Loupe / User's Guide / Loupe Server / User's Guide - Issues - Introduction
In This Topic
    User's Guide - Issues - Introduction
    In This Topic

    How it Works

    Loupe analyzes all of the log data it receives and categorizes each warning, error, or critical log message into Log Events.  These events are compared between all of the sessions that have been received to identify the unique Application Events.  Depending the rules defined on the server or manual actions you take these Application Events can be used to create Issues. 

    This multi-tier aggregation method means that vast amounts of log data can be summarized into the smallest number of distinct items to be reviewed. 

    Lifecycle of an Issue

    Once an Issue has been opened it's considered either New (if it was opened by a Rule) or Active (if it was opened by a person).  New issues are on their own list so it's easy to review the issues that are being created automatically and suppress ones that shouldn't have been created. 

    An Open issue can be commented on, assigned to a person for them to work on, have additional related Application Events added to it, and ultimately be either Resolved or Suppressed.

    Issues Vs. Alerts

    Loupe is designed to perform automatic issue management for development teams as opposed to providing Alerts for operations teams.  The key distinction is the workflow - An Application Event and ultimately an Issue it is related to is expected to be resolved in a specific version of the application.  By contrast, an Alert could be resolved and a new Alert open from the same underlying error message without requiring a new software version.  For example, a server losing network connectivity would cause errors that should raise an alert and once the network is restored the alert can be marked resolved.  If connectivity is lost again a new Alert should open.  Throughout this no new version of the application is generated.

    See Also