With the Generic View it is possible to create dashboards depending on your needs. The following capabilities are available.
| Capability Name | Description | Supported Request Types | Available Metrics |
|---|---|---|---|
| RUM Requests | Metrics in combination with user locations | All | Average Response Time Executions CPU Time DB Time Distinct Users (FRUN 4.0) Last Execution [Day] (FRUN 4.0) |
| RUM UI Requests | Front-end measurement for UI requests in combination with user location | SAPUI5 (256) Web Dynpro (257) Web GUI (258) | Average E2E Response Time Backend Time Network Time Executions Number of Roundtrips |
| RUM HTTP Metrics | Metrics for incoming http(s) requests | http (101) https(102) | Average E2E Response Time Executions Client Errors (FRUN 3.0 FP03) Server Errors (FRUN 3.0 FP03) Client Error Rate (FRUN 3.0 FP03) Server Error Rate (FRUN 3.0 FP03) |
| RUM HTTP Outgoing Metrics | Metrics for outgoing http(s) requests initiated by user requests (http(s), RFC, DIAG) | outgoing http (101) https(102) | Average E2E Response Time Executions |
| RUM Table Accesses | Metrics for table accesses provided by statistic record (tabrec) (FRUN 3.0 FP03) | All (ABAP) | Response Time Direct Reads Sequential Reads Modifications |
Metric Catalog
What should be displayed e.g. number of executions or response times.
Selected
Depending on the metric and the expected result it needs to be defined how a metric should be handled for Time Aggregation. These aggregation values are possible:
Average
When the time range is changed and another resolution is used a new average value is calculated. This makes sense if the result should contain for example the Average Response Time.
MIN
Always the minimum value of the value in the selected time range is provided.
MAX
Always the maximum value of the value in the selected time range is provided.
SUM
The sum of all values is calculated. This makes sense of the result should contain for example the number of executions or the workload of a metric.
COUNT
Provides the number of measurements
When more than one metric should be displayed you can choose which metrics(s) should be displayed on a second axis. When the values of the different metrics are on completely dimensions e.g. one metric is in bytes and another in MBytes a scale factor can be used.
Aggregated
Defines the reference information that should be displayed or not. When a dimension is selected e.g. Request Name the metrics don't contain this name in the result. If you want to have a dimension in the result the Aggregate flag must not be set.
Depending on the dimension the result set can be very huge. To avoid overloading the UI the number of data points is limited. Only the values of the top-n dimensions are displayed the rest will be aggregated to Others.
Each dimension can be filtered.
It is possible to use the wildcard *. If no wildcard is used it uses a substring search. Several values can be separated by character ; (semicolon). A single value can be excluded by using a leading ! (explanation mark)
Examples:
| odata | All values are returned containing odata in the name |
| SE* | All values are returned starting with SE |
| SE*;AL* | All values are returned starting with SE ORAL |
| !Z* | All values are returned not starting with Z |
| !Z*;!Y* | All values are returned not starting with Z AND not starting with Y |
| SE*;!2 | All values are returned starting with SE AND not containing 2 |
Some filters must be entered as technical values and are case sensitive. It is recommended to check first how the result would look like by using no filter.
The number of data points, resolution and top rank are dependent from each other. To keep the UI responsive and avoid that to many data points need to be rendered, the Resolution is dependent on the selected time range.
Resolution
When resolution Auto is selected it depends on the selected time range:
| Time range | Resolution |
|---|---|
| > 7 days | Day |
| > 4 hours | Hour |
| < 4 hours | Minute |
No. of Data Points
By default the number of data points is limited to 2200.
Top Rank
if no top rank is specified it is calculated as an optimal based on the number of time stamps specified by the Resolution. If the result set would contain more distinct values per time stamp than the specified value or the calculated optimal Rank all other dimensions are aggregated to value Others.
Examples:
You define a resolution of 1 Minute and select a long time range. If the selected dimensions for aggregation leads to many different results the result set is truncated to the number of data points. As a result only the latest entries are returned and the beginning of the selected time range might be missing. By decreasing the Top Rank you get probably less entries per time stamp and therefore a longer time range.
Starting with FRUN 4.0 it is possible to propagate events between views on a customer dashboard. Consuming views react on a selection change in a source view.
Example: Creating a simple dashboard with two views.
The first view should display the number of executions of the top 20 Requests and the second view should display on a time axis the response times of the request name selected in the first view.
Step by step description
Click on Select Metrics and choose Executions
Go to tab Aggregation and remove the Aggregate flag for Request Name
Go to Rendering set the View Title to Executions and choose the Chart Type Bar.
Go to View Management and change the Grid Layout by adding a second column.
Add another Generic View
Under Data Source click on Select Metrics and choose Average Response Time
Go to Selected and set Time Aggregation to Average
Go to tab Aggregation and remove the Aggregate flag for Request Name
Go to Rendering set the View Title to Response Time.
Ensure that the configuration of the second view is still selected and go to Selection Propagation and click on add (+)
Choose
When now one line in the first view (Executions) is selected the chart in the second view (Response Times) is updated and only one request is displayed.