View all bundles

pagerduty 0.0.4

Interact with pagerduty

Install

In chat:

@cog bundle install pagerduty 0.0.4

From the command line:

cogctl bundle install pagerduty 0.0.4

All Versions


Description

The pagerduty bundle can be configured with a few env vars. All commands require PAGERDUTY_ACCOUNT_SUBDOMAIN and PAGERDUTY_ACCOUNT_TOKEN to be set. That would be the subdomain for your PagerDuty account and the V1 API token respectively.

The alert command has an optional var, PAGERDUTY_DEFAULT_SERVICE_KEY. This is the integration key found on the integration tab for the service on PagerDuty's web UI. If set, any alerts that don't specify a service will be sent here. Note that if the service key is not set or a service isn't passed to the command, it will fail.

Commands ack and resolve have a couple extra vars. PAGERDUTY_DEFAULT_EMAIL, similar to PAGERDUTY_DEFAULT_SERVICE_KEY, will be used as the requester when acking or resolving incidents. Additionally, you may attach the requester to cog accounts. Using vars in the form, PAGERDUTY_EMAIL_FOR_<COG_USER> you can specify which PagerDuty email is associated with which Cog user. So for example, if your Cog username is 'bob', you would set the var PAGERDUTY_EMAIL_FOR_BOB. Then whenever you ack or resolve the proper PagerDuty account is associated with the action.

Commands

ack
Acknowledge incidents
alert
Trigger alerts
incidents
List incidents
oncall
Find out who is on-call for all services, or for a specific service
resolve
Resolve incidents

Homepage

https://github.com/cogcmd/pagerduty

Author

Matthew Peck matt@operable.io

Owner

@operable