Menu
AWS Lambda High Latency Troubleshooting
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/HolmesGPT/holmesgpt --skill lambda-performance-troubleshootingThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Any Elasticsearch error-log query against app-279-logs-* — these indices use ``lvl`` (keyword) for log severity, not ``severity`` or ``level``.
Guide for investigating slow PostgreSQL queries
Troubleshooting Application Gateway Problems
Showing SKILL.md
Based on SOC occupation classification
| 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)"