When configuring Daily Monitoring, only the start and end time may be defined and the expiration date is defined by the age of the collection rather than a specific date:ĭefines the application servers which the collectors will be started on. When this date is reached the collection is automatically deleted. The option determines the expiration date of the snapshot collection. Timeframeĭetermines when the SMON collectors should start and end. If for some reason there is a snapshot collection which covers a timeframe greater than 24 hours, see deleting large snapshot collections for steps to remove them safely. If more than 24 hours of monitoring is needed, use Daily Monitoring instead. SMON is not designed to gracefully handle multiple days of data in a single snapshot collection. When configuring snapshot monitoring, the timeframe, interval, and servers options defines the scope and collection rate of the content.ĭo NOT configure a timeframe greater than 24 hours. CPU and paging activity) the information is repeated in the rows following the snapshot in which it was collected until the next nth snapshot.
Each row in the Monitoring Data table corresponds to a single snapshot.įor content which is collected Every n times (e.g. This can occur when content which is collected every n snapshots, and the snapshots being displayed via the display only every option are not the same.įor example, if we are only viewing snapshots ending in :13 (hh:mm:13 display only every set to 60) and the Top CPU Processes (collected every 60th snapshot) were collected on snapshots ending in :00 (hh:mm:00) then SMON may raise the error previously mentioned when trying to display that content.Ĭlicking Execute on the snapshot filter dialog screen will take you to the overview data for the snapshot collection. Memory per mode) in the Monitoring Data overview screen, SMON will sometimes raise a "No detailed information available" error message. When trying to display the additional content (e.g. There is an issue when using the Display only every nth snapshot restriction. If you would like to see every snapshot change the Display only every nth snapshot value to 1. 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.