uptimeify_im_on_call

Who is on call right now (read at plan time, so it changes between runs). Incident Management must be active for the organization.

Example UsageCopy Anchor Link

# Who holds the pager of team 7 right now, per escalation tier.
data "uptimeify_im_on_call" "platform" {
  team_id = 7
}

output "first_tier_on_call" {
  value = [for u in data.uptimeify_im_on_call.platform.tiers[0].users : u.user_name]
}

SchemaCopy Anchor Link

OptionalCopy Anchor Link

• schedule_id (Number) Only this schedule.
• team_id (Number) Only this team; also fills tiers.

Read-OnlyCopy Anchor Link

• entries (Attributes List) One entry per schedule with someone on call now (GET /api/im/on-call), after the filters. (see below for nested schema)
• tiers (Attributes List) With team_id: one entry per escalation tier of the team with everyone on call now (GET /api/im/teams/{id}/on-call-now), overrides applied. Null without team_id. (see below for nested schema)

Nested Schema for entriesCopy Anchor Link

Read-Only:

• schedule_id (Number)
• shift_ends_at (String) End of the current shift (RFC 3339).
• team_id (Number)
• user_id (String) User id.
• user_image (String) Avatar URL, may be null.
• user_name (String) Display name, may be null.

Nested Schema for tiersCopy Anchor Link

Read-Only:

• tier_id (Number)
• tier_order (Number)
• uncovered_since (String) Since when nobody covers the tier; null when covered or not within 14 days.
• users (Attributes List) (see below for nested schema)

Nested Schema for tiers.usersCopy Anchor Link

Read-Only:

• user_id (String) User id.
• user_image (String) Avatar URL, may be null.
• user_name (String) Display name, may be null.