What is System Monitoring?

Framework observing is an everyday schedule action and this record gives a methodical bit-by-bit methodology for Server Monitoring. It gives an outline of specialized viewpoints and ideas for proactive framework checking. Not many of them are:

Actually taking a look at Application Servers.

Observing extensive Work Processes.

Observing Work Processes for Individual Instances.

Observing Lock Entries.

Computer processor Utilization

Accessible Space in Database.

Observing Update Processes.

Observing System Log.

Cradle Statistics

Some others are:

Checking Batch Jobs

Spool Request Monitoring.

Number of Print Requests

ABAP Dump Analysis.

Data set Performance Monitor.

Data set Check.

Observing Application Users.

Why Daily Basic checks/System Monitoring?

SAP Monitoring and Performance Checks: Complete Tutorial with Tcodes

How would we really do screen a SAP System?

Actually looking at Application Servers (SM51)

This exchange is utilized to really look at all dynamic application servers.

Here you can see which administrations or work processes are arranged in each occurrence.System monitoring and performance checks are critical aspects of managing an SAP (Systems, Applications, and Products in Data Processing) environment to ensure its smooth operation. Proper monitoring and performance checks help identify and address issues promptly, ensuring that SAP systems run efficiently and meet business needs. Here's a comprehensive guide on SAP system monitoring and performance checks:

1. System Landscape Overview:

• Begin by understanding your SAP system landscape, including the number of systems, their roles (development, quality assurance, production, etc.), and their dependencies.

2. Monitoring Tools:

• Utilize SAP Solution Manager or third-party tools like SAP CCMS (Computing Center Management System), SAP EarlyWatch Alert, or SAP Focused Run for comprehensive monitoring and performance analysis.

3. Key Metrics to Monitor:

• Monitor critical metrics such as CPU utilization, memory usage, disk I/O, network traffic, and database performance. Set thresholds for these metrics to trigger alerts when they exceed predefined values.

4. SAP Application Servers:

• Monitor application servers for resource utilization, response times, and work processes. Ensure they are evenly distributed to prevent overloading any single server.

5. Database Monitoring:

• Monitor the database server for performance, tablespace utilization, and SQL statement execution times. Regularly optimize database indexes and table structures.

6. Background Jobs:

• Monitor background job schedules and their execution. Ensure that critical jobs complete within the defined timeframes.

7. Network Monitoring:

• Keep an eye on network connectivity and latency between different SAP system components (application servers, database server, etc.). High network latency can impact system performance.

8. Log Files:

• Review log files for errors, warnings, and exceptions regularly. Investigate and address issues as they arise.

  See also here -->>

9. User Activity:

• Monitor user activity, such as login/logout times and transaction execution times. Identify and address performance bottlenecks that may affect end-user experience.

10. Batch Processing: - Monitor batch processing, including batch job completion times and resource usage. Optimize batch job schedules for better resource utilization.

11. Security and Authorization Checks: - Ensure that authorization checks are in place to prevent unauthorized access to sensitive data and functions within the SAP system.

12. System Health Checks: - Conduct regular system health checks to assess the overall system's stability and performance. This can include checking for software updates, patches, and system vulnerabilities.

13. Performance Tuning: - Continuously fine-tune the SAP system based on monitoring data. This may involve adjusting parameters, optimizing queries, and upgrading hardware or software components.

14. Capacity Planning: - Use historical data and performance trends to plan for future capacity needs. Ensure that the system can scale to accommodate growing workloads.

15. Documentation and Reporting: - Maintain detailed documentation of your monitoring procedures and findings. Generate regular reports to communicate system health and performance to stakeholders.

16. Incident Response: - Establish an incident response plan to address critical issues promptly. Define roles and responsibilities for handling incidents and outages.

17. Regular Review and Improvement: - Periodically review and update your monitoring strategy and performance checks to adapt to changing business requirements and technology advancements.

Checking Work Processes for Individual Instances SM50:

Shows generally running, pausing, halted and PRIV processes connected with a specific occurrence. Under this step we really look at every one of the cycles; the interaction status ought to continuously be pausing or running. Assuming any cycle is having a status other than pausing or running we really want to in like manner really take a look at that specific interaction and report.This exchange shows a ton of data like:Status of Work process (regardless of whether it's involved)Assuming the work cycle is running, you might have the option to see the move made by it in the Action segment.You might which at any point table is being worked upon

A portion of the regular issues:

The client consumes a large chunk of the day to sign on/not ready to logon/online exchange exceptionally sluggish. This could be the aftereffect of the DIA work processes are completely used. There could be additionally the aftereffect of long running position (red marker under the Time section). On the off chance that essential you can drop the meeting by choosing the positions then go to Process>Cancel Without center. This will drop the work and delivery the work cycle for other client/processA few clients might have PRIV status under Reason segment. This could be that the client exchange is huge to such an extent that it requires more memory. At the point when this happen the DIA work cycle will be 'possessed' by the client and won't allow different clients to utilize. In the event that this occurs, check with the client and assuming that conceivable run the occupation as a foundation work.On the off chance that there is a long print work on SPO work process, research the issue. It very well may be an issue connected with the print server or printer.

Experience the difference

Observing all inclusive Work Processes (SM66)

SAP Monitoring and Performance Checks: Complete Tutorial with TcodesBy checking the work interaction load utilizing the worldwide work process outline, we can rapidly explore the likely reason for a framework execution issue.Screen the work cycle load on all dynamic occurrences across the framework

Utilizing the Global Work Process Overview screen, we can see initially:

The situation with every application server

The motivation behind why it isn't running

Whether it has been restarted

The CPU and solicitation run time

The client who has signed on and the client that they signed on to

The report that is running

Be that as it may, in the event that the Update isn't dynamic then view as the underneath data:

Is the update dynamic, on the off chance that not, was it deactivated by the framework or by a client?

Click on SAP Monitoring and Performance Checks: Complete Tutorial with Tcodes button and get the data.

Click on SAP Monitoring and Performance Checks: Complete Tutorial with Tcodes button and get the underneath data:

Is any update dropped?

Is there a long line of forthcoming updates more established than 10 minutes?Checking Lock Entries (SM12)Execute Transaction SM12 and put '*' in the field User NameSAP gives a locking component to keep different clients from changing the record that you are dealing with. In certain circumstances, locks are not delivered. This could occur assuming the clients are cut off for example because of organization issue before they can deliver the lock.These old locks should be cleared or it could forestall access or changes to the records.We can utilize lock measurements to screen the locks that are set in the framework. We record just those lock passages which are having date time stamp of the earlier day.

Checking System Log (SM21)

We can utilize the log to pinpoint and redress mistakes happening in the framework and its current circumstance.We really look at the log for the earlier day with the accompanying choice/choice:Enter Date and time.Select Radio Button Problems and WarningsPress Reread System Log.

Must Know!