[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-03-12 UTC。"],[[["This content outlines health check methods for Apigee and Apigee hybrid, covering regional-level, environment-level, and custom proxy-based checks."],["Regional-level health checks assess the overall Apigee instance health within a region using the `/healthz/ingress` path and the `User-Agent: GoogleHC` header, returning `\"Apigee Ingress is healthy\"` if successful."],["Environment-level health checks verify the status of a specific environment by prepending `/healthz/` to a valid proxy basepath (e.g., `/catalog`) and using the `User-Agent: GoogleHC` header, with a `\"Server Ready\"` response indicating a healthy environment."],["Custom health checks allow for advanced validations through a dedicated API proxy, enabling checks based on factors like multiple environment status or target latency, but do not require the `User-Agent` header."],["The health check feature is available for Apigee hybrid versions 1.4 and higher, and if the health checks are made by Google Cloud load balancers then the correct user-agent header is set for you."]]],[]]