DongHyeonkaandClaude Opus 5
98a74e90a5
The forward upgrade to 26.7.3 was zero downtime across 87 samples, and since databasechangelog stayed at 210 the rollback to 26.7.0 also succeeded, which narrows D-2's conclusion: rolling back fails when the schema moved, not because of the version number. The row count is the check. Role changes never reach the upstream through request repetition; the session is a snapshot taken at login and only a new session picks up the new claim. Auditing the docs also surfaced that Prometheus scrapes only keycloak, kubelet, node-exporter and itself, so the B-layer experiments have no metrics to screenshot rather than missing screenshots. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
18 lines
741 B
Plaintext
18 lines
741 B
Plaintext
=== Prometheus 가 실제로 긁는 대상 (2026-09-04 18:10 KST) ===
|
|
keycloak 2개
|
|
kubelet 2개
|
|
node-exporter 2개
|
|
prometheus 1개
|
|
|
|
=== B층 구성 요소의 지표가 있는가 ===
|
|
redis_up 시계열 0개
|
|
redis_connected_clients 시계열 0개
|
|
redis_memory_used_bytes 시계열 0개
|
|
pg_up 시계열 0개
|
|
pg_stat_database_numbackends 시계열 0개
|
|
|
|
→ B-1·B-2·B-3·B-5 는 Grafana 증거를 만들 수 없다.
|
|
스크린샷을 안 찍은 것이 아니라 긁는 대상에 없다.
|
|
보완하려면 redis_exporter · postgres_exporter · BFF 의 /actuator/prometheus 를
|
|
scrape 대상에 추가해야 한다.
|