Enter Case number reference for associated cases.
Type: APM as a Service
Old Article ID: 4912
Old Article Type: diagnostic
QA has confirmed with Last Mile Development that the calculating logic of average response time in the DataView summary page under Synthetic Mobile is different than the average response time in the site detail page.
The average response times are not always the same on these 2 pages. This is a design issue.
You can execute the following stored procedures
1 Summary page
exec ulm_dataview_qry1 @monitor_id = 574977, @fromdate = '1/25/2013', @todate = '1/26/2013', @account_id = 10279, @gmtOffset = -300
2 Detail page
exec ulm_dataview_qry3 @monitor_id = 574977, @daysback = 33, @report_type = 'DVMonitorByDate', @account_id = 10279, @gmtOffset = -300
- Dynatrace Classic Portal
- Synthetic Monitoring Mobile
Occasionally you may notice what appears to be a discrepancy in the DataView section of Synthetic Mobile for Average Response Time.
When you look at the summary under DataView for a specific test, you will note a total Average Response Time for a specific day. When you click on the blue link for that day you are brought into a DataView page that shows the breakdown for that day by mobile peer. At the bottom of the column is the total Average Response Time for all peers. This number may not equal the number for total Average Response Time that you saw on the previous summary page.
To view the numbers: 1) Go to the Performance Tests tab in the GPN
2) Click on Synthetic Mobile
3) Click on DataView
4) Click on a mobile test
5) Notate the Average Response time for a specific day in this summary page
6) Click on the blue link for that day to dive deeper to the details
7) Look next to Total and see the Average Response Time of that day in the details section.
This is working as designed.
The average response time of the summary section does not always match the average response time of the details section once you dive deeper. This is why:
In the summary page, the total response time is calculated such that a test's response time will be set to 0 if 1 page failed.
In the detail page, the response time is calculated differently. A test's response time will set to 0 only if there are no successful pages throughout the test transaction.
That is why you may see a different total response time for the two pages.