A citizen portal UI calls a back-end that then invokes the Meraki API. On-call staff cannot join those hops when troubleshooting. Which logging-design choice fixes that?
Select an answer to reveal the explanation.
Short Explanation
A correlation id is the claim ticket that follows a package from counter to truck to door. Without it, UI, back-end, and Meraki attempts are three strangers in the log pile.
Full Explanation
Effective logging design propagates a request or correlation identifier across the UI, application back-end, and outbound Cisco API attempts the app owns. That stamp enables join queries during diagnosis. Isolated lines with no shared id defeat later troubleshooting even when each component logs verbosely.