- NAME
-
- gcloud alpha compute http-health-checks create - create an HTTP legacy health check to monitor load balanced instances
- SYNOPSIS
-
-
gcloud alpha compute http-health-checks createNAME[ --check-interval=CHECK_INTERVAL; default="5s"][ --description=DESCRIPTION][ --healthy-threshold=HEALTHY_THRESHOLD; default=2][ --host=HOST][ --port=PORT; default=80][ --request-path=REQUEST_PATH; default="/"][ --timeout=TIMEOUT; default="5s"][ --unhealthy-threshold=UNHEALTHY_THRESHOLD; default=2][ GCLOUD_WIDE_FLAG …]
-
- DESCRIPTION
-
(ALPHA)gcloud alpha compute http-health-checks createis used to create a legacy health check with a health check type of HTTP. HTTP health checks monitor instances in a load balancer controlled by a target pool. All arguments to the command are optional except for the name of the health check. For more information on load balancing, see https://cloud.google.com/compute/docs/load-balancing-and-autoscaling/. Note, creating a legacy health check is recommended only for a network load balancer. - POSITIONAL ARGUMENTS
-
NAME- Name of the HTTP health check to create.
- FLAGS
-
--check-interval=CHECK_INTERVAL; default="5s"-
How often to perform a health check for an instance. For example, specifying
will run the check every 10 seconds. The default value is10s. See $ gcloud topic datetimes for information on duration formats.5s --description=DESCRIPTION- An optional, textual description for the HTTP health check.
--healthy-threshold=HEALTHY_THRESHOLD; default=2- The number of consecutive successful health checks before an unhealthy instance is marked as healthy. The default is 2.
--host=HOST- The value of the host header used in this HTTP health check request. By default, this is empty and Google Compute Engine automatically sets the host header in health requests to the same external IP address as the forwarding rule associated with the target pool.
--port=PORT; default=80- The TCP port number that this health check monitors. The default value is 80.
--request-path=REQUEST_PATH; default="/"-
The request path that this health check monitors. For example,
. The default value is ``/´´./healthcheck --timeout=TIMEOUT; default="5s"-
If Google Compute Engine doesn't receive an HTTP 200 response from the instance
by the time specified by the value of this flag, the health check request is
considered a failure. For example, specifying
will cause the check to wait for 10 seconds before considering the request a failure. The default value is10s. See $ gcloud topic datetimes for information on duration formats.5s --unhealthy-threshold=UNHEALTHY_THRESHOLD; default=2- The number of consecutive health check failures before a healthy instance is marked as unhealthy. The default is 2.
- GCLOUD WIDE FLAGS
-
These flags are available to all commands: --account, --billing-project, --configuration, --flags-file, --flatten, --format, --help, --impersonate-service-account,
--log-http, --project, --quiet, --trace-token, --user-output-enabled,
--verbosity.
Run
$ gcloud helpfor details. - NOTES
-
This command is currently in ALPHA and may change without notice. If this
command fails with API permission errors despite specifying the right project,
you may be trying to access an API with an invitation-only early access
whitelist. These variants are also available:
$ gcloud compute http-health-checks create $ gcloud beta compute http-health-checks create
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2020-02-04.


