Skip to Content
Uptimeify Docs
Resources

uptimeify_im_service

A service of the Incident Management service catalog ("Webshop", "Customer portal") with its criticality, the responsible team and its monitors. An incident of a monitor that belongs to exactly one service is linked to that service. Needs an organization token of an organization admin. Import with the numeric id or the public id.

A service of the Incident Management service catalog ("Webshop", "Customer portal") with its criticality, the responsible team and its monitors. An incident of a monitor that belongs to exactly one service is linked to that service. Needs an organization token of an organization admin. Import with the numeric id or the public id.

Example Usage

resource "uptimeify_im_service" "webshop" {
  name          = "Webshop"
  description   = "Checkout and product pages."
  criticality   = "critical"
  owner_team_id = tonumber(uptimeify_im_team.platform.id)

  monitors = [
    { monitor_type = "website", monitor_id = tonumber(uptimeify_website.shop.id) },
    { monitor_type = "tcp", monitor_id = tonumber(uptimeify_tcp_monitor.db.id) },
  ]
}

Schema

Required

  • name (String) 1 to 200 characters, unique per organization regardless of case (409 imServiceNameTaken).

Optional

  • criticality (String) critical, high, medium (default) or low.
  • description (String) Up to 2000 characters.
  • monitors (Attributes Set) The monitors of this service, at most 500. Terraform owns the whole set; unset = none. Each must belong to the organization (404 imServiceMonitorNotFound). A monitor deleted later drops out of the service and shows up as a diff. (see below for nested schema)
  • owner_team_id (Number) Responsible team of the organization (404 imTeamNotFound). Deleting the team clears it.

Read-Only

  • created_at (String)
  • id (String) Numeric service id.
  • organization_id (Number)
  • public_id (String)
  • updated_at (String)

Nested Schema for monitors

Required:

  • monitor_id (Number) Numeric id of the monitor within its type, e.g. tonumber(uptimeify_website.shop.id).
  • monitor_type (String) website (also heartbeat and browser monitors), dns, icmp, smtp, ssh, tcp, ftp or imap_pop.

Import

Import is supported using the following syntax:

The terraform import command can be used, for example:

# Numeric service id or public id
terraform import uptimeify_im_service.webshop 12

On this page