Drupal Migration — Performance Monitor

Bottom line — Spectre_5 is running normally over the last 24 hours (mid-500s to high-600s ms response, apdex mostly 0.74–0.81), with request volume tracking the usual overnight lull and daytime ramp. The trailing week is stable in the 590–720ms band with error rates under 1%, and D10 (Drupal 10, 12 days in) is now tracking almost identically to the D8/D9 baselines on both response time and apdex.

• A single overnight spike to 1109ms at 02:04 CT stands out against an otherwise flat 24h response curve, but traffic in that bucket was light (1,276 requests) and error rate stayed low (0.39%) — consistent with reduced-load noise rather than a systemic issue.
• Jul 13 was the week's busiest day (~210K requests) yet response time only rose modestly to 722ms with apdex holding at 0.77, showing the app absorbs peak load without much degradation.
• Error rates across the trailing week stayed in a tight 0.25–0.82% band with no day standing out as anomalous.
• D10 (695ms avg, 0.78 apdex, 0.42% err) now sits almost exactly between D8 (679ms, 0.79 apdex, 0.39% err) and D9 (699ms, 0.77 apdex, 0.42% err) — the Drupal 10 migration shows no regression versus the prior two platforms after nearly two weeks of traffic.
• Monthly trend over the past 13 months shows response time oscillating in a 634–797ms range with no sustained upward drift, and June 2026 (693ms, 0.78 apdex) is in line with the recent average.

Method & caveats

• Cutovers. Drupal 9 / PHP 8 went live May 23, 2026; Drupal 10 Jul 4, 2026 — marked on every chart that spans them.
• Drupal 10 is an early read (~5 days). Its phase card uses the Jul 4–9 window directly.
• Recent spike. Jul 8 shows an isolated response jump (≈2× the prior day), coinciding with elevated reports/progress-API latency that day — an operational blip, not a migration regression.
• Source & retention. New Relic timeslice metrics (HttpDispatcher, Apdex, Errors/all), ~13-month retention — the full arc back to mid-2025 is covered. Percentiles (p95/p99) live in 8-day event data and are reported in the point-in-time reviews, not here.
• Refresh. Regenerated daily by a scheduled routine that re-queries New Relic and redeploys to this same URL.