Skip to content

Latest commit

 

History

History
206 lines (122 loc) · 6.29 KB

capturing-request-statistics-e86943a.md

File metadata and controls

206 lines (122 loc) · 6.29 KB

Capturing Request Statistics

With the Capture Request Statistics app, you can capture request statistics to find out which activities are running in your ABAP system.

Context

With the activation of a capture profile, you can capture system activities. Requests are recorded with technical information, such as response time, program name, or CPU time. Using the request statistics, you can investigate the performance or the resource consumption of a system or of a tenant in more detail.

In the Capture Request Statistics app, you can also find predefined profiles for capturing expensive requests (with names starting with SAP_). These predefined capture profiles are active by default, and you can't edit or deactivate them.

You can view the captured data from all profiles in the technical monitoring cockpit on the Captured Request Statistics and Request Processing screens. You can get to theRequest Processing screens by choosing System Workload from the menu. In addition, the captured ABAP statistics records are the basis for ABAP system sizing in the Perform System Sizing app.

Procedure

  1. On the SAP Fiori launchpad of your ABAP environment, search for the Capture Request Statistics app.

    The Capture Request Statistics app opens.

  2. To create a new capture profile, choose Create.

  3. Enter the following data:

    Field

    What to Enter

    Profile ID

    Enter a short, meaningful name for your profile. Don't use the prefix SAP_ because this prefix is reserved for profiles predefined by SAP.

    Description

    If needed, you can enter a longer description of your profile.

    Start/End Time

    The start and end time specify when request statistics were captured by the app. These fields are automatically filled after you have activated the profile.

    Retention Time

    Select how long you want to keep the captured request statistics stored in the system.

    Record Limit per Minute

    Enter the maximum number of records that you want the system to capture per minute.

    The record limit prevents that too much database memory is consumed by captured request statistics. The maximum possible record limit per minute is 1,000.

    Note:

    To get a realistic idea of the workload, consider a relatively high record limit. However, you must keep in mind that you generate load on your system while request statistics are captured.

    Sampling Rate

    Enter a sampling rate, which is the probability of capturing one single ABAP statistics record in percent.

    With the sampling rate, you ensure that a number of random records are selected during the capturing of request statistics.

    Target User Group

    Choose one of the target groups starting with Customer.

    Profile Type

    This field is automatically populated by the system. Only static profile types (with fixed values) are possible.

    Profile Owner

    The profile owner is automatically set to Customer when you create a new profile. Predefined profiles have the profile owner SAP.

    Health Monitoring

    You can select the checkbox Health Monitoring for any capture profile that you create. As a result, the total number of captured ABAP statistics records for these profiles is shown in Health Monitoring of SAP Cloud ALM.

  4. Choose Create.

    The profile has been created, but is still inactive and has no filter conditions yet.

  5. To define the filter conditions under which request statistics are captured, choose Create.

  6. With Field ID, Operator, High, and Low, you can select a filter condition that determines what kind of data is captured. For example, you might be interested in requests with a high ABAP CPU or network time. Alternatively, you can also select a program name to capture requests relating to that program, for example

    Note:

    If you don’t need to define a range (lower and upper limit), but only a single value, enter the value in the Low field.

    For example, you can select User ID as field ID, include equal to as operator and your business user name to capture all request statistics relating to your business user.

  7. Choose Create.

    A new filter condition has been created.

  8. To start capturing request statistics during the time period that’s defined in the profile, choose Activate.

    Make sure that you enter a start time that’s right now or in the future. You can’t activate profiles with a start time in the past.

Results

Request statistics are captured and processed by a collector that runs every minute. Therefore, you must expect that captured request statistics are displayed with a delay of a minute in the System Workload or in the Perform System Sizing app. Capturing request statistics is finished when the status of relevant capture profile has changed to Finished.

Note:

If you have a long-running request, ABAP statistics records for this request will only show up in the technical monitoring cockpit after the request is done. The collector then captures the request and calculates its workload over its runtime.