Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Heroku app that fires webhooks for triggered PagerDuty incidents
Branch: master
Pull request Compare This branch is 4 commits behind github-archive:master.

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
bin
lib
spec
.gitignore
Gemfile
Gemfile.lock
LICENSE
Procfile
README.md
Rakefile

README.md

PagerDuty Incident Webhooks

This fires a webhook of incident data for each triggered incident PagerDuty in your account. Ideally, you'd point this at another tiny app that processes the events and does your bidding with them - ships them to campfire, APN, a tiny sinatra app that pipes incidents to say...go nuts.

Re-triggered incidents will cause an additional webhook to be sent for the same incident. Make sure your endpoint is okay with this.

I hate to poll like this, but whatever. It works.

Running on Heroku

Clone this repo.

In the clone:

heroku create --stack cedar yourname-pagerduty-incident-webhooks --addons memcache heroku papertrail:test

Set the following config at heroku:

heroku config:add PAGERDUTY_ACCOUNT_SUBDOMAIN=foo
heroku config:add PAGERDUTY_AUTH_EMAIL=foo@foo.com
heroku config:add PAGERDUTY_AUTH_PASSWORD=foo
heroku config:add PAGERDUTY_WEBHOOK_ENDPOINT=http://requestb.in/1e88aqp1
heroku config:add POLL_INTERVAL=10

Ship it:

git push heroku master

Fire up a web process:

heroku scale web=1

Hit up papertrail and check on the logs.

Credit where Credit is Due

Large parts of this are based on the PagerDuty library @leejones wrote for pager_today.

Copying

Copyright 2012, GitHub, Inc. See the LICENSE file for license rights and limitations (MIT).

Something went wrong with that request. Please try again.