ES /docs

Api::V1::Admin::EditingsController#update (avg 1373ms, max 1651ms)

Service
cupixworks-api
Occurrences
219
Status
Reported
Confidence
85%
Actionability
28%
Cluster ID
4d6f8b93-3e5b-493f-8654-5d2bae2a67be
First Seen
2026-05-26 03:43 UTC
Last Seen
2026-06-19 20:13 UTC
Actions

Api::V1::Admin::EditingsController#update (avg 1373ms, max 1651ms)

What Happened#

2026-05-26 03:43~05:43 UTC 동안 ap-southeast-2 리전의 cupixworks-api 서비스에서 Api::V1::Admin::EditingsController#update 엔드포인트가 평균 1373ms, 최대 1651ms의 응답 지연을 보였다. Retool 자동화가 Editing 레코드의 state를 "done"으로 전환하는 과정에서 동기적 Elasticsearch 인덱싱과 cascading 콜백이 요청 시간의 70-90%를 소비한 것이 원인이다.

Quick Facts#

Field Value
resource_name Api::V1::Admin::EditingsController#update
top_frame app/models/editing.rb:43 (set_assigned_at)
env production, ap-southeast-2
avg_duration 1373ms
max_duration 1651ms (cluster), 5968ms (broader window)

Timeline#

  1. 2026-05-26 03:43:21Z — 최초 latency spike 감지 (ap-southeast-2)
  2. 2026-05-26 05:43:23Z — 마지막 slow request 기록
  3. 2026-05-26T06:00Z — error-sweeper가 latency 클러스터 생성

Scoring#

Confidence 85% · Actionability 28%

Confidence#

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