Threshold configuration for AWS Lambda

Add a new threshold configuration for Lambda function monitor.

When a new Lambda function gets added, it is associated with a default threshold profile. This profile doesn’t contain any pre populated metric values configured. You can either edit the default threshold profile or create yourself a new one.

To create a new threshold profile for your Lambda function monitor follow the below mentioned steps. To add users and to customize alert settings visit our User and Alert management page.

1. Click Admin > Configuration Profiles > Threshold and Availability.
2. Click Add Threshold and Availability in Threshold and Availability screen.
3. Specify the following details:
   • Monitor Type: Select Lambda Function from the drop down list.
   • Display Name: Provide a label for identification purpose.

   The performance counters supported for Lambda monitoring will be shown below. Configure values in the fields provided, these values will act as your thresholds. When a threshold gets breached, your monitor status will change to trouble and alerts will be triggered out via the configured notification channel. You can also view error log events to identify errors and bottlenecks.

   

   Once you are done configuring threshold values, you can go ahead and save the profile. Once done, the newly created threshold profile will be listed in the Threshold and Availability screen.

   Advanced threshold settings (Strategy)

   You can also validate the threshold breach by selecting relevant strategies and applying various conditions for any performance counter. For example, lets take a scenario where you have mapped your Lambda function to a stream based event source like Kinesis or DynamoDB streams. When new records get added, the Lambda service invokes your function to process them. If your application writes a particularly large batch of records, then the chances of your function invocation requests getting throttled gets a little high. For such a scenario, you don't need to get alerted at the onset. So instead you can define an alert strategy, that sends out notification only when the throttled metric continues to spike for 2 or 3 consecutive poll intervals. (Note: polling for Lambda function happens every 5 minutes)

   Advanced Threshold Settings (Strategy):
   Poll count serves as the default strategy to validate the threshold breach. You can validate threshold breach by applying multiple conditions (=,>, <, >=, <=) on your specified threshold strategy. The monitor’s status changes to ”Trouble”  when the condition applied to any of the below threshold strategies hold true:

   • Threshold condition validated during the poll count (number of polls): Monitor’s status changes to trouble when the condition applied to the threshold value is continuously validated for the specified “Poll count”.
   • Average value during poll count (number of polls): Monitor’s status changes to trouble, when the average of the attribute values, for the number of polls configured, continuously justifies the condition applied on the threshold value.
   • Condition validated during time duration (in minutes): When the specified condition applied on the threshold value is continuously validated, for all the polls, during the time duration configured, monitor’s status changes to trouble.
   • Average value during time duration (in minutes): Monitor’s status changes to trouble, when the average of the attribute values, for the time duration configured, continuously justifies the condition applied on the threshold value.

   
   Multiple poll check strategy will not be applied by default. During the conditions where no strategy could be applied, the threshold breach will be validated for a single poll alone.

    

   To make sure the condition applied on the strategy “Strategy-3: Time duration or Strategy-4: Average value during time duration” for threshold breach detection works as intended, you must ensure that you specify a time duration which is at least twice the applied check frequency for that monitor.

    

   Edit Threshold profile for Lambda function

   1. Click the profile which you want to edit.
   2. Edit the parameters which needs to be changed in the Edit Threshold Profile window.
   3. Click Save.

   Delete Threshold profile for Lambda function

   1. Click the profile in the Threshold and Availability screen which needs to be deleted.
   2. This will navigate to Edit Threshold Profile window.
   3. Click Delete.