Lumigo Docs

Knowing is half the battle with most failures, and AWS Lambda is no different. The sooner you are informed of an issue with your serverless architecture, the sooner you are able to begin work on a fix.

In support of this, Lumigo gives you the capability to send alerts directly to your Slack workspace or e-mail inbox.

Configuring Alert Policies

To configure alert policies for your functions:

Adding Alerts with the Lumigo UI

  1. Hit the 'Add Alert' button.
  2. Choose the type of alert and the alert’s condition (triggering event).
  3. Select the functions that should send this alert.
  4. Click on 'Add Alert'.

Adding Alerts with AWS Tags

If you are using auto-tracing for your Lambda functions, alerts will already be added automatically.

If you're not using auto-tracing, the fastest way of adding alerts to your functions automatically is by flagging them using AWS Tags. To do so:

  1. Open the configuration for your AWS Tags
  2. Create the tag lumigo:auto-alert and set the value to basic
  3. Apply the tag to your Lambda function
  4. Wait 15-20 minutes for the changes to propagate.

Lumigo will now automatically report statistics on your Lambda function!

  • Using the auto-alert tag will override any alert configurations that were previously configured with the UI.



We recommend that you limit the alert rate for policies that are based on single events in your system, such as Lambda Errors.

  • One function tends to fail in batches, with large periods of inactivity between them. Throttling this function's alerts to "24 Hours" will limit notifications to once a day, preventing you from being bombarded with Slack notifications abd emails.
  • For functions where all failures are critical, you can disable throttling entirely by selecting “Never” from the dropdown. With this option selected, you will receive a notification each time the function fails.

Ready to set up your alerts?

Updated 2 months ago


Suggested Edits are limited on API Reference Pages

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