Internal tools nobody monitors

Updated 1 October 2026 · BugsRadar team

Every company has them: the admin panel three people use, the nightly import, the report that runs on the first of the month, the little service that syncs two systems. They are not monitored because they are not the product. They break on a Tuesday and are found on the following Monday, usually by the person who needed the report.

One project for all of them

Internal tools don't need a project each. Make one project, "Internal", and connect it to the chat of the people who maintain them. The message names the tool through the module or the category, so "Internal · Error · Shop.Admin.Export" says which one broke. For the apps, add the package for .NET, Node.js or Python; for the scripts and scheduled jobs, one HTTP request with the HTTP endpoint, with category set to the job's name.

The jobs that run while nobody watches

The nightly import that fails on one row and exits "successfully" is the classic silent failure. A job that reports its own failure arrives in the chat the same night, with the host and the error. Ready-made guides: SQL Server Agent, Windows Task Scheduler, cron, systemd. A job that fails every night brings a full message every night; a job that fails every minute brings one message with a count.

Not everything is an error

An internal tool often logs warnings that deserve a look but not a notification at night. The packages send Error and above by default, and the floor can be lowered per logger if you want warnings too. On the Pro plan a rule on the channel keeps the internal project's noise out of the product team's chat: see Rules.

What it costs

Nothing, if "Internal" is one of your two Free projects; no event quotas either, so a chatty import doesn't matter. See Pricing.

What it doesn't do

It won't tell you that the monthly report never ran at all; that is a heartbeat monitor's job. It tells you the moment the report ran and failed. BugsRadar also keeps no history, so the question "has the import been flaky this quarter?" is answered by your chat's search, not by a dashboard.

Where to go next

The guides have the copy-paste for each scheduler. Background jobs and queues covers the workers behind the tools.