How to monitor Laravel in production (without Datadog)
Practical monitoring for small fleets: PHP-FPM, queues, deploy health, and automated repair without six-figure observability bills.
Infrastructure insights, engineering deep-dives and product updates.
Practical monitoring for small fleets: PHP-FPM, queues, deploy health, and automated repair without six-figure observability bills.
When per-client Forge accounts stop scaling — panels, deploys, monitoring, and repair in one control plane.
Paging humans for every CPU blip burns teams out. Shift to health-gated alerts and automated remediation for known failures.
Stop promoting broken releases — tie deploy cut-over to real production signals, not just green CI.
Engineering hours, bus factor, and missed incidents — why home-grown health bots rarely age well.
On-call tools route pain to humans. Reflex repairs PHP-FPM, queues, and disk pressure when policy allows.
From slow logs to 502s and OOM kills — symptoms, sizing, and playbooks that keep Laravel online.
Multi-tenant dashboards, client isolation, repair audit trails, and predictable per-server pricing.
Production checklist for Droplets: PHP-FPM, queues, TLS, and ongoing health after go-live.
Gunicorn, Celery, RDS, and reverse-proxy hygiene — what to watch after launch day.
The DNS trio that decides inbox placement — how to check it, fix it, and monitor drift across cPanel accounts.
Spamhaus, Barracuda, and the signals that your cPanel fleet is leaking outbound spam — before every customer inbox fails.
WHM reseller API tokens give fleet visibility — email auth, SSL, disk, and suspended accounts — without a root password.
Email auth drift, full disks, expired TLS, and blacklisted IPs — failures customers feel before your monitoring pings.
Security support ended in 2023 — a fleet-wide PHP version audit across WHM accounts before the next CVE becomes your weekend.
From reflexd signals to a logged repair: detect → evaluate → confirm or auto-run → verify → audit. A plain-English tour of the loop that keeps Linux servers boring.
Why a single Go binary, how heartbeats and commands work, and how the agent stays out of your request path while still seeing what matters on the host.
A realistic composite story — anonymised patterns from teams we talk to — about consolidating panels, deploys, and repair into one workflow.
The fields Reflex expects, risk tiers, dry-run behaviour, and a minimal playbook you can read without a PhD in DevOps.
Ploi is a capable PHP-first server panel. Reflex targets runtime health, automated repair, and deploy safety. An honest side-by-side for teams choosing a stack.
PM2 dashboards, memory leak detection, CPU profiling, health checks, and log aggregation — everything you need to keep Node.js servers alive in production.
From Gunicorn workers to systemd services, nginx reverse proxies, SSL termination, and environment management — deploy FastAPI properly.
Vercel costs climb fast at scale. Here is the complete guide to self-hosting Next.js with PM2, Docker, and nginx — and when it actually makes sense.
The math behind pm.max_children, dynamic vs static process managers, memory budgeting, pm.max_requests, and monitoring — no more guessing.
Forge plus monitoring plus alerting plus CI plus deploy tooling — the bills add up. A real breakdown of what teams actually spend, and where consolidation saves money.
Reflex started as a PHP-first tool with a Zend extension. Now the reflexd agent works with Node.js, Python, Go, Ruby — any Linux server. Here is why we expanded.
OOM kills, PHP-FPM crashes, nginx 502s, disk full, dead queue workers, SSL expiry, and more — each one explained, and how the Reflex Brain handles it.
Datadog is incredible for large organisations. But if you run fewer than 50 servers, you might be paying for complexity you do not need. An honest comparison.
PagerDuty wakes the right person. Reflex fixes the incident. When to use both — and when self-healing infrastructure replaces most pages.
New Relic's free tier is generous for observability. Reflex is for teams who want production issues fixed — not just graphed.
Restart scripts and health bots work until they don't. Bus factor, novel failures, and audit trails — what Reflex adds.
Per-host monitoring, per-user paging, and engineering time maintaining DIY scripts — model your stack against Reflex tiers.
A deep technical dive into how we instrument the PHP runtime at the interpreter level — and why no external monitoring tool can do what we do.
OOM kills, 502s, dead queue workers, disk full errors. You've seen them all at 3am. Here's the definitive guide to each one.
PHP was the obvious choice for a PHP monitoring tool. We chose Go anyway. Here's why.
The Linux Out-of-Memory killer is one of the most common causes of PHP-FPM crashes. A complete guide.
Forge-class provisioning versus Reflex Pipeline plus the Brain — where the products overlap, and where they diverge.
A step-by-step guide to atomic Laravel deployments using Reflex Pipeline.
After 18 months of building, we're opening up Reflex to a small group of developers.