DongHyeonkaandClaude Opus 5
b2963105a8
The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.
Follows the import procedure in README.md.
source/ the originating repository verbatim — 78 documents, 28 SVGs,
8 manifests, plus .source-revision recording the commit
final/ the SSOT
document.md 729 lines written from the 29 experiment documents, not
concatenated: what was predicted, what was measured, and
where the measurement itself was wrong
evidence/raw 125 outputs, flattened to <experiment>__<file> because
the originals collided (01-baseline.txt appeared three
times) and the audit only globs the top level
evidence/meta one per raw file; command and exitCode are null and the
README says why rather than inventing them
evidence/browser 22 captures
assets/ three diagrams through techviz
.techviz/ their VizSpecs
A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.
Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.
verify-pipeline.py passes. audit-records.py reports no issues.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2.0 KiB
2.0 KiB
kind, slug, title, topic, project, status, sourceRevision, rootTreeNode, evidenceCapturedOn, assets, evidence, source, module
| kind | slug | title | topic | project | status | sourceRevision | rootTreeNode | evidenceCapturedOn | assets | evidence | source | module | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CONCEPT | adapter-inbound-web-c15 | 상관 식별자를 만드는 필터가 세 벌이다 | observability-models | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-inbound-web-c15 | 2026-09-01 |
|
|
|
adapter-inbound-web |
상관 식별자를 만드는 필터가 세 벌이다
WebMvcRequestIdFilter·RequestLoggingFilter·WebFluxRequestContextFilter 셋이 상관 식별자를 각각 만든다. 세 번째는 전송이 달라 공존이 정상이고, 앞의 둘은 같은 서블릿 체인에서 같은 헤더를 두 번 처리한다.
본문
상관 식별자를 만드는 메커니즘이 셋이다.
| 메커니즘 | 헤더 | 저장 위치 |
|---|---|---|
WebMvcRequestIdFilter |
X-Request-Id, traceparent |
요청 속성(WebRequestId/WebTraceId) |
RequestLoggingFilter |
X-Request-Id, X-Correlation-Id, traceparent |
MDC |
WebFluxRequestContextFilter |
X-Request-Id, traceparent |
Reactor context |
RequestLoggingFilter 참조 위치
:::evidence key="adapter-inbound-web-c15" alt="코드베이스에서 RequestLoggingFilter 를 검색한 출력 22줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="RequestLoggingFilter 코드베이스 검색 — 22줄 · exit 0" zoom="true" :::
서블릿 체인에서 같은 헤더가 두 번 처리된다
세 번째는 전송이 달라 공존이 정상이다. 앞의 둘은 같은 서블릿 체인에서 같은 헤더를 두 번 처리한다. traceparent도 마찬가지로 두 번 파싱되며, RequestLoggingFilter는 응답에도 traceparent를 쓰고(:68) WebMvcRequestIdFilter는 쓰지 않는다.