The response to a Health Check probe had the HTTP response header field X-Load-Balancing-Endpoint-Weight, but its content was invalid (i.e., not a non-negative single-precision floating-point number in decimal string representation).
MissingWeight
The response to a Health Check probe did not have the HTTP response header field X-Load-Balancing-Endpoint-Weight.
UnavailableWeight
This is the value when the accompanied health status is either TIMEOUT (i.e.,the Health Check probe was not able to get a response in time) or UNKNOWN. For the latter, it should be typically because there has not been sufficient time to parse and report the weight for a new backend (which is with 0.0.0.0 ip address). However, it can be also due to an outage case for which the health status is explicitly reset to UNKNOWN.
UndefinedWeightError
A value indicating that the enum field is not set.
WeightNone
This is the default value when WeightReportMode is DISABLE, and is also the initial value when WeightReportMode has just updated to ENABLE or DRY_RUN and there has not been sufficient time to parse and report the backend weight.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-08 UTC."],[[["\u003cp\u003eThis page details the \u003ccode\u003eWeightError\u003c/code\u003e enum within the \u003ccode\u003eGoogle.Cloud.Compute.V1\u003c/code\u003e namespace, specifically focusing on its different error states related to health check probes and their responses.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eWeightError\u003c/code\u003e enum is used to represent various issues encountered when assessing the weight of an endpoint, such as \u003ccode\u003eInvalidWeight\u003c/code\u003e, \u003ccode\u003eMissingWeight\u003c/code\u003e, \u003ccode\u003eUnavailableWeight\u003c/code\u003e, \u003ccode\u003eUndefinedWeightError\u003c/code\u003e, and \u003ccode\u003eWeightNone\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eHealthStatus.Types.WeightError\u003c/code\u003e class has had numerous updates, as evidenced by the range of documented versions spanning from 1.0.0 to the latest 3.6.0, each accessible via a unique URL.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eWeightError\u003c/code\u003e field descriptions clarify that the \u003ccode\u003eInvalidWeight\u003c/code\u003e error means that the server sent an incorrect weight, the \u003ccode\u003eMissingWeight\u003c/code\u003e error means that the server didn't send a weight at all, and the \u003ccode\u003eUnavailableWeight\u003c/code\u003e means that the weight wasn't available due to timeout or an unknown state.\u003c/p\u003e\n"],["\u003cp\u003eThe most up to date and most recent version available for the \u003ccode\u003eWeightError\u003c/code\u003e class is 3.6.0, followed by 3.5.0 and then 3.4.0, with many previous versions available for review.\u003c/p\u003e\n"]]],[],null,[]]
