Setup Guide PerfMon

PerfMon: Techn.

Performance for

Reporting

with SAP Solution

Manager Release

7.1 SP5 and higher

Last Update November 2012

Setup Guide for Monitor

PerfMon: Techn. Performance for Reporting

© Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior

notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and

SQL Server® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®,

MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries,

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®,

Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM

are

trademarks of IBM Corp. in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1®, and Motif ® are registered trademarks of

the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood ®, MetaFrame®,

WinFrame®, VideoFrame®, MultiWin® and other Citrix product names

referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered

trademarks of W3C®, World Wide Web Consortium, Massachusetts

Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

J2EE™ is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc.,

used under license for technology invented and implemented by

Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business

Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE,

Management Cockpit, mySAP, mySAP.com, and other SAP products

and services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and in

several other countries all over the world. MarketSet and Enterprise

Buyer are jointly owned trademarks of SAP Markets and Commerce

One. All other product and service names mentioned are the

trademarks of their respective owners.

Disclaimer

Some components of this product are based on Java™. Any code

change in these components may cause unpredictable and severe

malfunctions and is therefore expressively prohibited, as is any

decompilation of these components.

Any Java™ Source Code delivered with this product is only to be used

by SAP’s Support Services and may not be modified or altered in any

way.

Documentation in the SAP Service Marketplace

You can find this documentation at the following address: http://service.sap.com/bpm

SAP AG

Neurottstraße 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

BPMon Analytics with SAP Solution Manager

May 2011 3

Table of Contents

1 INTRODUCTION AND MOTIVATION ....................................................................................................... 4

1.1 Monitoring Objects using Statistical Records for Performance ...................................................... 4

1.2 Further Setup Guides ............................................................................................................................ 5

2 TECHNICAL PREREQUISITES FOR EXTRACTION OF PERFORMANCE STATISTICS ...................... 6

2.1 Required Software Components .......................................................................................................... 6

2.2 Implement Business Process Analytics ............................................................................................. 6

2.3 Required SAP Notes.............................................................................................................................. 6

2.4 Activate BADI implementation ............................................................................................................. 6

2.5 Schedule report /SDF/BPM_REORG_TSTAD ..................................................................................... 7

3 SETUP DATA COLLECTION IN BPMON SETUP-TOOL ......................................................................... 8

3.1 Update Repository................................................................................................................................. 8

3.2 Create Performance Monitor ................................................................................................................ 9

3.3 Configure Performance Monitor ........................................................................................................ 10

3.4 Set Monitoring Schedule .................................................................................................................... 12

3.5 Activate Monitoring ............................................................................................................................. 13

3.6 Master Data Load................................................................................................................................. 13

3.7 Trend Analysis with Business Process Analytics ........................................................................... 14

3.8 Housekeeping of Data Storage in BPMon Analytics ....................................................................... 15

4 SETUP ALERTING IN BPMON SETUP-TOOL ....................................................................................... 16

4.1 On Business Process Step Create Application Monitor with Reference....................................... 16

4.2 Set Transaction, Key Figures and Thresholds for Alerting ............................................................ 17

4.3 Generate and Activate Customizing .................................................................................................. 18

4.4 Check Performance Key Figures in Alert Inbox ............................................................................... 19

5 BPO DASHBOARDS FOR REPORTING ON BUSINESS TRANSACTION PERFORMANCE ............. 21

5.1 Precondition for using BPO Dashboards ......................................................................................... 21

5.2 Access BPO Dashboards Applications............................................................................................. 21

5.3 Manage BPO Dashboards for Performance Key Figures ................................................................ 22

5.3.1 Analytical Key Figure Definition ................................................................................................ 22

5.3.2 Example Analytical Key Figure Definitions .............................................................................. 23

5.3.3 Example Panel Definitions .......................................................................................................... 25

5.3.4 Example Dashboard Definition .................................................................................................. 29

Trend Analysis Reporting with SAP Solution Manager

4 May 2011

1 Introduction and Motivation

The performance of the main business transactions is most crucial for the daily operations. Bad performance

of main business transactions can cause that

• dialog user have to wait for system response,

• business is delayed or even can't be performed,

• system load is increased and leads to hardware bottlenecks, so that the overall system slows down.

Therefore SAP recommends defining KPIs and thresholds for transaction performance. Required monitoring

