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 to include a minimum of 3 locations must be provided, or an error message is returned. Not specifying this field will result in uptime checks running from all 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 CheckConfig.
Classes
ContentMatcher
Used to perform string matching. It allows substring and regular expressions, together with their negations.
HttpCheck
Information involved in an HTTP/HTTPS uptime check request.
The path to the page to run the check against. Will be combined with the host (specified within the MonitoredResource) and port to construct the full URL. Optional (defaults to "/").
The authentication information. Optional when creating an HTTP check; defaults to empty.
The list of headers to send as part of the uptime check request. If two headers have the same key and different values, they should be entered as a single header, with the value being a comma-separated list of all the desired values as described at https://www.w3.org/Protocols/rfc2616/rfc2616.txt (page 31). Entering two separate headers with the same key in a Create call will cause the first to be overwritten by the second. The maximum number of headers allowed is 100.
ResourceGroup
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.
TcpCheck
Information required for a TCP uptime check request.