本文档介绍了如何解决在 Workload Manager 中使用 SAP 工作负载的可观测性服务时可能遇到的问题。
可观测性信息中心上未列出 SAP 系统 ID
为可观测性配置 Google Cloud的 Agent for SAP 并向托管 SAP 系统不同元素（例如 Central Services、应用服务器和 SAP HANA 数据库）的所有虚拟机的服务账号授予所需权限后，系统 ID 会显示在 SAP 可观测性信息中心上。如果未列出系统 ID，请按照以下部分中的说明检查代理配置和日志。
SAP 系统的健康状况为未指定（灰色）可能存在多个根本原因。此健康状况用于识别因缺少指标或设置而无法被 Workload Manager 正确评估的系统。导致此健康状态的最常见原因如下：
Google Cloud的 Agent for SAP 可能已停止或错误地报告了所需指标。如需了解详情，请参阅验证代理的安装。
如果 Agent for SAP 正在运行，但系统状态为 Unspecified，请检查代理中的进程监控和 SAP HANA 监控功能是否已启用，并根据虚拟机上运行的 SAP 进程正确配置。Central Services 和应用服务器需要启用 Process Monitoring，而 SAP HANA 数据库需要启用 Process Monitoring 和 SAP HANA Monitoring。
快速变化的 Process Monitoring 指标和缓慢变化的 Process Monitoring 指标的默认收集频率分别为 5 秒和 30 秒。如果这些值增加到高于默认值，您可能会看到健康状况为未指定。
在“系统概览”页面上，检查系统是否正确识别了架构和规模类型。如果这两个参数中的任何一个或两个都不正确，则Google Cloud的 Agent for SAP 或上传到 Google Cloud的 SAP 数据存在潜在问题。如需进一步分析，请与 Cloud Customer Care 联系。请参阅获取 Google Cloud的 Agent for SAP 支持。
由于指标 workload/sap/nw/instance/role 或 workload/sap/hana/ha/availability 无法正常工作或缺失，系统无法正确识别与每个虚拟机相关的角色。在“应用和数据库”信息中心的虚拟机列表中，检查已识别的 SAP 角色。
每种架构类型都需要以下角色：
集中式架构：中央服务、应用服务器和 SAP HANA 主节点。
分布式架构：中央服务、应用服务器和 SAP HANA 主节点。
分布式高可用性：中央服务、ERC、应用服务器、SAP HANA 主实例和 SAP HANA 辅助实例。
列表中的所有虚拟机都应分配有角色。
通过以下方式验证必需的指标是否具有有效值：检查 Cloud Monitoring 中的指标，或使用 timeSeries API 方法获取 Agent for SAP 推送的最新值。如果 Cloud Monitoring 中不存在相应指标或该指标没有值，则健康状况会标记为未指定，因为没有足够的数据来评估该指标。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[],[],null,["# Troubleshoot observability issues for SAP\n\n| **Preview**\n|\n|\n| This product or feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products and features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nThis document describes how to resolve issues that you might encounter while\nusing the observability service for SAP workloads in Workload Manager.\n\nSAP system ID is not listed on the observability dashboard\n----------------------------------------------------------\n\nAfter [configuring the Google Cloud's Agent for SAP](/workload-manager/docs/observe/sap/configure-agent) for observability and\ngranting the required permissions to service accounts for all VMs that host\nthe different elements of an SAP system (such as Central Services,\nApplication Servers, and SAP HANA databases), the system ID appears\non the SAP observability dashboard. If the system ID is not listed, check the\nagent configuration and logs as explained in the following sections.\n\n### Verify the agent configuration\n\nYou must ensure that all required features are correctly configured for the\nGoogle Cloud's Agent for SAP.\n\nTo get the status of the features of your agent instance, run the following command: \n\n sudo /usr/bin/google_cloud_sap_agent status\n\nThis command output summarizes the enabled and disabled features. It also\nindicates any missing IAM permissions or configuration issues.\nFor more information, see [Validate the setup for Workload Manager observability](/workload-manager/docs/observe/sap/configure-agent#validate-setup).\n\n### Check the VM instance logs\n\nIn the VM instance logs, view issues related to the Agent for SAP not being able to update the SAP system information.\nTo view logs, do the following:\n\n1. Select a VM to open the **Details** page.\n2. Click the **Observability** tab to display information about the VM.\n3. Select **All logs** and sort by Error as the **Severity**.\n\n Most of these errors are related to missing permissions for the service account\n attached to the VM. To resolve these errors, [grant the required permissions](/workload-manager/docs/observe/sap/prerequisites#service-account)\n to the service account.\n\n### Check logs using Cloud Logging\n\nYou must ensure that the Agent for SAP discovers your SAP workloads correctly.\nTo view log entries for the VM instance that hosts the agent, do the following:\n\n1. In the Google Cloud console, select **Logging** , and then select **Logs Explorer**:\n\n [Go to the Logs Explorer](https://console.cloud.google.com/logs)\n2. In the **Query** pane, select **Show query** and enter the following query:\n\n ```\n jsonPayload.@type:\"SapDiscovery\"\n ```\n\n If you cannot see any information from the VMs that host the agent, then the\n agent might not be configured or working properly. For more information,\n see [Configure Agent for SAP](/workload-manager/docs/observe/sap/configure-agent).\n3. Optional: To view logs related to the process when Agent for SAP\n uploads the SAP discovery data, use the following query:\n\n ```\n -jsonPayload.caller=~\"third_party/sapagent/internal/system/clouddiscovery/cloud_discovery.go\"\n -jsonPayload.caller=~\"third_party/sapagent/internal/system/sapdiscovery\"\n ```\n\nHealth status appears as unspecified\n------------------------------------\n\nThere might be multiple root causes for *Unspecified* (gray color) health status\nof the SAP system. This health status is used to identify systems that cannot\nbe correctly evaluated by Workload Manager due to missing metrics or settings.\nThe most common causes for this health status are as follows:\n\n- The Google Cloud's Agent for SAP might be stopped or incorrectly\n reporting the required metrics. For more information, see [Validate your installation of the agent](/sap/docs/agent-for-sap/latest/install-config-on-vm#validate-agent4sap-installation).\n\n- If Agent for SAP is up and running and the system status is *Unspecified* ,\n check that the [Process Monitoring](/sap/docs/agent-for-sap/latest/process-monitoring) and [SAP HANA Monitoring](/sap/docs/agent-for-sap/latest/monitoring-sap-hana) features are enabled and configured\n correctly in the agent depending on the SAP processes running on the VM.\n Central Services and Application Servers require Process Monitoring to be enabled\n while SAP HANA databases require Process Monitoring and SAP HANA Monitoring enabled.\n\n - The default values for the [collection frequency](/sap/docs/agent-for-sap/latest/process-monitoring#pm_metric_types) of the fast-changing and slow-changing Process Monitoring metrics are 5 seconds and 30 seconds respectively. If these values are increased above the default values, you might see the health status as *Unspecified*.\n- On the System overview page, check whether the **Architecture** and **Scale-Type**\n are correctly identified for your system. If any or both of these parameters\n are incorrect, then there is an underlying issue with either the\n Google Cloud's Agent for SAP or the uploaded SAP data to Google Cloud.\n For further analysis, contact Cloud Customer Care. See [Getting support\n for Google Cloud's Agent for SAP](/sap/docs/agent-for-sap/latest/troubleshooting#getting_support_for_agent).\n\n- The roles for each VM related to the system are not correctly identified due\n to the metrics `workload/sap/nw/instance/role`\n or `workload/sap/hana/ha/availability` not working correctly or missing.\n Check the identified SAP roles in the list of VMs on the Applications and Databases dashboards.\n\n | **Note:** On the observability dashboards, the *role* for a VM represents the SAP service hosted on that VM.\n\n The following roles are required for each of the architecture types:\n - Centralized Architecture: Central Services, Application Server, and SAP HANA Primary.\n - Distributed Architecture: Central Services, Application Server, and SAP HANA Primary.\n - Distributed with HA: Central Services, ERC, Application Server, SAP HANA Primary, and SAP HANA Secondary.\n\n All the VMs in the list should have a role assigned to them.\n- Verify that [the required metrics](/workload-manager/docs/observe/sap/view-dashboards#metrics) have a valid value by either checking\n the metric inside Cloud Monitoring or by using the [timeSeries](/monitoring/api/ref_v3/rest/v3/projects.timeSeries) API method\n to have the latest value pushed by the Agent for SAP. If the metric is not present in Cloud Monitoring or has no value,\n then the health status is marked as *Unspecified* because there is not enough data to evaluate such a metric.\n\n- On Distributed with HA architectures, check if there is a failed action\n in the cluster and perform a cleanup by running the following commands:\n\n ### RHEL\n\n ```sh\n pcs resource cleanup RESOURCE_ID\n ```\n\n ### SLES\n\n\n ```sh\n crm resource cleanup RESOURCE_ID\n ```\n\n \u003cbr /\u003e\n\n Replace \u003cvar translate=\"no\"\u003eRESOURCE_ID\u003c/var\u003e with the ID of the failed resource\n in the cluster.\n\n Failed action in the cluster might impact the metrics `workload.googleapis.com/sap/cluster/nodes`\n and `workload.googleapis.com/sap/cluster/resources` and it reports incorrect values.\n- Check whether the Google Cloud's Agent for SAP version is up to date and that\n you are running the latest version available. Newer versions of the\n agent contains fixes for issues and bugs related to observability metrics.\n Incorrect metrics might result in the *Unspecified* health status of the system.\n\n- For SAP HANA databases replicating to a secondary site, check if there is a valid cluster configuration between primary and secondary."]]