activities should be defined including procedures to measure the KPIs on a regular basis. The expectations

have to be part of a service level agreement between the business units and the operation center.

Performance Monitoring within Business Process Operations Work Center in SAP Solution Manager assists

you to check these defined KPIs and to react on exceeded thresholds in time: Performance data of

transactions to be monitored are extracted from the managed system into SAP Solution Manager's BW.

Monitoring of transactions with specified key figures is defined, so that alerting on performance critical

situations is enabled, when the runtime related thresholds are reached.

Furthermore you can investigate if there is a trend with increasing response times of a transaction, or if there

are peaks depending of the weekday or seasons.

A dashboard based functionality is provided with the possibility to report on different time frames and key

figures. So it can be used for daily reporting, management reporting or for controlling specific Service Level

Agreements.

1.1 Monitoring Objects using Statistical Records for Performance

The SAP Solution Manager collects specified data from managed systems and makes it centrally available

for alerting and reporting. With Business Process Monitoring (BPMon) different kinds of monitoring objects

are offered, to retrieve technical and business data.

In this guide we will describe the setup of monitoring object 'PerfMon: Techn. Performance for Reporting'.

This monitor retrieves statistical performance data of the business transactions (like you can see it with

transaction STAD). It offers different key figures like average response time, average DB time, etc. and

different select options like transaction, function code, user, etc. The data are saved in Solution Manger

BW's Info Cubes. Functions for evaluation are provided with Business Process Analytics (BP Analytics) and

Business Process Operations Dashboards (BPO Dashboards).


May 2011 5

There are some other monitoring objects in BPMon, which can be used for retrieving statistical performance

data, too. We want to give an overview with advantages and disadvantages of each of these performance

monitors:

Monitor Name Monitoring Type / Techn. Name

Advantages Disadvantages

Dialog Performance

Dialog Performance - Very low impact on workload since CCMS infrastructure is used

- Selection with function code and user not available

- Only dialog transactions can be monitored

Dialog Performance Monitor

Application Monitor / BOPERFMO

- Selection possible with function code and user

- Dialog, RFC and HTTP monitoring possible

- High workload on the managed system, if many statistics are collected, especially if there are many applications servers and if many dialog steps are executed

PerfMon: Techn. Performance for Reporting

Application Monitor / PETPERF1

- Selection possible with function code and user

- Dialog and HTTP monitoring possible

- Impact on workload is low, since the data collection takes place via basis workload collector RSCOLL00

- Provides data in BP Analytics

- Delay of at least 2 hours until the data get visible in Business Process Monitoring

- RFC monitoring not yet possible

1.2 Further Setup Guides

In this setup guide we will explain how to set up the application monitor 'PerfMon: Techn. Performance for

Reporting'. This setup guide will not explain the general procedure for using and setting up BPMon, BP

Analytics and BPO Dashboards. The setup guides for BPMon, BP Analytics and BPO Dashboards are

available at http://www.service.sap.com/bpm in the “Media Library” under “Technical Information” and should

be regarded as basis documents for this setup guide.

There you also find the corresponding document that describes the setup for older releases, i.e. the Setup Guide - PerfMon: Techn. Perf. for Reporting 7.0 SP23+.

http://www.service.sap.com/bpm

http://www.service.sap.com/~sapidb/011000358700001295502012E/Setup_PerfMon_70_SP23.pdf

http://www.service.sap.com/~sapidb/011000358700001295502012E/Setup_PerfMon_70_SP23.pdf


6 May 2011

2 Technical Prerequisites for Extraction of Performance Statistics

As technical precondition for performance monitoring with the monitoring object monitor 'PerfMon: Techn.

Performance for Reporting' the statistical performance data extraction from the managed system into the

SAP Solutions Manager's BW has to be set up. For this the infrastructure provided by Business Process

Analytics is used. Additionally a BADI has to be activated in the managed system.

2.1 Required Software Components

In order to setup and use the monitoring object 'PerfMon: Techn. Performance for Reporting', the following

minimum releases of software components are necessary.

Solution Manager 7.0 SPS 23 (ST 400 SP23, BI_CONT 7.04 SP6, ST A/PI Type M)

Each connected managed system must have at least installed

o SAP_BASIS 700,

o ST-PI 2008_1_700 SP4

o ST-A/PI 01M* SP1

2.2 Implement Business Process Analytics

