Observability¶
How errors, metrics and traces are collected per component.
| Component | Errors | Metrics / traces |
|---|---|---|
| Website | Sentry | Cloudflare Workers logs / observability |
| Platform | — | Cloudflare Workers logs / observability |
| AI | — | Cloudflare Workers logs / observability |
| App | Sentry | OpenTelemetry → Grafana LGTM (Loki/Tempo/Mimir), Prometheus (/metrics/) |
| Blog / CMS | Sentry (PHP SDK) | New Relic (deploys via Quicksilver) |
Notes¶
- The Cloudflare Workers (Website, Platform, AI) use Cloudflare's built-in logs and observability; the Website additionally reports errors to Sentry.
- The App emits OpenTelemetry traces/metrics to a Grafana LGTM stack
(Loki for logs, Tempo for traces, Mimir for metrics) and exposes Prometheus
metrics at
/metrics/; errors go to Sentry. - WordPress reports errors to Sentry (PHP SDK) and marks deploys in New Relic through Pantheon Quicksilver hooks.
Live Cloudflare logs
For the Workers, use the cloudflare skill (or wrangler tail) to stream live
logs when debugging an edge issue.