Operators need the same request identifier in API Gateway access logs, Lambda logs, and X-Ray traces for a single citizen complaint. What practice enables that correlation?
Select an answer to reveal the explanation.
Short Explanation
Chasing one citizen ticket across three tools without a shared id is like hunting a library book with three different call numbers. Carry one request or correlation id through API Gateway, Lambda logs, and X-Ray. Then one complaint becomes one story.
Full Explanation
Correlation requires propagating a consistent request identifier across observability signals—API Gateway access logs, application logs, and distributed traces. Generating fresh ids per hop, logging unrelated settings, or disabling access logs breaks end-to-end investigation. Shared identifiers let municipal operators reconstruct a single citizen request path.