ES /docs

Api::V1::IssuesController#create (avg 2481ms, max 2615ms)

Service
cupixworks-api
Occurrences
3
Status
Pr_created
Confidence
95%
Actionability
44%
Cluster ID
a3694e54-bc29-4e54-9756-5160d5a272ad
First Seen
2026-05-28 03:58 UTC
Last Seen
2026-05-28 06:13 UTC
Actions
현재 상태 pr_created 에서는 실행할 액션이 없습니다.

Api::V1::IssuesController#create (avg 2481ms, max 2615ms)

What Happened#

2026-05-28 03:5804:22 UTC 사이 cupixworks-api의 Api::V1::IssuesController#create 엔드포인트에서 평균 2481ms, 최대 2615ms의 응답 지연이 ap-southeast-1과 ap-southeast-2 리전에서 2건 발생했다. DB 시간은 1447ms로 정상이며, 외부 Issue Service(AWS Lambda + API Gateway)에 대한 동기 HTTP POST 호출이 전체 응답 시간의 80% 이상을 차지했다.

Quick Facts#

Field Value
resource_name Api::V1::IssuesController#create
top_frame app/services/cupix/issue_service.rb:117
env production, ap-southeast-1 / ap-southeast-2
avg_duration 2481ms
max_duration 2615ms
issue-service infra AWS Lambda (arm64, Node.js) + API Gateway + DynamoDB

Timeline#

  1. 2026-05-28T03:58:31Z — 첫 번째 slow request 발생 (ap-southeast-2, 2344ms)
  2. 2026-05-28T04:09:16Z — 두 번째 slow request 발생 (ap-southeast-2, 2558ms)
  3. 2026-05-28T04:22:43Z — 세 번째 slow request 발생 (ap-southeast-1, 2612ms)
  4. 2026-05-28T04:22:36Z — error-sweeper가 latency cluster로 감지

Scoring#

Confidence 95% · Actionability 44%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 25 code refs, 2 log queries
Code path explicitness 3/3 25 file:line refs
Log evidence 3/3 section, query, pattern
RCA structure 3/3 3/3 sections
Revision history 2/3 2 revision(s)
Agent execution 3/3 success

Actionability#

Dimension Score Detail
Fix complexity 5/5 trivial
Affected files 1/5 28 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