ES /docs

Api::V1::ReviewsController#load (avg 10529ms, max 10529ms)

Service
cupixworks-api
Occurrences
1
Status
Reported
Confidence
85%
Actionability
28%
Cluster ID
41303473-aec5-46f4-9214-6902a7d0e91f
First Seen
2026-07-10 13:47 UTC
Last Seen
2026-07-10 13:47 UTC
Datadog↗ Slack↗
Actions

Api::V1::ReviewsController#load (avg 10529ms, max 10529ms)

What Happened#

2026-07-10 22:47 KST 경, cupixworks-api production 환경 (us-west-2) 에서 GET /api/v1/reviews/goj0cu/load 요청이 10529ms 걸린 뒤 500 으로 종료됐다. 근본 원인은 ReviewRepository#records 가 호출한 Elasticsearch (::Record.search) 쿼리가 Faraday HTTP client 의 10 초 request timeout (Faraday::TimeoutError) 에 걸린 것이며, 해당 예외는 fallback 대상이 아니라 그대로 상위로 재-raise 되어 500 이 반환됐다.

Quick Facts#

Field Value
exception.class Faraday::TimeoutError
exception.message Operation timed out after 10002 milliseconds with 0 bytes received
top_frame app/repositories/concerns/accessible_entities_repository/review.rb:15-17
runtime Ruby on Rails (cupixworks-api), Elasticsearch client via Faraday/Patron
env production, us-west-2
tenant cupix

Affected Teams#

Team / Domain Error Count Impact
cupixworks-api / Review (facility=21093, review=goj0cu) 1 Review 상세 화면 최초 진입 시 10초 지연 후 500 실패
파생 영향 (Operation timed out 로그 기준 7일 창) 30+ 동일 ES timeout 이 PanoRepository, CaptureRepository, WorkareaRepository, RecordRepository, AssetRepository, ClusterRepository, VideoRepository, EditingEntityRepository, Pano._update_document 등에서도 발생. Review 만의 문제가 아니라 ES 응답성 저하가 광범위하게 영향 중

Timeline#

  1. 2026-07-10 22:47:28 KST — 이전 동일 controller 요청 (k2dfc9/load) 은 200 정상 응답
  2. 2026-07-10 22:47:33 KST (±) — goj0cu/load 진입, ReviewRepository#load 가 compute_load_info 경로로 들어가 _record_ids 를 호출 → records → ::Record.search 로 ES 요청 전송 (trace first_seen)
  3. 2026-07-10 22:47:45 KST — Failed to get records - Operation timed out after 10002 milliseconds with 0 bytes received (status:error, class:ReviewRepository, function:records) 로그 기록
  4. 2026-07-10 22:47:45 KST — 동일 시점에 [500] GET /api/v1/reviews/goj0cu/load 로그, error 배열 ["Faraday::TimeoutError", "Operation timed out after 10002 milliseconds with 0 bytes received"]
  5. 2026-07-10 22:47:51 KST — 이후 동일 controller 의 다른 review (73538) 는 501.85ms 로 정상 처리 재개

Scoring#

Confidence 85% · Actionability 28%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 15 code refs, 7 log queries
Code path explicitness 3/3 15 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