Alerting

Bugsink sends alerts when issues arise in your applications, allowing you to address problems before they escalate.

Alert Rules

By default, you’ll be notified for any state change that makes things worse, such as:

• New issues
• Regressions
• Unmuted issues

Email Settings

Email configuration is user-centric, so you can choose for which projects you want to receive alerts when this happens. This is implemented in a stepped manner:

• User level: Set your global preference for receiving alerts to yes or no.

• Team level: For any given team, choose the default alerting behavior (to you) for associated projects. Here you can choose to use your global preference or override it.

• Project level: For each project, you can choose to receive alerts or not. As with the team level, you can choose to use the team default or override it for a specific project.

Webhooks / Slack

Project-level webhooks let you send alerts to chat tools like Slack. Each webhook receives alerts for the project it’s attached to. The current implementation supports Slack-compatible incoming webhooks; other backends can follow the same pattern.

To set one up, create an incoming webhook URL in your chat tool, then add it to your project in Bugsink. You’ll be notified for any new or worsening issue—same logic as email alerts.

You can read more in the 1.6 release blog post.

What’s Next?

Some of the features we’re working on to improve alerting:

• Project-level “sensitivity” settings: the ability to send alerts only when a new issue occurs n times, or n times in a given period.
• Rate-limiting of alerts (global, per project, or per user), to avoid overwhelming you with notifications.