Does every error have to make noise?
Not unless you want it to. Notify on a new error, a recurrence after resolution, a frequency threshold, or every unresolved occurrence. Each project gets its own rules.
Some errors deserve a tap on the shoulder. Others can wait. Tell Telebugs what matters, then choose where the alert should find you: email, browser push, Slack, Discord, Microsoft Teams, or a webhook.
Not unless you want it to. Notify on a new error, a recurrence after resolution, a frequency threshold, or every unresolved occurrence. Each project gets its own rules.
Yes. Tell a project to notify only for fatal and error events. Warning, info, debug, and sample events remain stored and searchable. They simply stop asking for your attention.
Yes. Turn on email, browser push, and as many webhooks as you need. Slack, Discord, and Microsoft Teams come with ready-made templates. The project’s rules decide when to alert; the enabled channels decide where it goes.
Send a test email, push notification, or webhook from the configuration screen. Better to find a bad URL or missing browser permission now than during the next production error. The notification manual has the channel setup details.