Uptimeify Docs
Data Sources

uptimeify_tcp_monitor

Look up one TCP monitor by numeric id or public id. Secrets are never readable.

Look up one TCP monitor by numeric id or public id. Secrets are never readable.

Example Usage

data "uptimeify_tcp_monitor" "this" {
  id = "42"
}

Schema

Required

  • id (String) Numeric id or public id.

Read-Only

  • allowed_check_country_codes (Set of String) Upper-case ISO 3166-1 alpha-2 codes of the allowed check locations. Unset = all locations.
  • check_interval (Number) Minutes between checks, 1 to 1440. Defaults to 30. The customer's package can require a larger minimum.
  • created_at (String)
  • customer_id (Number) Customer the monitor belongs to. Changing it moves the monitor to another customer of the same organization in place.
  • expect_banner (String) Text the server's greeting must contain, at most 255 characters.
  • hostname (String) Host name or IP address only: no scheme, no path, no spaces.
  • management_type (String) managed or self_service. Only organization writers choose it; customer tokens always get self_service. Defaults to managed.
  • name (String) Display name, 1 to 255 characters.
  • organization_id (Number)
  • port (Number)
  • public_id (String) Public UUID of the TCP monitor.
  • status (String) active, maintenance or disabled. Defaults to active.
  • timeout_seconds (Number) Timeout per check in seconds, 1 to 60. Defaults to 30.
  • updated_at (String)

On this page