Implement Request Correlation ID Tracing (X-Request-ID) to Celery Worker Logs

[hardikkaurani]

🟡 Intermediate Issue

Problem

HTTP X-Request-ID headers from API requests are not propagated to Celery async worker logs, making it impossible to correlate API requests with background task execution.

Why It Matters

Request-ID tracing enables end-to-end request correlation for debugging, audit logging, and observability across the distributed system.

Suggested Files

• backend/app/jobs/queue/tasks.py
• backend/app/core/ (middleware or logging module)

Definition of Done

• X-Request-ID propagated to Celery task contextvars.
• Worker logs include matching request_id context.
• Pytest verifies request ID propagation.

[hardikkaurani]

👋 Maintainer Solution Guide:

1. Add middleware that reads or generates X-Request-ID on each HTTP request
2. Store it in Python contextvars.ContextVar
3. In backend/app/jobs/queue/tasks.py, read the context var and include request_id in task kwargs/headers
4. Worker log messages should include request_id field
5. Test with pytest verifying the ID appears in both API response headers and task logs

Critical observability feature! 🔍