About TaskBeacon
TaskBeacon watches scheduled scripts. Your Stata do-file, R or Python script, SAS program, SPSS syntax or PowerShell task sends a short ping when it starts and when it ends. If a ping doesn't come in time, the script reports an error, a run takes far longer than usual, or the row count suddenly drops, you get an alert by email or in Slack, Teams, Discord, Google Chat, ntfy or a webhook. TaskBeacon can also check websites and APIs (with SSL and domain expiry) and read Power BI, SharePoint/OneDrive, dbt Cloud, Fivetran and Azure Data Factory runs.
Who it is for
Analysts and small data teams whose reports and imports run on their own PC or a server, started by Windows Task Scheduler, cron or SQL Server Agent. The scheduler only knows the exit code; TaskBeacon also notices when the job never ran, or ran and loaded nothing.
Why it exists
Most monitoring tools are built for developers and servers. Scripts written by analysts fail quietly: a do-file stops at an error but Stata still exits with 0, or a nightly import loads zero rows and nobody notices until a report is wrong. TaskBeacon is built for that case: no agent to install, a few lines to paste, and the checks for odd data are on by default.
What it sees
Only the pings: the time, start / finish / fail, the numbers your script chooses to send (such as a row count) and, on a failure, the last 20 lines of output (or the error message). Never your data, files or databases. See the privacy notice.
Status
TaskBeacon is free to start, and every feature is open to everyone for now. Planned pricing is on the Pricing page, with our promise to early users.
Contact
Questions, bugs, a language that should be supported: support@taskbeacon.io.
Logos
Product names and logos belong to their owners and are shown only to say TaskBeacon works with them. R logo © 2016 The R Foundation, CC BY-SA 4.0.