Lumigo Docs

Set Up Alerts

Knowing when issues occur is a critical capability in monitoring your environment. The sooner you are informed on issues, the sooner you can begin work on a fix.

In support of this, Lumigo allows you to configure alert policies and send notifications to your preferred channels and email.

Lumigo comes with a number of predefined Alert Policies. You can define additional Alert Policies in the Alerts Policy page, which you can access by clicking the Alerts Policy button.

1. Set Up Notification Channels

Preferred notification channels are configured from within the Lumigo dashboard. Open your Integrations settings page Settings > Integrations to choose your notification channels. For email integrations, simply provide the alert email address. For other service providers, please refer to their respective documentation sections.

2. Set Up Alert Policies

Once you've connected Lumigo to your critical notification channels, you'll need to choose which alerts to receive. Click on the "Alerts Config" on the side navigation bar to open the Alerts Policies page.

  1. Select the service you want to set up the alert for
  2. Select the resources that you wish to monitor for alerts
  3. Select the alert type and define the condition
  4. Define the notification preferences
  5. 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.

Sample Alert Scenarios:

Below are a couple 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.

Updated 3 days ago

Set Up Alerts

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.