Add request logging middleware with correlation ID injection

[usmanimamu17-create]

Labels / Complexity: observability · Trivial — 2 pts

Summary

The backend has a CorrelationMiddleware (app/middleware/correlation.py) that generates or propagates correlation IDs, but request logging does not include the correlation ID in every log entry. This makes it difficult to trace requests across services when debugging issues.

Proposal

• Update app/core/logging_config.py to include correlation_id in the log format
• Ensure all loggers use the correlation context from app/utils/correlation_ctx.py
• Verify that the correlation ID is included in the X-Correlation-ID response header

Acceptance criteria

• Every log entry includes the correlation_id field
• The X-Correlation-ID header is present in all API responses
• A test verifies correlation ID propagation from request to response

Out of scope

Distributed tracing with OpenTelemetry (already implemented via app/core/tracing.py).

Getting started

Files in scope:

• app/core/logging_config.py
• app/middleware/correlation.py
• app/utils/correlation_ctx.py

Build/test commands:

pytest tests/test_correlation_exceptions.py

Good first files to read: app/middleware/correlation.py, app/core/logging_config.py.

[Taylor-Kay]

Please can i work on this

[grantfox-oss]

🦊 GrantFox — @Taylor-Kay has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #243)
2. Your PR will be reviewed by the ApexChainx maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@Taylor-Kay's PR #256 was approved and merged by @usmanimamu17-create.

🏆 @Taylor-Kay: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (131 total points). Track your full progress on GrantFox.

👏 Great work, @Taylor-Kay! Keep contributing to ApexChainx.