Telegram error alerts for .NET, Node.js and Python apps
Every new error of your application lands in a Telegram chat, group or channel, sent by your own bot: the first occurrence at once, with its stack trace, and repeats as a live count in that same message, without a new notification.
Free plan · your own bot · your events are never stored
What arrives
A message about one error starts with the project name and the level, then the exception and its message, where it happened, the environment, host, version and time, the event's properties and the stack trace.
- While the error keeps happening, the count of repeats is written into that first message: 10 minutes after it was sent, then after 30 minutes, an hour, and every 6 hours. No new notification.
- When a window passes without repeats, the error is closed; its next occurrence arrives as a new first message.
- Prefer a message per count? Live count on the Channels page turns the editing off for this channel.
- When the chat can't keep up, the waiting errors arrive bundled: one message, one line per error, grouped by project.
- BugsRadar keeps to Telegram's limits and waits whenever Telegram asks.
What you need
A bot from @BotFather
Send /newbot to @BotFather and keep the token it replies with. The bot only needs to be able to post.
A chat ID
A private chat with the bot, a group it is added to, or a Telegram channel where it is an administrator. The setup guide shows how to find the ID.
Checked, encrypted, masked
BugsRadar checks the token and the chat with Telegram before saving, stores them encrypted and shows only a mask afterwards. Send test puts a test message in the chat.
The steps, in order: Set up Telegram.
From any platform
The channel is chosen in the web app, not in the code: the same package, the same call, whatever the chat.
- .NET - one NuGet package:
ILogger, Serilog, NLog, log4net and direct calls, for ASP.NET Core, worker services, console apps and .NET Framework. - Node.js - one npm package: uncaught errors, Express, winston, pino and direct calls, with TypeScript types.
- Python - one package from PyPI: the logging module, loguru, uncaught exceptions, Django, Flask and FastAPI.
- Scripts, cron jobs and pipelines - one HTTP request from Bash, PowerShell or any language, with ready-made guides for cron, systemd, SQL Server Agent, backups and CI/CD.
When something changes
The channel stays yours; BugsRadar only tells you when it stops working.
- Token revoked or bot removed from the chat? BugsRadar turns the channel off, marks it Turned off by BugsRadar with the last error, and the project's page shows it. Fix the cause and press Check again.
- Another bot or another chat? Credentials can't be edited: add a new Telegram channel and delete the old one.
- Telegram asks to slow down? Delivery pauses and resumes on its own, and errors that waited arrive bundled.
Questions developers ask
Why do I need my own bot?
Messages go from your bot to your chat, so you stay in control: you choose who is in the chat and can revoke the token at any time. BugsRadar stores the token encrypted and shows only a mask after saving.
Does BugsRadar read my chat?
No. The token is used only to send BugsRadar's own messages and to write the count of repeats into them.
Can the alerts go to a Telegram channel instead of a group?
Yes. Add the bot to the channel as an administrator that can post messages; channel IDs are negative numbers, as the setup guide shows.
Can several projects share one channel?
Yes. One channel can serve several projects, and a project can have several channels: the Free plan includes 2 projects and 3 channels, Pro has no limit.
Does BugsRadar store my errors?
No. An event stays in memory only until it is delivered to your channels; nothing is written to a database. BugsRadar keeps only what it needs to run: your email, your projects and the encrypted settings of your channels.
Connect Telegram in a few minutes
Sign in with your email, create a project, paste the bot token and the chat ID.
Next: Discord alerts →