PagerDuty Weekly Reliability Report

Overview

This flow produces a weekly reliability report from PagerDuty. Every Monday at 08:00 UTC it pulls the incident list, slices it into the current reporting window and the prior window, and computes per-service and overall metrics: total incidents, mean time to acknowledge (MTTA), mean time to resolve (MTTR), and after-hours pages. It builds a branded HTML report with a per-service week-over-week breakdown table, emails it to engineering leadership, and posts highlights to a Teams channel. Services whose incident count rose by at least a configurable threshold are flagged as trending worse.

Why it matters: Reliability improves when teams can see the patterns. A consistent, zero-effort weekly readout drives alert tuning, surfaces noisy services, and anchors reliability conversations - without anyone assembling the numbers by hand. State: Off (demo).

Use Case

An SRE / engineering org wants a weekly, no-effort summary of incident load and response performance by service, with week-over-week trend flags, delivered to leadership by email and to the team's Teams channel. The flow is connector-first and ships Off; going live requires only authorizing the connections and setting the environment-variable values.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
PagerDuty	shared_pagerduty	GetIncidents
Office 365 Outlook	shared_office365	SendEmailV2
Microsoft Teams	shared_teams	PostMessageToConversation

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Reporting window

Change flowlibs_ReliabilityLookbackDays for a fortnightly or monthly cadence (also adjust the Recurrence interval).

After-hours definition

Adjust flowlibs_AfterHoursStartHour / EndHour (UTC) to match the team's business hours.

Trend sensitivity

Raise/lower flowlibs_WoWAlertThresholdPct to flag more or fewer worsening services.

Per-team reports

Duplicate the flow and filter incidents by escalation policy or team to send targeted versions.

Richer MTTA

For sub-acknowledgement timing detail, follow each incident with GetIncidentNotes or the PagerDuty REST log_entries endpoint.

Power BI

Pair with the PagerDuty-metrics-to-Power-BI flow to back the email with a live dashboard.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@and(greaterOrEquals(ticks(item()?['created_at']), ticks(variables('varWindowStart'))), less(ticks(item()?['created_at']), ticks(variables('varWindowEnd'))))

@div(sub(ticks(coalesce(item()?['last_status_change_at'], item()?['created_at'])), ticks(item()?['created_at'])), 600000000)

@div(sub(ticks(first(item()?['acknowledgements'])?['at']), ticks(item()?['created_at'])), 600000000)

@or(greaterOrEquals(int(formatDateTime(item()?['created_at'],'HH')), variables('varAfterHoursStart')), less(int(formatDateTime(item()?['created_at'],'HH')), variables('varAfterHoursEnd')))

@if(greater(outputs('Compose_Service_Last_Count'),0), div(mul(sub(outputs('Compose_Service_This_Count'),outputs('Compose_Service_Last_Count')),100), outputs('Compose_Service_Last_Count')), if(greater(outputs('Compose_Service_This_Count'),0),100,0))

Customize & download