feat: propagate request correlation ids across services - #248
Merged
elizabetheonoja-art merged 1 commit intoAug 19, 2026
Conversation
telemarkdigital-publisher
force-pushed
the
telemark-correlation-id-245
branch
from
August 19, 2026 13:50
1695220 to
4cd75b8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary: Adds sanitized x-correlation-id extraction/generation middleware, stores the ID in request/task context, returns it on responses, includes it in structured JSON logs, propagates it through service-mesh HTTP calls, and attaches it to Kafka/message headers. Adds unit and integration coverage for HTTP context/response propagation, message headers, and log correlation fields. Testing: Not run locally because cargo/rustfmt are not installed in this Windows Codex environment. Closes #245.