Class UptimeCheckConfig (1.1.2)

This message configures which resources and services to monitor for availability.

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

The monitored resource <https://cloud.google.com/monitoring/api/resources>__ associated with the configuration. The following monitored resource types are supported for Uptime checks: uptime_url, gce_instance, gae_app, aws_ec2_instance, aws_elb_load_balancer

The type of Uptime check request.

Contains information needed to make a TCP check.

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

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.

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.

Optional. Used to perform content matching. This allows matching based on substrings and regular expressions, together with their negations. Only the first 4 MB of an HTTP or HTTPS check’s response (and the first 1 MB of a TCP check’s response) are examined for purposes of content matching.

The type of content matcher that will be applied to the server output, compared to the content string when the check is run.

Information involved in an HTTP/HTTPS Uptime check request.

If true, use HTTPS instead of HTTP to run the check.

Optional (defaults to 80 when use_ssl is false, and 443 when use_ssl is true). The TCP port on the HTTP server against which to run the check. Will be combined with host (specified within the monitored_resource) and path to construct the full URL.

Boolean specifiying whether to encrypt the header information. Encryption should be specified for any headers related to authentication that you do not wish to be seen when retrieving the configuration. The server will be responsible for encrypting the headers. On Get/List calls, if mask_headers is set to true then the headers will be obscured with ******.

The content type to use for the check.

The request body associated with the HTTP request. If content_type is URL_ENCODED, the body passed in must be URL-encoded. Users can provide a Content-Length header via the headers field or the API will do so. The maximum byte size is 1 megabyte. Note: As with all bytes fields JSON representations are base64 encoded.

The resource submessage for group checks. It can be used instead of a monitored resource, when multiple resources are being monitored.

The resource type of the group members.

Information required for a TCP Uptime check request.