CrashAlert

Know about a crash before your clients do.

When a plugin or theme throws a fatal error, WordPress emails the site owner —

hours later, easily lost in spam, and always in cryptic PHP jargon. CrashAlert

makes the same information instant, readable and actionable:

• Instant alerts to Telegram, email and a custom webhook.

• Culprit attribution — the alert names the plugin, mu-plugin or theme

that owns the failing file (with its version).

• Plain-language explanations — “Call to undefined function” becomes

“Plugin versions diverged — roll back the last update”, in English or Russian.

• Recovery notice — a green message when the site starts responding again.

• Correlation with updates — “what changed in the 24 h before the crash?”

is answered right in the event card.

• Rate-limited — a flood of identical errors produces one alert with a

repeat counter, not a hundred messages.

• Failure history with a filterable timeline, kept for your chosen

retention period (default 60 days) and fully removed on uninstall.

• Local crash log — CrashAlert stores captured errors in its own table

in YOUR WordPress database (that is what the Event timeline shows), kept

for the retention period you set in the settings (default 60 days) and

fully removed on uninstall. This storage is local, exists regardless of

the optional telemetry, and nothing in it is sent anywhere unless you

enable telemetry — in which case only sanitized daily aggregates leave

your site.

• Privacy-friendly by design — alerts go ONLY to the channels you

configure yourself (your own Telegram bot, your site’s email, your own

webhook endpoint). Crash data stays in your own database; the optional,

off-by-default error telemetry (see “External Services”) is the only way

anything reaches the developer, and only if you switch it on. No IPs

stored, stack traces sanitized (relative paths, no call arguments).

CrashAlert never limits your site: the monitor itself is guarded so it can

never be the cause of a white screen, and healthy requests pay a microsecond

overhead.

Looking for more? The optional CrashAlert Pro companion adds a PHP

deprecation radar (warnings that will become fatals in future PHP versions),

com/en/product/crashalert/

Why not just rely on the WordPress core email?

Core recovery emails go to the site owner’s address, are easy to miss, contain

a raw stack trace, say nothing about repeats, and never tell you the site is

back. CrashAlert covers exactly those gaps — and delivers to Telegram, where

site owners actually live.

Pro Version

An optional companion plugin adds (one license = one site, 12 months of updates):

• Unlimited alert channels — free covers one of each type (1 Telegram chat,

1 email, 1 webhook), Pro adds as many as you need

• PHP deprecation radar — deprecated code you must fix before the next PHP upgrade

• Weekly health report by email

The free version is fully functional on its own and never limited.

com/product/crashalert/

External Services

CrashAlert sends notifications ONLY to services you configure in its own

settings. The only connection to the developer’s own service is the

optional, off-by-default error telemetry described at the end of this

section — nothing is sent until you enable it yourself.

— Telegram notifications —

org), used to deliver

instant crash alerts to your own bot and chat.

* What data is sent and when: your site hostname, the time of the crash, the

error message (truncated to 200 characters), the file path, the plugin or

theme name and version identified as the culprit, the affected page URL and

a repeat counter — sent only when a fatal error is caught, or when you

press “Send test to Telegram” in the settings.

* Opt-in: the feature is fully disabled until you enter your own bot token

and chat id; you can clear them at any time to switch it off.

org/tos

org/privacy

— Email notifications —

* What the service is: your own site’s email system (wp_mail), used to send

the same alert to the address you choose (site admin by default).

* What data is sent and when: the same alert content as above, only when an

alert fires. Delivery depends on the mail configuration of YOUR site.

— Custom webhook —

* What the service is: any HTTP endpoint you paste into the plugin settings

(for example, your own Slack/Discord relay or log collector).

* What data is sent and when: a JSON payload with the same alert content,

only when an alert fires or when you press the webhook test button.

* The endpoint is yours; the plugin does not provide, host or proxy this

service.

• Optional, off by default: anonymous error reports. If the admin enables

the checkbox in the plugin settings, a daily batch of sanitized crash

signatures already captured by CrashAlert (message, file name:line, the

culprit plugin or theme, versions, site address) is sent to

com/api/telemetry so recurring crashes get fixed faster.

Nothing is sent while the checkbox is off.

Why: I am an independent developer, and this is the only way I learn about

bugs I cannot reproduce myself. The free plugin makes no requests at all

until you enable this option; when an error happens, an anonymous

com so I can fix it in the next release.

Nothing else ever leaves your site, and you can switch it off at any

moment. Every report is read by a human.

Example of exactly what one report looks like (sanitized):

2

That is the whole payload — no content, no user data, no usage tracking.

Disabling telemetry clears any queued reports immediately.

com/en/terms/

com/en/privacy/