Show TOC

Function documentationEnd User Experience Monitor

 

The End User Experience Monitor allows you to do the following:

  • As a level 1 user, you can monitor the availability and response times of systems, from an end user perspective.

  • As a level 2 user, you can also run traces and analyze causes of bottlenecks or errors.

You can monitor the system data supplied by the EEMon robots using various graphical displays. These views are in default tabs. You can adjust the predefined tabs, or configure new tabs for your queries. Choose the views which are most useful to you. All views in one tab are different views of the same data.

You can specify how the data in each tab is formatted. You can:

  • specify a monitoring period, for example an hour

  • specify how the results are to be collated at EEMon robot or EEMon script level. You can summarize results by the following criteria:

    • The error code of the last run is displayed

    • The highest error code is displayed (worst case)

    • For availability, the highest error code is displayed, for performance, an error code which is the numerical mean of the runs

  • Specify whether response times are displayed at step level.

You can activate or deactivate the following views in the tabs:

Name

Query

Description

Overview

How do EEMon scripts behave in the various locations in the overview?

You get an overview of all EEMon scripts across all EEMon robots. It can, for example, be useful to create two instances of the view Overview, with worst case and mean values, in various tabs, for a current view of the status of your system landscape. Symbols indicate the status, and the type of any errors. For more information, see: Error Codes in End User Experience Monitor.

Script tile

Can a specified business process run at all locations?

For each EEMon script, the execution status is displayed for the individual EEMon robots. You can group the EEMon scripts; for example, you can group them by the significance of the business processes or by system role (production, test). You can use an appropriate graphic as background, to show the grouping criterion. For further information, see Adjust User Interface.

Robot tile

Can all business processes run at a specified location? You can, for example, check whether, and how, a network problem restricted the performance of a location.

For each EEMon robot, the EEMon scripts it performs are displayed, along with their execution status. For example, you can use a geographical map as background and sort the EEMon robots by the geographical distribution of their locations.

For further information, see Adjust User Interface.

Script and robot trees

With what availability and performance could specified business processes be performed at the various locations? In which steps did problems occur?

Shows the response times and aggregate status of the EEMon script runs, for each EEMon script per EEMon robot, or for each EEMon robot per EEMon script. You can show or hide the response times at EEMon script step level. You can adjust the processing load, depending on the frequency of execution and the period under consideration. If you perform a trace, you can analyze the trace data. For more information about performing traces, see Temporarily Change Error Analysis Parameters.

Status statistics

What percentage of the runs of a specified EEMon script in a specified EEMon robot have the statuses green, yellow, and red respectively?

The pie chart shows the percentages of each status. The number of runs on which the percentage is based, and the error code, in square brackets, are shown.

Refresh resets the assignment to an EEMon script or EEMon robot.

Response time

How do the response times of EEMon scripts change over time? Are the thresholds for some locations too low or too high? Is a bottleneck temporary, or does performance through time indicate a permanent infrastructure problem? Is EEMon script performance reduced because a certain step is critical?

You determine when bottlenecks occur. To determine whether a specific step is responsible for a performance problem, you can display the response times for entire scripts and individual steps. For deeper, cross-system and long-time trend analyses, you can analyze the SAP Solution Manager contents with SAP NetWeaver Business Warehouse (BW).

Script history

How often does an EEMon script run at each location, and with what result?

The timeframe shows the frequency and staus of the runs of a script. You can also show and hide summed EEMon script performance and availability data with the Option button.

Robot history

How often do EEMon scripts run at a specified location, and with what results?

The timeframe shows individual runs and their status. You can identify measurement gaps, and decide whether to change the frequency of measurement for specified business processes. For further information, see Adjust Parameters. You can also show and hide summed EEMon script performance and availability data with the Option button.

Tree browser

How long does, for example, a specified step of a business process take, at one location, or in comparison between two locations? What differences are there, for example, between functionally identical steps which had different performance in different EEMon scripts?

You query the system, and configure the tree hierarchy according to your requirements. There are query criteria under Configuration, in Column Repository, which you can Drag&Drop into the Tree Structure. You can adjust the column sequence in the tree browser, by Drag&Drop, until the data is in a meaningful sequence for you. You can compare, for example, just the “Logon” step in two EEMon scripts (prerequisite: you have assigned the same name to functionally identical steps in the design and realization of EEMon scripts in the EEMon editor). Or you can compare all Linux and Windows systems. You use the Tree Browser to display large amounts of data, from long monitoring periods clearly. You can create a tab for each query. Or you can position several Tree Browsers in one tab.

Prerequisites

  • The administrator has installed EEMon robots in user-near hosts at various locations.

  • The administrator has created EEMon scripts to simulate business processes and distributed them to the EEMon robots.

  • You have Level 1 or Level 2 user authorization.

Activities

  • Start EEMon

  • Configure End User Experience Monitor for your analyses or operations control

  • Run traces to identify the causes of errors

  • Load EEMon robot run log in the EEMon editor to identify the causes of errors

  • Display status of server trace data collection in application log

  • Export data as Microsoft Excel file

The end user experience monitoring data is also available in other applications. You can:

  • Analyze long-term data in SAP Netweaver BW.

  • Display EEMon alerts in the Unified Alert Inbox.