Pagerduty, Inc.

John Gary Ryan Laban

Andrew Gregory Miklas

Ali Basiri

Ian Alexander Enders

Dan Alexandru Solomon

Paul James Rechsteiner

Kenneth Lloyd Patrick Rose

Owen Hee-chul Kim

Eric William Sigler

Daniel Morrison Byrd

Ashwin Maroti Jiwane

Embodiments are directed towards generating and managing schedules. In at least one of the various embodiments, these schedules may be configured to schedule team members, rotating which team member is active ('on-call'). In at least one of the various embodiments, these may be employed to determine which resource is responsible to respond and/or resolve incidents that may be reported and/or detected. In at least one of the various embodiments, if a team member is determined to be the on-call or responsible team member, the notification engine may determine the methods for notify the responsible of the incidents. Schedules previews may be updated in real-time as the schedule is edited.

Realtime schedule management interface

Embodiments are directed towards a notification message system arranged to generate notification messages. Responsible resources may be determined based on the notification messages and a schedule. A plurality of message providers that have a provider profiles may be determined based on the responsible resources and a region. A message provider from the plurality of message providers may be determined based on its provider profile. The notification messages may be provided to the message provider so they can be provided to the responsible resources. The provider profiles may be updated based on performance metrics associated with the message provider.

Robust routing and delivery of notifications

Embodiments are directed towards generating schedules for managing team members that may be responsible to be on-call for responding to incidents. Schedules may be configured to schedule team members and manage the rotation of one or more team members assigned to one or more schedule layers. Also, schedules may be employed to determine which team member may be responsible to respond and/or resolve incidents that may be reported and/or detected. If a team member is determined to be the on-call or responsible team member, a notification engine may determine the methods for notify the responsible of the incidents. Further, the notification engine may monitor whether the responsible team has received the notification. The notification engine may employ one or more other notification methods to ensure that the responsible team member may be notified.

Schedule management interface

Growing community of inventors

Toronto, Canada

John Gary Ryan Laban