Slack error alerts for .NET, Node.js and Python apps
Every new error of your application lands in a Slack channel, posted through an Incoming Webhook of your own Slack app: the first occurrence at once, with its stack trace, and the count of repeats as short summaries. Slack comes with the Business plan.
Business plan · your own Slack app · your events are never stored
What arrives
A message about one error carries a colored bar by level, the project name, the exception and its message, where it happened, the environment, host, version and time, the event's properties and the stack trace in a code block.
- An Incoming Webhook can't edit a message, so the repeats arrive as summaries at the same moments as the live count in Telegram and Discord: 10 minutes after the first message, then after 30 minutes, an hour, and every 6 hours.
- When a window passes without repeats, the error is closed; its next occurrence arrives as a new first message.
- When the channel can't keep up, the waiting errors arrive bundled: one message, one line per error, grouped by project.
- BugsRadar keeps to Slack's limits for webhooks and waits whenever Slack asks.
What you need
An Incoming Webhook of your own Slack app
Create an app at api.slack.com/apps, turn on Incoming Webhooks and add a webhook to the channel that should receive the errors. Slack gives you a URL on hooks.slack.com; that URL is the only thing BugsRadar needs.
One webhook, one channel
A webhook posts to the channel you picked when you created it. Another Slack channel is another webhook and another BugsRadar channel.
Checked, encrypted, masked
BugsRadar posts a short message to the channel to check the webhook before saving, stores the URL encrypted and shows only a mask afterwards. Send test posts a test message.
The steps, in order: Set up Slack.
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 app stays yours; BugsRadar only tells you when it stops working.
- Webhook deleted or the app removed from the workspace? 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 channel? Credentials can't be edited: add a new Slack channel with the new webhook and delete the old one.
- Slack asks to slow down? Delivery pauses and resumes on its own, and errors that waited arrive bundled.
Questions developers ask
Why an Incoming Webhook and not a bot token?
A webhook can do one thing: post to one channel. There is no token with wider access to your workspace, and you revoke it in the app's settings whenever you want. BugsRadar stores the URL encrypted and shows only a mask after saving.
Why summaries instead of a live count?
An Incoming Webhook can't edit a message once it is posted, so the count of repeats arrives as a short summary at the same moments as the live count in Telegram and Discord: 10 minutes after the first message, then after 30 minutes, an hour, and every 6 hours.
Does it work with Slack Enterprise Grid and GovSlack?
Yes. Webhooks on hooks.slack.com and hooks.slack-gov.com are accepted.
Can several projects share one channel?
Yes. One channel can serve several projects, and a project can have several channels; with rules each channel gets only the errors that fit its filter.
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 Slack in a few minutes
Sign in with your email, upgrade to Business, create a project, paste the webhook URL.
Next: Microsoft Teams alerts →