Error rate for a city payments Lambda is flat, but p99 latency spik…

Question

Error rate for a city payments Lambda is flat, but p99 latency spiked. X-Ray shows a slow downstream payment provider call rather than elevated Lambda CPU. Where should the team focus first?

Accepted Answer

The downstream dependency highlighted by the trace, not an assumed local CPU bottleneck in the Lambda. — Flat errors plus a p99 spike is a traffic jam, not a crash. X-Ray pointing at the payment provider means look downstream first—do not blame the Lambda CPU when the trace already named the slow neighbor.

Answer

Only vertical scaling of Lambda memory without reading traces.

Answer

Deleting all CloudWatch log groups to reduce latency.

Answer

Rewriting DynamoDB table names because latency always means a wrong table name.

Error rate for a city payments Lambda is flat, but p99 latency spiked. X-Ray shows a slow downstream payment provider call rather than elevated Lambda CPU. Where should the team focus first?

Short Explanation

Full Explanation