Stay organized with collections
Save and categorize content based on your preferences.
This document describes how to resolve issues that you might encounter while
using the observability service for SAP workloads in Workload Manager.
SAP system ID is not listed on the observability dashboard
After configuring the Google Cloud's Agent for SAP for observability and
granting the required permissions to service accounts for all VMs that host
the different elements of an SAP system (such as Central Services,
Application Servers, and SAP HANA databases), the system ID appears
on the SAP observability dashboard. If the system ID is not listed, check the
agent configuration and logs as explained in the following sections.
Verify the agent configuration
You must ensure that all required features are correctly configured for the
Google Cloud's Agent for SAP.
To get the status of the features of your agent instance, run the following command:
sudo/usr/bin/google_cloud_sap_agentstatus
This command output summarizes the enabled and disabled features. It also
indicates any missing IAM permissions or configuration issues.
For more information, see Validate the setup for Workload Manager observability.
Check the VM instance logs
In the VM instance logs, view issues related to the Agent for SAP not being able to update the SAP system information.
To view logs, do the following:
Select a VM to open the Details page.
Click the Observability tab to display information about the VM.
Select All logs and sort by Error as the Severity.
Most of these errors are related to missing permissions for the service account
attached to the VM. To resolve these errors, grant the required permissions
to the service account.
Check logs using Cloud Logging
You must ensure that the Agent for SAP discovers your SAP workloads correctly.
To view log entries for the VM instance that hosts the agent, do the following:
In the Google Cloud console, select Logging, and then select Logs Explorer:
In the Query pane, select Show query and enter the following query:
jsonPayload.@type:"SapDiscovery"
If you cannot see any information from the VMs that host the agent, then the
agent might not be configured or working properly. For more information,
see Configure Agent for SAP.
Optional: To view logs related to the process when Agent for SAP
uploads the SAP discovery data, use the following query:
There might be multiple root causes for Unspecified (gray color) health status
of the SAP system. This health status is used to identify systems that cannot
be correctly evaluated by Workload Manager due to missing metrics or settings.
The most common causes for this health status are as follows:
The Google Cloud's Agent for SAP might be stopped or incorrectly
reporting the required metrics. For more information, see Validate your installation of the agent.
If Agent for SAP is up and running and the system status is Unspecified,
check that the Process Monitoring and SAP HANA Monitoring features are enabled and configured
correctly in the agent depending on the SAP processes running on the VM.
Central Services and Application Servers require Process Monitoring to be enabled
while SAP HANA databases require Process Monitoring and SAP HANA Monitoring enabled.
The default values for the collection frequency
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.
On the System overview page, check whether the Architecture and Scale-Type
are correctly identified for your system. If any or both of these parameters
are incorrect, then there is an underlying issue with either the
Google Cloud's Agent for SAP or the uploaded SAP data to Google Cloud.
For further analysis, contact Cloud Customer Care. See Getting support
for Google Cloud's Agent for SAP.
The roles for each VM related to the system are not correctly identified due
to the metrics workload/sap/nw/instance/role
or workload/sap/hana/ha/availability not working correctly or missing.
Check the identified SAP roles in the list of VMs on the Applications and Databases dashboards.
The following roles are required for each of the architecture types:
Centralized Architecture: Central Services, Application Server, and SAP HANA Primary.
Distributed Architecture: Central Services, Application Server, and SAP HANA Primary.
Distributed with HA: Central Services, ERC, Application Server, SAP HANA Primary, and SAP HANA Secondary.
All the VMs in the list should have a role assigned to them.
Verify that the required metrics have a valid value by either checking
the metric inside Cloud Monitoring or by using the timeSeries API method
to have the latest value pushed by the Agent for SAP. If the metric is not present in Cloud Monitoring or has no value,
then the health status is marked as Unspecified because there is not enough data to evaluate such a metric.
On Distributed with HA architectures, check if there is a failed action
in the cluster and perform a cleanup by running the following commands:
RHEL
pcs resource cleanup RESOURCE_ID
SLES
crm resource cleanup RESOURCE_ID
Replace RESOURCE_ID with the ID of the failed resource
in the cluster.
Failed action in the cluster might impact the metrics workload.googleapis.com/sap/cluster/nodes
and workload.googleapis.com/sap/cluster/resources and it reports incorrect values.
Check whether the Google Cloud's Agent for SAP version is up to date and that
you are running the latest version available. Newer versions of the
agent contains fixes for issues and bugs related to observability metrics.
Incorrect metrics might result in the Unspecified health status of the system.
For SAP HANA databases replicating to a secondary site, check if there is a valid cluster configuration between primary and secondary.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],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."]]
