Uptimeify Docs
Resources

uptimeify_monitor_tag

Puts one tag on one monitor. A monitor carries at most 5 tags. Import with <monitor_type>/<monitor_id>/<tag_id>.

Puts one tag on one monitor. A monitor carries at most 5 tags. Import with <monitor_type>/<monitor_id>/<tag_id>.

Example Usage

resource "uptimeify_monitor_tag" "shop_production" {
  monitor_type = "website"
  monitor_id   = 12
  tag_id       = tonumber(uptimeify_tag.production.id)
}

Schema

Required

  • monitor_id (Number) Numeric id of the monitor.
  • monitor_type (String) One of website, dns, icmp, smtp, ssh, tcp, ftp, imap_pop, customer_domain, customer_ip.
  • tag_id (Number) Numeric tag id.

Read-Only

  • id (String) <monitor_type>/<monitor_id>/<tag_id>.

Import

Import is supported using the following syntax:

The terraform import command can be used, for example:

# <monitor_type>/<monitor_id>/<tag_id>
terraform import uptimeify_monitor_tag.shop_production website/12/34

uptimeify_maintenance_window

A maintenance window: alerts and incidents of its targets are suppressed while it runs. Set targets and/or tag_ids, or customer_id alone for the whole customer. A window with only organization-wide tags applies organization-wide. Import with the numeric id or the public id.

uptimeify_notification_channel

A notification channel of the organization, or of one customer with customer_id. Secrets live in secret_config_wo and never enter the state. An active channel to the same recipient cannot exist twice (409). Website overrides are not managed here. Import with the numeric id.

On this page

Example UsageSchemaRequiredRead-OnlyImport