IT-Conductor Blog

SAP End-User Experience Monitoring

Posted by Danica Esteban on Apr 7, 2021 7:50:49 AM

With contributions from David Stavisski, Femi Charles, and Linh Nguyen 


SAP Basis Monitoring for Application Locks and Enqueue

Posted by Linh Nguyen on Oct 11, 2018 11:32:10 AM

Monitoring SAP Application Locks and Enqueue

The restriction on data modification, while a data record is being changed by another user, is to ensure data consistency within an SAP system. This is achieved through the use of enqueue service/lock management mechanism which handles locks in the lock table. This locking concept prevents concurrent access to data records by multiple users which may lead to data inconsistency.


SAP Basis Monitoring for Database Performance Analysis

Posted by Linh Nguyen on Oct 4, 2018 10:39:54 AM

DB Performance Analysis

Top down service management involves App, DB, OS and other infrastructure components, performed in a correlated fashion.  Identifying performance bottlenecks promptly within the database is very critical for enterprise applications which heavily depend on OLTP or OLAP transactions. Proactive database performance monitoring will prevent incidences that can threaten the stability of your systems. It's imperative therefore to have an effective tool and automated process for monitoring the health of your systems to ensure the continuous availability and performance of mission-critical enterprise applications.


SAP Basis Monitoring for Workload Performance

Posted by Linh Nguyen on Sep 25, 2018 5:20:42 PM

SAP Workload Monitoring

Good application and system design incorporates both high availability and performance.  A best practice in monitoring performance is managing workloads as KPIs against system bandwidth/capacity utilization.  Establishing performance baselines and constantly monitoring workload KPIs against it as a way of managing service levels. 


Alexa! Get me an AWS Marketplace SaaS SAP Monitoring App

Posted by Linh Nguyen on Aug 31, 2017 8:51:37 AM

What Amazon Wants, Amazon Gets!

Amazon wanted some groceries, Alexa got Whole Foods.  Officially on Monday August 28, 2017 the deal was done, Amazon Echo and Dot devices were being sold in Whole Foods stores.


S/4HANA Monitoring is LIVE on SAP App Center

Posted by Linh Nguyen on Aug 16, 2017 6:11:19 PM

It's LIVE on SAP App Center Approved for S/4HANA Monitoring!

SAP has approved IT-Conductor SaaS platform for immediate monitoring of S/4HANA (including HANA Monitoring and SAP Monitoring of supported technologies).  It intelligently orchestrates complex IT operations, saving SAP customers up to 90% of time and cost of SAP Monitoring and Application Performance Management.

IT-Conductor simplifies monitoring of SAP products (e.g. ABAP, BOBJ, PO) based on different types of DBMS (e.g. ASE, HANA, Oracle, DB2, MS*SQLServer), and add-on components (e.g. SLT, RFC).

Take the SAP App Center Tour


Advanced SAP Monitoring Features by IT-Conductor

Posted by Linh Nguyen on Jul 25, 2017 9:24:54 PM


IT-Conductor is a SaaS platform which intelligently orchestrates complex IT operations, saving SAP customers up to 90% of time and cost of SAP Monitoring and Application Performance Management.

IT-Conductor simplifies monitoring of SAP products (e.g. ABAP, BOBJ, PO) based on different types of DBMS (e.g. ASE, HANA, Oracle, DB2, MS*SQLServer), and add-on components (e.g. SLT, RFC).

  • Drill-down feature
  • SQL Jobs
  • Key Performance Indicator (KPI)
  • CCMS Alert

SAP Patches Can Fix or Break SAP Performance

Posted by Linh Nguyen on Oct 5, 2016 10:55:45 PM


Ever hopeful or worried that SAP patches may fix or break your system's performance?  Let's face it, if we have a specific problem, we hope a patch will fix it.  However, given patches are now mostly delivered in packages or bundles (particularly support packs), we're worried at the same time it may break something else.  Even if all functionality remains intact, there is always a chance performance may be impacted, for better or worse.

That's why we recommend to include SAP Performance Best Practices for Implementation, Upgrade & Migration.  Case in point, while monitoring Solution Manager with IT-Conductor (yes that will be another topic in itself that we'll cover in another post), we were pleasantly surprised, unlike most cases, that a set of patches actually improved the system performance.  Without the proper SAP monitoring tools and context, it would be pretty hard to pinpoint the cause and effect of such action.

