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.3 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-outbound-persistence-jpa-c19 | runbook이 지목하는 지표를 만드는 호출이 없다 | state-machines-and-ownership | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-outbound-persistence-jpa-c19 | 2026-09-01 |
|
|
|
adapter-outbound-persistence-jpa |
runbook이 지목하는 지표를 만드는 호출이 없다
JpaTransactionObservation.recordCompletionUnknown(...) 구현은 존재하지만 production에서 그것을 부르는 곳이 없다.
본문
JpaTransactionObservation.recordCompletionUnknown(...) 구현은 존재한다. 하지만 production에서 참조 수를 세면 이렇다 — JpaObservabilityAutoConfiguration construction = 0, JpaTransactionObservation.recordCompletionUnknown(...) call = 0, recordCommitted/recordRolledBack/recordTimedOut call도 0.
JpaObservabilityAutoConfiguration 참조 위치
:::evidence key="adapter-outbound-persistence-jpa-c19" alt="코드베이스에서 JpaObservabilityAutoConfiguration 를 검색한 출력 2줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="JpaObservabilityAutoConfiguration 코드베이스 검색 — 2줄 · exit 0" zoom="true" :::
기본 listener도 비어 있다
JpaPlatformRuntimeAutoConfiguration이 만드는 default RetryEventListener도 empty implementation이며, JpaObservabilityAutoConfiguration을 통해 metric listener로 합성하지 않는다.
runbook 신호의 생성 근거를 찾지 못했다
runbook의 jpa.transaction.completion.unknown signal은 현재 source wiring으로는 생성 근거를 찾지 못했다. 이 observability factory 전체의 reachability 문제는 later observation/baseline capability sub-scope에서 다시 exhaustive하게 확인한다. 여기서는 completion-unknown path의 cross-scope evidence로만 기록한다.