Lambda functions may be an integral part of the correct operation of cloud native applications. Failures, throttles, or slow execution of Lambda functions could result in problems for upstream users or applications. You need to alert on these conditions.
AWS: Cloudwatch data
- Configure the Splunk Add-on for Amazon Web Services.
- Ensure that your deployment is ingesting AWS data through one of the following methods:
- Pulling the data from Splunk via AWS APIs. At small scale, pull via the AWS APIs will work fine.
- Pushing the data from AWS into Splunk via Lambda/Firehose to Splunk HTTP event collector. As the size and scale of either your AWS accounts or the amount of data to be collected grows, pushing data from AWS into Splunk is the easier and more scalable method.
- Run the following search. You can optimize it by specifying an index and adjusting the time range.
index="<AWS index name>" metric_dimensions="FunctionName=*" sourcetype="aws:cloudwatch" | table _time metric_dimensions metric_name Average Unit
The table provides an explanation of what each part of this search achieves. You can adjust this query based on the specifics of your environment.
|index="<AWS index name>"||Search the index(s) where AWS data is stored.|
|metric_dimensions="FunctionName=*"||Filter the results down to only Lambda function metrics.|
|sourcetype="aws:cloudwatch"||Filter the results to only the AWS CloudWatch data.|
|| table _time metric_dimensions metric_name Average Unit||Display the results in a table with columns in the order shown.|
Use these results to gain visibility into the health and performance of all Lambda functions deployed across your AWS infrastructure and take appropriate action.
You might also be interested in other processes associated with the Managing an Amazon Web Services environment use case.