Set Up Alerts

When something goes wrong in your development or production environment, you will want to know about it immediately and fix it. Lumigo lets you closely monitor your environment and alert you about any issue as soon as it arises.

Lumigo comes with a number of predefined Alert Policies, and you can define (and edit) additional Alert Policies from the Alert Policies page.

Set Up Notification Channels

When a problem occurs, the first thing you may want to do is to notify your team so that they can investigate and troubleshoot the issue. Lumigo enables you to define individual notifications for each alert depending on its urgency. You can notify people about urgent alerts or email people about alerts that can wait.

To configure notifications, navigate to Settings > Integration. The following notification services are available in Lumigo:

20702070

Creating Alerts

To create alerts:

  • Navigate to Alerts and click Create New Alert.
  • Select the type of alert you want to create.
  • Select the service and resources to which the alert applies.
  • Specify the condition that will trigger the alert.
  • Click Save
26702670

📘

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.

Sample Alert Scenarios

The following are 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 when 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: