Alert when something fails

Updated 1 October 2026 · BugsRadar team

Not every failure is an exception inside your application. A backup that didn't finish, a cron job that exited with an error, a deploy that broke, a service that stopped: each of them can report itself to your Telegram, Discord or Pushover with one HTTP request. Pick the guide for your case; each one is a few lines to paste.

All guides

• SQL Server Agent - an alert when a job fails, with the step that failed and its error, without Database Mail.
• Backups - pg_dump, mysqldump, rsync and robocopy scripts that report their own failure.
• CI/CD pipelines - a failed build or deploy in GitHub Actions, GitLab CI/CD, Azure Pipelines and Jenkins.
• Cron - one line in crontab, or a wrapper for all jobs.
• Windows Task Scheduler - PowerShell and command-line tasks that report a failure.
• systemd - OnFailure= for services and the services that timers start.

What they have in common

• Every guide sends the same request: POST https://api.bugsradar.com/api/v3/notify with the project's API key in the X-Api-Key header and the text of the message as the body. It is a few lines of curl or PowerShell; the parameters, responses and limits are in the HTTP endpoint docs.
• You need a BugsRadar project with a channel and the project's API key: see Get started. The key lives in an environment variable or in the secrets of your CI system, never in a script that goes into a repository.
• A job that fails once a night brings a full message every night. A job that fails every minute brings one message and counts the repeats in it, so the chat stays readable: see repeats and grouping.

Your case isn't here?

Anything that can run curl or Invoke-RestMethod can use the same request: a Docker healthcheck, a Kubernetes job, an Airflow task, a PowerShell script on a workstation. Start from the quick start of the HTTP endpoint. If you would like a guide for your case, write to us.