Tutorial: Set up monitoring for SAP ASE

Open the CloudWatch console.

From the left navigation pane, under Infrastructure monitoring, choose Application Insights.

The Application Insights page displays the list of applications that are monitored with Application Insights, and the monitoring status for each application. In the upper right-hand corner, choose Add an application.

On the Specify application details page, from the dropdown list under Resource group, select the Amazon resource group that contains your SAP ASE database resources. If you haven't created a resource group for your application, you can create one by choosing Create new resource group under the Resource group dropdown. For more information about creating resource groups, see the Amazon Resource Groups User Guide.

Under Monitor CloudWatch Events, select the check box to integrate Application Insights monitoring with CloudWatch Events to get insights from Amazon EBS, Amazon EC2, Amazon CodeDeploy, Amazon ECS, Amazon Health APIs and notifications, Amazon RDS, Amazon S3, and Amazon Step Functions.

Under Integrate with Amazon Systems Manager OpsCenter, select the check box next to Generate Amazon Systems Manager OpsCenter OpsItems for remedial actions to view and get notifications when problems are detected for the selected applications. To track the operations that are performed to resolve operational work items, called OpsItems, that are related to your Amazon resources, provide an SNS topic ARN.

You can optionally enter tags to help you identify and organize your resources. CloudWatch Application Insights supports both tag-based and Amazon CloudFormation stack-based resource groups, with the exception of Application Auto Scaling groups. For more information, see Tag Editor in the Amazon Resource Groups and Tags User Guide.

Choose Next to continue to set up monitoring.

On the Review detected components page, the monitored components and their workloads automatically detected by CloudWatch Application Insights are listed.

Choose Next.

On the Specify component details page, enter the username and password of your SAP ASE databases.

Review your application monitoring configuration, and choose Submit.

The application details page opens, where you can view the Application summary, the list of Monitored components and workloads, and Unmonitored components and workloads. If you select the radio button next to a component or workload, you can also view the Configuration history, Log patterns, and any Tags that you have created. When you submit your configuration, your account deploys all of the metrics and alarms for your SAP ASE system, which can take up to 2 hours.

Open the CloudWatch console.

From the left navigation pane, under Infrastructure monitoring, choose Application Insights.

The Application Insights page displays the list of applications that are monitored with Application Insights, and the monitoring status for each application.

Under Monitored components, select the radio button next to the component name. Then, choose Manage monitoring.

Under EC2 instance group logs, you can update the existing log path, log pattern set, and log group name. In addition, you can add up to three additional Application logs.

Under Metrics, you can choose the SAP ASE metrics according to your requirements. SAP ASE metric names are prefixed with asedb. You can add up to 60 metrics per component.

Under ASE configuration, enter the username and password for the SAP ASE database. This is the username and password that Amazon CloudWatch agent uses to connect to the SAP ASE database.

Under Custom alarms, you can add additional alarms to be monitored by CloudWatch Application Insights.

Review your application monitoring configuration and choose Submit. When you submit your configuration, your account updates all of the metrics and alarms for your SAP HANA system, which can take up to 2 hours.

Open the CloudWatch console.

In the left navigation pane, choose Alarms>All alarms.

Select the radio button next to the alarm that was automatically created by CloudWatch Application Insights. Then choose Actions, and select Edit from the dropdown menu.

Edit the following parameters under Metric.

1. Under Statistic, choose one of the statistics or predefined percentiles, or specify a custom percentile. For example, p95.45.

2. Under Period, choose the evaluations period for the alarm. When you evaluate the alarm, each period is aggregated into one data point.

Edit the following parameters under Conditions.

1. Choose whether the metric must be greater than, less than, or equal to the threshold.

2. Specify the threshold value.

Under Additional configuration edit the following parameters.

1. Under Datapoints to alarm, specify the number of data points, or evaluation periods, that must be in the ALARM state to initiate the alarm. When the two values match, an alarm is created that enters ALARM state if the designated number of consecutive periods are exceeded. To create an m out of n alarm, specify a lower value for the first data point than for the second. For more information about evaluating alarms, see Evaluating an alarm.

2. Under Missing data treatment, choose the behavior of the alarm when some data points are missing. For more information about missing data treatment, see Configuring how CloudWatch alarms treat missing data.

3. If the alarm uses a percentile as the monitored statistic, a Percentiles with low samples box appears. Choose whether to evaluate or ignore cases with low sample rates. If you choose ignore (maintain alarm state), the current alarm state is always maintained when the sample size is too low. For more information about percentiles with low samples, see Percentile-based CloudWatch alarms and low data samples.

Choose Next.

Under Notification, select an SNS topic to notify when the alarm is in ALARM state, OK state, or INSUFFICIENT_DATA state.

Choose Update alarm.