CloudWatch Metric Guide
AWS Lambda CloudWatch AlarmsThresholds, failures, and debugging guides
4 CloudWatch metrics covered for AWS Lambda. Each guide includes the recommended alarm threshold, common root causes, and how ConvOps automatically diagnoses it when it fires.
4
metrics covered
AWS/Lambda
namespace
9
verification checks
AWS Lambda metrics
Errors
Errors counts the number of Lambda invocations that resulted in a function error — including exceptions thrown by the function code and runtime errors (timeout, out-of-memory, handler not found).
Threshold
> 0 in any 5-minute window for critical functions; > N errors/minute for high-volume functions (set N based on your acceptable error rate)
Duration
Duration measures the elapsed wall-clock time from when the Lambda function handler begins executing to when it returns or times out. CloudWatch publishes minimum, maximum, average, and percentile statistics.
Threshold
p99 Duration > 80% of the function's configured timeout
Throttles
Throttles counts invocation requests that Lambda rejected because concurrent execution limits were reached. A throttled invocation was not executed — the caller receives a 429 TooManyRequestsException.
Threshold
> 0 for critical functions; for high-volume functions, a low absolute count threshold based on your acceptable drop rate
ConcurrentExecutions
ConcurrentExecutions reports the number of Lambda function instances actively processing events at any given time, across the entire account or per function when filtered by function name.
Threshold
> 800 concurrent executions at the account level (for accounts at the default 1,000 limit)
Audit your setup
Missing a AWS Lambda alarm?
The free ConvOps Audit scans your CloudWatch setup and flags missing or misconfigured AWS Lambda alarms in 5 minutes. No credit card. Read-only access.
Looking for alarms across other AWS services? View the full CloudWatch metric guide — thresholds and debugging guides for RDS, Lambda, ECS, ALB, EC2, and DynamoDB.
When a AWS Lambda alarm fires, ConvOps Diagnose reads CloudWatch Logs, CloudTrail, and resource state to deliver a plain-English root cause to WhatsApp or Slack in under 60 seconds. See how ConvOps Diagnose works →