Skip Navigation
Show nav
Dev Center
  • Get Started
  • Documentation
  • Changelog
  • Search
  • Get Started
    • Node.js
    • Ruby on Rails
    • Ruby
    • Python
    • Java
    • PHP
    • Go
    • Scala
    • Clojure
    • .NET
  • Documentation
  • Changelog
  • More
    Additional Resources
    • Home
    • Elements
    • Products
    • Pricing
    • Careers
    • Help
    • Status
    • Events
    • Podcasts
    • Compliance Center
    Heroku Blog

    Heroku Blog

    Find out what's new with Heroku on our blog.

    Visit Blog
  • Log inorSign up
View categories

Categories

  • Heroku Architecture
    • Compute (Dynos)
      • Dyno Management
      • Dyno Concepts
      • Dyno Behavior
      • Dyno Reference
      • Dyno Troubleshooting
    • Stacks (operating system images)
    • Networking & DNS
    • Platform Policies
    • Platform Principles
  • Developer Tools
    • Command Line
    • Heroku VS Code Extension
  • Deployment
    • Deploying with Git
    • Deploying with Docker
    • Deployment Integrations
  • Continuous Delivery & Integration (Heroku Flow)
    • Continuous Integration
  • Language Support
    • Node.js
      • Working with Node.js
      • Node.js Behavior in Heroku
      • Troubleshooting Node.js Apps
    • Ruby
      • Rails Support
      • Working with Bundler
      • Working with Ruby
      • Ruby Behavior in Heroku
      • Troubleshooting Ruby Apps
    • Python
      • Working with Python
      • Background Jobs in Python
      • Python Behavior in Heroku
      • Working with Django
    • Java
      • Java Behavior in Heroku
      • Working with Java
      • Working with Maven
      • Working with Spring Boot
      • Troubleshooting Java Apps
    • PHP
      • PHP Behavior in Heroku
      • Working with PHP
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
    • .NET
      • Working with .NET
  • Databases & Data Management
    • Heroku Postgres
      • Postgres Basics
      • Postgres Getting Started
      • Postgres Performance
      • Postgres Data Transfer & Preservation
      • Postgres Availability
      • Postgres Special Topics
      • Migrating to Heroku Postgres
    • Heroku Key-Value Store
    • Apache Kafka on Heroku
    • Other Data Stores
  • AI
    • Working with AI
    • Heroku Inference
      • Inference API
      • Quick Start Guides
      • AI Models
      • Inference Essentials
    • Vector Database
    • Model Context Protocol
  • Monitoring & Metrics
    • Logging
  • App Performance
  • Add-ons
    • All Add-ons
  • Collaboration
  • Security
    • App Security
    • Identities & Authentication
      • Single Sign-on (SSO)
    • Private Spaces
      • Infrastructure Networking
    • Compliance
  • Heroku Enterprise
    • Enterprise Accounts
    • Enterprise Teams
    • Heroku Connect (Salesforce sync)
      • Heroku Connect Administration
      • Heroku Connect Reference
      • Heroku Connect Troubleshooting
  • Patterns & Best Practices
  • Extending Heroku
    • Platform API
    • App Webhooks
    • Heroku Labs
    • Building Add-ons
      • Add-on Development Tasks
      • Add-on APIs
      • Add-on Guidelines & Requirements
    • Building CLI Plugins
    • Developing Buildpacks
    • Dev Center
  • Accounts & Billing
  • Troubleshooting & Support
  • Integrating with Salesforce
  • Add-ons
  • All Add-ons
  • Dead Man's Snitch
Dead Man's Snitch

This add-on is operated by Dead Man's Snitch, LLC

Dead simple monitoring for Heroku Scheduler, cron jobs, or any periodic process

Dead Man's Snitch

Last updated January 01, 2025

Table of Contents

  • Provisioning the add-on
  • Using with Heroku Scheduler
  • Using inside your code
  • Dashboard
  • Troubleshooting
  • Migrating between plans
  • Removing the add-on
  • Support

Dead Man’s Snitch is an add-on for monitoring your periodic processes such as Heroku Scheduler or cron jobs.

Ever have a periodic process fail to run? Make a code change and your nightly backups fail? Weekly emails not send and you don’t notice until a customer complains? Dead Man’s Snitch has you covered.

We’ll notify you when your processes don’t run, allowing you to react quickly to correct the problem.

