This guide describes common issues that you can investigate if the monitoring agent for SAP NetWeaver isn't working.
Check the logs
You can start troubleshooting the monitoring agent for SAP NetWeaver related issued by checking the logs of the agent.
Check the logs in the directory that is specific to your operating system:
Insufficient IAM permissions
On the VM instance details page in Google Cloud console, note the name of the
VM service account. For example:
On the IAM & Admin home page, confirm that the service account includes
an IAM role that includes the
If you installed the Cloud Monitoring agent (not the monitoring agent for SAP NetWeaver), then you might need to grant additional IAM permissions to your VM service account, such as the predefined Monitoring Metric Writer role. To confirm the permissions that the Monitoring agent requires, see the Cloud Monitoring documentation:
Incorrect access scopes for the VM service account
Access scopes are the legacy method of specifying permissions for your instance.
A best practice is to set the full
cloud-platform access scope on the
instance, then securely limit the service account's API access with
IAM roles. For example:
If you do limit the access scopes of your VM, then you must ensure that the host VM has the following access scopes:
To change the access scopes, you need to stop your VM instance, make the changes, and then restart the instance. For instructions, see the Compute Engine documentation. You don't need to make any changes to permissions for IAM roles for this issue.
Missing or incorrect SAP Host Agent
For the monitoring system to work, your SAP NetWeaver system must have the SAP Host Agent installed and the required minimum patch level for the Host Agent. For instructions to install the SAP Host Agent, see the SAP documentation.
For version requirements for the SAP Host Agent, refer to the following SAP Notes:
- Linux: SAP Note 2460297 - SAP on Linux on Google Cloud Platform: Enhanced Monitoring
- Windows: SAP Note 1409604 - Virtualization on Windows: Enhanced Monitoring
If the host server that is running the monitoring agent for SAP NetWeaver was created without a public IP address, then the monitoring agent cannot be downloaded. For a description about how to set up a NAT gateway that gives the host server outbound access to the internet, see the deployment guide for your operating system:
- Setting up a NAT gateway on a Compute Engine VM
- SAP NetWeaver on Linux Deployment Guide
- SAP NetWeaver on Windows Deployment Guide
Port not available
The monitoring agent for SAP NetWeaver listens for requests on port
18181. This port
must be available or the monitoring agent cannot start up. If it is not,
then the SAP Host Agent logs show a
Connection Refused error. Make sure port
18181 is available for the monitoring agent for SAP NetWeaver. If another service
is using port
18181, then you might need to restart the other service or otherwise
reconfigure it so that it uses another port.
Missing configuration file ( Bare Metal Solution only )
configuration.yaml file is required on the host server to enable the
monitoring agent for SAP NetWeaver in a Bare Metal Solution environment. If you need to
configuration.yaml file after installing the monitoring agent for SAP NetWeaver,
then follow these steps:
configuration.yamlfile in the following directory that is specific to your operating system:
configuration.yamlfile, include the following line:
Restart the monitoring agent for SAP NetWeaver. For more information, see Restarting the monitoring agent for SAP NetWeaver.
Getting support for monitoring agent for SAP NetWeaver
If you need help resolving a problem with the monitoring agent for SAP NetWeaver, then gather the required diagnostic information and contact Cloud Customer Care. For more information, see Monitoring agent for SAP NetWeaver diagnostic information.