[[["容易理解","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-09-04 (世界標準時間)。"],[[["\u003cp\u003eThis page provides guidance on accessing health status dashboards within Google Distributed Cloud (GDC) air-gapped appliance infrastructure to monitor component health.\u003c/p\u003e\n"],["\u003cp\u003eGDC monitors both hardware (server nodes) and software (clusters, VMs, storage) components, and the dashboards visualize their respective health metrics.\u003c/p\u003e\n"],["\u003cp\u003eAccessing the health status dashboards requires role-based access controls, as detailed in the linked "Before you begin" section.\u003c/p\u003e\n"],["\u003cp\u003eThe Grafana endpoints for both the \u003ccode\u003einfra-obs\u003c/code\u003e project and the root admin cluster can be accessed using the provided URLs, after replacing the placeholder variables with the relevant GDC URLs.\u003c/p\u003e\n"],["\u003cp\u003eHealth status dashboards can be utilized for performance tuning, feature development, and proactively identifying and resolving potential issues with GDC components.\u003c/p\u003e\n"]]],[],null,["# Monitor health status\n\nThis page describes how to access the health status dashboards to monitor and identify potential issues.\n\nHealth status helps you visualize the essential metrics of your Google Distributed Cloud (GDC) air-gapped appliance infrastructure and provides a high-level overview of component health. Visualizing health status dashboards helps you identify root causes, diagnose behaviors, and obtain additional context during your investigation for resolving problems.\n\nGDC monitors and provides the health status for each hardware and software component which includes:\n\n- Hardware: server node\n- Software: clusters, VMs, and storage\n\nHealth status dashboards let you visualize the metrics with which each component measures monitoring status.\n\nBefore you begin\n----------------\n\nThe root clusters contain a Grafana instance for infrastructure operators. These Grafana instances contain the health status dashboards.\n\nYou need role-based access controls to access data visualizations safely on dashboards of the Grafana instance. For this reason, follow the instructions of the [Before you begin section to query and view metrics on dashboards](/distributed-cloud/hosted/docs/latest/appliance/platform/pa-user/query-and-view-metrics#before-you-begin-grafana) to access the dashboards on the Grafana instances.\n\nGrafana endpoint\n----------------\n\nOpen one of the following URLs to access the Grafana endpoint of either the `infra-obs` project or the root admin cluster:\n\n- **Grafana endpoint of the `infra-obs` project:**\n\n https://\u003cvar translate=\"no\"\u003eGDC_URL\u003c/var\u003e/infra-obs/grafana\n\n Replace \u003cvar translate=\"no\"\u003eGDC_URL\u003c/var\u003e with the URL of an organization in GDC.\n- **Grafana endpoint of the root admin cluster:**\n\n https://\u003cvar translate=\"no\"\u003eROOT_ADMIN_CLUSTER_URL\u003c/var\u003e/grafana\n\n Replace \u003cvar translate=\"no\"\u003eROOT_ADMIN_CLUSTER_URL\u003c/var\u003e with the URL of the root admin cluster in GDC.\n\nUse case examples\n-----------------\n\nThis section includes examples on how you can use the dashboard for practical cases.\n\n### Performance tuning\n\nIf a component is performing poorly but not necessarily impacting SLO or firing alerts, you can communicate proactively to developers and prevent future issues from occurring.\n\nLikewise, a component might want to know how its feature operates to make the right performance tradeoffs. Health status are one mechanism for collecting the information that components need.\n\n### Feature development\n\nSuppose a customer requests changes or GDC plans to release a new feature. In that case, you can observe health status for the relevant components to determine the feasibility of supporting the new feature or change. Also, health status can be used to make product decisions when prioritizing the work.\n\nFor example, suppose a component has an average latency of 500 ms and is interested in reducing it to 250 ms. In that case, the team can calculate the relative cost of a 50% incremental reduction and compare it with designing an endpoint with 250 ms response time."]]
