IT-Conductor Blog

What to Monitor when you are Not Monitoring SAP

Posted by Linh Nguyen on Jan 27, 2016 11:15:42 PM

What To Monitor When You Are Not Monitoring SAP

SAP Basis folks often frown upon the task of SAP monitoring.  I'll gladly admit that it's not a glamorous task and is normally laborious, especially troubleshooting or trying to generate reports.   I'm sure if you can delegate it among your team members, you probably would. Monitoring becomes something one does when there's a problem, or at critical times like go-lives and busy processing window.  That's not really active monitoring.  Then there's the question of what to monitor when you actually do it, because you may need different information for each situation.  So, what should we monitor when we're not really monitoring SAP? 

The idea is to always collect monitoring data from as many service components as possible and practical and store them in useful format for performance intelligence.  Still, you are not really monitoring it - it's not practical when you have many systems and not enough resources.  You need a tool to do it, so you will have it and it can be available for analysis or proactive management if needed.  When we engage with customers on monitoring projects, they often have a wish list.  Many of them have common requirements, so we've composed a list you might find useful as metrics or alerts to add to your specific list if they are not already on there, CCMS already collect many of them but they may not be in useful format. 

SAP Netweaver

ABAP App Server

  • Workload
    • ResponseTime avg / transactions
    • FrontendResponseTime
    • RollTime
    • DBRequestTime
    • WP Utilisation
    • ProgramErrors
    • DialogSteps
    • FrontEndNetTime
    • UsersLoggedIn
  • Dump /Syslog
    • System log ( local- Global)
    • Abap Runtime Error
    • Update terminations
    • Enqueue status
  • Communication
    • Gateway
    • RFC Connections
    • Queues / ARFC / TRFC
    • Inbound queue
    • Outbound queue
  • Buffer: All buffer types especially Program, and table
    • DirectoryUsed
    • SpaceUsed
    • HitRatio
    • Swap
  • Batch Processing
    • Jobs
      • Runtime
      • Status
      • Delays
    • BW Process Chains

Database

  • Space management: Tablespaces, containers
    • Free space
    • Used space
    • Status
  • Performance
    • Cache quality
    • Long running statements
    • RDBMS alerts
  • DB consistency
  • DB statistics status
  • Backup & Archive status

Operating System

  • Filesystems / Disks
    • Freespace
    • Percentage_Used
    • IO service times
  • CPU / Core / Thread
    • CPU_Utilization
    • 5minLoadAverage
    • Idle
    • CPU I/O Waiting
    • User Utilization
    • System Utilization
  • Memory / Paging Area
    • Free Memory
    • Configured Memory
    • Page_In / Out
    • Data Transfer In / Out
  • Network /Lan
    • Packets_In / Out
    • Collisions
    • Errors In / Out

Miscellaneous

  • Transport errors
  • Security Audit events

If this list seems like a lot, that doesn't even cover application specific monitoring like J2EE, Enterprise Portals, CRM, SCM, BW, etc.  That's the reason why many SAP customers struggle to efficiently and effectively manage the performance and alert data, even with Solutions Manager due to the management overhead.

Want to manage it the simpler way?  Subscribe to our cloud-based IT-Conductor and most of the above are already covered in an intelligent manner.  With a few clicks and a few minutes, you can monitor and alert on your SAP systems.  Truly monitor without you monitoring it yourself!

See Value Proposition & Try It  

Linh Nguyen

Written by Linh Nguyen

Linh was born in democratic Vietnam, escaped from the communist after the war as a boat-people refugee to Malaysia, subsequently immigrated to Australia where he attended high-school and completed dual-degrees in Computer Science & Computer Engineering in just 5 years. He started SAP career in Melbourne, then came to the US in the mid-1990s as a SAP technical consultant. He built a software and consulting company in Silicon Valley in 1996 named OZSoft and has been an entrepreneur with a passion to automate IT processes. In 2014, he started IT-Conductor, Inc. as CEO and co-founder along with David Stavisski, with the goal to help IT organizations to Stop Guessing and Start Managing by automating IT operations using a cloud-based platform IT-Conductor.

Topics: SAP monitoring, Availability monitoring

FREE IT-Conductor Trial to Monitor SAP

Posts by Topic

see all

Recent Posts

Subscribe to Email Updates