ES /docs

Api::V1::TrashesController#index (avg 2323ms, max 2789ms)

Service
cupixworks-api
Occurrences
10
Status
Reported
Confidence
85%
Actionability
36%
Cluster ID
b6e11297-e848-4929-b3c6-2f557ed31fd8
First Seen
2026-05-26 04:34 UTC
Last Seen
2026-05-28 05:58 UTC
Actions

Api::V1::TrashesController#index (avg 2323ms, max 2789ms)

What Happened#

2026-05-26 04:34~04:50 UTC 사이에 cupixworks-api의 TrashesController#index 엔드포인트가 평균 2323ms, 최대 2789ms의 응답 시간을 기록했다. 총 5건의 요청이 모두 HTTP 200을 반환했지만, 정상 응답 시간(~900ms)의 2.5배를 초과했다. 영향을 받은 사용자는 단일 팀(hec-test-dangjin)의 peter.nam@cupix.com 계정이다.

Quick Facts#

Field Value
resource_name Api::V1::TrashesController#index
top_frame app/repositories/trash_repository.rb:195
env production, us-west-2
avg_duration 2323ms
max_duration 2789ms

Timeline#

  1. 2026-05-26T04:34:35Z — 최초 지연 요청 발생 (2787ms, host: ip-10-1-80-134)
  2. 2026-05-26T04:34:46Z — 두 번째 요청 (2294ms, host: ip-10-1-144-228)
  3. 2026-05-26T04:46:46Z — 세 번째 요청 (2154ms, host: ip-10-1-80-134)
  4. 2026-05-26T04:50:34Z — 마지막 지연 요청 (1916ms, host: ip-10-1-144-228)
  5. 2026-05-26T13:25:00Z — 동일 엔드포인트 응답 시간 900ms로 정상화 확인

Scoring#

Confidence 85% · Actionability 36%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 11 code refs, 2 log queries
Code path explicitness 3/3 11 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 19 file(s)
Single repo 1/3 3 service(s)
Immediate actions 0/3 absent
Testability 2/3 test mentioned
External dependency 1/3 external deps found
Data migration 3/3 no migration