Geo: Add correlation ID when a secondary site proxies requests to a primary

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Work on this issue
• Close this issue

What / why

Because GitLab Geo is composed of multiple services (at least one primary and one secondary site), relevant logs need to have a common identifier to allow debugging across services.

For example, when a Git Push occurs, the correlation ID should propagate across sites.

Proposal

• When a secondary site proxies a request to a primary site, it should include its correlation ID
• When a primary site receives a proxied request from a secondary site, it should use the included correlation ID

Implementation

TBD