ES /docs

Api::V1::Admin::TeamsController#update (avg 3632ms, max 4612ms)

Service
cupixworks-api
Occurrences
3
Status
Reported
Confidence
85%
Actionability
28%
Cluster ID
81db1612-e324-433b-a3cd-70a73f1f9a28
First Seen
2026-05-27 02:47 UTC
Last Seen
2026-05-27 17:20 UTC
Actions

Api::V1::Admin::TeamsController#update (avg 3632ms, max 4612ms)

What Happened#

2026-05-27 02:47 UTC, cupixworks-api 서비스의 Api::V1::Admin::TeamsController#update 엔드포인트에서 평균 3632ms, 최대 4612ms의 응답 지연이 발생했다. ap-southeast-2 리전의 team ID 157에 대해 Prism/CS 1.1.6 클라이언트가 연속 3회 PATCH 요청을 보냈으며, 그 중 2건이 latency 임계값(500ms)을 초과했다.

Quick Facts#

Field Value
resource_name Api::V1::Admin::TeamsController#update
top_frame app/models/concerns/eventable/team.rb:12
env production, ap-southeast-2
deploy production-ap-southeast-2-20260526t0527z0-dd7bd097-cupixworks

Timeline#

  1. 02:47:42Z — Prism/CS가 team 157에 대한 show 요청 수행 (18ms, 정상)
  2. 02:47:54Z — 첫 번째 PATCH 요청 (97ms, 정상 — Segment 이벤트 미발생)
  3. 02:47:55Z — 두 번째 PATCH 요청 (4610ms, Segment 이벤트 발생 확인)
  4. 02:47:57Z — 세 번째 PATCH 요청 (2651ms, Segment 이벤트 발생 확인)

Scoring#

Confidence 85% · Actionability 28%

Confidence#

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