Skip to content

api-gateway lacks a global request id in logs for cross-service correlation #568

Description

@therealjhay

ProblemEach service logs its own ids; without a shared header propagation, tracing a payment across gateway → settlement → indexer is manual.

  1. No distributed request-id header.
  2. Logs not correlated.
  3. Troubleshooting slow.

Solution

  • Propagate a trace/request id across service boundaries.
  • Log it consistently.
  • Test propagation.

Acceptance Criteria

  • One id correlates a request across services.
  • Logs carry it.
  • pnpm build passes.

Note for Contributors: Write a clear PR description. Show a correlated trace across services.

Activity

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

Metadata

Metadata

Assignees

Labels

GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardThird CampaignCampaign: Third Campaign

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions