# Registry: Metrics # Schema owner: feature-contract-registry-governance # Owner branch: feature-metrics-alerting-contract # Last updated: 2026-05-22 # # 읽는 법 # - 이름: Micrometer dot.case에 단위 접미사(.seconds | .bytes | .total)를 붙인다. # - tag 값 개수(cardinality) 상한의 정본은 feature-metrics-alerting-contract의 "Cardinality Bounds" 표다. # - 값 개수가 많은 tag는 어디서도 쓰지 않는다: user_id, request_id, raw_url, raw_query, # raw_header_value, ip_address. 어떤 행에도 나오면 안 된다. # - tenant_id label은 크기가 정해진 매핑 표의 id나 cohort bucket만 쓴다(ULID 원문 금지). # - error_code tag의 cardinality_limit은 error-codes.yaml 행 수를 따른다(최대 100). # - alert_severity_thresholds 값은 경보 조건을 사람이 읽는 글로 적은 것이다. 지표 이름·연산자· # 기간(5m, 1h)은 원문 그대로 두고, 테스트는 키(p1·p2·p3)와 값이 비어 있지 않은지만 본다. metrics: # === HTTP 서버 (inbound) === # source: feature-metrics-alerting-contract — Metric/Alert Defaults # "HTTP metric | http.server.requests with method/status/uri-template | raw URL or user id tag" - name: http.server.requests type: timer unit: seconds tags: - name: method cardinality_limit: 8 allowed_values: [GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS, OTHER] - name: status cardinality_limit: 7 allowed_values: [1xx, 2xx, 3xx, 4xx, 5xx, ok, other] - name: uri_template cardinality_limit: 200 validation: must_be_template_not_raw_uri percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: p1: "error_rate > 5%가 5m 동안, 또는 > 10%가 1m 동안" p2: "error_rate > 1%가 10m 동안" p3: "error_rate > 0.1%가 1h 동안" owner_branch: feature-metrics-alerting-contract log_field_mapping: [method, status, uri_template] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: feature-metrics-alerting-contract — P1/P2/P3 정량 기준 (HTTP latency p99) # "P1: p99 > 5s 5분 / P2: p99 > 1s 10분 / P3: p99 > 500ms 30분" - name: http.server.requests.latency type: timer unit: seconds tags: - name: method cardinality_limit: 8 allowed_values: [GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS, OTHER] - name: uri_template cardinality_limit: 200 validation: must_be_template_not_raw_uri percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: p1: "p99 > 5s가 5m 동안" p2: "p99 > 1s가 10m 동안" p3: "p99 > 500ms가 30m 동안" owner_branch: feature-metrics-alerting-contract log_field_mapping: [method, uri_template, duration_ms] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # === HTTP client (outbound 의존 대상) === # source: feature-metrics-alerting-contract — Metric/Alert Defaults # "dependency metric | dependency.client.requests with dependency.name/type/outcome | endpoint with secret tag" # source: feature-outbound-http-client-baseline — "circuit breaker metric은 dependency.name, dependency.type, outcome까지만 tag로 허용" - name: dependency.client.requests type: timer unit: seconds tags: - name: dependency_name cardinality_limit: 50 - name: dependency_type cardinality_limit: 10 allowed_values: [http, grpc, db, cache, queue, broker, other] - name: outcome cardinality_limit: 5 allowed_values: [SUCCESS, FAILURE, CIRCUIT_OPEN, TIMEOUT, REJECTED] percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: p1: "필수 의존 대상이 2m 동안 응답하지 않음" p2: "선택 의존 대상이 5m 동안 저하됨" p3: "급증 경보(기준선의 10배)" owner_branch: feature-metrics-alerting-contract log_field_mapping: [dependency_name, dependency_type, outcome, duration_ms] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: feature-outbound-http-client-baseline — decisions # "retry/circuit breaker 기본 라이브러리는 Resilience4j" # source: feature-metrics-alerting-contract — "retry/CB minimum: resilience4j.retry.calls{outcome}" - name: resilience4j.retry.calls type: counter unit: total tags: - name: name cardinality_limit: 50 - name: outcome cardinality_limit: 5 allowed_values: [SUCCESS, FAILURE, CIRCUIT_OPEN, TIMEOUT, REJECTED] percentiles: null histogram_buckets: null alert_severity_thresholds: p2: "재시도 소진 비율 > 1%가 10m 동안" owner_branch: feature-outbound-http-client-baseline log_field_mapping: [dependency_name, outcome, retry_attempt] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: feature-metrics-alerting-contract — "resilience4j.circuitbreaker.state" - name: resilience4j.circuitbreaker.state type: gauge unit: total tags: - name: name cardinality_limit: 50 - name: state cardinality_limit: 6 allowed_values: [CLOSED, OPEN, HALF_OPEN, DISABLED, FORCED_OPEN, METRICS_ONLY] percentiles: null histogram_buckets: null alert_severity_thresholds: p1: "필수 의존 대상의 state == OPEN이 2m 동안" p2: "선택 의존 대상의 state == OPEN이 5m 동안" owner_branch: feature-outbound-http-client-baseline log_field_mapping: [dependency_name] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: feature-metrics-alerting-contract — "resilience4j.circuitbreaker.calls{outcome}" - name: resilience4j.circuitbreaker.calls type: timer unit: seconds tags: - name: name cardinality_limit: 50 - name: outcome cardinality_limit: 5 allowed_values: [SUCCESS, FAILURE, CIRCUIT_OPEN, TIMEOUT, REJECTED] percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: p2: "CIRCUIT_OPEN 비율 > 1%가 10m 동안" owner_branch: feature-outbound-http-client-baseline log_field_mapping: [dependency_name, outcome, duration_ms] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # === DB connection pool === # source: feature-persistence-failure-baseline — Hikari Alert Threshold # "pool wait p99 > 100ms 5분 지속 → P2 / pool exhaustion (active = max) > 1분 → P1" # source: feature-metrics-alerting-contract — "hikaricp.connections.acquire{outcome='timeout'} p99 > 100ms" - name: hikaricp.connections.acquire type: timer unit: seconds tags: - name: pool cardinality_limit: 5 - name: outcome cardinality_limit: 3 allowed_values: [SUCCESS, TIMEOUT, FAILURE] percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: p1: "pool 고갈(active == max)이 1m 동안" p2: "acquire p99 > 100ms가 5m 동안" owner_branch: feature-persistence-failure-baseline log_field_mapping: [pool, outcome] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: feature-persistence-failure-baseline — In scope "Hikari metric 노출 기준" + Hikari Alert Threshold - name: hikaricp.connections.usage type: timer unit: seconds tags: - name: pool cardinality_limit: 5 percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: p2: "usage p99가 10m 넘게 높음" owner_branch: feature-persistence-failure-baseline log_field_mapping: [pool] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: feature-persistence-failure-baseline — In scope "Hikari metric 노출 기준" - name: hikaricp.connections.active type: gauge unit: total tags: - name: pool cardinality_limit: 5 percentiles: null histogram_buckets: null alert_severity_thresholds: p1: "active == max가 1m 동안" owner_branch: feature-persistence-failure-baseline log_field_mapping: [pool] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: feature-metrics-alerting-contract — Histogram Buckets/Percentile "DB query: same" - name: db.query.duration type: timer unit: seconds tags: - name: operation cardinality_limit: 20 allowed_values: [select, insert, update, delete, batch, ddl, other] - name: outcome cardinality_limit: 3 allowed_values: [SUCCESS, FAILURE, TIMEOUT] percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: p2: "p99 > 1s가 10m 동안" owner_branch: feature-metrics-alerting-contract log_field_mapping: [operation, outcome, duration_ms] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # === 백그라운드 작업 / 비동기 executor === # source: feature-background-job-async-contract — Decisionized Work Items "saturation policy" # "AbortPolicy default (core=10, max=50, queue=200)" - name: executor.saturation type: gauge unit: total tags: - name: executor_name cardinality_limit: 10 percentiles: null histogram_buckets: null alert_severity_thresholds: p2: "queue 크기 > 용량의 80%가 5m 동안" p1: "거절 비율 > 0이 1m 동안" owner_branch: feature-background-job-async-contract log_field_mapping: [executor_name] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: feature-background-job-async-contract — Decisionized Work Items "saturation | bounded executor + rejection log" - name: executor.rejected.total type: counter unit: total tags: - name: executor_name cardinality_limit: 10 - name: policy cardinality_limit: 3 allowed_values: [AbortPolicy, CallerRunsPolicy, DiscardPolicy] percentiles: null histogram_buckets: null alert_severity_thresholds: p1: "rejection_count > 0이 1m 동안" owner_branch: feature-background-job-async-contract log_field_mapping: [executor_name, policy] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: feature-background-job-async-contract — Decisionized Work Items "retry/DLQ | exp backoff jitter, max 3, DLQ exhausted" - name: job.retry.total type: counter unit: total tags: - name: job_name cardinality_limit: 50 - name: outcome cardinality_limit: 4 allowed_values: [SUCCESS, RETRY, EXHAUSTED, DLQ] percentiles: null histogram_buckets: null alert_severity_thresholds: p2: "EXHAUSTED 비율 > 1%가 10m 동안" owner_branch: feature-background-job-async-contract log_field_mapping: [job_name, outcome, retry_attempt] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: feature-background-job-async-contract — "DLQ after exhausted attempts" - name: job.dlq.total type: counter unit: total tags: - name: job_name cardinality_limit: 50 percentiles: null histogram_buckets: null alert_severity_thresholds: p1: "DLQ 비율 > 0이 5m 동안 계속" owner_branch: feature-background-job-async-contract log_field_mapping: [job_name] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # === Distributed lock === # source: feature-distributed-lock-contract D7 — "metric lock.acquisition (tag: outcome = # acquired/timeout/error) — 신규 제안" / D5 — try-lock + 유한 waitTime + lease(TTL). 분산 # 상호배제(distributedLockProvider) 획득 시도 결과를 센다. key 는 tag 로 넣지 않는다 # (무한 cardinality — 위 전역 금지 규칙). timeout outcome 은 LOCK_ACQUISITION_TIMEOUT 발생과 1:1. - name: lock.acquisition type: counter unit: total tags: - name: outcome cardinality_limit: 3 allowed_values: [acquired, timeout, error] percentiles: null histogram_buckets: null alert_severity_thresholds: p2: "timeout 비율 > 5%가 10m 동안" owner_branch: feature-distributed-lock-contract log_field_mapping: [outcome] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: feature-distributed-lock-contract §Edge / D5 (SI-LOCK-C5) — "lease 만료 후 unlock → # ConcurrentModificationException — 삼킴 금지, 로그+metric 후 정상 흐름 복귀". lease가 이미 만료된 뒤의 # 해제를 센다(보유자가 close()를 부르기 전에 다른 인스턴스가 JdbcLock 행을 회수함). 0이 아닌 비율이 # 이어지면 lease TTL이 실제 임계 구역 시간보다 짧다는 뜻이다 — APP/lease TTL을 늘리거나 보호하는 일을 # 줄인다. 획득 결과가 아니라서 lock.acquisition과 다른 counter다. - name: lock.lease.expired type: counter unit: total tags: [] percentiles: null histogram_buckets: null alert_severity_thresholds: p2: "lease-expired 비율 > 0이 10m 동안 계속" owner_branch: feature-distributed-lock-contract log_field_mapping: [] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # === Outbox 발행기 === # source: feature-domain-event-outbox-contract — Outbox Defaults # "DB outbox table with eventId, aggregateId, eventType, payload, occurredAt, status, attemptCount, nextAttemptAt" - name: outbox.publisher.published.total type: counter unit: total tags: - name: event_type cardinality_limit: 50 - name: outcome cardinality_limit: 5 # 행 상태가 아니라 relay 한 바퀴의 결과(OutboxRelayResult.Outcome)다. IN_FLIGHT는 상태라 세지 않는다. # STALE: relay의 claim을 결과를 쓰기 전에 다른 쪽이 넘겨받았다(V17 lease fence). RELEASED: 멈추는 relay가 # 쓰지 않은 claim을 돌려줬다. allowed_values: [PUBLISHED, FAILED, DEAD, STALE, RELEASED] percentiles: null histogram_buckets: null alert_severity_thresholds: p2: "FAILED 비율 > 1%가 10m 동안, 또는 STALE > 0이 10m 동안(in-flight timeout이 relay 정지보다 짧다)" owner_branch: feature-domain-event-outbox-contract log_field_mapping: [event_type, outcome, event_id] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: feature-domain-event-outbox-contract — 행 상태 enum PENDING/IN_FLIGHT/PUBLISHED/FAILED/DEAD - name: outbox.publisher.lag type: gauge unit: seconds tags: - name: event_type cardinality_limit: 50 percentiles: null histogram_buckets: null alert_severity_thresholds: p2: "lag > 60s가 10m 동안" p1: "lag > 300s가 5m 동안" owner_branch: feature-domain-event-outbox-contract log_field_mapping: [event_type] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: feature-domain-event-outbox-contract — row status enum + Outbox Defaults attemptCount # PARKED: 끝없이 재시도되던 행을 운영자가 붙잡아 둠 (re-review 2026-11-03 RR-05-03). - name: outbox.pending.size type: gauge unit: total tags: - name: status cardinality_limit: 6 allowed_values: [PENDING, IN_FLIGHT, PUBLISHED, FAILED, DEAD, PARKED] percentiles: null histogram_buckets: null # DEAD > 0: claim은 내주지 않을 행을 relay 결과 없이 DEAD로 옮기므로 # outbox.publisher.published.total{outcome=DEAD}가 그것을 놓친다 (re-review round 2, RR-02-12). alert_severity_thresholds: p1: "DEAD > 0 (runbook://outbox/dead-letter)" p2: "PENDING 크기가 10m 동안 늘어남" owner_branch: feature-domain-event-outbox-contract log_field_mapping: [status] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: re-review 2026-11-03 RR-05-03 — 지금의 거절과 답이 없는 발행은 끝없이 재시도된다. 이 둘은 # 10번 이상 미뤄진 FAILED 행을 세고(OutboxMetrics LONG_RETRY_DEFERRED_CLAIMS, publish-failed runbook §4.1 # 조회), 그중 가장 오래된 것의 나이를 잰다. - name: outbox.retry.long.size type: gauge unit: total tags: [] percentiles: null histogram_buckets: null alert_severity_thresholds: p2: "> 0이 10m 동안 (runbook://outbox/publish-failed §4.1)" owner_branch: feature-domain-event-outbox-contract log_field_mapping: [] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - name: outbox.retry.long.age type: gauge unit: seconds tags: [] percentiles: null histogram_buckets: null alert_severity_thresholds: p2: "> 3600 (runbook://outbox/publish-failed §4.1)" owner_branch: feature-domain-event-outbox-contract log_field_mapping: [] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # === 캐시 === # source: feature-cache-consistency-contract — Decisionized Work Items "cache pattern | cache-aside default" - name: cache.gets.total type: counter unit: total tags: - name: cache_name cardinality_limit: 50 - name: result cardinality_limit: 3 allowed_values: [hit, miss, error] percentiles: null histogram_buckets: null alert_severity_thresholds: p3: "hit_ratio < 기준선의 0.5배가 1h 동안" owner_branch: feature-cache-consistency-contract log_field_mapping: [cache_name, result] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: feature-cache-consistency-contract — "invalidation = after-commit only", "invalidation 실패가 조용히 무시되면 실패" - name: cache.invalidations.total type: counter unit: total tags: - name: cache_name cardinality_limit: 50 - name: outcome cardinality_limit: 3 allowed_values: [SUCCESS, FAILURE, SKIPPED] percentiles: null histogram_buckets: null alert_severity_thresholds: p2: "FAILURE 비율 > 0이 5m 동안" owner_branch: feature-cache-consistency-contract log_field_mapping: [cache_name, outcome] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: redis-production-capability — 크기가 정해진 캐시 전용 L1 (선택) - name: cache.local.requests.total type: counter unit: total tags: - name: cache_name cardinality_limit: 50 - name: result cardinality_limit: 4 allowed_values: [hit, miss, error, bypass] percentiles: null histogram_buckets: null alert_severity_thresholds: p3: "bypass 또는 error 비율이 기준선보다 높은 상태가 15m 동안" owner_branch: redis-production-capability log_field_mapping: [cache_name, result] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: redis-production-capability — 로컬 stale 나이 상한 - name: cache.local.entry.age.seconds type: timer unit: seconds tags: - name: cache_name cardinality_limit: 50 percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: p3: "p99가 설정한 로컬 TTL에 가까운 상태가 30m 동안" owner_branch: redis-production-capability log_field_mapping: [cache_name] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: redis-production-capability — 크기가 정해진 무효화와 세대 대조(reconciliation) - name: cache.local.maintenance.total type: counter unit: total tags: - name: cache_name cardinality_limit: 50 - name: event cardinality_limit: 14 allowed_values: - evict_cardinality - evict_weight - evict_ttl - evict_invalidation - flush_invalidation - reconcile_generation_changed - reconcile_unchanged - reconcile_error - subscriber_disconnected - subscriber_overflow - subscriber_malformed - subscriber_publish_success - subscriber_publish_error - other percentiles: null histogram_buckets: null alert_severity_thresholds: p2: "reconcile_error, subscriber_overflow, 또는 끊김이 5m 동안 계속" owner_branch: redis-production-capability log_field_mapping: [cache_name, event] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # === Redis 연결 lane === # source: review 2026-11-03 RR-04-02 — 캐시의 조건부 쓰기는 자기 lane(CACHE_SCRIPT)을 받았다. 캐시 채우기가 # idempotency·rate limiting·lease의 SCRIPT lane 연결을 가져가지 못하게 하려는 것이다. 이 meter들이 lane마다 # 그것이 지켜지는지 보여 준다. redis-runtime RedisLaneMetrics가 RedisRuntimeOwner가 pool로 가진 모든 lane에 # 대해, context에 MeterRegistry가 있을 때만 낸다. 모든 counter 계열은 기동 때 0으로 등록한다. - name: redis.lane.acquire.wait.seconds type: timer unit: seconds tags: - name: lane # lane 이름: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, # TRANSACTION, ADMIN (redis-sdk), 그리고 서비스가 RedisLaneContribution으로 조립한 lane. cardinality_limit: 12 - name: outcome cardinality_limit: 2 allowed_values: [admitted, refused] # RedisLaneMetrics가 등록하는 모양: percentile histogram(publishPercentileHistogram, 예상 범위 # 1ms..10s)이고, client 쪽 percentile과 SLO 경계는 없다. 아래 p99는 bucket 위의 histogram_quantile이다 # (re-review 2026-11-04 RR-03-17). percentiles: null histogram_buckets: percentile_histogram alert_severity_thresholds: p2: "SCRIPT admitted p99 > 100ms가 10m 동안(정확성 lane이 줄을 서고 있다)" p3: "CACHE_SCRIPT admitted p99 > 100ms가 30m 동안" owner_branch: redis-production-capability log_field_mapping: [lane, outcome] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - name: redis.lane.acquire.refused.total type: counter unit: total tags: - name: lane # lane 이름: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, # TRANSACTION, ADMIN (redis-sdk), 그리고 서비스가 RedisLaneContribution으로 조립한 lane. cardinality_limit: 12 - name: reason cardinality_limit: 4 allowed_values: [saturated, closing, interrupted, connect_failed] percentiles: null histogram_buckets: null alert_severity_thresholds: p1: "정확성 role을 고른 상태에서 SCRIPT 또는 REGULAR의 saturated나 connect_failed가 0보다 큰 상태가 2m 동안" p2: "CACHE_SCRIPT saturated가 기준선보다 높은 상태가 10m 동안" owner_branch: redis-production-capability log_field_mapping: [lane, reason] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - name: redis.lane.connections.opened.total type: counter unit: total tags: - name: lane # lane 이름: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, # TRANSACTION, ADMIN (redis-sdk), 그리고 서비스가 RedisLaneContribution으로 조립한 lane. cardinality_limit: 12 percentiles: null histogram_buckets: null alert_severity_thresholds: p3: "warm-up 뒤 opened 비율이 기준선보다 높은 상태가 15m 동안(느린 Redis에 다시 연결하며 흔들림)" owner_branch: redis-production-capability log_field_mapping: [lane] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - name: redis.lane.connections.discarded.total type: counter unit: total tags: - name: lane # lane 이름: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, # TRANSACTION, ADMIN (redis-sdk), 그리고 서비스가 RedisLaneContribution으로 조립한 lane. cardinality_limit: 12 - name: reason cardinality_limit: 2 allowed_values: [invalidated, broken] percentiles: null histogram_buckets: null alert_severity_thresholds: p3: "invalidated 비율이 기준선보다 높은 상태가 15m 동안(timeout·실패한 호출이 연결을 버림)" owner_branch: redis-production-capability log_field_mapping: [lane, reason] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - name: redis.lane.connections.active type: gauge unit: total tags: - name: lane # lane 이름: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, # TRANSACTION, ADMIN (redis-sdk), 그리고 서비스가 RedisLaneContribution으로 조립한 lane. cardinality_limit: 12 percentiles: null histogram_buckets: null alert_severity_thresholds: p2: "SCRIPT active == 설정한 maximum-script-connections가 5m 동안" owner_branch: redis-production-capability log_field_mapping: [lane] compatibility_impact: additive required_test: contract-verification:metrics-cardinality - name: redis.lane.connections.pending type: gauge unit: total tags: - name: lane # lane 이름: REGULAR, SCRIPT (redis-runtime), CACHE_SCRIPT (cache-redis), BLOCKING, # TRANSACTION, ADMIN (redis-sdk), 그리고 서비스가 RedisLaneContribution으로 조립한 lane. cardinality_limit: 12 percentiles: null histogram_buckets: null alert_severity_thresholds: p2: "SCRIPT pending > 0이 5m 동안" owner_branch: redis-production-capability log_field_mapping: [lane] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # === 로그 appender === # source: feature-log-management-contract — Sampling Policy (final) # "async appender overflow default: drop oldest INFO/DEBUG with counter metric (log.appender.dropped.total)" - name: log.appender.dropped.total type: counter unit: total tags: - name: appender cardinality_limit: 5 - name: level cardinality_limit: 2 allowed_values: [INFO, DEBUG] percentiles: null histogram_buckets: null alert_severity_thresholds: p2: "dropped > 0이 10m 동안 계속" owner_branch: feature-log-management-contract log_field_mapping: [appender, level] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # === 분산 추적 === # source: feature-distributed-tracing-contract — decisions # "trace sampling rate default = prod 1%, dev/local 100%; shipped runtime profiles are local|dev|prod" - name: tracing.sampling.rate type: gauge unit: total tags: - name: profile cardinality_limit: 3 allowed_values: [prod, dev, local] percentiles: null histogram_buckets: null alert_severity_thresholds: p3: "실제 비율이 설정값과 1h 동안 어긋남" owner_branch: feature-distributed-tracing-contract log_field_mapping: [profile] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # === JVM 기본 === # source: feature-metrics-alerting-contract — In scope "JVM/process metric" - name: jvm.memory.used type: gauge unit: bytes tags: - name: area cardinality_limit: 2 allowed_values: [heap, nonheap] - name: id cardinality_limit: 10 percentiles: null histogram_buckets: null alert_severity_thresholds: p2: "heap used / max > 0.85가 10m 동안" owner_branch: feature-metrics-alerting-contract log_field_mapping: [area, id] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: feature-metrics-alerting-contract — In scope "JVM/process metric" - name: jvm.gc.pause type: timer unit: seconds tags: - name: action cardinality_limit: 10 - name: cause cardinality_limit: 10 percentiles: [0.5, 0.9, 0.95, 0.99] histogram_buckets: slo_driven alert_severity_thresholds: p2: "p99 pause > 500ms가 10m 동안" owner_branch: feature-metrics-alerting-contract log_field_mapping: [action, cause] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: feature-metrics-alerting-contract — In scope "JVM/process metric" - name: jvm.threads.live type: gauge unit: total tags: [] percentiles: null histogram_buckets: null alert_severity_thresholds: p3: "thread 수 > 기준선의 2배가 30m 동안" owner_branch: feature-metrics-alerting-contract log_field_mapping: [] compatibility_impact: additive required_test: contract-verification:metrics-cardinality # source: feature-metrics-alerting-contract — In scope "JVM/process metric" (process uptime) - name: process.uptime type: gauge unit: seconds tags: [] percentiles: null histogram_buckets: null alert_severity_thresholds: p1: "uptime이 예상 밖으로 < 60s로 초기화됨(crash loop 신호)" owner_branch: feature-metrics-alerting-contract log_field_mapping: [] compatibility_impact: additive required_test: contract-verification:metrics-cardinality