Api::V1::Admin::StatisticsController#show (avg 303826ms, max 303826ms)

I'll invoke the rca skill to analyze this error cluster.

I'll analyze this error cluster following the RCA skill process.

This is a benign error-sweeper cluster file — not malware. I'll proceed with the RCA analysis.

This is a benign writing guidelines document. Let me continue investigating. This is a latency clust

This cluster is a `svc:*` scope, so proceed with normal RCA. It's grouped with two other clusters in

Benign controller code. Let me look at the repository and query option.

Benign repository code. Let me check the Statistic model and default sort ordering.

Now let me check the Datadog logs/APM around this incident window, and check the Statistic table's c

Now let me search Datadog for the specific trace and logs.

Cluster is a latency issue (`cluster_type: latency`, ~304s response). Let me search Datadog for this

Let me search more specifically for the slow trace and any related duration/error indicators around

Interesting — Datadog shows KST timestamps (18:29–19:38 = 09:29–10:38 UTC). The requests are frequen

Datadog timestamps here appear to be in KST already (18:xx = ~09:xx UTC). The cluster's `first_seen`

Default per_page is 30, max 300. Now let me look at the polymorphic `_statisticable` — this is where

Now let me check what other clusters in the same incident window contained — they may reveal an unde

Both clusters share the same short window — statistics is 303s, ApiController#index is 15.7s. Let me

Let me instead check for PostgreSQL health metrics around the incident window.

No postgres metrics available. Let me also check general Rails request rate and see if there was a s

No errors — just latency. Let me check whether the request actually completed (looking around exactl

Let me see the message with the timing/duration data. Also check for `page` param usage:

The Datadog log message text is truncated in the search output — the timestamp `18:51:34` = 09:51:34

No prior episode. Let me also check the total statistics count context — this is a large polymorphic

I have enough evidence. Let me also confirm — the search method in `Admin::StatisticRepository` call

Confirmed — captures, editings, sitetracks, deviations, users all write statistics on every started/

OK. In `Admin::StatisticRepository#search`, the code passes the ActiveRecord relation to `.paginate`

Timestamp conversions (UTC → KST +9): `2026-07-25T09:51:34.302Z` → `2026-07-25 18:51:34 KST`.

RCA report written. Per the user's instruction, I will NOT modify the cluster frontmatter — the pipe

I'll search for the StructuredOutput tool schema.

RCA complete. Report written to `content/docs/incidents/83691355-5b5c-4ea2-800c-b04cb6a89ae9/rca.mdx