Skip to content

feat: propagate gateway correlation IDs and structured logs - #24

Merged
ramioooz merged 1 commit into
mainfrom
feature/222-gateway-correlation-logging
Sep 4, 2026
Merged

ramioooz merged 1 commit into
mainfrom
feature/222-gateway-correlation-logging

Conversation

@ramioooz

@ramioooz ramioooz commented Sep 4, 2026

Copy link
Copy Markdown
Member

Summary

  • Add a WebFlux correlation filter for every Gateway exchange, including rejected and unmatched requests.
  • Reuse a bounded safe X-Correlation-ID or generate a UUID.
  • Propagate the ID to downstream requests and return it in responses.
  • Enable ECS JSON console logging and emit one completion record with route, status, duration, environment, and correlation.id.
  • Keep credentials, tokens, cookies, request bodies, and banking data out of the request log.
  • Document the contract and SIT behavior.

Tracking

Closes digital-bank-java/.github#222

Related:

Verification

  • ./mvnw --batch-mode --no-transfer-progress verify
  • 20 tests passed.
  • Focused route integration: 7 tests passed.
  • helm lint helm --values helm/values-sit.yaml --strict
  • helm template api-gateway helm --values helm/values-sit.yaml
  • git diff --check

Merge Order

This PR is independent of config-repo#42, infra-sit#24, and infra-sit#25 and can merge in any order. No delay is required. After merge, rebuild/roll out the Gateway in SIT, then verify the response header and ECS records through the existing port-forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

TASK: Add gateway correlation ID propagation and structured request logging

1 participant