![]() ![]() This allows initial filtering to be done prior to viewing the snapshots and is useful if you know the timeframe the problem occurred or if the issue was isolated to an application server/user/WP type/etc.īecause the default interval of SMON is 1 second (and since most content is only collected every 10th or 60th interval) the default restriction is to display every 30th snapshot. If collections do exist in the system, the home screen with be the Snapshot Monitor screen, listing these collections:ĭouble clicking a snapshot collection (or selecting a collection and clicking the Display Overview Data button) will display the Filter dialog screen: If no snapshot collections exist yet in the system, the home screen of SMON will be the Start Snapshot Monitoring screen: To access SMON, execute transaction /n/SDF/SMON (a leading "/n" is required due to the namespace) or run report /SDF/SMON in transaction SE38. See SAP Note 2651881 - How to configure SMON for performance monitoring and analysis. In lower SAP NETWEAVER releases where SMON is not available, /SDF/MON can be used as an alternative ( SAP Note 2383809) How to Schedule SMON Refer to SAP Note 539977 for steps on installing & updating ST-PI. ![]() The system must have Software Component ST-PI Release 740 with SP-Level 0002 or higher. SMON is first made available in SAP NETWEAVER 7.4 ) between snapshots and are started as RFC calls in an "async w/o result" connection.Ĭollected snapshots are stored in Snapshot Collections.Ĭustomers sometimes express concern over these long-running collector tasks thinking their system has a performance problem, but the behavior is expected and not an indication of a performance problem see SAP Note 2229255 - Long RFC response times when you use /SDF/MON. SMON works by starting long-running collectors, one per application server. It is recommended to use SMON instead of /SDF/MON. ![]()
0 Comments
Leave a Reply. |