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 — Over the last 24 hours Spectre_5 ran within its normal band (roughly 550–700ms response, apdex 0.74–0.88) apart from one brief overnight latency spike. The trailing week has been flat and healthy, with error rates staying under 0.6%. Early Drupal 10 (D10) numbers since the Jul 4 cutover are encouraging: average response time and apdex have recovered to match or beat the Drupal 8 baseline, reversing the regression seen during the Drupal 9 window.
Isolated overnight spike: at 04:06 CDT today response time jumped to ~2.48s (vs. a typical 550–700ms) and apdex fell to 0.47, the 24h low, during a low-traffic window (988 reqs); the error rate stayed flat at 0.2%, pointing to a latency-only event rather than a broader outage.
7-day trend is stable: daily response time held in a tight 552–668ms band with apdex between 0.77 and 0.84 and error rates at or below 0.56% every day.
Drupal 9 (May 23 – Jul 3) was the weakest of the three platform phases: highest average response time (699ms), lowest apdex (0.77), and highest error rate (0.42%).
Drupal 10 early read (since Jul 4, 2.74M requests) shows a clear recovery: response time down to 663ms, apdex back to 0.79, and error rate down to 0.38% — all better than Drupal 9 and roughly matching or edging out Drupal 8.
Outside the single overnight spike, no other notable multi-day error-rate or apdex degradation appears in the 7-day or monthly trend.
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.