Request Correlation ID Propagation Across Services

[elizabetheonoja-art]

Problem Statement

Debugging distributed requests requires correlating logs across multiple services. Implementing correlation ID propagation enables end-to-end request tracing.

Technical Bounds

• Generate unique correlation ID at API gateway
• Propagate via HTTP headers and message queues
• Include in all log outputs automatically
• Store in request context for downstream use

Steps

1. Implement correlation ID middleware
2. Add header propagation for HTTP calls
3. Integrate with message queue producers/consumers
4. Update logging framework to include correlation ID
5. Add distributed tracing visualization

[telemarkdigital-publisher]

I can take this if still available. Plan: add a request correlation ID middleware/context path, propagate the ID on outbound HTTP and queue boundaries where the current code exposes those seams, include the correlation ID in structured logs, add focused middleware/propagation tests, and document any visualization follow-up that is outside the repo's present tracing stack. Expected verification: cargo test --workspace plus targeted tests for request/header/log propagation. I will wait for maintainer/GrantFox assignment or acknowledgment before substantial implementation.

[telemarkdigital-publisher]

Submitted PR #248: #248. It adds sanitized x-correlation-id middleware, request/task context storage, response header echoing, structured-log correlation fields, service-mesh HTTP propagation, Kafka/message header propagation, and focused tests. Local validation note: git diff --check passes; cargo/rustfmt are not installed in this Windows Codex environment, so I could not run the Rust test suite locally.

[telemarkdigital-publisher]

PR #248 was merged for this assigned issue: #248 @grantfox-oss please confirm if any reward tracking or follow-up is needed from my side.