Skip to content

examples: X-Request-Id and request correlation docs - #9

Merged
matviychuk merged 2 commits into
mainfrom
docs/request-correlation-examples
Apr 9, 2026
Merged

examples: X-Request-Id and request correlation docs#9
matviychuk merged 2 commits into
mainfrom
docs/request-correlation-examples

Conversation

@matviychuk

Copy link
Copy Markdown
Contributor

Aligns samples with PlanVault request correlation: optional inbound X-Request-Id / traceparent, echoed response header, RFC 7807 instance on errors, and async session logging.

Changes

  • README.md — behaviour note + pointers to main repo docs/api-reference.md and api-docs.
  • scripts/bash-e2e — one X-Request-Id per run (openssl hex fallback).
  • frontend/react-chat — fresh X-Request-Id per HTTP call; errors append [support id: …] from header or instance.
  • webhooks/kafka-trigger — Python / Scala / Java workers send X-Request-Id per POST; README note; Python DLQ log includes response echo when present.

Verification

  • npm test in frontend/react-chat
  • sbt compile (scala-fs2), mvn compile (java-spring), py_compile (worker.py)

Made with Cursor

Bohdan added 2 commits April 9, 2026 10:44
- Root README: request correlation (headers, instance, CORS) with links.
- bash-e2e: stable X-Request-Id per run for log grep / support.
- react-chat: fresh X-Request-Id per fetch; error UI shows support id from header or RFC 7807 instance.
- Kafka workers (Python, Scala, Java): X-Request-Id per webhook POST; Python logs echoed id on DLQ path.
- Kafka README: note on correlation for inbound deliveries.

Made-with: Cursor
@matviychuk
matviychuk merged commit 83b7ffe into main Apr 9, 2026
10 checks passed
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.

1 participant