When something goes wrong you will want to know about it as soon as possible so that you can immediately get to work fixing it. Lumigo provides you with the ability to closely monitor your environment and be notified of a problem as soon as it arises so that you can quickly take remedial action.
Lumigo comes with a number of predefined Alert Policies, and you can define (and edit) additional Alert Policies from the Alert Policies page, which you can access by clicking the Alerts button on the navigation bar or Manage Alerts on the Issues page.
The first thing you want to do when a problem occurs is to notify the relevant staff so that they can investigate the problem and take remedial action. Lumigo enables you to define notifications individually for each alert type depending on its urgency: you can page people about urgent alerts or email people about alerts that can wait.
The Notification channels currently available in Lumigo are shown below.
Once you've connected Lumigo to your preferred notification channels, you'll need to choose which alerts to receive. Click on the "Alerts" on the navigation bar, which you can access by clicking the Settings button on the navigation bar.
- Select the service you want to set up the alert for
- Select the resources that you wish to monitor for alerts
- Select the alert type and define the condition
- Define the notification preferences
- Click “Save Alert”
Note: We recommend that you limit the notification frequency for policies that are based on single events in your system, such as Lambda Errors. This reduces potential noise when sifting through alerts in high-traffic systems.
Below are a couple of different alert scenarios that can be managed through Lumigo's Alert Policies:
- You have a batch processor built on AWS Lambda that is driven by a single function. This function is only active when batches are processed, at which point multiple failures are generated in a row. Using a notification frequency value of "24 hours" prevents your slack channel from receiving hundreds of notifications by reducing the notification period to once every 24 hours.
- You have a business-critical function that drives your payment platform integration. When this Lambda function fails, you have to know immediately - every failure is critical. Using a notification frequency value of "Every Error" lets you receive each alert as the failures occur, generating emails to support and notifications in PagerDuty as needed.
Prevent alert emails from going to spam
While the spam filters for email providers are pretty good, sometimes they make mistakes in flagging emails as spam. Here's how to make sure alerts emails don't land in your spam folder:
Updated about a month ago