Rules
Updated 1 October 2026 · BugsRadar team
Without rules, every channel of a project gets every error of that project. A rule is a filter on one channel of one project: the channel gets an error only when the error fits every condition of the filter. Rules come with the Pro plan.
What a rule is
To set a filter, open the project in the web app and press Edit filter next to the channel. A condition you leave empty fits any error.
Conditions
| Condition | What fits |
|---|---|
| Level | Errors of this level and above: Warning, Error or Critical. |
| Modules | One or several, separated by commas. A module fits the module of the error, its logger name (category) or a part of that name between dots: Payments fits MyApp.Payments.StripeService. |
| Environments | One or several, separated by commas: the environment your application reports, such as Production or Staging. An error without an environment fits no filter that names environments. |
Upper and lower case make no difference.
Examples
| Channel | Filter | What it gets |
|---|---|---|
| Pushover of the person on call | Level: Critical | Critical errors only |
| A Discord channel for staging | Environments: Staging | Everything from Staging |
| The team's Telegram group | Environments: Production | Everything from Production |
| The payments team's chat | Modules: Payments | Errors of the payments module |
How errors are routed
An error goes to every channel whose filter it fits. If it fits none, it goes nowhere: the project's page warns you when every working channel of the project has a filter. The first message of an error and the count of its repeats go to the same channels. The same error in two environments is counted separately, so Staging and Production never share a message.
When the Pro plan ends
When the Pro plan ends, filters count as extras of the Free plan: error alerts are paused until you remove the filters or renew the plan. Removing a filter works on any plan.
Next: What you receive →