ES /docs

Api::V1::CapturesController#invoke (avg 1106ms, max 1106ms)

Service
cupixworks-api
Occurrences
1
Status
Reported
Confidence
85%
Actionability
28%
Cluster ID
be6fdf81-3973-446a-ae15-fd8bbb1846e1
First Seen
2026-05-27 05:23 UTC
Last Seen
2026-05-27 05:23 UTC
Actions

Api::V1::CapturesController#invoke (avg 1106ms, max 1106ms)

What Happened#

2026-05-27 05:23:58 UTC에 cupixworks-api 서비스의 Api::V1::CapturesController#invoke 엔드포인트에서 1106ms의 응답 시간이 관측되었다. 요청은 정상적으로 HTTP 200으로 완료되었으나, 500ms 임계값을 초과하는 latency로 클러스터가 생성되었다. Retool을 통한 배치 호출(동일 사용자가 42초 내 4건 호출) 중 발생하였다.

Quick Facts#

Field Value
resource_name Api::V1::CapturesController#invoke
command create_3d_reconstruction
top_frame app/invokers/capture_invoker.rb:48
duration 1106ms (DB: 216ms)
env production, us-west-2
user chan.lee@cupix.com (Retool/2.0)

Timeline#

  1. 05:23:40Z — 첫 번째 invoke 요청 (capture 702937, 674ms)
  2. 05:23:58Z — 클러스터 대상 invoke 요청 (capture 702874, 1106ms)
  3. 05:24:12Z — 세 번째 invoke 요청 (capture 702936, 1324ms)
  4. 05:24:22Z — 네 번째 invoke 요청 (capture 702528, 925ms)

Scoring#

Confidence 85% · Actionability 28%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 12 code refs, 3 log queries
Code path explicitness 3/3 12 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 21 file(s)
Single repo 1/3 2 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