ES /docs

Api::V1::FacilitiesController#index (avg 1118ms, max 1183ms)

Service
cupixworks-api
Occurrences
115
Status
Reported
Confidence
85%
Actionability
28%
Cluster ID
ec7fa6da-6cf9-4543-be92-8b4390b8e0ba
First Seen
2026-05-26 03:44 UTC
Last Seen
2026-06-19 20:12 UTC
Datadog↗ Slack↗
Actions

Api::V1::FacilitiesController#index (avg 1118ms, max 1183ms)

What Happened#

2026-05-26 03:44~12:44 UTC 사이에 cupixworks-api 서비스의 FacilitiesController#index 엔드포인트에서 평균 1158ms, 최대 4125ms의 응답 지연이 3개 리전(ap-southeast-2, us-west-2, eu-central-1)에서 26건 발생했다. 모든 요청은 HTTP 200으로 성공하였으나, 500ms SLA를 초과하는 latency가 지속적으로 관측되었다.

Quick Facts#

Field Value
resource_name Api::V1::FacilitiesController#index
top_frame app/repositories/base_repository.rb:70
env production (ap-southeast-2, us-west-2, eu-central-1)

Affected Teams#

Team / Domain Error Count Impact
erwalls (us-west-2) 3 445개 facility 조회 시 최대 4.1초 지연, UX 저하
sinsw (ap-southeast-2) 2 289개 facility 조회 시 2.1~2.3초 지연
built (ap-southeast-2) 5 112개 facility 조회 시 0.8~1.1초 지연
기타 다수 16 소규모 팀에서도 0.5~1초 지연 발생

Timeline#

  1. 2026-05-26T03:44:52Z — 최초 latency 감지 (ap-southeast-2)
  2. 2026-05-26T05:15:45Z — sinsw 팀 2.1초 지연 발생 (289 facilities, per_page:300)
  3. 2026-05-26T11:50:40Z — erwalls 팀 3.4초 지연 발생 (444 facilities, per_page:300)
  4. 2026-05-26T11:53:17Z — 최대 지연 4.1초 기록 (erwalls, serialization: 3409ms)
  5. 2026-05-26T12:44:41Z — 마지막 감지

Scoring#

Confidence 85% · Actionability 28%

Confidence#

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