Skip to content

Latest commit

 

History

History
44 lines (29 loc) · 2.47 KB

sap-monitoring-getting-started.md

File metadata and controls

44 lines (29 loc) · 2.47 KB
copyright lastupdated keywords subcollection
years
2024, 2024
2024-12-04
SAP, SAP Monitoring, {{site.data.keyword.cloud_notm}}, {{site.data.keyword.ibm_cloud_sap}}, SAP Workloads, SAP HANA
sap

{{site.data.keyword.attribute-definition-list}}

Getting started with {{site.data.keyword.cloud_notm}} Monitoring for SAP systems

{: #mon-getting-started}

The following information describes a specific use case for setting up monitoring for SAP.

To prepare for the monitoring scenario, deploy one {{site.data.keyword.cloud}} Monitoring instance and one virtual server in IBM VPC.

{{site.data.keyword.cloud}} Monitoring offers predefined SAP dashboards from {{site.data.keyword.cloud}} dashboard library free of charge. {: shortdesc}

This setup does not support SAP systems in a High Availability setup. {: restriction}

The metrics of monitored SAP systems are collected by an application that runs on the SLES VPC host. This means that you need an extra VPC host if your deployable architecture is RHEL-based.

The detailed information about Monitoring in {{site.data.keyword.cloud}} is described in Collecting metrics by using Prometheus remote write{: external}.

As a prerequisite for getting started you have to deploy an infrastructure and SAP system landscape that is up and running without issues.

The following architecture overview diagram shows {{site.data.keyword.cloud}} Monitoring for SAP systems when the infrastructure and SAP system landscape are built by a deployable architecture{: external}.

Figure 1. {{site.data.keyword.cloud}} Monitoring for SAP systems {: caption="{{site.data.keyword.cloud}} Monitoring for SAP systems" caption-side="bottom"} {: external download="sap-monitoring-in-ibm-cloud.svg"}

To set up SAP monitoring, you must perform the following tasks.