The course is part of this learning path
SAP landscapes are substantial and complex deployments that require constant monitoring to ensure optimal and efficient operation. It's not practical to manually keep an "eye" on virtual machines and network resources to ensure they aren't overwhelmed by spikes in workload or sitting idle or underutilized, consequently wasting money. Azure provides several services and tools that assist in monitoring infrastructure use in near real-time with automated alerts and resource scaling. Azure provides built-in integration with SAP database and application logs, providing a complete picture of overall system performance. This course explores these Azure services and how you can use them to monitor and optimize your SAP workloads.
- Get a foundational understanding of Azure Monitor and Network Insights
- Learn how to set up basic networking monitoring
- Understand what Azure Site Recovery is and how to set to implement it through the Azure portal
- Learn about SAP Hardware and Cloud measurement Tools as well as SAP Application Performance Standard
- Get an overview of Azure Advisor and how how to optimize Azure ExpressRoute
- Anyone who wants to learn how to monitor and optimize their SAP landscapes using Azure services
- Those studying for Microsoft's AZ-120 exam
To get the most out of this course, you should understand how to operate SAP workloads on Azure. If are new to this, we recommend you take the following courses first:
Microsoft provides an Azure Monitor service customized for SAP solutions which works with virtual machines and Large Instances and supports HANA and SQL Server databases. However, unlike the regular Azure Monitor service, it doesn't collect resource metrics but sends SAP custom logs to the log analytics system. Once the log data is aggregated into Log Analytics, you can use Azure Workbooks, and Kusto queries to create custom reports, dashboards, and alerts and integrate the data with systems like helpdesk and ticketing. Because SAP is third-party software running on Azure infrastructure, the log data collected is dependent on installed monitoring providers and how they're configured.
Here we can see various SAP data sources feeding Azure Monitor for SAP Solutions.
SAP NetWeaver telemetry includes SAP system and application server availability in terms of dispatcher instance process availability, ICM, gateway, message, and Enqueue servers and IGS Watchdog. Statistics and trends are logged for Enqueue Locks and queue and work process usage.
Linux OS telemetry includes CPU use, running, and blocked processes along with fork count. Memory use, both cached and buffered, along with page swapping and swap rate. Bytes read and written by block device are recorded for file system usage, along with read and write latency by block device. Network performance is logged in terms of bytes and packets in and out. Pacemaker cluster telemetry is recorded as node, resource, and STONITH block device status, as well as quorum votes, ring status, and location constraints.
Database telemetry for SAP HANA and SQL Server includes CPU, memory, and disk use. For HANA, Azure Monitor also collects network and file system use, database growth, system replication, backup, and host status. For SQL Server, Azure Monitor records the usual telemetry like blocking processes, SQL wait statistics, most expensive queries, and logged errors. SAP-specific data includes SAP system ID and the 12 largest SAP tables.
Hallam is a software architect with over 20 years experience across a wide range of industries. He began his software career as a Delphi/Interbase disciple but changed his allegiance to Microsoft with its deep and broad ecosystem. While Hallam has designed and crafted custom software utilizing web, mobile and desktop technologies, good quality reliable data is the key to a successful solution. The challenge of quickly turning data into useful information for digestion by humans and machines has led Hallam to specialize in database design and process automation. Showing customers how leverage new technology to change and improve their business processes is one of the key drivers keeping Hallam coming back to the keyboard.