ES /docs

Api::V1::SitetracksController#captures (avg 13190ms, max 13190ms)

Service
cupixworks-api
Occurrences
1
Status
Reported
Confidence
85%
Actionability
44%
Cluster ID
e49dced0-5cfe-4d49-a823-9abb88cbcd67
First Seen
2026-07-08 16:39 UTC
Last Seen
2026-07-08 16:39 UTC
Actions

Api::V1::SitetracksController#captures (avg 13190ms, max 13190ms)

What Happened#

2026-07-09 01:39 KST 에 cupixworks-apiGET /api/v1/sitetracks/:id/captures 요청 한 건이 13.07초 걸려 latency threshold 를 넘겼다. Sitetrack 20896 에 대한 요청이었고 응답은 HTTP 200 이었지만, DB 5.78s + serialization 4.29s 로 대부분의 시간을 소비했다. 반환된 capture 는 total_entries: 1 로 단 1건이었다.

Quick Facts#

Field Value
resource_name Api::V1::SitetracksController#captures
top_frame app/repositories/sitetrack_repository.rb:33-47
serializer CaptureSerializer (~45 attributes, ~30 concern mixins)
duration 13072.19 ms (db 5782.8 ms, serialization 4287 ms)
params per_page=100, page=1, id=20896, fields=[45개]
result total_entries: 1 (1 capture 반환)
user team gilbaneco (id 780), user id 49405
user_agent cupix-agent
host ip-10-1-80-134.us-west-2.compute.internal
env production, us-west-2
deploy production-us-west-2-20260708t0836z0-5c918141-cupixworks

Affected Teams#

Team / Domain Error Count Impact
gilbaneco (team 780) 1 cupix-agent 클라이언트에서 sitetrack captures 응답 13초 지연

과거 14일 창에서 같은 endpoint 가 5초 이상 걸린 요청은 27건 관측됐다 (아래 Log Evidence 참고). 다수의 tenant/team 에 걸쳐 나타난다.

Timeline#

  1. 2026-07-08 17:36 KST — 배포 production-us-west-2-20260708t0836z0-5c918141-cupixworks 롤아웃 (참고용, 이 요청 이전).
  2. 2026-07-09 01:39:16 KST — 요청 수신, sitetrack 20896 의 captures 조회 시작.
  3. 2026-07-09 01:39:29 KST — 13.07s 후 [200] 응답 완료. error-sweeper 가 latency cluster 로 캡처.

Scoring#

Confidence 85% · Actionability 44%

Confidence#

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