FatalGuard

Pro

Pro: alert routing

By default every fatal goes to your main Telegram chat. Routing lets you send a particular plugin’s fatals to a different chat — so, for example, WooCommerce crashes land in the shop’s channel while everything else comes to you.

Set it up

Go to FatalGuard → Alerts and find Extra Telegram targets. Add one target per line, in this format:

chat_id | plugin-slug | optional-bot-token
  • chat_id — the destination chat (a group looks like -100123456789).
  • plugin-slug — the plugin whose fatals should go here. A fatal is matched when it originates from that plugin (by its path under wp-content/plugins/).
  • optional-bot-token — use a different bot for this target, or leave it blank to use your primary bot.

Example

-100200300400 | woocommerce | 
-100500600700 | acme-crm | 111222:AA-second-bot-token

WooCommerce fatals go to the first chat via your main bot; Acme CRM fatals go to the second chat via a dedicated bot.

How matching works

A target with a plugin slug only fires for fatals coming from that plugin. Fatals from anywhere else continue to your main chat. This is additive — routing doesn’t turn off your primary alert, it adds a destination for the plugins you name.

Good for agencies

Routing shines when one WordPress install (or one client) has several stakeholders: the developer watches everything, while each app’s owner only hears about their own plugin. Pair it with the Agency plan’s 20-site license to run it across every client.