Overview

Amazon CloudWatch Monitoring for SAP NetWeaver ABAP-based environments powered by AWS Lambda.

Please see our blog post SAP Monitoring: A serverless approach using Amazon CloudWatch for more info on the motivation and concept!

Prerequisites

• SAP NetWeaver ABAP 7.4 or higher (ECC, S4, BW, ...)
  • SAP Component ST-PI Release 740 SP 08 or higher.
  • SAP statistical records enabled (transaction codes stad / st03).
    If not active by default, please check SAP note 2369736.
  • SAP RFC user and password - see "Setting it up -> Step 1"
• SAP S-User to download SAP Java Connector – see “Setting it up -> Step 2”
• Amazon VPC security group(s) allowing inbound/outbound traffic on port 33<instanceID>, so that the Lambda function can connect via the private subnet to the SAP system to be monitored – see also previous section “Architecture.”
• For Production systems, make sure to enable CloudWatch detailed monitoring according to SAP note 1656250.

Setting it up

Please follow the step-by-step guide.

Architecture

Note: You will have to deploy a single instance of this application per SAP System ID!

The resulting dashboards can look as follows

Further Read

• Cost Considerations
• Performance & Overhead Considerations
• Known Issues
• Collected Metrics
• Troubleshooting

License

This project is licensed under

This solution requires the SAP Java Connector from SAP SE to be added manually.

All rights reserved.