Loupe Server - Notifications
In This Topic
Loupe can automatically generate notifications in response to events like new errors being detected or issues being closed. These notifications can be sent to services like Google Hangouts, Microsoft Teams, Slack or email to Loupe users.
Image Title
|
What Kind of Notifications Are Supported?
There are several types of notifications the Server can generate:
- New Session Notification: When a qualifying session is received with a summary of the overall session. View a sample notification.
- Session Events Notification: When a qualifying session is received for each qualifying event within the session. View a sample notification.
- New Event: The first time a unique event has been received.
- Event for Review: An event has been added to the review list, waiting for triage.
- Issue Opened or Reopened: For the requested applications receive an alert whenever an issue is opened or reopened.
- Issue Changed: For the requested applications receive an alert whenever an issue is modified.
- Issue Closed: For the requested applications receive an alert whenever an issue is suppressed or resolved.
- Alert Opened or Reopened: An alert was opened or reopened.
- Alert for Review: An alert was added to the list for manual review.
- Alert Changed: An alert was updated (other than being opened or closed).
- Alert Closed: An open alert has been resolved or suppressed.
These events are generated automatically as data arrives at the server, is analyzed, and users interact with the server.
Configuring Notifications
Administrators can configure all notifications using the Notification area from the Administration option on the user menu. This displays the Notification Rules in three lists based on the event that would trigger the notification.
Individual Users can configure notifications just for themselves in the Your Settings area from the user menu. This displays all of the Notification Rules that involve that user. New rules can be added and modified that will exclusively send messages to the current user.
When an issue is assigned to an individual they are automatically notified. When an issue is modified or closed the current assigned user is also notified. When an issue is closed the individual that opened it is notified. No configuration is required for these notifications.
Recommended Notifications
Application Event for Review
To best support the triage process within Loupe we recommend a member of the development team (such as the technical lead or project manager) get notified each time a new error shows up on the review list for an application they're responsible for. Alternately, route this to your team communication channel in Slack or Teams. This will keep you informed as new problems show up that need to be investigated.
Alert Opened or Reopened
If you want to monitor what's happening in your critical production area, set up a notification for alerts in the Application Environments that have the appropriate promotion level, such as Production. This event can produce a lot of information so it may be best to run it to a team communication channel on Slack or Teams instead of email.
Which Sessions Trigger Notifications?
- When a session arrives at the Server it's checked against the suppression rules. If it matches, session notifications won't be generated (although application event and issue notifications can since they are not specific to any particular session).
- The session is checked against all of the notification rules to identify if it should be scanned for session notifications or message notifications.
- If it matches two rules that would result in the same content to the same destination (service or user) only a single message will be sent.
- The final message(s) are sent out to the list of unique services and email addresses.
For more information on how to configure notification rules, see Loupe Server - Notification - Rules.
See Also