Workload Manager's observability service for SAP is a built-in monitoring solution for SAP workloads running on Google Cloud. This solution helps you improve issue detection, root cause analysis, and troubleshooting. It leverages the existing built-in alerting and monitoring features in Google Cloud. The observability service combines the infrastructure metrics and your SAP application metrics into a unified view to help correlate events and understand the health status of your SAP system across all layers of the environment.
Workload Manager creates a logical representation of each SAP system, identified by the SAP system ID (SID), and provides a system-centric view of the workload. This lets you check the health and status of your workload at the system level, rather than the status of each underlying resource it consists of.
Use cases
The observability service for SAP in Workload Manager is recommended for the following use cases:
- Get a unified view of your SAP systems with an overall health status and sublayer health status.
- See an overview of each SAP system, including the different layers and resources they consist of.
- Perform troubleshooting and root cause analysis by using preconfigured dashboards that help correlate events across the infrastructure and application layers.
- View monitoring metrics for your infrastructure, operating system, and application on a single dashboard.
- View upcoming maintenance events for instances in a specific system, for supported machine types.
How it works
The following high-level architecture diagram shows how the information for observability dashboards is collected and sent to Workload Manager.
Each component sends the following information:
Agent for SAP:
- Sends the following metrics to Cloud Monitoring
- Process Monitoring metrics
- SAP HANA Monitoring metrics
- Sends logs related to your SAP system to Cloud Logging
- Sends information on the underlying SAP system directly to Workload Manager
Ops Agent:
- Sends infrastructure and guest OS information to Cloud Monitoring
Cloud Asset Inventory:
- Provides the following instance metadata:
- Maintenance events
- Instances states
- Instances machine types
SAP system mapping
The Agent for SAP can only collect information on its underlying host. In order to create a system-centric view and logical mapping of the SAP system, it contains additional features, which when enabled collects the following information and sends it to Workload Manager.
- Compute Engine instance name and number
- Attached storage (disks, NFS)
- Related load balancers, instance groups, health checks, forwarding rules, firewall rules
- IP addresses
- Database software name and version
- Application software name and version
- SAP system ID (SID): application and database
Workload Manager then performs a reconciliation process using the provided data to create a logical mapping of each SAP system which is referred to by the underlying SAP system ID (SID).
The following figure summarizes the system mapping in Workload Manager:
Pricing
The observability service for SAP in Workload Manager is available at no additional cost. However, the information for the observability dashboard comes from agents that are installed on each VM instance. These agents send data to Cloud Monitoring and Cloud Logging and you incur costs associated with these services.
The following table provides an estimated cost of the required features that must be enabled on each VM for SAP observability.
| Agent | Feature | Estimated monthly cost (per VM) |
|---|---|---|
| Agent for SAP | Process monitoring metrics, collected at the default frequency | $5.64 |
| Agent for SAP | SAP HANA monitoring metrics, collected at the default frequency. | $0.56 |
| Ops Agent | Monitoring: Agent metrics | No charge for default agent metrics. |
For more information, see Agent for SAP pricing and the Ops agent pricing. You can configure both agents to increase the frequency of metrics collection. You might incur more costs for the additional volume of metrics sent to Cloud Monitoring. In addition, both agents contain other features that might lead you incurring charges outside the scope of observability for SAP depending on the usage of those features.
You might also want to disable the SAP HANA monitoring and process monitoring metrics collection features in the agent to avoid any additional costs associated with Cloud Monitoring and Cloud Logging.
If you don't want to view any of your SAP workloads on the observability dashboard, remove the workload from the dashboard.
What's next
- Read about the supported SAP systems.
- Learn about prerequisites for SAP observability.
- Learn how to observe an SAP workload.