---
title: "PagerDuty | Skills We Assign For | Azendo"
description: "PagerDuty for incident response — escalation, alert fatigue, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/pagerduty/"
---

[Skills](https://azendo.co/skills/) Observability 

# PagerDuty.

PagerDuty is an incident response platform handling on-call schedules, escalation policies, alert routing and deduplication, incident timelines and post-incident review data.

## Where PagerDuty fits on a long engagement.

The mechanics are straightforward; the discipline is not. What decides whether an on-call rotation is sustainable is the proportion of pages that are actionable. A rotation where most alerts are noise trains responders to dismiss them, and the one that mattered is dismissed along with the rest.

Tracking that ratio is the single most useful metric in incident response, and it is rarely measured. Teams measure mean time to resolve, which is a lagging outcome, rather than measuring how many pages should have fired at all.

## What an assigned team does with PagerDuty.

Distributed teams change on-call arithmetic. A team spread across time zones can cover more of the clock during working hours, which is materially different from one team carrying nights.

Our delivery sits five hours ahead of Northern Europe, which is part of why the working-hours overlap works the way it does — the reasoning is set out in [why we deliver from Thailand](https://azendo.co/why-thailand/).

## What we use PagerDuty for.

* Escalation that reaches someone Policies with real fallbacks, so an unacknowledged page does not simply stop.
* Alert noise measured and reduced Tracking what proportion of pages were actionable, which is the number that predicts burnout.
* Timelines for post-incident review An automatic record of what happened when, so review is analysis rather than recollection.

## How PagerDuty capacity is assigned.

On-call and incident response arrangements are agreed explicitly at scoping, including which hours are covered by whom, as part of [how the monthly fee is built](https://azendo.co/pricing/).

## Roles we assign PagerDuty for

* [Site Reliability Engineer Cloud and DevOps](https://azendo.co/services/cloud-and-devops/site-reliability-engineer/)

## Service lines it sits in

* [Cloud and DevOps](https://azendo.co/services/cloud-and-devops/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in observability

* [SLO and error budget design — skill we assign for](https://azendo.co/skills/slo-and-error-budget-design/)
* [Prometheus — skill we assign for](https://azendo.co/skills/prometheus/)
* [OpenTelemetry — skill we assign for](https://azendo.co/skills/opentelemetry/)
* [CloudWatch — skill we assign for](https://azendo.co/skills/cloudwatch/)
* [Observability — skill we assign for](https://azendo.co/skills/observability/)
* [Sentry — skill we assign for](https://azendo.co/skills/sentry/)
* [Logging — skill we assign for](https://azendo.co/skills/logging/)
* [audit logging — skill we assign for](https://azendo.co/skills/audit-logging/)

## Tell us what your roadmap needs PagerDuty for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)