PagerDuty integration: page the right team when tests fail

Qualflare now integrates with PagerDuty. When a launch fails or a serious defect is reported, Qualflare opens an incident on the right PagerDuty service, and closes it again when the problem clears.

What's new

• Installed from PagerDuty. Connect through PagerDuty's own app install instead of pasting a routing key, and choose the services Qualflare may page.
• Different services per project. One install can cover several PagerDuty services, and each project rule chooses which one to page, so each team gets its own alerts.
• Severity that makes sense. Leave severity on Automatic and Qualflare decides:
  • defects use the defect's priority
  • failed launches are tiered by how much broke
  • failure clusters are warnings
  • recoveries are informational, which never pages
• Incidents that resolve themselves. Defect Resolved and Launch Completed close the incident opened by their failing counterpart. Launch incidents are tracked per project and branch.
• Pick your events. Choose from Defect Created, Defect Resolved, Launch Completed, Launch Failed, Cluster Created and Milestone Completed.

How to connect it

A workspace admin installs PagerDuty under Workspace → Integrations. Each project then adds a rule under Project → Integrations → PagerDuty. Select events in pairs, such as Launch Failed with Launch Completed, so incidents close automatically.