بنقرة واحدة
بنقرة واحدة
| name | lambda-performance-troubleshooting |
| description | AWS Lambda High Latency Troubleshooting |
This runbook helps diagnose and resolve AWS Lambda function performance issues including high latency, timeouts, and cold starts.
Use CloudWatch to check Lambda function latency over time:
aws cloudwatch get-metric-statistics --namespace <lambda-namespace> \
--metric-name Duration --dimensions Name=FunctionName,Value=<function-name> \
--statistics Average,Maximum --start-time <start-time> \
--end-time <end-time> --period 300
Look for errors or slow operations in CloudWatch Logs:
aws logs filter-log-events --log-group-name <lambda-log-group>/<function-name> \
--filter-pattern "[ERROR] OR [WARN] OR timeout" --limit 100
Query CloudWatch for cold start frequency:
aws cloudwatch get-metric-statistics --namespace <lambda-namespace> \
--metric-name InitDuration --dimensions Name=FunctionName,Value=<function-name> \
--statistics Average,Count --start-time <start-time> \
--end-time <end-time> --period 300
Verify Lambda isn't hitting concurrency limits:
aws cloudwatch get-metric-statistics --namespace <lambda-namespace> \
--metric-name ConcurrentExecutions --dimensions Name=FunctionName,Value=<function-name> \
--statistics Maximum --start-time <start-time> \
--end-time <end-time> --period 60
Check if function needs more memory allocation:
aws logs insights start-query --log-group-name <lambda-log-group>/<function-name> \
--start-time <epoch-start> --end-time <epoch-end> \
--query-string "fields @timestamp, @message | filter @type = 'REPORT' | stats max(@maxMemoryUsed), avg(@memorySize)"
Guide for investigating slow PostgreSQL queries
Troubleshooting Application Gateway Problems
Database Connection Troubleshooting
Python Application Memory Troubleshooting
Service Connectivity Issues
Use this skill when the user asks to "patch a CVE", "fix a CVE", "handle a CVE", "check a CVE", or discusses Docker image vulnerabilities, docker scout findings, or Go/dependency CVE remediation in the Dockerfile.