BugsRadar

Channels

Updated 1 October 2026 · BugsRadar team

A channel is where the alerts of a project go: a Telegram chat, a Discord channel or a Pushover application. A project can have several channels, and one channel can serve several projects.

Your own credentials

BugsRadar delivers through your own credentials. They are checked with the service when you save the channel, stored encrypted and never shown again - only a mask such as …a1b2. Credentials can't be edited: to change a token or a webhook, create a new channel and delete the old one. One channel can serve several projects.

Set up a channel

On the project's page press Add channel and choose the service. Each one needs something different:

BugsRadar checks the credentials with the service before saving them; Send test sends a test message. Slack, Microsoft Teams, Google Chat and PagerDuty are coming with the Business plan.

Live count

In Telegram and Discord the count of repeats is written into the message of the first occurrence, without a new notification. Live count on the Channels page turns this off for a channel: each count then arrives as a new message. Pushover can't edit a message, so there the repeats always arrive as summaries. What the messages look like: What you receive.

When a channel fails

If the service is briefly unavailable or asks BugsRadar to slow down, delivery pauses and resumes on its own. If the service keeps refusing - the token was revoked, the bot was removed from the chat, the webhook was deleted - BugsRadar turns the channel off and marks it Turned off by BugsRadar with the last error; messages that were waiting for it are dropped.

Fix the cause and press Check again: BugsRadar checks the credentials with the service and turns the channel back on. The channel's On / Paused switch is yours alone and never clears a turn-off by BugsRadar.

Next: Telegram →