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 (409imServiceNameTaken).
Optional
criticality(String)critical,high,medium(default) orlow.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 (404imServiceMonitorNotFound). 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 (404imTeamNotFound). 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,ftporimap_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 12uptimeify_im_schedule_override
An override (vacation, swap) on an on-call schedule. Import with <schedule_id>/<override_id>.
uptimeify_im_statuspage_rule
An Incident Management status page rule: incidents of team_id at min_severity or worse set the status page to target_state. Needs team-admin rights on the team (or organization admin). Manual overrides (POST /api/im/statuspage-rules/override) are an incident-time action and not managed by Terraform. Import with the numeric id.