Hi, my name is Bharat Ramaka,
and I'm a Solutions Architect on the SAP Team here at AWS.
Today, I'm going to show you how to set up monitoring
for your SAP applications on AWS with Amazon CloudWatch.
This will allow you to keep an eye on performance changes,
utilization, instance help, and more, with automatic dashboards,
actionable insights, and metric collection,
storage, and retention.
To start, install SAP HANA,
or an SAP application server on an Amazon EC2 instance.
We recommend one of our 130 plus SAP certified instances.
In this case, I have installed SAP NetWeaver system on SAP
HANA database using an r5.4x large instance,
with 128gb of RAM for SAP HANA,
and m5.2x large for SAP application server.
We will start by configuring Amazon CloudWatch.
First, we need to ensure the detail monitoring is turned on.
This changes the monitoring interval
from default five minutes to one minute.
Then, we need to install AWS
Data Provider inside the EC2 instance.
AWS Data Provider is a mandatory component
for receiving integrated support from SAP and AWS.
It gathers AWS-specific information about instance type,
instance ID, key system information like processors
and memory and resource consumption data.
The information AWS Data Provider finds is crucial for AWS
and SAP to analyze any performance issues.
Here, I have logged into the EC2 instance
and downloaded the Data Provider package from the S3 bucket.
Links to these are provided in the description.
If you look at the SAP DBOS Cockpit, we can see the enhanced monitoring
is false and AWS Data Provider is not present.
We’ll start the installation of the AWS Data Provider.
This can be done online without impacting our SAP system.
Once installed, the Data Provider connects with the OS collector,
providing and exchanging the necessary information.
Once the installation is complete, a quick way to check to see
if Data Provider is running is to look at Port 8888.
We can also query the local host URL
to download the metrics it is collecting.
Now, if we switch back to the SAP screen and hit refresh,
I can see that enhanced monitoring is true
and the AWS Data Provider for SAP
has been successfully installed on the EC2 instance.
We will start seeing the details populate here.
We'll be able to see the instance type, CPU, memory, disk usage,
and all the KPI’s information being populated,
but we may need to give it a few minutes
before the metrics start showing up in CloudWatch.
If you go to the instance page and select the monitoring tab,
we can see the dashboard with all the information for CPU network.
All the information has already started getting collected.
That's how you configure CloudWatch and enable Data Provider
for any SAP application server or SAP HANA database.
We can also use CloudWatch to set up EC2 auto recovery
for added resiliency.
I'm going to simulate with an AWS command line interface,
on this instance,
to show that EC2 action is triggered based on the CloudWatch alarm.
First, let's create the CloudWatch alarm.
We will go to the CloudWatch Management Console,
and then into the alarm section, create alarm,
select metric, EC2, per instance metric,
and choose status check: failed system.
This opens the specify metric and conditions page.
We'll make it minimum
with an interval of one minute
and value greater than zero and click
on there to open additional configuration.
I would like the alarm to be triggered for two data points.
So, we’ll set that here and click next.
Here, we have an option to select SNS topic.
I am choosing email notification.
You can also choose and enable mobile notifications.
Here, we can add an EC2 action.
We have four options.
We can recover, stop, terminate, or reboot the instance.
Let us choose recover instance.
Click next.
Here, under the name,
we'll give EC2 auto recovery.
Under the add name and description section,
we will put the alarm name and description as EC2 auto recovery.
Click next.
Scroll down to the bottom and create an alarm.
This takes us to our alarms console.
The status for this alarm rates insufficient data.
So, we’ll wait for the status to change.
We can refresh it every few seconds until it's finished.
Once it's ready, the alarm will turn green.
I'm going to simulate this alarm in our EC2 instance.
It takes just a moment for the configuration to connect.
Since we cannot predict network or hardware failure,
we will simulate it with this alarm from EC2 instance
using AWS Command Line.
Let's go to the CloudWatch console.
We can see our alarm is triggered.
Let's go into the alarm and see the system events.
We can look at the history data to get additional insights
and, under this history data,
we can see that it's the simulation command
we have given from that AWS command line.
We can see that alarm has taken an action
and recovered the instance and we are back to green.
CloudWatch has automatically provisioned
a new instance to give you resiliency using spare
EC2 capacity, and all you pay for is for the cost of the alarm.
That's how you configure Amazon CloudWatch
monitoring and observability for SAP applications.
Links to all of the documentation is available
in the description below.
In a future video, we will talk about configuring Amazon CloudWatch
monitoring in a serverless architecture
and custom metrics for scenarios such as work processes full.
To learn more, go to aws.amazon.com/CloudWatch.
Thanks for watching.