Let's see how we became aware of problems, then related the cause and effect:

1. The Problem and Symptom

  • Service Level Alerts and notification indicated that the system was under stress with automated Health checks
  • We also received email notification via subscription that one of the app servers had prolonged periods of 'CPU Idle 0%'

2. Find the Root-cause Part 1

  • In the Health chart with RED status bars above, we can click on a single button to determine the cause from all underlying components monitored for the system (or what we better refer to as a Service)
  • Expanding the service tree where there are warning indicators we find both Background utilization and CPU Idle on the same page with a high degree of negative correlation (i.e. Batch processes maxing out while CPU Idle hugs the zero line)

3. Find the Root-cause Part 2

  • What workload was running that took all the batch work processes.  Well this is pretty hard to find in hindsight, but we've got a secret weapon!  Click on the app server icon having the issues and a menu pops up with a choice to look at WorkProcesses snapshot
  • Looks like we had a combination of Solman batch and ChaRM running a long time, and no free batch processes

4. The Fix

  • The Basis team applied some Solman add-on support packages, and guess what happened - Look at the charts below - the middle chart shows when patches were applied, things began to improve around mid-night.  Was it coincidence?  Maybe, but what's probable, look at the correlation when charts of metrics and events are synchronized with each other, all on a single-pane


SAP Performance Workload Monitoring

Posted by Linh Nguyen on Dec 15, 2015 9:04:16 PM

SAP performance management includes workload monitoring on top of resource utilization.  As simple as workload monitoring sounds, today still not many solutions exist for customers to easily monitor the performance of transactions, reports, batch, RFC workloads.

Visit our webinar series Mastering SAP Monitoring - Workload Monitoring for an in-depth discussion about what workloads are and how best to monitor them: Solve the SAP Workload Monitoring Challenge.

SAP Solution Manager has IT Performance Report, and CCMS has ST03 workload analysis with EarlyWatch transaction reports.  However, these are historical reports, not monitors that can alert when their performance degrades.

If you have no tools but CCMS, here is a tip on setting up Transaction SLA which has been there since R/3 4.6C, whereby only dialog transactions can be configured to report response times in RZ20 with yellow and red thresholds.  However, historical performance values are not easily charted for analysis, and you would likely need to branch off to ST03.  Nevertheless, use this setup if you want to see how it works as you will need to maintain a table ALTRAMONI.  

There are some better alternatives that will monitor most workload types such as dialog transactions, batch jobs, BI reports, HTTP/S transactions, RFC, etc. and can filter by terminal, client, user, app server.


7 Telltale Signs If your IT Operations is Operational

Posted by Linh Nguyen on Oct 7, 2015 6:41:44 PM


Some of our readers may remember how SAP Basis used to be the one-stop shop for all technical SAP, Database, OS, Servers, Storage, yes and even Network and Security.  Basis teams designed, built and operated, which meant we also scheduled jobs, monitored performance, and of course were on call for all things technical SAP.  Those days of working in Basis Operations maybe long gone for large enterprises with segregation of duties and specialization due to increased complexities and compliance requirements, but sometimes we wonder if those were the good old days when it was more efficient.

Today, most enterprise IT division comprise of many technology silos and teams which function as shared services.  IT Operations is one of those centralized shared services, and SAP Basis are separated out from System Administrators, DBAs, etc.  Everybody relies on IT Operations (sometimes referred to NOC - Network Operations Center) to provide centralized monitoring and share incident management with IT Helpdesks.  Sounds rosy right?  It can be, but many times there's also the law of unintended consequences when things are really inefficient.  ITSM (IT Service Management) specialists would know - there must be people, processes and products to implement to make it operational.  It's like the 3-legged stool, all must be present to be functional.

I have been on both sides of Basis and Operations, here are 7 telltale signs that may indicate an organization's IT Operations may not be Operational, or at least not optimally, why we think it's not, and what typical fixes are.

FREE IT-Conductor Trial to Monitor SAP

Posts by Topic

see all

Recent Posts

Subscribe to Email Updates