Headline production metrics across the platform's upgrade arc — Drupal 8 (PHP 7.4) → Drupal 9 (PHP 8) → Drupal 10. Switch the range to see the last 7 days, month-by-month, or the full history since the migration began.
App Spectre_5 (live)Source New Relic APMData as of —Refresh daily (scheduled routine)
Last full day
Most recent complete day vs the day before.
Interpretation · updated daily by Claude
Automated read of the latest data — bottom line, phase comparison, and notable trends.
Bottom line — Spectre_5 is healthy over the last 24 hours (460–640ms response, apdex 0.74–0.80 outside one overnight blip) and stable across the last 7 days. The Drupal 11 phase, now running since Aug 1 (~9.64M requests), shows the best response time and error rate of any phase recorded, with D10 and D8 both running slower and leakier by comparison. No anomalies tie back to the Aug 1 upgrade window itself — it sits well outside the current 24h/7-day lookback.
24h: a single overnight spike at 02:08 CDT (1463ms response, apdex dropped to 0.58) stands out against an otherwise flat night; this mirrors a recurring overnight latency pattern seen in prior periods and is not error-driven (err stayed at 0.0%).
7d: Oct 3 was a low-traffic day (50.4K requests vs. 150–230K on surrounding days) but had the week's best response time (480ms) and apdex (0.81) — consistent with lighter load rather than a problem.
D11 early read: resp 592ms / apdex 0.77 / err 0.20% over 9.64M requests, beating both the D10 baseline (663ms / 0.78 / 0.36%) and the original D8 baseline (679ms / 0.79 / 0.39%). With roughly 9x the request volume of D10's shorter window, this is a substantial sample, not a thin one — the Drupal 11 upgrade looks like a clear net improvement on both latency and error rate so far.
D9 remains the outlier phase (699ms resp, 0.42% err, the highest of the four), while D8/D10/D11 cluster closer together.
The Aug 1 05:00–07:00 CDT maintenance window is excluded from the D10/D11 aggregates above; at today's date it has aged out of both the 24h and 7-day series and is too brief to register as a visible dip in the weekly-binned long-range chart.
By release phase
Full-period averages per production version. Change vs the Drupal 8 baseline.
Performance over time
Response time, error rate and Apdex for the selected range.
Average response time
—
milliseconds · lower is better
Drupal 8Drupal 9Drupal 10dashed = version cutover
Error rate
% of requests
Apdex
target 0.5 s
Period
Resp (ms)
Apdex
Error %
Requests
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.
Spectre LMS · Production performanceServer-side New Relic APM aggregates.