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 now Spectre's largest-traffic phase (5.45M requests since Aug 1) and its early read is favorable: average response time is down to 610ms — the fastest of all four phases — with the lowest error rate (0.29%) and an apdex of 0.76, essentially matching D9/D10 and well ahead of the D8 baseline on speed. Traffic over the last 24h and 7 days looks healthy and follows the normal weekday/weekend rhythm, with no sustained regressions. One short overnight latency spike stands out and is worth a quick look, but it self-resolved within the hour.
D11 early read vs. baseline: Drupal 11's 610ms average response beats D8 (679ms), D9 (699ms) and D10 (663ms), and its 0.29% error rate is the best of the four phases — a strong start, though the phase is now ~41 days old (5.45M requests) so this reflects a real production sample, not a thin one.
Overnight anomaly (last 24h): the 02:05 CDT hour shows a sharp response-time spike to 2,144ms (vs. a ~550ms baseline) with apdex dropping to 0.44 — the single worst hour in the 24h window. It recovered fully by 03:05, so it reads as a transient blip (e.g. a cache warm or backend hiccup) rather than an ongoing issue, but is worth a spot-check in New Relic if it recurs.
Weekly traffic pattern (last 7 days): weekend days (Sep 05–06) show request volume dropping to ~40K/day versus ~100–160K/day on weekdays — the usual weekday/weekend cadence, not an anomaly.
Error rate stable, trending down: error rate has improved phase-over-phase from D9's peak of 0.42% down to D11's 0.29%, with no elevated error days in the last 7 days beyond ordinary noise (0.17%–0.56%).
Maintenance window note: the 2026-08-01 05:00–07:00 Chicago deploy/maintenance window is deliberately excluded from both the D10 and D11 phase aggregates above so neither version is scored on downtime; that window is now over 5 weeks in the past and has scrolled out of the current 24h/7d/monthly time-series views, so it is no longer visible as a dip in those charts.
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.