PagerDuty Elixir v0.0.1 PagerDuty.EscalationPolicy

Escalation policies make sure the right people are alerted at the right time.

An escalation policy determines what user or schedule will be notified first, second, and so on when an incident is triggered.

Escalation policies are used by one or more service.

Escalation Rules

An escalation policy is made up of multiple escalation rules.

Each escalation rule represents a level of on-call duty.

It specifies one or more user or schedule to be notified when an unacknowledged incident reaches that escalation rule.

The first escalation rule in the escalation policy is the user that will be notified first about the triggered incident.

If no on-call user for a given escalation rule has acknowledged an incident before the escalation rule’s escalation delay has elapsed, the incident escalates to the next escalation rule.

Attributes

@id: id
@summary: A short-form, server-generated string that provides succinct, important information about an object suitable for primary labeling of an entity in a client. In many cases, this will be identical to name, though it is not intended to be an identifier.
@type: either incident or incident_reference
@self: the API show URL at which the object is accessible
@html_url: a URL at which the entity is uniquely displayed in the Web app
@name: The name of the escalation policy.
@description: Escalation policy description.
@num_loops: The number of times the escalation policy will repeat after reaching the end of its escalation. (defaults to 0) (minimum of 0)
@repeat_enabled: Whether or not to allow this policy to repeat its escalation rules after the last rule is finished.
@escalation_rules:
@services: (minLength 0)
@teams: Teams associated with the policy. Account must have the teams ability to use this parameter. (minLength 0)

Summary

Types

t()

Types

t()

t() :: %PagerDuty.EscalationPolicy{description: String.t, escalation_rules: list, html_url: String.t, id: String.t, name: String.t, num_loops: integer, repeat_enabled: boolean, self: String.t, services: list, summary: String.t, teams: list, type: String.t}