Services

What are Pagerduty services

As per Pagerduty:

A technical service reflects a discrete piece of functionality that is wholly owned by one team. One or more technical services combine to deliver customer-facing or business capabilities.

Services interact with /chatops oncall commands to display who is currently on-call in Slack.

Current services used by support

Customer Support

• Service link
• Escalation policy: Customer Emergency Rotation
• Integrations
  • Zendesk
  • API
  • Customer Emergency Escalation Channel
• Extensions and Add-Ons
  • Slack V2

Incident Management - CMOC

• Service link
• Escalation policy: Incident Management - CMOC Rotation
• Integrations
  • Slack to PagerDuty
  • Pingdom to CMOC
  • woodhouse
• Extensions and Add-Ons
  • Slack V2

Support Managers

• Service link
• Escalation policy: Support Managers
• Integrations
  • Slack
• Extensions and Add-Ons
  • Slack V2

AMER Response Crew

• Service link
• Escalation policy: Support Managers
• Integrations
  • Email
• Extensions and Add-Ons
  • Slack V2

Customer Support - US Federal

• Service link
• Escalation policy: US Federal Customer Emergency Rotation
• Integrations
  • N/A
• Extensions and Add-Ons
  • N/A

Change management

As the Pagerduty changes are unique in deployment, please see Pagerduty change management for more information.

Labels to use

For all issues and MRs involving Pagerduty fields, the label Support-Ops-Category::Pagerduty should be used.

Change criticality

Due to wildly varying nature and impact adding/editing/deleting things in Pagerduty can impose, all issues/MRs related to Pagerduty need to have the their criticality manually determined