Business Process Analytics has to be implemented, see 'Setup Guide - Business Process Analytics' (at

http://www.service.sap.com/bpm in the “Media Library” under “Technical Information”).

This comprises:

Activation of Info Cube 0SM_BPMRH from BI Content in Solution Manager

Activation of the HTTP Services for Web Dynpro components

Activation of Solution Manager Diagnostics Extractor Framework (EFWK)

Authorizations for Business Process Analytics

Solution with defined systems and business processes

2.3 Required SAP Notes

Following corrections should be implemented (in addition to the SAP Notes mentioned in the 'Setup Guide -

Business Process Analytics'):

SAP Note Corrected with

1494650 BPMon: Wrong Alerting Values in new Performance Monitoring ST 400 SAPKITL435

1598647 BPMon: PerfMon: Reorganization of Table /sdf/bpm_tstad ST-PI 2008_1_700 SP5

2.4 Activate BADI implementation

In the managed system activate the implementation /SDF/BPM_STORE_STAD of the BADI

“WORKLOAD_STATISTIC”.

This BADI is called during the run of the report SWNCColl which is triggered by the RSColl00 mechanism.

The report SWNCColl is reading the STAD records from the application server instances. The task of the

BADI implementation is to store the STAD records for the transactions for which BPMon is activated into the

table /SDF/BPM_TSTAD.

Details how to activate the classic BAdI implementations in a SAP system:



May 2011 7

(1) Start transaction SE18, choose the radio button 'BAdI Name' and enter WORKLOAD_STATISTIC. Press

Display button.

(2) In menu 'Implementation' choose 'Change' and select /SDF/BPM_TSTAD by double click. Then activate

this implementation.

2.5 Schedule report /SDF/BPM_REORG_TSTAD

Schedule a daily job executing report /SDF/BPM_REORG_TSTAD with an appropriate variant to delete data

from the /SDF/BPM_TSTAD table. E.g. you can delete the statistical records that are older than 24 hours.

The BPMon Data Collector, that is normally scheduled hourly, has then already extracted the statistical data

to the Solution Manager BW.


8 May 2011

3 Setup Data Collection in BPMon Setup-Tool

In Business Process Monitoring you define, for which systems and for which transactions statistical

performance data are transferred into SAP Solution Manager's BPMon BW Info Cube. The Data Collection

can be set up in the Business Process Monitoring Setup Tool, which you can enter via Solution Manager

Workcenter.

3.1 Update Repository

The application monitor 'PerfMon: Techn. Performance for Reporting' is delivered with add-on ST-A/PI on the

managed systems. To make the monitor available in the SAP Solution Manager, the monitor definition need

to be transferred from the managed system to a central repository in the SAP Solution Manager System.

Below the node of your solution on the node “Logical Components” an update of the Central Application

Monitoring Repository is offered. To get the monitors available it is required to select the managed system

first and then to click the button “Load Monitor Definitions”.


May 2011 9

3.2 Create Performance Monitor

The logical component from which data should be collected for reporting has to be selected. For being visible

in the BPMon Setup-Tool the system and client combination has to be in the leading role for the solution.

Press button “Create” to create a new monitoring object.

A popup opens and allows selecting the monitor type for

data collection. Set a flag at “Cross Application".

Select the monitor 'PerfMon: Techn. Performance for

Reporting' from F4-Help. You can define your own

Monitoring Object Name.

Press „Ok‟.

The new monitoring object is now visible in the monitoring object list of the selected logical component.


10 May 2011

3.3 Configure Performance Monitor

Double click the monitoring object to open its configuration. On the tab “Monitoring Configuration” you have

to maintain the object parameters and select the desired key figures.

In the area “Parameters on Object Level” enter the transaction(s) that you want to monitor. Select the "Group

by" checkbox for the transaction parameter. You can also use the following parameters:

Report: Name of the ABAP report

Function code: The function code can be used to monitor separate steps of a transaction. The function code is also known as the "CUA internal command".

Call type: Type of statistical record such as DIA, BTC, RFC, or UPD


May 2011 11

User pattern: The user pattern allows you to restrict the selection of statistical records and consider only those that belong to specific users.

Instance: Application server instance

Threshold for Degr.: This parameter is valid only if you want to use one of the following key figures: "Total Runtime of Records Above Threshold", "Total DB Time of Records Above Threshold", or "Total CPI Time of Records Above Threshold". With these key figures, you can monitor the performance of dialog steps that have a runtime above the degradation threshold that you maintain using this parameter.

In the area “Key Figures” you define, which key figures to be evaluated.

For some of the key figures a threshold parameter has to be set. This allows monitoring the performance of

dialog steps that have a runtime above the degradation threshold that you maintain using this parameter.

Creating key figures for statistical records above a threshold makes sense in cases where transaction

runtime is regularly having runaway values, i.e. the transaction runtime regularly exceeds the average

runtime highly. It is not possible to monitor these sporadic increases in response time by only looking at the

average values. By using key figures with defined thresholds you can monitor the number and total runtimes

of these regularly runaways. In this way you can later set up alerting for the average response time values of

the transaction and for the runaway values, too.

Below pictures illustrate the necessity for using a degradation threshold. Although in both cases the average

response time is equal for the measured dialog steps, we have in the 2nd picture long running dialog steps,

which should be monitored.

Let's build a business example: The save operation of transaction VA01 - 'Create Sales Order' should be

monitored. In most executions (99%) the number of line items is very low. However there are some few big

customers ordering a lot and the response time for these orders is much higher. Because big orders have a

high value, they should be processed quickly. So you want to monitor the total runtime of these big orders.

With using a degradation threshold this is possible.

Below is the list of the performance monitoring related key figures (alert types) of Application Monitor

'PerfMon: Techn. Performance for Reporting'.

Key Figure Description

Avg. Runtime The "Avg. Runtime" key figure measures the average response time of the monitored transaction(s) within the penultimate full hour.


12 May 2011

Avg. Database Time

The "Avg. Database Time" key figure measures the average database time (part of the response time) of the monitored transaction(s) within the penultimate full hour.

Avg. CPU Time

The "Avg. CPU Time" key figure measures the average CPU time of the monitored transaction(s) within the penultimate full hour.

Avg. GUI Time

The "Avg. GUI Time" key figure measures the average GUI time (part of the response time) of the monitored transaction(s) during the penultimate full hour

Avg. Frontend Network Time

The "Avg. Frontend Network Time" key figure measures the average front end network time of the monitored transaction(s) during the penultimate full hour.

Total Runtime

The "Total Runtime" key figure measures the total runtime of the monitored transaction(s) during the penultimate full hour.

Total Database Time

The "Total Database Time" key figure measures the total database time of the monitored transaction(s) during the penultimate full hour.

Total CPU Time

The "Total CPU Time" key figure measures the total CPU time of the monitored transaction(s) during the penultimate full hour.

Total GUI Time

The "Total GUI Time" key figure measures the total GUI time of the monitored transaction(s) during the penultimate full hour.

Total Frontend Network Time

The "Total Frontend Network Time" key figure measures the total front end network time of the monitored transaction(s) during the penultimate full hour.

Number of Records

The "Number of records" key figure measures the number of statistical records (= number of dialog steps) of the monitored transaction(s) during the penultimate full hour.

Number of Records above Threshold

The key figure "Number of Records Above Threshold" measures the number of statistical records (= number of dialog steps) in the monitored transaction(s) during the penultimate full hour that have a longer runtime than the specified degradation threshold.

Total Runtime of Records above Threshold

The key figure "Total Runtime of Records Above Threshold" measures the total runtime for statistical records (= number of dialog steps) in the monitored transaction(s) during the penultimate full hour that have a longer runtime than the specified degradation threshold.

Total DB Time of Records above Threshold

The key figure "Total DB Time of Records Above Threshold" measures the total database time for statistical records (= number of dialog steps) in the monitored transaction(s) during the penultimate full hour that have a longer runtime than the specified degradation threshold.

Total CPU Time of Records above Threshold

The key figure "Total CPU Time of Records Above Threshold" measures the total CPU time for statistical records (= number of dialog steps) in the monitored transaction(s) during the penultimate full hour that have a longer runtime than the specified degradation threshold.

3.4 Set Monitoring Schedule

Within the tab “Monitoring Schedule” the user can decide how often a data collection should run.


May 2011 13

Normally you will want to monitor transactions during business hours. As period we suggest to enter 60

minutes. It does not make sense to decrease the period, as the data that are extracted from the managed

system are created hourly by basis report RSColl00.

3.5 Activate Monitoring

After you have set the sub checks of the monitor to 'Done' (green hook), generate and activate the

monitoring.

The extractor for the transactional data is started.

3.6 Master Data Load

A second extractor is needed for extracting the transaction related master data. The master data contains in

this case the transaction names in different languages.

Go to the node “Logical Components” and select the system where the extractor should run. Press the

button “Load BW Master Data”.


14 May 2011

In the popup flag the line with Semantic ID 'BC_TCODE' and press button "Load BW Master Data". The

status of the Master Data Load will be set to 'Scheduled'. After some minutes after pressing "Refresh" the

status will change to 'Loaded'.

3.7 Trend Analysis with Business Process Analytics

After the data collection has been set up and the data

extraction took place, you can evaluate the measured key

figures with Business Process Analytics. This is available via

a link under 'Common Tasks' in the left navigation area in the

BPO work center. In case performance problems with a

monitored transaction occur, you can check if there is a trend

with increasing response times of a transaction, or if there

are peaks depending of the weekday or seasons.

To display performance history:

1. Select a time frame (where data were already extracted).

2. Select the relevant application monitor.


May 2011 15

3. Select transaction.

4. Press button Trend Analysis.

3.8 Housekeeping of Data Storage in BPMon Analytics

To avoid problems during usage of BPMon Analytics with increasing response times of the BPMon Analytics

UI or with increasing growth of data storage use of Info Cube 0SM_BPMRH, especially its fact table

/BI0/F0SM_BPMRH, we recommend to activate a housekeeping for the Info Cube in BW according to SAP

Note 1514022 (BPMon Analytics - BW Housekeeping for Info Cube).


16 May 2011

4 Setup Alerting in BPMon Setup-Tool

In order to use Alerting based on the performance data available in the SAP Solution Manager's BPMon BW

Info Cube, the data collection had to be configured and activated before on the level of logical components in

the BPMon Setup-Tool as described above.

4.1 On Business Process Step Create Application Monitor with Reference

Access the BPMon Setup-Tool via the SAP Solution Manager work center for Business Process Operations.

Select first the relevant business process, then in the sub tree the relevant business process step. Press the

“Create” button.

A popup opens and allows selecting the monitor

type for alerting. Set a flag at “Cross Application".

Select the monitor 'PerfMon: Techn.

Performance for Reporting' from F4-Help. You

can define your own Monitoring Object Name.

Press „Ok‟.


May 2011 17

Since a monitoring object with the

same monitoring type was

created on the assigned logical

component already, you are

asked now, if you want to create

the monitoring object with a

reference to the existing

monitoring object.

Press button “Yes”.

The new monitoring object is now visible in the monitoring object list of the selected business step. The

alerting will retrieve the data from the referenced object defined for the logical component.

4.2 Set Transaction, Key Figures and Thresholds for Alerting

Double click the monitoring object to open its configuration. On the tab “Monitoring Configuration” you have to maintain the object parameters, the desired key figures and the thresholds for each selected key figure.


18 May 2011

You may have configured to collect the performance data of several transactions into the SAP Solution Manager's BW. On business step level you can filter for specific transactions now. „Transaction‟ is the only dimension offered on the level of logical components. Other selection criteria for restricting the collected data can be defined in the referenced monitoring object on the level of the logical component, but not on business step level.

Select the key figures you want to configure alerting for. See details in section 3.3.

Enter the thresholds for yellow and red alerts.

Proceed with defining Notifications, Analysis Tools and Monitoring Team as for non BW based alerting.

4.3 Generate and Activate Customizing

To finalize the configuration of the monitoring object for alerting generate and activate the customizing.


May 2011 19

4.4 Check Performance Key Figures in Alert Inbox

The Alert Inbox is the central point for Alert handling. If set up, email notifications on alerts can be sent out

with customized messages to the operator automatically. From the email the operator has direct access to

the alert inbox.

Below is a screenshot of the Alert Inbox that shows alerts regarding performance.

The alert message contains information about the measured value of the key figure, e.g. the average

response time of a transaction of the penultimate hour. With the alert list you can see the measured values

of all preceding hours.


20 May 2011

For details on the Alert Inbox see the corresponding chapter in the “Setup Guide - Business Process

Monitoring”, that is available at http://www.service.sap.com/bpm in the “Media Library” under “Technical

Information”.



May 2011 21

5 BPO Dashboards for Reporting on Business Transaction Performance

The BPO Dashboards provide the possibility to report on different time frames and key figures. So it can be used for daily reporting, management reporting or for controlling specific Service Level Agreements.

The general setup guide for BPO Dashboards is available at http://www.service.sap.com/bpm.

In the next sections we will describe with some examples, how to set up the BPO Dashboards for reporting on business transaction performance key figures.

5.1 Precondition for using BPO Dashboards

Implement all notes required for your Solution Manager release as described in the setup guide for BPO Dashboards, implement the coding enhancements mentioned in SAP Notes 1599307 and 1610692.

BP Analytics needs to be setup.

Setup the monitor 'PerfMon: Techn. Performance for Reporting' for the relevant key figures as described in the preceding sections.

5.2 Access BPO Dashboards Applications

You can open the setup and the display application for BPO Dashboards via the Business Process Operations Workcenter.



22 May 2011

5.3 Manage BPO Dashboards for Performance Key Figures

The BPO Dashboards are defined in three steps: key figure definition, panel definition and dashboard definition.

5.3.1 Analytical Key Figure Definition

The analytical key figures define the view you want to have on the available collected performance data. Technically the data are located in the cube 0SM_BPMRH in Solution Manager system.

See below the analytical key figure definition screen.

Let‟s go through the different elements, that have to be maintained for performance key figures.

You have to assign the analytical key figure to a specific repository name representing a key figure definition in BPMon. The key figure definitions of the monitor 'PerfMon: Techn. Performance for Reporting' belong to the repository names containing the string „PETPERF1‟.


May 2011 23

Select the key figure you want to report on.

As category you can select a time unit like hour, day, week and month.

As drilldown you can use the transaction code. If you want to use rating tables you must declare a characteristic for drilldown, as on this characteristic the rating thresholds are defined.

With filters the displayed data are restricted. Use filters on

time, e.g. relative filter on yesterday, the last seven days, last 4 weeks, last month or last quarter

transaction, if several transactions are monitored with the identical monitoring object or if you want to define rating thresholds depending on the transaction code

monitoring ID to assign the correct monitoring object defined in the BPMon Setup-Tool to the analytical key figure

Performance data are collected by different monitor objects, which are configured in the BPMon Setup-Tool. You may have several monitoring objects of type 'PerfMon: Techn. Performance for Reporting', e.g. if you want to monitor performance key figures of different countries separately. When setting up the BPO dashboards, you need to set filters on these monitoring objects via the monitoring ID.

See example definitions below.

5.3.2 Example Analytical Key Figure Definitions

All defined example key figures report on the average response time of transaction CIC0.

Example Analytical Key Figure 1: We use category „Calendar Day‟ and filtering on the last 7 days to report an average response time of the


24 May 2011

last 7 days per day.

Relative filter used for CALDAY:

For the transaction code „CIC0' rating thresholds are maintained.

Example Analytical Key Figure 2: With Category „Time (hh)‟ and filtering on yesterday we report the average response times yesterday per


May 2011 25

hour.

We maintained rating thresholds on transaction code „CIC0'.

5.3.3 Example Panel Definitions

Based on the above two analytical key figure types we built several panels with several analytical key figures e.g. analytical key figure 1 assigned to the panel. Each analytical key figure is assigned to a monitoring object, which collects statistical data for a group of users working in a specific region. Important is that the users of different regions can be identified via the user prefix and therefore in the monitoring object configuration the selection criterion „User Pattern‟ can be used.


26 May 2011

Example Panel 1: Trend Chart

This is the displayed panel. The measured average response times of different regions can be compared.


May 2011 27

Example Panel 2: Dynamic Rating Table

This is the displayed panel. The response times of the different regions with ratings are displayed in different columns. The defined rating threshold can be different for each region.


28 May 2011

Example Panel 3: Stacked Column Chart The panel is built on example analytical key figure 2.

This is the displayed panel


May 2011 29

Example Panel 4: Dynamic Rating Table This panel is built on example analytical key figure 2.

This is the displayed panel

5.3.4 Example Dashboard Definition

This is a dashboard definition containing the 4 example panels.


30 May 2011

With the dashboard type you define how the panels are organized on the dashboard.

The daily performance values from the last week are displayed in the first row, the hourly performance values from yesterday are displayed in a second row.

Setup Guide PerfMon

Documents

Transcript of Setup Guide PerfMon