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.
Classes
ContentMatcher
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.
HttpCheck
Information involved in an HTTP/HTTPS Uptime check request.
Optional (defaults to "/"). The path to the page against which
to run the check. Will be combined with the host
(specified within the monitored_resource) and port to
construct the full URL. If the provided path does not begin
with "/", a "/" will be prepended automatically.
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.