Dead Man’s Snitch makes monitoring periodic processes dead simple.

Provisioning the add-on

Dead Man’s Snitch can be attached to a Heroku application via the CLI:

A list of all plans available can be found here.

$ heroku addons:create deadmanssnitch
-----> Adding deadmanssnitch to collective-idea-4005... done, v18 (free)

Once Dead Man’s Snitch has been added a DEADMANSSNITCH_API_KEY setting will be available in the app configuration and will contain your API key if you would like to access Dead Man’s Snitch programatically. Your installation can be confirmed with the heroku config:get command.

$ heroku config:get DEADMANSSNITCH_API_KEY
vq7hfm8uxPcWl-kqcu_ITQ

After installing Dead Man’s Snitch open the dashboard to configure monitoring for your processes.

$ heroku addons:open deadmanssnitch

Using with Heroku Scheduler

These examples use pgbackups-archive for saving off-site backups. Read more about it in this blog post.

Integrating into Heroku Scheduler is simple. For each Snitch you create, curl the unique URL (replacing the URL in these examples with your own) after each task:

rake pgbackups:archive && curl https://nosnch.in/208cd43444

You can pass custom data to your Snitch

rake pgbackups:archive && curl -d "m=just checking in" https://nosnch.in/208cd43444

You can even time your jobs and pass the result to your snitch:

m=`time ( rake pgbackups:archive &> /dev/null) 2>&1` && curl -d "m=$m" https://nosnch.in/208cd43444

Using inside your code

You can use Dead Man’s Snitch from any language that can fetch a URL.

In Ruby, a simple example is:

require 'open-uri'

response = open("https://nosnch.in/208cd43444")

Put it after some complex code, and Dead Man’s Snitch will alert you if it fails to run.

URLs will return a 2xx HTTP status code.

Dashboard

For more information on the features available within the Dead Man’s Snitch dashboard please see the docs at deadmanssnitch.com/faq.

The Dead Man’s Snitch dashboard allows you to configure Snitches to monitor your processes. Each Snitch gives you a unique URL and notification settings.

The dashboard can be accessed via the CLI:

$ heroku addons:open deadmanssnitch
Opening deadmanssnitch for collective-idea-4005…

or by visiting the Heroku Dashboard and selecting the application in question. Select Dead Man’s Snitch from the Add-ons menu.

Troubleshooting

The most common issues is grabbing the wrong URL for a Snitch. Double-check that you copy it correctly.

In most setups, Dead Man’s Snitch won’t get notified if the process it is monitoring fails. Make sure your process is actually working and exiting properly.

Migrating between plans

Use the heroku addons:upgrade command to migrate to a new plan.

$ heroku addons:upgrade deadmanssnitch:newplan
-----> Upgrading deadmanssnitch:newplan to collective-idea-4005... done, v18 ($19/mo)
       Your plan has been updated to: deadmanssnitch:newplan

Removing the add-on

Dead Man’s Snitch can be removed via the CLI.

This will destroy all associated data and cannot be undone!

$ heroku addons:destroy deadmanssnitch
-----> Removing deadmanssnitch from collective-idea-4005... done, v20 (free)

Support

All Dead Man’s Snitch support and runtime issues should be submitted via one of the Heroku Support channels. Any non-support related issues or product feedback is welcome at via email to hi@deadmanssnitch.com.

Keep reading

  • All Add-ons

Feedback

Log in to submit feedback.

Zara 4 DeDup

Information & Support

  • Getting Started
  • Documentation
  • Changelog
  • Compliance Center
  • Training & Education
  • Blog
  • Support Channels
  • Status

Language Reference

  • Node.js
  • Ruby
  • Java
  • PHP
  • Python
  • Go
  • Scala
  • Clojure
  • .NET

Other Resources

  • Careers
  • Elements
  • Products
  • Pricing
  • RSS
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku Blog
    • Heroku News Blog
    • Heroku Engineering Blog
  • Twitter
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku
    • Heroku Status
  • Github
  • LinkedIn
  • © 2025 Salesforce, Inc. All rights reserved. Various trademarks held by their respective owners. Salesforce Tower, 415 Mission Street, 3rd Floor, San Francisco, CA 94105, United States
  • heroku.com
  • Legal
  • Terms of Service
  • Privacy Information
  • Responsible Disclosure
  • Trust
  • Contact
  • Cookie Preferences
  • Your Privacy Choices