ES /docs

Cupix::StorageService missing S3 timeout config — AWS SDK default retry hang

Service
cupixworks-api
Occurrences
22
Status
Dismissed
Confidence
85%
Actionability
28%
Cluster ID
6c99a04e-ad8b-410f-b25f-3bade7a7068d
First Seen
2026-05-30 13:41 UTC
Last Seen
2026-08-04 19:49 UTC
Datadog↗ Slack↗
Actions
현재 상태 dismissed 에서는 실행할 액션이 없습니다.

Cupix::StorageService missing S3 timeout config — AWS SDK default retry hang

What Happened#

2026-05-30 22:41 KST, eu-central-1 리전의 cupixworks-api에서 check_cover_uploading 엔드포인트가 15,928ms 응답 시간을 기록했다. 동일 시간대 다른 요청은 모두 470-490ms 내에 처리되었으며, DB 시간은 정상(22ms)이었으므로 S3 HEAD 요청의 지연이 원인으로 확인되었다.

Quick Facts#

Field Value
resource_name Api::V1::AssetsController#check_cover_uploading
top_frame app/models/concerns/coverable.rb:37
env production, eu-central-1
duration 15,928ms (avg 470ms for same action)
asset_key nhwhefcxcg3w

Timeline#

  1. 2026-05-30 22:41:14 KST — cover_upload_url 호출 완료 (58ms), 클라이언트에 presigned S3 URL 발급
  2. 2026-05-30 22:41:15 KST — check_cover_uploading 요청 시작 (asset nhwhefcxcg3w)
  3. 2026-05-30 22:41:31 KST — check_cover_uploading 응답 완료 (15,928ms, HTTP 200)
  4. 2026-05-30 22:50:13 KST — Error Sweeper가 latency 클러스터로 감지

Scoring#

Confidence 85% · Actionability 28%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 8 code refs, 2 log queries
Code path explicitness 3/3 8 file:line refs
Log evidence 3/3 section, query, pattern
RCA structure 3/3 3/3 sections
Revision history 0/3 0 revision(s)
Agent execution 3/3 success

Actionability#

Dimension Score Detail
Fix complexity 1/5 critical
Affected files 1/5 14 file(s)
Single repo 1/3 3 service(s)
Immediate actions 0/3 absent
Testability 0/3 no test info
External dependency 1/3 external deps found
Data migration 3/3 no migration