2405432 - Using the Performance Metrics Portal

SAP Knowledge Base Article - Public

2405432 - Using the Performance Metrics Portal

Symptom

This KBA will provide information on the Perfomance Metrics Portal

Environment

BizX

Resolution

Using the Performance Metrics Portal

You can query performance and usage data directly from the UI.
The left pane presents the monitored performance metrics divided into two sections:

System Usage Reports
● Login Count
● Daily Active Users
● Search Terms
● Locations
● Browsers 
● Devices

System Performance Reports
● Transactions
● Page Performance
● Modules
● Session Time

The right pane presents the usage and performance data graphically based on the selected timeframe.

perfmetrics.JPG

Figure 1: Performance Metrics Portal

 

Below the graph, a table with the instances having the highest volume of the selected metric appears. The entries in the table can be sorted or filtered by clicking on a column header, and entering value criteria.

perf2.JPG

 

Timeframes
You can select a timeframe (Last 30 days, Last 7 days, and Last 24 hoursfrom the dropdown box on the toolbar above the graph.

 PERF3.png

 Figure 2: Timeframe

Graphs that are shown with entries having month/week granularity can be drilled down into day/hourly granularity by clicking on the date in the X-axis. Clicking on a date will show an hourly-based graph.

System Usage Reports

  • Login Count

The report for Login Count enables you to see the number of login transactions in your system.

You can drill-down in the graph from month/week timeframe to day/hourly data by clicking on the desired bar.

The metrics presented in the graph are:

Volume - the number of logins.
Average Data Center Time - the time that each transaction spent in the data center, after the initial entry point (first load balancer).

perf4.png

Figure 3: Login Count Report

 

  • Daily Active Users

The report for Daily Active Users enables you to see the number of total visits, in addition to the unique visits per day in your system.

You can drill-down in the graph from month/week timeframe to day/hourly data by clicking on the desired bar.

The metrics presented in the graph are:
- Date
- Volume - the total number of active user logins displayed as a bar graph.
- Unique Volume - the number of unique active users logins displayed as a line graph.

i Note

The Last 7 days and Last 30 days timeframe filter display each day as an individual entry on the horizontal axis. Therefore, if we have a scenario where there same set of five users login every day, the unique count for each of the days would be 5, and the daily chart will show 5 daily active users. However, you will not know if those are the same unique logins on a daily basis.

To provide this information, a count of the unique users in the given timeframe is displayed next to the timeframe filter.

perf5.png

Figure 4: Daily Active Users

 

  • Serach Terms

The report for Search Terms allows you to see the most frequently searched terms in the system. It also provides the total number of search results for each search term.

You can drill down in the graph from month/week timeframe to day/hourly data by clicking on the desired bar.

The metrics presented in the graph are:

Catalog - the number of search results for LMS catalog searches
Action/People - the number search results for action or people search terms
Other - the number of search terms that do not fall into the first two categories

Below the graph is a table that includes the following details about the results:

- Search Term
- Type
- Volume (Count)
- Percentage
- Search Result Count

 

Search Terms3.1.4.JPG

Figure 5: Search Terms

  • Locations

The report for Locations provides you with a map view and a table view of the locations from which your customers are accessing the application.

The metrics presented in the table are:

Location - the location of the customer accesssing the application.
Volume - the number of transactions per location.
Average End User Time - the sum of data center time and network time.
Average Network Time - the time it took the transaction to go from the customer network to the data center.
Average Data Center Time - the time that each transaction spent in the data center, after the initial entry point (first load balancer).

fig6.JPG

Figure 6: Location Report

  • Browsers

The report for Browsers provides a breakdown of the browser types being used to access the application.

You can drill-down in the graph from month/week timeframe to daily/hourly data by clicking on the desired bar.

The metrics presented in the graph and table are:
Browser - the type of browser used to access the application.
Volume - the number of transactions.
Average End User Time - the sum of data center time and network time.
Average Network Time - the time it took the transaction to go from the customer network to the data center.
Average Data Center Time - the time that each transaction spent in the data center, after the initial entry point (first load balancer).

 

fig7.JPG

Figure 7: Browser Report

 

  • Devices

The report for Devices provides a breakdown of the device types being used to access the application.

You can drill-down in the graph from month/week timeframe to daily/hourly data by clicking on the desired bar.
The metrics presented in the graph and table are:
Device - the type of device used to access the application.
Volume - the number of transactions.
Average End User Time - the sum of data center time and network time.
Average Network Time - the time it took the transaction to go from the customer network to the data center.
Average Data Center Time - the time that each transaction spent in the data center, after the initial entry point (first load balancer).

 

fig8.JPG

Figure 8: Devices Report

System Performance Reports

  • Transactions

The report for Transactions (the end-to-end service) allows you to view the various network and data center response times.

You can filter the data by choosing a specific Module from the filter dropdown.

You can also drill-down in the graph from month/week timeframe to day/hourly data by clicking on the desired bar.

The metrics presented in the graph and table are:
Transactions - the list of end-to-end services identified in the report.
Volume - the number of transactions.
Average Data Center Time - the time that each transaction spent in the data center, after the initial entry point (first load balancer).
Average Network Time - the time it took the transaction to go from the customer network to the data center.
Average End User Time - the sum of data center time and network time.NoteOthers that appears in the report, refers to a list of transactions that do not have a logical label assigned to them. Each transaction is built originally from the URL that was invoked, which was not something easily readable. Therefore, we grouped all of these unlabeled transactions into the Others bucket.

i Note

 Others that appears in the report, refers to a list of transactions that do not have a logical label assigned to them. Each transaction is built originally from the URL that was invoked, which was not something easily readable. Therefore, we grouped all of these unlabeled transactions into the Others bucket.

fig9.JPG

Figure 9: Transactions

  • Page Performance

The report for Page Performance allows you to see how long it takes for your pages and content to render and load.

You can drill down in the graph from month/week timeframe to day/hourly data by clicking on the desired bar.
The metrics presented in the graph and table are:
Pages - name of the pages in the report.
Volume - number of pages.
Average Page Load Time - total time required to load a complete page.
Average Base Page Time - average time required to load the main request of a page.
Average Page Content Time - average time to load static content requests.
Average Page Render Time - average time to render the entire page.NoteOthers that appears in the report, refers to a list of pages that do not have a logical label assigned to them. Each page is built originally from the URL that was invoked, which was not something easily readable. Therefore, we grouped all of these unlabeled transactions into the Others bucket.

fig10.JPG

Figure 10: Page Performance Report

  • Modules

The report for Modules (a set of transactions, such as Employee Central) allows you to view the various network and data center response times.

You can drill down in the graph from month/week timeframe to day/hourly data by clicking on the desired bar.

The metrics presented in the graph are:
Modules - name of modules identified in the report.
Volume - number of transactions per module.
Average End User Time - the sum of data center time and network time.
Average Network Time - the time it took the transaction to go from the customer network to the data center.
Average Data Center Time - the time that each transaction spent in the data center, after the initial entry point (first load balancer).

iNote

Others that appears in the report, refers to an aggregated list of transactions that are unknown. OTHERS that appear in the report, are known transactions but they have not been assigned to a specific module.

fig11.JPG

Figure 11: Modules Report

 

  • Session Time

The report for Average Session Time allows you to view the average time each user session lasts and the number of sessions.

You can drill down in the graph from month/week timeframe to day/hourly data by clicking on the desired bar.

The metrics presented in the graph are:
Date - the date of the session.
Average Session Time - the average time each user session lasts.
Session Count - number of sessions.

 fig12.JPG

Figure 12: Session Time Report

See Also

 Using the Usage Analytics Page

Keywords

Usage Analytics, Performance Metrics , KBA , LOD-SF-PLT , Foundational Capabilities & Tools , How To

Product

SAP SuccessFactors HCM Suite all versions