P1 gateway: propagate X-Request-ID to upstreams

[SlavaKuntsov]

Phase / Priority / Area

Phase 14 · Priority P1 · Area gateway

Зависимости

Blocks: #11, #12, #14

Scope

services/gateway/internal/proxy/proxy.go:18, services/gateway/cmd/server/main.go (middleware.RequestID), services/metadata, services/upload, services/auth

Goal

Трассировка запроса end-to-end.

Acceptance Criteria

• X-Request-ID (chi), X-User-ID, X-Forwarded-For прокидываются во все ReverseProxy.Director
• Логи metadata/upload содержат request_id

Проверки

curl -H X-Request-ID:test123 /api/v1/videos → grep логов всех сервисов содержит test123

Out of scope

Метрики

[SlavaKuntsov]

Pull request opened

#39 — will auto-close via Closes #11 on merge.

Verification

• make lint-go — 0 issues
• make lint-py — success
• make lint-front — ok
• make test-go/test-py — pass
• make up --build -d — all Healthy (prometheus, loki, grafana)
• make e2e — PASS
• curl -H X-Request-ID:test123 → logs contain trace_id; Loki query {service="gateway"} |= "test123" — success

Remaining risks

• Loki allow_structured_metadata false (v11), Promtail docker.sock, rabbitmq_queue_depth Gauge 0 — см. PR Risks