CrashAlert vs Query Monitor
CrashAlert Pro (Yodsira) vs Query Monitor — an honest comparison — including where they win
Query Monitor is a superb, free developer tool: while you are logged in, it shows database queries, hooks, errors and performance on every page. CrashAlert solves a different moment: 3 a.m., a plugin update goes wrong, the site white-screens, and nobody is logged in to look — because nobody can.
A fatal error kills the page before any debugging bar can render. CrashAlert lives at the error-handler level: it catches the fatal, tells you on Telegram within seconds, names the culprit plugin and version, and sends a "site is back up" notice when the crash stops. It is the smoke detector to Query Monitor's multimeter.
Side by side
| CrashAlert Pro | Query Monitor | |
|---|---|---|
| Reports fatals with nobody logged in | Yes — its whole job | - |
| Telegram alert within seconds | Yes | - |
| Culprit plugin + version named | Yes, in every alert | Manual inspection |
| Recovery notice ("site is back up") | Yes, file-based | - |
| Queries, hooks, per-page profiling | - | Yes — its core strength |
| Runs during development | Either, happily | Made for it |
| Overhead on production | ~5 ms on healthy requests | Admin-only by design |
| Pricing model | $29 one-time license per site, 1 year of updates | Free |
Where the alternative is the better fit
- You are actively debugging a plugin you develop — Query Monitor, free and excellent, is the right tool.
- You need database query analysis or performance profiling during development.
The verdict
They are not rivals; they cover different hours of the day. Keep Query Monitor for development hours. Choose CrashAlert for the other 23 hours — production, nobody watching, one-time $29 for the alarm that wakes you before your customers do.