GetUptimeCheckConfigResult

data class GetUptimeCheckConfigResult(val checkerType: String, val contentMatchers: List<ContentMatcherResponse>, val displayName: String, val httpCheck: HttpCheckResponse, val internalCheckers: List<InternalCheckerResponse>, val isInternal: Boolean, val monitoredResource: MonitoredResourceResponse, val name: String, val period: String, val resourceGroup: ResourceGroupResponse, val selectedRegions: List<String>, val tcpCheck: TcpCheckResponse, val timeout: String, val userLabels: Map<String, String>)

Constructors

Link copied to clipboard
fun GetUptimeCheckConfigResult(checkerType: String, contentMatchers: List<ContentMatcherResponse>, displayName: String, httpCheck: HttpCheckResponse, internalCheckers: List<InternalCheckerResponse>, isInternal: Boolean, monitoredResource: MonitoredResourceResponse, name: String, period: String, resourceGroup: ResourceGroupResponse, selectedRegions: List<String>, tcpCheck: TcpCheckResponse, timeout: String, userLabels: Map<String, String>)

Types

Link copied to clipboard
object Companion

Properties

Link copied to clipboard

The type of checkers to use to execute the Uptime check.

Link copied to clipboard

The content that is expected to appear in the data returned by the target server against which the check is run. Currently, only the first entry in the content_matchers list is supported, and additional entries will be ignored. This field is optional and should only be specified if a content match is required as part of the/ Uptime check.

Link copied to clipboard

A human-friendly name for the Uptime check configuration. The display name should be unique within a Cloud Monitoring Workspace in order to make it easier to identify; however, uniqueness is not enforced. Required.

Link copied to clipboard

Contains information needed to make an HTTP or HTTPS check.

Link copied to clipboard

The internal checkers that this check will egress from. If is_internal is true and this list is empty, the check will egress from all the InternalCheckers configured for the project that owns this UptimeCheckConfig.

Link copied to clipboard

If this is true, then checks are made only from the 'internal_checkers'. If it is false, then checks are made only from the 'selected_regions'. It is an error to provide 'selected_regions' when is_internal is true, or to provide 'internal_checkers' when is_internal is false.

Link copied to clipboard

The monitored resource (https://cloud.google.com/monitoring/api/resources) associated with the configuration. The following monitored resource types are valid for this field: uptime_url, gce_instance, gae_app, aws_ec2_instance, aws_elb_load_balancer k8s_service servicedirectory_service cloud_run_revision

Link copied to clipboard

A unique resource name for this Uptime check configuration. The format is: projects/PROJECT_ID_OR_NUMBER/uptimeCheckConfigs/PROJECT_ID_OR_NUMBER is the Workspace host project associated with the Uptime check.This field should be omitted when creating the Uptime check configuration; on create, the resource name is assigned by the server and included in the response.

Link copied to clipboard

How often, in seconds, the Uptime check is performed. Currently, the only supported values are 60s (1 minute), 300s (5 minutes), 600s (10 minutes), and 900s (15 minutes). Optional, defaults to 60s.

Link copied to clipboard

The group resource associated with the configuration.

Link copied to clipboard

The list of regions from which the check will be run. Some regions contain one location, and others contain more than one. If this field is specified, enough regions must be provided to include a minimum of 3 locations. Not specifying this field will result in Uptime checks running from all available regions.

Link copied to clipboard

Contains information needed to make a TCP check.

Link copied to clipboard

The maximum amount of time to wait for the request to complete (must be between 1 and 60 seconds). Required.

Link copied to clipboard

User-supplied key/value data to be used for organizing and identifying the UptimeCheckConfig objects.The field can contain up to 64 entries. Each key and value is limited to 63 Unicode characters or 128 bytes, whichever is smaller. Labels and values can contain only lowercase letters, numerals, underscores, and dashes. Keys must begin with a letter.