Add lita-pagerduty to your Lita instance's Gemfile:
gem "lita-pagerduty"Create a PagerDuty API key (v2). You will need to give it FullAccess to update incidents.
Add the following variables to your Lita config file:
config.handlers.pagerduty.api_key = ''
config.handlers.pagerduty.email = ''If your account has the teams capability and you want to scope Lita's access to a specific set of teams, you can set the list of teams by adding the following to your config file:
config..handlers.pagerduty.teams = [ "team-a", "team-b" ]pager identify <email address> - Associate your chat user with your email address
pager forget - Remove your chat user / email association
pager incidents all - Show all open incidents
pager incidents mine - Show all open incidents assigned to me
pager incident <incident ID> - Show a specific incident
pager notes <incident ID> - Show all notes for a specific incident
pager ack all - Acknowledge all triggered incidents
pager ack mine - Acknowledge all triggered incidents assigned to me
pager ack <incident ID> - Acknowledge a specific incident
pager resolve all - Resolve all triggered incidents
pager resolve mine - Resolve all triggered incidents assigned to me
pager resolve <incident ID> - Resolve a specific incident
pager oncall - List available schedules
pager oncall <schedule> - Show who is on call for the given schedule
pager base - List available schedules (uses the same call as `oncall` above.)
pager base <schedule> - Show the base layer of a schedule. This is useful if your schedule has a foundation rotation (eg weekly), with layers on top.