Alerts go through your own bot, webhook or app
Give BugsRadar the credentials of your own Telegram bot, Discord webhook, Pushover application, Slack or Google Chat webhook, Teams workflow or PagerDuty service. You decide who reads the chat, and BugsRadar keeps to each service's limits: it waits whenever the service asks. Telegram, Discord and Pushover are on every plan, Free included; Slack, Microsoft Teams, Google Chat and PagerDuty come with Business.
Channels
| Channel | You provide | Repeats | Plan |
|---|---|---|---|
| Telegram | The token of your own bot and the chat ID | Counted in the first message, no new notification | Free |
| Discord | A webhook URL of the channel | Counted in the first message, no new notification | Free |
| Pushover | An application token and a user or group key | Short summaries | Free |
| Slack | An Incoming Webhook URL of your Slack app | Short summaries | Business |
| Microsoft Teams | A Workflows webhook URL of the channel | Short summaries | Business |
| Google Chat | An incoming webhook URL of the space | Short summaries | Business |
| PagerDuty | An Events API v2 integration key of the service | Join the open incident | Business |
Telegram
A private chat, a group or a channel. Messages come from the bot you create with @BotFather; the count of repeats is written into the first message, so a crash loop is one message, not a flood. About Telegram alerts · Set up Telegram
Discord
Any text channel of your server, through a webhook. There is no bot to install, and the count of repeats is written into the first message here too. About Discord alerts · Set up Discord
Pushover
Push notifications on your phone or desktop, for one person or a whole delivery group. A notification is short and comes without the stack trace; repeats arrive as summaries. About Pushover alerts · Set up Pushover
Slack
A channel of your workspace, through an Incoming Webhook of your own Slack app: a message with a colored bar by level and the stack trace in a code block. A webhook can't edit a message, so repeats arrive as summaries. Business plan. About Slack alerts · Set up Slack
Microsoft Teams
A channel of your team, through a Workflows webhook: an Adaptive Card with the facts and the stack trace. The old Office 365 connectors are retired and not used. Repeats arrive as summaries. Business plan. About Teams alerts · Set up Microsoft Teams
Google Chat
A space of your Google Workspace, through an incoming webhook of the space: a card with the stack trace in a code block. Repeats arrive as summaries. Business plan. About Google Chat alerts · Set up Google Chat
PagerDuty
Incidents on your service through an Events API v2 integration: a new error opens an incident with the stack trace in its details, repeats of the same error join it instead of paging again, and the severity follows the level. Business plan. About PagerDuty incidents · Set up PagerDuty
How delivery works
- Checked before saving. When you save a channel, BugsRadar checks its credentials with the service, stores them encrypted and shows only a mask afterwards. Send test puts a test message in the chat.
- The service sets the pace. BugsRadar keeps to each service's limits and waits when the service asks. Errors that can't go out one by one arrive bundled: one message, one line per error.
- A broken channel doesn't go unnoticed. If a token is revoked, the bot is removed from the chat or the webhook is deleted, BugsRadar turns the channel off and shows the reason. Fix it and press Check again.
- One channel, several projects. A channel can serve several projects, and a project can have several channels: the Free plan includes 2 projects and 3 channels. With rules on the Pro plan, each channel gets only the errors that fit its filter.
Work channels with Business
Slack, Microsoft Teams, Google Chat and PagerDuty come with the Business plan, together with an organization: members with roles, teams, single sign-on, an audit log and a management API. See Pricing.