Error alert settings

The Error Alerts tab emails you when JavaScript errors appear on your site. The whole design problem here is noise: an alert that fires constantly gets filtered into a folder nobody reads, so the settings exist mainly to keep the volume down.

Settings

• Enable email alerts — the master switch.
• Recipients — who gets the mail. Use a team alias rather than an individual, so alerts survive people changing roles.
• Minimum severity — Critical only, or Warning and above. Start with critical only.
• At most one email per — a rate limit. A broken deploy can throw thousands of errors in a minute; this ensures that arrives as one email.
• Muted URL patterns — suppress alerts from URLs you do not control.

What to mute

Most sites accumulate errors that are real but not actionable: browser extensions injecting scripts, third-party widgets, bot traffic hitting URLs that never existed. Mute those patterns so the alerts that remain are ones you can act on.

Alerts vs error logs

Alerts are for the errors that need someone's attention now. The full record always lives in Error logs, so muting an alert never means losing the data.

For alerts on metrics rather than errors — a traffic drop, a conversion-rate fall — see Alerts.