gcloud beta compute http-health-checks create Stay organized with collections Save and categorize content based on your preferences.
- NAME
- gcloud beta compute http-health-checks create - create a legacy HTTP health check
- SYNOPSIS
gcloud beta 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
(BETA)Legacy HTTP health checks are required if you want toimplement health checking for a target pool backend of an external passthroughNetwork Load Balancer. Though you can use legacy HTTP health checks in certainother Google Cloud Platform load balancing configurations and for managedinstance group autohealing, you should consider a non-legacy HTTP health checkcreated withhealth-checks create httpinstead.For more information about the differences between legacy and non-legacy healthchecks see:https://cloud.google.com/load-balancing/docs/health-check-concepts#category_and_protocol
For information about what type of health check to use for a particular loadbalancer, see:https://cloud.google.com/load-balancing/docs/health-check-concepts#lb_guide
- 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 forinformation 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 instanceis 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 Compute Engine automatically sets the host header in healthrequests to the same external IP address as the forwarding rule associated withthe 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 Compute Engine doesn't receive an HTTP 200 response from the instance by thetime specified by the value of this flag, the health check request is considereda failure. For example, specifying
willcause the check to wait for 10 seconds before considering the request a failure.The default value is10s. See $gcloud topic datetimes forinformation on duration formats.5s --unhealthy-threshold=UNHEALTHY_THRESHOLD; default=2- The number of consecutive health check failures before a healthy instance ismarked as unhealthy. The default is 2.
- GCLOUD WIDE FLAGS
- These flags are available to all commands:
--access-token-file,--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 beta and might change without notice. Thesevariants are also available:
gcloudcomputehttp-health-checkscreategcloudalphacomputehttp-health-checkscreate
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-05-07 UTC.