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 — Drupal 11 is outperforming every prior phase on the metrics that matter most: 593ms average response time (11% faster than D10's 663ms, 15% faster than D8's 679ms) and the lowest error rate of any phase so far at 0.22% (vs. 0.36% on D10 and 0.39% on D8). Apdex holds steady at 0.77, in line with D9/D10 and just below D8's 0.79. The last 24h and 7d show healthy, stable traffic with no elevated error rates.
D11 early read: two months into Drupal 11, the 8.94M-request sample is no longer thin and the trend is consistently positive — faster responses and fewer errors than both the D10 baseline it replaced and the original D8 baseline, with apdex unchanged. Early verdict: a clean, low-risk upgrade so far.
The 2026-08-01 05:00–07:00 Chicago maintenance window is excluded from the D10/D11 phase aggregates so neither version is penalized for downtime; that window falls outside the current 24h/7d lookback (which is now ~2 months later) so it will not appear as a dip in those charts going forward.
One hourly response-time spike in the last 24h at 02:09 Chicago (973ms, ~1.8× the surrounding baseline) stands out, but error rate stayed at 0.00% that hour, consistent with a transient latency blip rather than a fault.
Day-over-day traffic in the last 7 days is steady (211K–232K requests/day Sep 28–Oct 1) with error rates staying at or below 0.04%, no anomalies.
Longer-term weekly volume has roughly doubled year-over-year (~600K/week a year ago to ~1.0–1.2M/week in the past month), so D11's larger absolute request count partly reflects organic traffic growth, not just phase length.
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.