Uptimeify Docs
Datenquellen

uptimeify_im_routing_rule

Datenquelle uptimeify_im_routing_rule: Beispiel, alle Attribute.

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

Read one Incident Management routing rule by id.

Beispiel

data "uptimeify_im_routing_rule" "db" {
  id = "17"
}

Schema

Pflichtfelder

  • id (String) Numeric rule id.

Nur lesbar

  • created_at (String)
  • match (Attributes) What the rule matches; all set fields must match. Unset or {} = catch-all. All ids must belong to the organization. (siehe verschachteltes Schema)
  • organization_id (Number)
  • priority (Number) Lower runs first. Default 100.
  • severity_override (String) Unset = keep the mapped severity.
  • team_id (Number) The team that receives matching incidents.
  • updated_at (String)

Verschachteltes Schema für match

Read-Only:

  • customer_ids (List of Number) Customer ids. At most 500.
  • field_matches (Map of String) Payload field -> expected value, at most 50 entries.
  • monitor_ids (List of Number) Ids of any monitor type (website, DNS, ICMP, ...). At most 500.
  • severity (List of String) sev1 to sev4.
  • source_ids (List of Number) Alert source ids. At most 500.
  • tags (List of String) Alert tags. At most 200.

Auf dieser Seite