We recently migrated our SAP environment to AWS to avoid being stuck on ECC after support ended. While everything seemed fine initially, we've been hit with performance complaints from users and a lack of visibility into what's actually happening. Our previous monitoring was agent-based, which doesn't work in the cloud, and we didn't set up a replacement during the stress of migration. Now when we face issues like slow month-end processes or background job failures, we're left guessing about what's wrong. CloudWatch shows us EC2 metrics but lacks the details we need for SAP. How have others handled monitoring in this situation? What tools or strategies have provided effective visibility into SAP workloads without needing to start from scratch with our on-prem setup?
5 Answers
While AWS costs can be tight, we found a good compromise with AWSight for security monitoring until our budget got sorted out. It's not a complete solution, but it addresses key areas while you figure out more comprehensive monitoring.
Transitioning to cloud SAP monitoring is tricky. You'll likely need a hybrid monitoring strategy. Use agentless cloud metrics like CloudWatch and CloudTrail for infrastructure health, layer in SAP’s logs for app-specific insights, and consider deploying lightweight agents for critical services. Combining these data points into a SIEM or analytics platform can really help identify slow jobs and problematic transactions without requiring a complete overhaul of your old monitoring setup.
I've been through this too! The phase where you think 'we'll deal with monitoring later' can really backfire. Relying solely on CloudWatch won’t cut it since it doesn't capture application-level details. What worked for us was using enhanced CloudWatch metrics alongside OS-level monitoring on EC2 instances. We tied those to SAP work process stats and metrics from HANA to pinpoint where the bottlenecks were—between dialog and background jobs. Also, keep an eye on EBS volumes for any bursts during peak times, like month-end—that was a big issue for us!
For infrastructure, CloudWatch plus AWS Health Dashboard works fine, but for actual application monitoring consider tools like Avantra or Centerity, which are tailored for SAP in the cloud. Set up early watch alerts in Solution Manager if that's available to you, as it’s part of your SAP license. Using ST06 and OS06 transactions can correlate OS performance with users' experiences. For background jobs, alerts from SM37 can help catch long-running or failed jobs while you build an improved monitoring system.
We started with basic CloudWatch metrics and the AWS SSM agent before moving on to more sophisticated methods later. It’s important to build a monitoring system that gives you real-time insights.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures