Uptimeify Docs
Datenquellen

uptimeify_im_on_call

Datenquelle uptimeify_im_on_call: Beispiel, alle Attribute.

Die Beschreibungen auf dieser Seite kommen direkt aus dem Provider-Schema und sind deshalb englisch.

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

Beispiel

# 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]
}

Schema

Optional

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

Nur lesbar

  • entries (Attributes List) One entry per schedule with someone on call now (GET /api/im/on-call), after the filters. (siehe verschachteltes 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. (siehe verschachteltes Schema)

Verschachteltes Schema für entries

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.

Verschachteltes Schema für tiers

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) (siehe verschachteltes Schema)

Verschachteltes Schema für tiers.users

Read-Only:

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

Auf dieser Seite