Dead Man's Snitch is a monitoring tool for cron, Heroku Scheduler, or any periodic process. Dead Man's Snitch will notify you when your scheduled tasks don't run so you can investigate before it becomes a problem.
Have you ever had a backup fail or an email campaign not go out? Dead Man's Snitch will tell you right away when something doesn't happen so you can fix it. Still not convinced? Learn more in this blog post.
A snitch looks like this:
$ curl https://nosnch.in/c2354d53d2.
It's a unique URL we create for you to add to jobs you want monitored. If
you want to add a snitch to your backup cronjob it would look something like
$ run_backups_or_something && curl https://nosnch.in/c2354d53d2.
Receiving an email when cron is working can be helpful, but it's hard to tell when things don't run. The lack of an email in your inbox is hard to detect. Dead Man's Snitch solves this problem by sending you an email if your task hasn't checked in when it should. A second email notification will be sent once your task begins reporting again.
Any language that can fetch a URL.
Yes! We have Field Agent to make it super simple.
Anyone who signs up to our free plan gets one free snitch and access to standard intervals (hourly, daily, weekly, monthly). You can upgrade to any of our paid plans for more snitches, enhanced intervals and other premium features. If you'd like more snitches you can:
Dead Man's Snitch is a product of Collective Idea, a software development & consulting company based in Holland, Michigan.
We use Dead Man's Snitch for our own clients every day. We're building it to be a service that we want to use, and hope you will too!
If you have an hourly, daily, weekly, or monthly task, great! Choose the same interval. If your task is delayed (or depending on how long it takes to complete) you may receive an alert that your process hasn't checked-in. As soon as your task finishes, you will be notified that it's working again.
If your task runs at a different interval than what we currently have available, no problem. Take how often your task runs and round UP to the next Dead Man's Snitch interval. For example, if you have a job that runs every six hours, choose daily.
Intervals are how we know how often to check to make sure your job checked in. At the end of the specified period of time, Dead Man's Snitch looks back to see if the job checked-in during that period. If it did, great. If it didn't, you'll be alerted.
The time we check up on your snitch depends on the type of alert you select. There are two types currently available, Basic and Smart. Basic Alerts have a static time that they check up on your snitch, and alert you if something is wrong. That static time depends on the interval you choose.
|15 Minute||0:00, 0:15, 0:30, 0:45|
|30 Minute||0:30, 0:30|
|Hour||Every hour, on the hour|
|Week||12:00 AM Monday|
|Month||Midnight, 1st of the month|
Smart Alerts learn from your snitches behavior. After a few consistent check-ins, we will start shifting the time we check up on your snitch so you can be alerted as soon as possible if something goes wrong. If your job is not consistent with check-in times, your alert times will default to standard intervals.
Basic Alerts are available for any snitch. Smart Alerts are available for hourly, daily, weekly, and monthly interval snitches on the Surveillance Van plan, and for monthly interval snitches on all other plans.
If you have your snitch set up to use Smart Alerts, then you’re all good. We’ll pay attention to when your snitch receives check-ins so you can be alerted as soon as possible.
If you have Basic Alerts, you can still check in whenever, but you will be alerted faster the closer your job pings to the end of an interval when we check up on your snitch. This is explained in more detail on our blog.
Why yes! Error Notices, which are available on the Surveillance Van plan, will catch and then notify you of any errors that occur on your end even if your job checked in on time.
If your plan supports Error Notices, just tell us the exit status of your job after every run. (Note: If you're using Field Agent, the status code is automatically sent for you)
$ run_backups_or_something; curl https://nosnich.in/c2354d53d?s=$?
You'll receive a notice if your job reports an error (represented by an exit
status other than
0) or if your job goes missing and fails to
By default, emails will be sent to the email address you signed up with. You can set a per-snitch alert email when you create your snitch. You can also set an account-wide alert email address by signing in to your account and clicking your email address at the top of your dashboard. If you choose not to have a per-snitch alert email address, we fall back to your account alert email address. If you don't have an account-wide alert email address, we default back to your account sign-up address.
Yes! You can send alerts to multiple emails by separating them with commas. Any email already affiliated with the account will autocomplete to prevent accidentally mistyping an address.
The badge next to your snitch on your dashboard indicates its current status. If the snitch URL hasn't been hit yet, the badge will be gray. The badge will turn green after a check-in by hitting the snitch URL. If the snitch has missed a checked-in the badge will turn blue. A snitch that is paused will be yellow.
By default, the dashboard displays snitches alphabetically. The best way to keep your dashboard organized is to tag each snitch. This blog post explains how tags work.
After you create your snitch and curl it after your task, simply hit the URL.
Snitches are automatically unpaused when they are pinged.
We want to make sure you have it installed and working correctly to kick off the process.
You should check back in a day or so to make sure it started. We will email you around three days after you create or pause a snitch to make sure you know it hasn't started back up yet.
Just hit the URL manually and then wait. We suggest you do this with an hourly snitch so you don't have to wait forever. To manually hit the URL, either curl it after your cron job and hit return, or copy and paste your snitch into a new browser and hit return. Refresh your Dead Man's Snitch dashboard and you should see a green badge next to your snitch indicating that it's working.
Easy. Head to your snitch settings page, choose the new interval and confirm the change.
Click the gear icon next to your snitch name, then "Delete."
No! Any language's HTTP library will work. Just send a request to your
unique snitch URL. If you send a message in the request body, be sure to set
Content-Type: application/x-www-url-formencoded in the request
headers. Alternately, you can ignore the headers and put the message in the
URL query parameters:
For 15 and 30 minute snitches we keep ten days; for hourly snitches, fifteen days; for daily, a month; for weekly, six months; for monthly, two years.
We tried making everything in the user's timezone, but then it led to second-guessing what was going on. Since our audience is made up of developers and sysadmins and we are always thinking in different timezones, we decided to use UTC.
2017-02-23 20:59:12 UTC
Unless you check in super often, you shouldn't hit our rate limits. After the first 10 pings in an hour, snitches are limited to one hit per minute.
No, it checks to make sure your process hit the URL at least once each period (UTC). Technically, it could hit the URL at the beginning of one period and the end of the next and show success. We do it this way because things that are set to run every hour will not always finish in the exact same time and so you may get a lot of false failures.
Send us a direct message by clicking on the ? (when logged in) in the bottom right-hand corner of any Dead Man's Snitch page. We're always ready to help! Questions, comments or feedback? Email us at email@example.com.