Loupe Monitor provides operations-focused features for teams operating software they develop.  Compared to Loupe Resolve:

• Where Apps Run Matters: The environment where an application is running is the primary factor for importance - Production errors are very important, but errors in the same software running on a developer desktop don't.
• Multiple Apps can Work Together: Modern systems often have multiple applications that all have to work together to deliver functionality.  For example, a web application and background order processing services both have to be monitored together.
• Fixing Problems isn't just Software: Most problems are operational in nature, fixed by correcting an external system like a database or network.  Fixes often don't involve shipping new versions of software.

Loupe Monitor addresses these problems by taking the log data sent by agents and grouping it into different Application Environments and Services.  When errors are found in the log data an Alert is opened (or updated) to track the problem until it's fixed.

What Loupe Monitor Does

Once your application is set up to use Loupe Monitor, you can:

• Track Problems with Alerts: When a runtime error occurs - whether the result of a software bug or a problem with how your application is hosted or an external dependency - an Alert is opened so you can track the problem from start to finish.
• Investigate Performance: See metrics aggregated across all instances of a clustered application to see how web pages perform, how often database calls are made (and how long they took), and other custom metrics you capture.  For more information, see User's Guide - Monitor - Investigate.
• Understand your Application: View the detailed log data across all instances of a clustered application to see what happened, step by step, as your application ran.  For more information, see User's Guide - Monitor - Investigate.

How it Works

The same Loupe data for each session - logs, metrics, and events - is grouped together by Application Environment Service (such as your Web Application in Production) and then distinct errors will be pulled together into Alerts and displayed on the dashboard in Loupe Monitor.

To take advantage of Loupe Monitor:

1. Define an Application Environment: Let Loupe know the application and environment combinations you care about.  For example, a given web application running in production. See User's Guide - Monitor - Application Environments.
2. Add Loupe to your Application: If you haven't already, add Loupe to your application software following the relevant instructions in Getting Started - Adding Loupe to your Application .
3. Add the Application Key to your config: Each Application Environment has a unique Application Key so Loupe can bundle together the right sessions.
4. Run your Application: As your application runs, the Loupe session data will get merged together to create a common log view and errors will be integrated into alerts.  If you have multiple applications working together, each will automatically create a Service within the Application Environment.