Drupal Migration — Performance Monitor

Bottom line — Spectre_5 remains healthy 7+ weeks into the Drupal 11 upgrade: average response time is 594 ms on D11, the best of the four phases, and the error rate (0.26%) is the lowest yet, both improving on the D10 (664 ms, 0.36%) and D8 (679 ms, 0.39%) baselines. Apdex is essentially flat across phases (0.77–0.79), so the gains look like real latency/error improvements rather than a change in user experience scoring. The last 24 hours and 7 days show normal traffic-following-load behavior with one isolated overnight anomaly.

• D11 early read: with roughly 7.25M requests logged since Aug 1, Drupal 11 is now a substantial (not thin) sample — response time and error rate are both trending better than D10 and D8, while apdex is holding steady around 0.77.
• Overnight spike: the 02:07 America/Chicago hour in the last 24h shows response time jumping to 1701 ms and apdex dropping to 0.47, against a backdrop of very light overnight traffic (~1.5K requests) — a low-volume outlier rather than a sustained issue, since the following hours return to baseline.
• Weekly pattern normal: the 7-day view shows the expected weekend traffic dip (Saturday Sep 19 at ~29K requests vs. ~150-210K on weekdays) with response time and error rate staying in the usual 527–634 ms / 0–0.3% range — no anomalies beyond the overnight spike above.
• D10/D11 error trend: error rate has declined phase-over-phase since D9 (0.42% → 0.36% → 0.26%), consistent with post-upgrade stabilization rather than a regression from the Drupal 11 migration.
• Maintenance window: the Aug 1 05:00–07:00 Chicago maintenance/deploy window is deliberately excluded from both the D10 and D11 phase aggregates so neither version is scored on downtime. It has since rolled off both the 24h and 7d views (7+ weeks old) and isn't a distinct dip in the current weekly history chart at this resolution.

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.