CrashAlert

Description

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.
• 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). Nothing is ever sent to the developer. No IPs stored,
  stack traces sanitized (relative paths, no call arguments). See the
  “External Services” section below.

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),
unlimited alert channels and a weekly health report: https://yodsira.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.

External Services

CrashAlert sends notifications ONLY to services you configure in its own
settings. It never contacts yodsira.com servers and includes no telemetry.

— Telegram notifications —
* What the service is: Telegram Bot API (api.telegram.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.
* Terms: https://telegram.org/tos
* Privacy: https://telegram.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.