Skip to content

feat(session): log Meraki X-Request-Id on 5xx responses (beta forward-port of #420)#425

Open
TKIPisalegacycipher wants to merge 1 commit into
betafrom
forward-port/x-request-id-beta
Open

feat(session): log Meraki X-Request-Id on 5xx responses (beta forward-port of #420)#425
TKIPisalegacycipher wants to merge 1 commit into
betafrom
forward-port/x-request-id-beta

Conversation

@TKIPisalegacycipher

Copy link
Copy Markdown
Collaborator

Forward-port of #420 to the beta branch.

Logs the Meraki X-Request-Id response header on 5xx responses so it can be handed to Meraki for server-side log lookup. Included in the per-retry warning and, once retries are exhausted, logged at error level. When the header is absent, none is logged in its place.

Applied as a clean git cherry-pick -x of the #420 feature commit; beta's 5xx handling was byte-identical to main's pre-#420 state.

Tests: 13 X-Request-Id tests pass.

🤖 Generated with Claude Code

When a 5xx response is received, the sync and async REST sessions now log
the Meraki X-Request-Id response header so users can hand it to Meraki to
look up the request in server-side logs. The id is included in the
per-retry warning and, once retries are exhausted, logged at error level.
When the header is absent, "none" is logged in its place to aid debugging.

(cherry picked from commit 6e22423)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant