An Alert Policy defines the conditions under which an alert is triggered for a resource and, optionally, specifies whether to generate notifications to the relevant team members, by email or other channels such as Slack or PagerDuty.
On the “Alert Config” page, click the “Create New Alert”
- 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”
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:
- Open the configuration for your AWS Tags
- Create the tag
lumigo:auto-alertand set the value to
- Apply the tag to your Lambda function
- Wait 15-20 minutes for the changes to propagate.
Lumigo will now automatically report statistics on your Lambda function!
- Using the
auto-alerttag will override any alert configurations that were previously configured with the UI.
We recommend that you limit the notification frequency 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 notifications.
- 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.
Updated 3 days ago