The data terms used by RUEI are explained in Table E-1. Note that the following conventions are used:
Data and dimension level items for which no value is found or assigned by RUEI processing will be represented as "(no value)" in the RUEI UI, including dashboards, reports, and the data browser. At the database level, such values are stored as database NULL values.
Items that contain "(%)" represent percentages. For example, "Error hits (%)" represents the percentage of hits that had errors associated with them.
Items that contain "per" in their title represent averages. The text after "per" indicates its scope. For example, "content errors per session" represents the average number of content errors detected per user session.
Items that contain "P95 (%)" are averages with a percentile limit of 95% applied. This removes extreme values at the highest end before taking the average and, therefore, provides a more reliable indication.
Items that do not contain "per" or "(%)" represent totals. For example, "Failed hits" represents the total number of hits that for any reason resulted in an error.
Table E-1 Data Terms
Item | Descriptions |
---|---|
Aborted |
The number of user flows that were aborted. |
Aborted User Flows (%) |
Percentage of user flows that were aborted. |
Active Time on Ended Userflow |
Active time in ended user flow. |
Active Users |
A list of active user names. |
Active on Step |
Actions that did not change the state of the user flow. |
Activity Inside User Flow |
The number of user flows where activity was seen when end-users where inside the user flow definition. |
Activity Moving Outside User Flow |
The number of user flows where activity was seen when end users where moving outside the user flow definition. |
Activity Without An Error on Step |
The number of activities seen on the step without any (technical) error. |
Activity on Step |
The number of step activities (page views related to activity in the step). |
Apdex per Call |
Apdex is a method for calculating and reporting a metric of transactional application response time in the form of an index with a value of 0 to 1. This number is calculated as an average per call, where a failed / poor satisfaction is reported as 0, a OK satisfaction as 0.5 and a good as 1. |
Application Hits |
The total number of objects. |
Application Hits per Day |
The average number of requested objects for pages in a day. |
Application Hits per Hour |
Hits per hour |
Application Hits per Minute |
Hits per minute |
Application Hits per Page |
The average number of requested objects for a page. |
Application Hits per Second |
Hits per second |
Application Hits per Session |
The average number of requested objects during a client session. |
Application Hits per Session |
The average number of requested objects during a client session. Based on the number of concurrent sessions. |
Application Hits per Session |
The average number of requested objects during a client session. Based on the number of started sessions. |
Application Violation Calls |
The total number of poor webservice calls and Web site, network, server, and content errors detected. |
Application Violation Calls (%) |
The percentage of webservice calls for which poor page views and Web site, network, server, and content errors were detected. |
Application Violation Page Views |
The total number of poor page views and Web site, network, server, and content errors detected during a session. |
Application Violation Page Views |
The total number of poor page views and Web site, network, server, and content errors detected. |
Application Violation Page Views (%) |
The percentage of page views for which poor page views and Web site, network, server, and content errors were detected. |
Application Violations |
The total number of poor page views and Web site, network, server, and content errors detected during userflow activity. |
Application Violations(%) |
The percentage of page views for which poor page views and Web site, network, server, and content errors were detected. |
Average Active Time per User Flow |
Transaction active duration time in each user flow. |
Average Duration per User Flow |
Transaction duration time in each user flow. |
Average Idle Time per User Flow |
Transaction idle duration time in each user flow. |
Average Monetary Value per Flow |
The monetary value upon end per flow. |
Average Outside Time per User Flow |
Transaction outside duration time in each user flow. |
Average Page Load Time per Ended Flow |
The average loading time per ended flow during userflow activity. |
Average Page Views per Ended Flows |
The average number of page views per flow during userflow activity. |
Avg Monetary Value on Complete |
The average monetary value of user flows upon completion. |
Avg Monetary Value on Failure |
The average monetary value loss on the abortion or session timeout of the user flow. |
Avg Page Load Time per Step Summed |
The average monetary value loss on the abortion or session timeout of the user flow. |
Browser Busy Time (%) |
The percentage of delay time (in milliseconds) of the total end to end time due to browser activity at the client end. This is, the period during which the client TCP window size is indicated as 0. |
Browser Busy Time per Hit |
The average delay time (in milliseconds) per hit due to browser activity at the client end. This is, the period during which the client TCP window size is indicated as 0. |
Browser Busy Time per Page |
The average delay time (in milliseconds) per page due to browser activity at the client end. This is, the period during which the client TCP window size is indicated as 0. |
Browser Complete Time |
The average time between request start and the time when the user agent sets the current document readiness to "complete". |
Browser Exceptions |
The number of exceptions that were recorded by the browser. |
Browser Hits |
The number of objects on a page as being measured by the Browser JS Library. |
Browser Interactive Time |
The average time between the moment the user agent starts establishing the connection to the server and moment the page becomes interactive for the user. |
Browser Response Time |
The average time taken for the user agent to receive first byte of data from the server. |
Browser Time |
The average time taken, after receipt, for a page to be loaded by client browser |
Calls |
The total number of service function calls. |
Cancelled User Flows |
The number of stopped user flows (either due to abortion or session timeout). |
Client Abort Application Hits |
Client abort hits |
Client Abort Application Hits |
Client abort hits |
Client Abort Calls |
The number of service function calls where the client aborted the transfer, because the client closed the connection while the function was still loading. |
Client Abort Calls (%) |
Percentage of service function calls where the client aborted the transfer, possibly because the client closed the browser, or clicked reload, or clicked away, while the function was still loading. |
Client Abort Page Views |
The number of page views where the client aborted the transfer, possibly because the client closed the browser, or clicked reload, or clicked away, while the page was still loading. |
Client Abort Page Views |
The total number of page views during a session where the client aborted the transfer, possibly because the client closed the browser, or clicked reload, or clicked away, while the page was still loading. |
Client Abort Page Views (%) |
Percentage of page views where the client aborted the transfer, possibly because the client closed the browser, or clicked reload, or clicked away, while the page was still loading. |
Client Aborts per Session |
Total number of page views per session where the client aborted the transfer, possibly because the client closed the browser, or clicked reload, or clicked away, while the page was still loading. |
Client Data |
The number of bytes sent from the client to the Web server. |
Client Packets |
The number of packets sent from the client to the Web server. |
Client Time per Call |
The total delay time per service function call due to activity at the client end. |
Collection Error Calls |
The number of service calls where a data collection error was encountered, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Error Calls (%) |
The percentage of service calls where a data collection error was encountered, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Error Hits |
The number of hits where a data collection error was encountered, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Error Hits (%) |
The percentage of hits where a data collection error was encountered, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Error Page Views |
The number of page views where a data collection error was encountered, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Error Page Views |
The total number of page views where a data collection error was encountered, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Error Page Views (%) |
The percentage of page views where a data collection error was encountered, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Error Views (%) |
The percentage of views where a data collection error was encountered, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Error on Step |
The number of steps where a data collection error was encountered (considering only step activities), possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Errors |
There was an error during data collection, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Errors Ended Flows (%) |
The percentage of times a data collection error was encountered while analyzing a userflow activity. |
Collection Errors Ended User Flows |
The number of times a data collection error was encountered while analyzing a userflow activity. |
Completed User Flows |
The number of completed user flows. |
Completed User Flows (%) |
Percentage of completed user flows. |
Content Error Calls |
The number of times a content error was determined during a service function call. |
Content Error Calls (%) |
The percentage of service function calls for which a content error was determined. |
Content Error Page Views |
The number of page views for which a content error was determined. |
Content Error Page Views |
The total number of page views during a session that a content error was determined upon page display. |
Content Error Page Views (%) |
The percentage of page views for which a content error was determined upon page display. |
Content Error Views (%) |
The percentage of page views for which a content error was determined. |
Content Error on Step |
The number of content errors seen on step (considering only step activities). |
Content Errors |
The predefined content string was not found, or an error string was found, on the page. For example, the page should contain the string "Welcome to our Web site", but this was not found. |
Content Errors Ended Flows(%) |
The percentage of page views for which a content error was determined during userflow activity. |
Content Errors Ended User Flows |
The predefined content string was not found, or an error string was found, on the page. For example, the page should contain the string "Welcome to our Web site", but this was not found during userflow activity. |
Content Errors per Session |
The average number of times during a session that a content error was determined upon page display. |
Content Notification Function Calls |
The number of function calls for which a content notifcation was determined. |
Content Notification Function Calls (%) |
The percentage of function calls for which a content notifcation was determined. |
Content Notification Page Views |
The number of page views for which a content notifcation was determined. |
Content Notification Page Views |
The total number of page views during a session that a content notifcation was determined upon page display. |
Content Notification Page Views (%) |
The percentage of page views for which a content notifcation was determined. |
Content OK Calls |
The number of times a predefined content string was found during a service function call. |
Content OK Calls (%) |
The percentage of service function calls for which a predefined content string was found. |
Content OK Page Views |
The number of times a predefined content string was found upon page display. |
Content OK Page Views (%) |
The percentage of page views for which a predefined content string was found upon page display. |
Content Size per Call |
The average size (in bytes) of the raw content of an object in a service function call. |
Content Size per Hit |
The average size (in bytes) of the content of an object. |
Content Size per Page |
The average size (in bytes) of all objects (excluding the header) on a page. |
Cookie Seen (%) |
The percentage of page views that could be identified from a session-specific tracking scheme. Sessions that could not be identified via cookies or other schemes are identified by IP address, in combination with browser-specific information. |
Database Time (%) |
The percentage of database response time in the total end to end time. |
Database Time per Hit |
The average database response time (in milliseconds) of an object. |
Database Time per Page |
The average database response time (in milliseconds) of a page. |
Delayed Log Ratio (%) |
The percentage of Collector log files which had a processing delay associated with them. |
Denominator |
The number used as denominator to calculate the KPI value (depends on KPI metric). |
Duration Time on Ended Userflow |
Duration time in ended user flow. |
Duration per (Started) User Flow |
The time spent in this user flow. It is calculated as the sum of the page loading and reading times, divided by the number of started user flows. |
Duration per Transition |
The time spent on this step. It is calculated as the sum of the page loading and reading times, divided by the number of transitions. |
Dynamic Application Hits per Page |
The average number of dynamic objects on a page. |
Dynamic Content Size per Hit |
The average content size (in bytes) of dynamic objects. |
Dynamic Content Size per Page |
The average content size (in bytes) of all dynamic objects on a page. |
Dynamic End to End Time per Page |
The average combined dynamic network time and dynamic server response time for all objects within a displayed page. |
Dynamic Header Size per Hit |
The average size (in bytes) of all dynamic objects in the header part of an HTTP request. |
Dynamic Header Size per Page |
The average total size (in bytes) of all headers for dynamic objects on a page. |
Dynamic Network Time per Hit |
The average time (in milliseconds) taken for a dynamic object to be transferred over the network. Note that this includes both request and response transmission. |
Dynamic Network Time per Page |
The average time (in milliseconds) taken for all dynamic objects within a page to be transferred over the network. Note that this includes both request and response transmission. |
Dynamic Server Time per Hit |
The average server response time (in milliseconds) for a dynamic object within a page. |
Dynamic Server Time per Page |
The average server response time (in milliseconds) for all dynamic objects within a page. |
Dynamic Size per Hit |
The average size (in bytes) of a requested dynamic object. |
Dynamic Size per Page |
The average total size (in bytes) of all dynamic objects within a page. |
Dynamic Time per Hit |
The average end-to-end time (in milliseconds) for all dynamic objects. |
Dynamic Time per Page |
The average time (in milliseconds) for all dynamic objects on the page. |
End to End Time |
The end-to-end time of a pageview |
End to End Time per Call |
The average combined network time and server response time for an object within a service function call. |
End to End Time per Call P95 |
The average combined network time and server response time for an object within a service function call, with a percentile limit of 95% applied. This removes extreme values at the highest end and, therefore, provides a more reliable indication. |
End to End Time per Hit |
The average combined network time and server response time for an object within a displayed page. |
End to End Time per Page |
The average combined network time and server response time for all objects within a displayed page. |
End to End Time per Page P95 |
The average combined network and server response time for all objects within a displayed page, with a percentile limit of 95% applied. This removes extreme values at the highest end and, therefore, provides a more reliable indication. |
Ended User Flows |
Numbers of ended user flow. |
Ended User Flows |
The number of ended user flows (by completion, abortion, or session timeout). |
Error (%) on Step |
The percentage of errors seen on step (considering all step activities). |
Error Application Hits |
The number of hits that had errors associated with them. |
Error Application Hits (%) |
The percentage of hits that had errors associated with them. |
Error Calls |
The total number of service function calls that for any reason were not successfully invoked. |
Error Calls (%) |
The percentage of service function calls that for any reason were not successfully invoked. |
Error Page Views |
The total number of page views that for any reason were not successfully displayed. |
Error Page Views (%) |
The percentage of page views that for any reason were not successfully displayed. |
Error Page Views Ended Flows |
The total number of page views that for any reason were not successfully displayed during userflow activity. |
Error Page Views Ended Flows(%) |
The percentage of page views that for any reason were not successfully displayed during userflow activity. |
Error on Step |
The number of errors seen step (considering only step activities). |
Errors per Session |
The average number of service function call errors that occurred during a session. |
External Time (%) |
The percentage of response time spend for external calls in the total end to end time. |
External Time per Hit |
The average response time (in milliseconds) spend for external calls of an object. |
External Time per Page |
The average response time (in milliseconds) spend for external calls of a page. |
Failed Application Hits |
The total number of hits that for any reason resulted in an error. |
Failed Calls |
The number of service function calls with errors. This could be because the server did not respond at all, responded with an HTTP response code 400-599, the network timed-out, required content was not found, or a site error has been found. |
Failed Views |
The total number of page views with errors. This could be because the server did not respond at all, responded with an HTTP result code 400-599, the network timed-out, required content was not found, or a site error has been found. |
Flow Transitions |
The number of transitions (moves) in the user flow that change the status. That is, all actions that do not lead to the current step being repeated. |
Good Application Hits |
The number of hits whose loading time was within the defined threshold. |
Good Calls |
The number of service function calls that had an end-to-end time (that is, all server and network times) below the specified threshold. |
Good Page Views |
The number of page views for which the page loading time was within the defined page-loading satisfaction threshold. |
Good Page Views (%) |
The percentage of page views for which the page loading time was within the defined page-loading satisfaction threshold. |
Good Page Views Ended Flows |
The number of page views for which the page loading time was within the defined page-loading satisfaction threshold during userflow activity. |
Good Page Views Ended Flows(%) |
The percentage of page views for which the page loading time was within the defined page-loading satisfaction threshold during userflow activity. |
Good Step Activities |
The number of step activities that were loaded into the client browser within the defined page-loading satisfaction threshold. |
Header Size per Call |
The average size (in bytes) of the header of a requested object in a service function call. |
Header Size per Hit |
The average size (in bytes) of the header of a requested object. |
Header Size per Page |
The average size (in bytes) of the header of a page. |
Hours |
The number of hours |
Idle Returns |
Returns to the user flow after a delay of at least the configured step idle time. When a session time-out is reached, it is also marked as step idle. This ensures that idle out and idle in can be related directly. |
Idles |
There was no activity by the end-user for at least the configured step idle time. |
KPI Average Value |
The average value of a KPI. |
KPI Down Time |
The total downtime (in minutes) for a KPI. |
KPI Entity |
The KPI calculation period. |
KPI Failures (%) |
The percentage of time spent during which the KPI was in a failing state. |
KPI Max Target |
The maximum target for the KPI at calculation. |
KPI Min Target |
The minimum target for the KPI at calculation. |
KPI Success |
Indicator of the KPI's current status (OK, failing, or undefined). |
KPI Success (%) |
The percentage of time spent during which the KPI was in a successful state. |
KPI Up Time |
The total uptime (in minutes) for a KPI. |
Last User Flow Step Number |
The total number of steps defined for this user flow. |
Max Logout Page Views |
The maximum logout page views. |
Max Page Load Time |
The maximum load time. |
Max Resolution Time |
The longest period of time during which the KPI was outside its configured boundaries. |
Max Step Number |
The highest user flow step number (used for step number calculations). |
Median Dynamic End to End Time |
The median combined dynamic network time and dynamic server response time for all objects within a displayed page. |
Median Dynamic Size |
The median size (in bytes) for all dynamic objects. |
Median End to End Time |
The median combined network time and server response time for an object. |
Median Page Browser Time |
The median browser time of all pages. |
Median Page Load Time |
The median loading time of all pages. |
Median Page Network Time (%) |
The median percentage of end-to-end time for page views spend in network transfer time to deliver all info |
Median Page Read Time |
The median time from which the last requested object for a page has been loaded into the client browser, and the client requests another page. |
Median Page Server Time (%) |
The median percentage of end-to-end time for page views spend in server to process all necessary info |
Median Static End to End Time |
The median combined static network time and static server response time for all objects within a displayed page. |
Median Static Size |
The median size (in bytes) of all static objects, including header and body. |
Monetary Value on Stopped User Flows |
The total monetary value that was "lost" due to session timeout. |
Network Error Application Hits |
The number of network errors determined for objects. |
Network Error Application Hits (%) |
The percentage of objects for which network errors were determined. |
Network Error Calls |
The number of times a network error was determined during a service function call. |
Network Error Calls (%) |
The percentage of times a network error was determined during a service function call. |
Network Error Page Views |
The number of times a network error was determined upon page display. |
Network Error Page Views |
The total number of times during a session that a network error was determined upon page display. |
Network Error Page Views (%) |
The percentage of times a network error was determined upon page display. |
Network Error Views (%) |
The percentage of times a network error was determined during page views. |
Network Error on Step |
The number of network errors seen on the step(considering only step activities). |
Network Errors |
Network errors are hits which were not delivered completely from the TCP level view. Possible reasons are a server-related problem with the connection, or a server time-out occurs when a server fails to respond to a client request. |
Network Errors Ended Flows |
The number of times a network error was determined upon page display during userflow activity. |
Network Errors Ended Flows(%) |
The percentage of times a network error was determined upon page display during userflow activity. |
Network Errors per Session |
The average number of times a network error was determined during a session. |
Network OK Calls |
The number of service function calls were no network error was determined. |
Network OK Calls (%) |
The percentage of service function calls during which no network error was determined. |
Network OK Page Views |
The number of pages were no network error was determined during page display. |
Network OK Page Views (%) |
The percentage of page views during which no network error was determined. |
Network Time |
The network time of a pageview |
Network Time (%) |
The percentage of network time in the total end to end time for pages. |
Network Time per Call |
The average time taken for an object to reach the client browser after reply from the server during a service function call. |
Network Time per Call P95 |
The average time taken for an object to reach the client browser after reply from the server during a service function call, with a percentile limit of 95% applied. This removes extreme values at the highest end and, therefore, provides a more reliable indication. |
Network Time per Hit |
The average time taken for an object to reach the client browser after reply from the server. |
Network Time per Page |
The average time (in milliseconds) taken for all threads in a network to reach the client. |
Network Time per Page Ended Flows |
The average time (in milliseconds) taken for all threads in a network to reach the client during userflow activity. |
Network Time per Page P95 |
The average time (in milliseconds) taken for all threads in a network to reach the client, with a percentile limit of 95% applied. This removes extreme values at the highest end before taking the average and, therefore, provides a more reliable indication. |
Network Timeout Application Hits |
The number of network time-outs determined for objects. |
Network Timeout Application Hits (%) |
The percentage of objects for which network time-outs were determined. |
Network Timeout Calls |
The number of service function calls during which a network time-out occurred. |
Network Timeout Calls (%) |
The percentage of service function calls during which a network time-out occurred. |
Network Timeout Page Views |
The number of page views during which a network time-out occurred. |
Network Timeout Page Views (%) |
The percentage of page views during which a network time-out occurred. |
Numerator |
The numerator used to calculate the KPI value. Its selection depends on the KPI metric. |
OK Application Hits |
The number of objects that had an end-to-end time (that is, all server and network times) of less than the specified poor threshold, but higher than the good threshold. That is, the object request, while not optimal, was OK. |
OK Calls |
The number of service function calls that had an end-to-end time (that is, all server and network times) of less than the specified function call poor threshold, but higher than the good threshold. That is, the function calling, while not optimal, was OK. |
OK Page Views |
The number of page views that were loaded into the client browser within a time greater than the defined page loading good threshold, but less than the poor threshold. That is, the page loading, while not optimal, was OK. |
OK Page Views (%) |
The percentage of page views that were loaded into the client browser within a time greater than the defined page loading good threshold, but less than the poor threshold. That is, the page loading, while not optimal, was OK. |
OK Page Views Ended Flows |
The number of page views that were loaded into the client browser within a time greater than the defined page loading good threshold, but less than the poor threshold during userflow activity. That is, the page loading, while not optimal, was OK. |
OK Page Views Ended Flows(%) |
The percentage of page views that were loaded into the client browser within a time greater than the defined page loading good threshold, but less than the poor threshold during userflow activity. That is, the page loading, while not optimal, was OK. |
OK Step Activities |
The number of page views that were loaded into the client browser within a time greater than the defined page loading good threshold, but less than the poor threshold. That is, the page loading, while not optimal, was OK. (looking at step activities) |
Outside |
The number of times the end-user performed activities that did not match the user flow/step definition. |
Outside Returns |
Actions that brought the end-user back inside the user flow. |
Page Apdex |
Apdex is a method for calculating and reporting a metric of transactional application response time in the form of an index with a value of 0 to 1. This number is calculated as an average per page, where a failed / poor satisfaction is reported as 0, a OK satisfaction as 0.5 and a good as 1. |
Page Download Time |
The average time taken for a page from page start till last object loaded. |
Page External Download Time |
The average time taken for a page, from page start till last object loaded, from perspective of browser. |
Page Internal Download Time |
The average time taken for a page, from page start till last object loaded, from perspective of the RUEI process. |
Page Load Time |
The average loading time per page during a session. |
Page Load Time |
The average loading time per page. |
Page Load Time Ended Flows |
The average loading time per page during userflow activity. |
Page Load Time P95 |
The average loading time (in seconds) per page, with a percentile limit of 95% applied. This removes extreme values at the highest end before taking the average and, therefore, provides a more reliable indication. |
Page Load Time per Page Ended Flows |
The average page load time (in seconds) per page during userflow activity. |
Page Loadtime per Transition |
The average page load time (in seconds) per transition. |
Page Loadtime per User Flow |
The average page load time (in seconds) per user flow (based on the total page load time and the number of started user flows). |
Page Network Time (%) |
The percentage of network time in the total end to end time for pages. |
Page Read Time |
The average time from which the last requested object for a page has been loaded into the client browser, and the client requests another page. |
Page Read Time P95 |
The average time (in seconds) from which the last requested object for a page has been loaded into the client browser, and the client requests another page, with a percentile limit of 95% applied. This removes extreme values at the highest end before taking the average and, therefore, provides a more reliable indication. |
Page Sequence Number |
The sequence number of a page view within a session. |
Page Server Time (%) |
The percentage of server time in the total end to end time for pages. |
Page Views |
The total number of page views during a session. |
Page Views |
The total number of page views. |
Page Views Ended Flows |
The total number of page views during userflow activity. |
Page Views per Day |
The average number of page views per day. |
Page Views per Hour |
The average number of page views per hour. |
Page Views per Session |
The average number of page views per session. |
Page Views per Session |
The average number of pageviews per session. Based on the number of concurrent sessions. |
Page Views per Session |
The average number of pageviews per session. Based on the number of started sessions. |
Percentage of Aborted Flows |
The percentage of flows that were ended prematurely through abort condition that was met |
Percentage of Completed Flows |
The percentage of flows that were successfully completed |
Percentage of Stopped Flows |
The percentage of flows that were ended prematurely through session timeout |
Percentage of Success Flows |
The percentage of flows that were successfully completed |
Poor Application Hits |
The number of objects that had an end-to-end time of greater than the specified poor threshold. |
Poor Calls |
The number of service calls that had an end-to-end time of greater than the specified service function call poor threshold. |
Poor Page Views |
The number of page views where the client had to wait longer than the specified page-poor threshold for the page to load. |
Poor Page Views |
The total number of page views during a session where the client had to wait longer than the specified page-poor threshold for the page to load. |
Poor Page Views (%) |
The percentage of page views where the client had to wait longer than the specified page-poor threshold to load in the client browser. |
Poor Page Views Ended Flows |
The number of page views where the client had to wait longer than the specified page-poor threshold for the page to load during userflow activity. |
Poor Page Views Ended Flows(%) |
The percentage of page views where the client had to wait longer than the specified page-poor threshold to load in the client browser during userflow activity. |
Poor Step Activities |
The number of step activities that took longer than the specified page-poor threshold to load in the client browser. |
Progress Off Completion |
The difference between the number of completions and the average number of transitions to a next step. |
Progress from Previous Step |
The number of times the end-user progressed from the previous step to this step. |
Progress per Step |
The number of transitions to a next step divided by the maximum number of steps. |
Progress to Next, Skipping Current |
The number of times the end-user progressed from the previous step to a further step, bypassing the current step. |
Progressed |
The number of transitions resulting from movement up or down the user flow. |
Reply Content Size per Call |
The average size (in bytes) of the response body for an object in a service function call. |
Reply Content Size per Hit |
The average size (in bytes) of the response body for an object. |
Reply Header Size per Call |
The average size (in bytes) of the response header for an object in a service function call. |
Reply Header Size per Hit |
The average size (in bytes) of the response header for an object. |
Reply Size per Call |
The average size (in bytes) of the response header and body for an object in a service function call. |
Reply Size per Hit |
The average size (in bytes) of the response header and body for an object. |
Request Content Size per Call |
The average size (in bytes) of the request body for an object in a service function call. |
Request Content Size per Hit |
The average size (in bytes) of the request body for an object. |
Request Header Size per Call |
The average size (in bytes) of request header for an object in a service function call. |
Request Header Size per Hit |
The average size (in bytes) of request header for an object. |
Request Size per Call |
The average size (in bytes) for the request header and body for an object in a service function call. |
Request Size per Hit |
The average size (in bytes) for the request header and body for an object. |
Request Time per Call |
The average response time (in milliseconds) for a service function call. |
Request Time per Hit |
The average time taken (in milliseconds) for an object. |
Returns from Next Step |
The number of times the end-user returned from the next step to this step. |
Returns from Next, Skipping Current |
The number of times the end-user returned from the next step to an earlier step, bypassing the current step. |
SLA Daily Result |
The average daily value of an SLA. |
SLA Daily Target |
The defined daily level of the SLA's service agreement. |
SLA Down Time |
The total downtime of an SLA (in minutes). |
SLA Entity |
The SLA calculation period. |
SLA Failures (%) |
The percentage of SLA failure. |
SLA Friday |
Indicates whether an SLA was successfully achieved for all Fridays. |
SLA Max Value |
The maximum target for the SLA. |
SLA Min Value |
The minimum target for the SLA. |
SLA Monday |
Indicates whether an SLA was successfully achieved for all Mondays. |
SLA Monthly Result |
Indicates whether the SLA was successfully achieved on a monthly basis. |
SLA Monthly Target |
The defined monthly level of the SLA's service agreement. |
SLA Result |
Indicates whether the SLA has been achieved for the selected period. |
SLA Saturday |
Indicates whether an SLA was successfully achieved for all Saturdays. |
SLA Success (%) |
The percentage of SLA success for the selected period. |
SLA Sunday |
Indicates whether an SLA was successfully achieved for all Sundays. |
SLA Target |
The defined level of the SLA's service agreement. |
SLA Thursday |
Indicates whether an SLA was successfully achieved for all Thursdays. |
SLA Tuesday |
Indicates whether an SLA was successfully achieved for all Tuesdays. |
SLA Up Time |
The total time (in minutes) that the SLA has been up. |
SLA Wednesday |
Indicates whether an SLA was successfully achieved for all Wednesdays. |
SLA Weekly Result |
Indicates whether the SLA was successfully achieved on a weekly basis. |
SLA Weekly Target |
The defined weekly level of the SLA's service agreement. |
SLA Yearly Result |
Indicates whether the SLA was successfully achieved on a yearly basis. |
SLA Yearly Target |
The defined yearly level of the SLA's service agreement. |
Server Abort Application Hits |
The number of times a server abort was determined during an object request. This can arise for a number of reasons, including the server reset the connection, the server sent incorrect data, or the client disappeared unexpectedly. |
Server Abort Application Hits (%) |
The percentage of objects for which a server abort was determined. |
Server Abort Calls |
The number of times a server abort was determined during a service function call. This can arise for a number of reasons, including the server reset the connection, the server sent incorrect data, or the client disappeared unexpectedly. |
Server Abort Calls (%) |
The percentage of service function calls for which a server abort was determined. |
Server Abort Page Views |
The number of times a server abort was determined upon page display. This can arise for a number of reasons, including the server reset the connection, the server sent incorrect data, or the client disappeared unexpectedly. |
Server Abort Page Views (%) |
The percentage of page views for which a server abort was determined. |
Server Data |
The number of bytes sent between the server and the client. |
Server Error Application Hits |
The number of objects for which a server error was determined. Server errors are objects that result in the HTTP response code 500-599. |
Server Error Application Hits (%) |
The percentage of objects for which a server error was determined. Server errors are objects that result in the HTTP response code 500-599. |
Server Error Calls |
The number of times a server error was determined during a service function call. |
Server Error Calls (%) |
The percentage of service function calls for which a server error was determined. |
Server Error Ended Flows(%) |
The percentage of page views for which a server error was determined upon display during userflow activity. |
Server Error Page Views |
The number of times a server error was determined upon page display. |
Server Error Page Views |
The total number of times during a session that a server error was determined upon page display. |
Server Error Page Views (%) |
The percentage of page views for which a server error was determined upon display. |
Server Error Views (%) |
The percentage of page views for which a service error was determined. |
Server Error on Step |
The number of server errors (looking at step activities only) |
Server Errors |
Server errors are hits that result in an HTTP error code 500-599. |
Server Errors Ended Flows |
The number of times a server error was determined upon page display during userflow activity. |
Server Errors per Session |
The average number of server errors that were determined upon page display during a session. |
Server Packets |
The number of packets sent between the server and the client. |
Server Time |
The server time of a pageview |
Server Time (%) |
The percentage of server time in the total end to end time for pages. |
Server Time Ended Flows |
The total server response time (in milliseconds) during userflow activity. |
Server Time per Call |
The average server response time per service function call. |
Server Time per Call P95 |
The average server response time per service function call, with a percentile limit of 95% applied. This removes extreme values at the highest end and, therefore, provides a more reliable indication. |
Server Time per Hit |
The average server response time per hit. |
Server Time per Page |
The average server response time (in milliseconds) per page. |
Server Time per Page Ended Flows |
The average server response time (in milliseconds) per page during userflow activity. |
Server Time per Page P95 |
The average server response time (in milliseconds) per page, with a percentile limit of 95% applied. This removes extreme values at the highest end before taking the average and, therefore, provides a more reliable indication. |
Server Timeout Application Hits |
The number of objects for which a server timeout was determined. A server time-out occurs when a server fails to reply to a client request. That is, no response, or part there of, is ever sent. |
Server Timeout Application Hits (%) |
The percentage of objects for which a server timeout was determined. A server time-out occurs when a server fails to reply to a client request. That is, no response, or part there of, is ever sent. |
Server Timeout Calls |
The number of server time-outs that were determined during a service function call. A server time-out occurs when a server fails to reply to a client request. That is, no response, or part there of, is ever sent. |
Server Timeout Calls |
The number of server time-outs that were determined during a service function call, with a percentile limit of 95% applied. This removes extreme values at the highest end before taking the average and, therefore, provides a more reliable indication. A server time-out occurs when a server fails to reply to a client request. That is, no response, or part there of, is ever sent out. |
Server Timeout Page Views |
The number of page views for which a server timeout was determined. A server time-out occurs when a server fails to reply to a client request. That is, no response, or part there of, is ever sent. |
Server Timeout Page Views |
The number of page views for which a server timeout was determined, with a percentile limit of 95% applied. This removes extreme values at the highest end and, therefore, provides a more reliable indication. A server time-out occurs when a server fails to reply to a client request. That is, no response, or part there of, is ever sent out. |
Session Duration |
The average session duration (in seconds). |
Session Duration |
The average session duration (in seconds). Based on the number of concurrent sessions. |
Session Duration |
The average session duration (in seconds). Based on the number of started sessions. |
Session End Time |
Session end time |
Session Load Time |
The average time (in seconds) spent loading pages per session. |
Session Load Time |
The average time (in seconds) spent loading pages per session. Based on the number of concurrent sessions. |
Session Load Time |
The average time (in seconds) spent loading pages per session. Based on the number of started sessions. |
Session Read Time |
The average time (in seconds) spent viewing pages per session. This is the time taken between the page (and all its objects) being loaded, and the next page request. In other words, the time available for the visitor to read the page. |
Session Read Time |
The average time (in seconds) spent viewing pages per session. This is the time taken between the page (and all its objects) being loaded, and the next page request. In other words, the time available for the visitor to read the page. Based on the number of concurrent sessions. |
Session Read Time |
The average time (in seconds) spent viewing pages per session. This is the time taken between the page (and all its objects) being loaded, and the next page request. In other words, the time available for the visitor to read the page. Based on the number of started sessions. |
Session Start Time |
Session start time |
Session Time per Page |
The average time (in seconds) spent on a page during a session. |
Session Time per Page P95 |
The average time (in seconds) spent on a page during a session, with a percentile of 95% applied. This removes extreme values at the highest end before taking the average and, therefore, provides a more reliable indication. |
Sessions |
The number of sessions. Each time a visitor comes to your web site (after a gap of at least 15 minutes) is counted as a new session. Based on the number of started sessions. |
Sessions |
The number of sessions. Each time a visitor comes to your web site (after a gap of at least 15 minutes) is counted separately. Based on the number of concurrent sessions. |
Sessions |
The number of sessions. Each time that a visitor comes to your web site (after a gap of at least 15 minutes) a session is counted. |
Sessions on First Step |
The number of sessions that show the first step in the user flow. |
Sessions on Last Step |
The number of sessions that show the last step in the user flow. |
Sessions on Step |
The number of sessions that show the selected user flow. |
Sessions per Day |
The average number of sessions per day. |
Size per Call |
The average size (in bytes) of the request and response for an object in a service function call. |
Size per Hit |
The average size (in bytes) of the request and response for an object. |
Start Time |
The start time of the (first) session |
Started User Flows |
The number of started user flows. |
Static Application Hits per Page |
The average number of static objects on a page. |
Static Content Size per Hit |
The average size (in bytes) of a requested static object within the body. |
Static Content Size per Page |
The average total size (in bytes) of all static objects within the header of a page. |
Static End to End Time per Page |
The average combined static network time and static server response time for all objects within a displayed page. |
Static Header Size per Hit |
The size (in bytes) of all static objects within the header of an object. |
Static Header Size per Page |
The average total size (in bytes) of all static objects within the header of a page. |
Static Network Time per Hit |
The average time (in milliseconds) taken for a static object to reach the client browser after reply from the server. |
Static Network Time per Page |
The average time (in milliseconds) taken for all static objects within a page to reach the client browser after reply from the server. |
Static Server Time per Hit |
The average server response time (in milliseconds) for a static object within a page. |
Static Server Time per Page |
The average total server response time (in milliseconds) for all static objects within a page. |
Static Size per Hit |
The average size (in bytes) of a requested static object. |
Static Size per Page |
The average total size (in bytes) of all static objects within a page. |
Static Time per Hit |
The average end-to-end time (in milliseconds) for all dynamic objects. That is, the sum of their network and server response times. |
Static Time per Page |
The average end-to-end time (in milliseconds) for all static objects on the page. That is, the sum of their network and server response times. |
Stats Status Code |
Indicates the status of TCP traffic monitored during a snapshot. See Verifying Monitored Network Traffic. |
Step Changes |
Actions that brought the end-user one step further/back in the user flow (including start and complete). |
Step Number |
The number of the step within the user flow. |
Stopped User Flows |
The number of user flows that ended due to session timeout. |
Stopped User Flows (%) |
Percentage of user flows that ended due to session timeout. |
Success Application Hits |
The number of objects that were successfully loaded within the defined satisfaction threshold. |
Success Percentage |
Percentage of completed user flows within progressed user flows (max 100%). |
Success Ratio |
The user flow success ratio (calculated by dividing the number of completed user flows by the number of progress transitions). |
Test Dynamic Network Time |
The time (in milliseconds) for all dynamic objects within service test (beacon) traffic to be transferred over the network. |
Test Dynamic Server Time |
The server response time (in milliseconds) for service test (beacon) traffic. |
Test Load Time |
The time (in seconds) to load pages within service test (beacon) traffic. |
Test Network Error Page Views (%) |
The percentage of page views within service test (beacon) traffic for which a network error was determined. |
Test Page Views |
The number of page views within service test (beacon) traffic. |
Test Read Time |
The time (in seconds) within service test (beacon) traffic from the last requested page object having been loaded by the client, and the client requesting another page. |
Test Server Error Page Views (%) |
The percentage of page views for which an error was determined within service test (beacon) traffic. |
Test Sessions |
The number of sessions within service test (beacon) traffic. |
Test Static Network Time |
The time (in milliseconds) for static objects within service test (beacon) traffic to be transferred over the network. |
Test Static Server Time |
The server response time (in milliseconds) for static objects within service test (beacon) traffic. |
Test Traffic Application Page Views |
The total number of poor page views, Web site, network, server, and content errors detected within service test (beacon) traffic. |
Test Traffic Collection Error Page Views (%) |
The percentage of page views where a data collection error was encountered while analyzing a service test (beacon) traffic. |
Test Traffic Content Error Page Views (%) |
The percentage of page views within service test (beacon) traffic for which a content error was determined. |
Test Traffic User Violations |
The total number of content notifications and client aborts detected with service test (beacon) traffic. |
Test Traffic Violation Page Views |
The percentage of page views for which user and application violations were detected within service test (beacon) traffic. |
Test Traffic Web Site Error Page Views (%) |
The percentage of page views for which an error was determined within service test (beacon) traffic. |
Test Visit Time |
The time (in seconds) for sessions within service test (beacon) traffic. |
The Number of Days |
The number of days |
Throughput |
Total throughput on the server (in KB/sec). |
Time Spent per Flow |
The average time spent per flow |
Total Active Time Spent in Flow |
Total active time in completed user flow. |
Total Browser Busy Time |
The time taken (in milliseconds), after receipt, for a page to be loaded by the client browser. |
Total Client Time |
The total delay time (in milliseconds) due to activity at the client end. |
Total Collection Error Percentage on Abort |
Percentage of collection errors on aborted user flows. |
Total Collection Error Percentage on Cancel |
Percentage of collection errors on stopped user flows. |
Total Collection Error Percentage on Completed |
Percentage of completed user flows that contained collection errors. |
Total Collection Error Percentage on Stopped User Flows |
The percentage of collection errors seen on session timeout. |
Total Collection Error on Abort |
Total number of collection errors on aborted user flows. |
Total Collection Error on Cancel |
Total number of collection errors on stopped user flows. |
Total Collection Error on Completed |
Total number of collection errors on completed user flows. |
Total Collection Error on Stopped User Flows |
Total number of collection errors seen at session timeout. |
Total Content Error Percentage on Abort |
Percentage of content errors on aborted user flows. |
Total Content Error Percentage on Cancel |
Percentage of content errors on stopped user flows. |
Total Content Error Percentage on Completed |
Percentage of completed user flows that contained content errors. |
Total Content Error Percentage on Stopped User Flows |
The percentage of content errors seen on session timeout. |
Total Content Error on Abort |
Total number of content errors on aborted user flows. |
Total Content Error on Cancel |
Total number of content error on stopped user flows. |
Total Content Error on Completed |
Total number of content errors on completed user flows. |
Total Content Error on Stopped User Flows |
Total number of content errors seen at session timeout. |
Total Content Size |
The body size (in bytes) of the page. |
Total Count |
The total number of the session. |
Total Database Time |
Total total database time (in milliseconds). |
Total Dynamic Application Hits |
The total number of dynamic objects. |
Total Dynamic Content Size |
The total body size (in bytes) for all dynamic objects. |
Total Dynamic Header Size |
The total header size (in bytes) for all dynamic objects. |
Total Dynamic Network Time |
The total network time (in milliseconds) taken for all dynamic objects. |
Total Dynamic Server Time |
The total server response time (in milliseconds) taken for all dynamic objects. |
Total Dynamic Size |
The total size (in bytes) for all dynamic objects. |
Total Dynamic Time |
The total time (in milliseconds) for all dynamic objects. |
Total End to End Time |
The total end-to-end time (in milliseconds). This includes both the network transfer time and the server response time. |
Total Error Percentage on Abort |
Percentage of all errors on aborted user flows. |
Total Error Percentage on Cancel |
Percentage of total errors on stopped user flows. |
Total Error Percentage on Completed |
The percentage of errors on completed user flows. |
Total Error Percentage on Stopped User Flows |
Percentage of errors seen at session timeout. |
Total Errors on Abort |
Total number of errors on aborted user flows. |
Total Errors on Cancel |
Total number of errors on stopped user flows. |
Total Errors on Completed |
Total number of errors on completed user flows. |
Total Errors on Stopped User Flows |
Total number of errors seen at session timeout. |
Total External Time |
The total response time (in milliseconds) taken by external calls. |
Total Good Page Views on Abort |
Total number of good page views on aborted user flows. |
Total Good Page Views on Cancel |
Total number of good page views on stopped user flows. |
Total Good Page Views on Completed |
Total number of good page views on completed user flows. |
Total Good Page Views on Stopped User Flows |
Total number of good user flow page views at session timeout. |
Total Good Percentage on Abort |
Percentage of good page views on aborted user flows. |
Total Good Percentage on Cancel |
Percentage of good page views on stopped user flows. |
Total Good Percentage on Completed |
The percentage of good page views on completed user flows. |
Total Good Percentage on Stopped User Flows |
Percentage of good user flow page views at session timeout. |
Total Header Size |
The header size (in bytes) of the page. |
Total Idle Time Spent in Flow |
Total idle time in completed user flow. |
Total Monetary Value |
The total monetary value |
Total Monetary Value on Abort |
The total monetary value that was lost due to end-users aborting the user flow. |
Total Monetary Value on Complete |
The total monetary value gained through completed user flows. |
Total Monetary Value on Failure |
The total monetary value loss on the abortion or session timeout of the user flow. |
Total Network Error Percentage on Abort |
Percentage of network errors on aborted user flows. |
Total Network Error Percentage on Cancel |
Percentage of network errors on stopped user flows. |
Total Network Error Percentage on Completed |
The percentage of network errors on completed user flows. |
Total Network Error Percentage on Stopped User Flows |
Percentage of network errors seen for user flows at session timeout. |
Total Network Errors on Abort |
Total number of network errors on aborted user flows. |
Total Network Errors on Cancel |
Total number of network errors on stopped user flows. |
Total Network Errors on Completed |
Total number of network errors on completed user flows. |
Total Network Errors on Stopped User Flows |
Total number of network errors at session timeout. |
Total Network Time |
The total network transfer time (in milliseconds). |
Total Network Time on Abort |
Total network time (in milliseconds) spent on aborted user flows. |
Total Network Time on Cancel |
Total network time spent on stopped user flows. |
Total Network Time on Completed |
Total network time (in milliseconds) spent on completed user flows. |
Total Network Time on Stopped User Flows |
Total network time (in milliseconds) spent on user flows at session timeout. |
Total OK Page View Percentage on Abort |
Percentage of OK page views on aborted user flows. |
Total OK Page View Percentage on Cancel |
Percentage of OK page views within stopped user flows. |
Total OK Page View Percentage on Completed |
Percentage of OK page views on completed user flows. |
Total OK Page View Percentage on Stopped User Flows |
Percentage of OK user flow page views on session timeout. |
Total OK Page Views on Abort |
Total number of OK page views on aborted user flows. |
Total OK Page Views on Cancel |
Total number of OK page views within stopped user flows. |
Total OK Page Views on Completed |
Total number of OK page views on completed user flows. |
Total OK Page Views on Stopped User Flows |
The number of OK user flow page views on session timeout. |
Total Object Size per Page |
The average total size (in bytes) for all objects within a page view. |
Total Outside Time Spent in Flow |
Total outside time in completed user flow. |
Total Page Load Time |
The total time (in milliseconds) for all page views to be processed by the client browser. |
Total Page Load Time on Abort |
Total page-load time (in seconds) spent on aborted user flows. |
Total Page Load Time on Cancel |
Total page-load time (in seconds) spent on stopped user flows. |
Total Page Load Time on Completed |
Total page load time (in seconds) spent on completed user flows. |
Total Page Load Time on Stopped User Flows |
Total page-load time (in seconds) for user flows at session timeout. |
Total Page Read Time |
The total time (in seconds) from which the last requested object for a page has been loaded into the client browser and the client requests another page. |
Total Page Views on Abort |
Total number of page views on aborted user flows. |
Total Page Views on Cancel |
Total number of page views on stopped user flows. |
Total Page Views on Completed |
Total number of page views on completed user flows. |
Total Page Views on Ended Userflows |
Total number of page views on ended user flows. |
Total Page Views on Stopped User Flows |
Total number of user flow page views at session timeout. |
Total Poor Page Views on Abort |
Total number of poor page views on aborted user flows. |
Total Poor Page Views on Cancel |
Total number of poor page views on stopped user flows. |
Total Poor Page Views on Completed |
Total number of poor page views on completed user flows. |
Total Poor Page Views on Stopped User Flows |
Total number of poor page views seen for user flows at session timeout. |
Total Poor Percentage on Abort |
Percentage of poor page views on aborted user flows. |
Total Poor Percentage on Cancel |
Percentage of poor page views on stopped user flows. |
Total Poor Percentage on Completed |
The percentage of poor page views on completed user flows. |
Total Poor Percentage on Stopped User Flows |
Percentage of poor page views seen for user flows at session timeout. |
Total Reply Content Size |
The total size (in bytes) of all response body parts. |
Total Reply Header Size |
The total size (in bytes) of all response header parts. |
Total Reply Size |
The total size (in bytes) of all replies, including both header and body. |
Total Request Content Size |
The total size (in bytes) of all request body parts. |
Total Request Header Size |
The total size (in bytes) of all request header parts. |
Total Request Size |
The total size (in bytes) of all requests, including both header and body. |
Total Request Time |
The total time (in milliseconds) for all requests. |
Total Server Error Percentage on Abort |
Percentage of server errors on aborted user flows. |
Total Server Error Percentage on Cancel |
Percentage of server errors on stopped user flows. |
Total Server Error Percentage on Completed |
The percentage of server errors on completed user flows. |
Total Server Error Percentage on Stopped User Flows |
Percentage of user flow server errors seen at session timeout. |
Total Server Errors on Abort |
Total number of server errors seen on aborted user flows. |
Total Server Errors on Cancel |
Total number of server errors on stopped user flows. |
Total Server Errors on Completed |
Total number of server errors on completed user flows. |
Total Server Errors on Stopped User Flows |
Total number of user flow server errors seen at session timeout. |
Total Server Time |
The total server response time (in milliseconds). |
Total Server Time on Abort |
Total server time (in milliseconds) spent on aborted user flows. |
Total Server Time on Cancel |
Total server time (in milliseconds) spent on stopped user flows. |
Total Server Time on Completed |
Total server time (in milliseconds) spend on completed user flows. |
Total Server Time on Stopped User Flows |
The total server time (in milliseconds) spent on user flows at session timeout. |
Total Session Time |
The total time (in seconds) of all sessions. |
Total Static Application Hits |
The total number of all static objects. |
Total Static Content Size |
The total size (in bytes) of all static object body sections. |
Total Static Header Size |
The total size (in bytes) of all static header sections. |
Total Static Network Time |
The total network transfer time (in milliseconds) of all static objects. |
Total Static Server Time |
The total server response time (in milliseconds) of all static objects. |
Total Static Size |
The total size (in bytes) of all static objects, including header and body. |
Total Static Time |
The total network and server time (in milliseconds) for all static objects. |
Total Time Spent in Flow |
The total time spent in flow |
Total Traffic |
The total size (in bytes) of all pages and their objects. |
Total Transfer Time |
The total time (in milliseconds) taken to reach the client after reply from the server. |
Total Web Site Error Percentage on Abort |
Percentage of Web site errors on aborted user flows. |
Total Web Site Error Percentage on Cancel |
Percentage of Web site errors within stopped user flows. |
Total Web Site Error Percentage on Completed |
Percentage of Web site errors on completed user flows. |
Total Web Site Error Percentage on Stopped User Flows |
Percentage of user flow Web site errors on session timeout. |
Total Web Site Errors on Abort |
Total number of Web site errors on aborted user flows. |
Total Web Site Errors on Cancel |
Total number of Web site errors within stopped user flows. |
Total Web Site Errors on Completed |
Total number of Web site errors on completed user flows. |
Total Web Site Errors on Stopped User Flows |
Total number of user flow Web site errors on session timeout. |
Traffic per Day |
The average daily size (in bytes) of all pages and their objects. |
Traffic per Session |
The average total size (in bytes) of all pages and their objects during the session. |
Traffic per Session |
The average total size (in bytes) of all pages and their objects during the session. Based on the number of concurrent sessions. |
Traffic per Session |
The average total size (in bytes) of all pages and their objects during the session. Based on the number of started sessions. |
Transaction Step Number |
The sequence of a step within a user flow. |
Transfer Time (%) |
The percentage of time (in milliseconds) taken to reach the client after reply from the server in the end to end time. |
Transfer Time per Call |
The average time (in milliseconds) taken for a service function call to reach the client after reply from the server. |
Transfer Time per Hit |
The average time (in milliseconds) taken for an object to reach the client browser after reply from the server. |
Transfer Time per Page |
The average time (in milliseconds) taken for all objects on the page to reach the client browser after reply from the server. |
Transitions |
Actions that brought the end user one step further/back in the user flow (including start and complete). |
Transitions to Next Step |
The number of transitions to the next user flow step (including start and complete). |
Transitions to Previous Step |
The number of transitions to the previous step. |
User Dynamic Network Time |
The time (in milliseconds) for dynamic objects to be transferred across the network within service test (real-user) traffic. |
User Dynamic Server Time |
The server response time (in milliseconds) for dynamic objects within service test (real-user) traffic. |
User Flow Completion (%) |
The percentage of user flows started during sessions that were successfully completed. |
User Flow Load Time |
The total loading time (in seconds) for all pages in the user flow. |
User Flow Network Time |
The total network transfer time (in milliseconds) for all pages in the user flow. |
User Flow Page Views |
The number of page views within the user flow. |
User Flow Read Time |
The total read time for all pages in a user flow (between the last requested object for a page being loaded into the client browser, and the client requesting another page). |
User Flow Server Time |
The total server response time (in milliseconds) for all pages in the user flow. |
User Flow Visit Time |
The total time (in seconds) a client spent on a user flow. That is, until they either successfully completed it, or abandoned it. |
User Flows Ended |
The number of flows that ended (either succesfull or prematurely) |
User Flows Failed |
The number of flows that were ended prematurely through abort or session timeout |
User Flows Inactive |
The number of user flows that are inactive (calculated based on idle and outside figures). |
User Flows Success |
The number of flows that were successfully completed |
User Load Time |
The time (in seconds) to load pages within service test (real-user) traffic. |
User Network Error Page Views (%) |
The percentage of page views for which a network error was determined within service test (real-user) traffic. |
User Page Views |
The number of page views within service test (real-user) traffic. |
User Read Time |
The time (in seconds) within service test (real-user) traffic from the last requested page object having been loaded by the client, and the client requesting another page. |
User Server Error Page Views (%) |
The percentage of page views for which a server error was determined within service test (real-user) traffic. |
User Static Network Time |
The time (in milliseconds) for static objects within service test (real-user) traffic to transfer over the network. |
User Static Server Time |
The server response time (in milliseconds) for static objects within service test (real-user) traffic. |
User Traffic Application Violation Page Views |
The total number of content notifications and client aborts detected within service test (real-user) traffic. |
User Traffic Collection Error Page Views (%) |
The percentage of page views for which a collection error was detected within service test (real-user) traffic. |
User Traffic User Content Error Page Views (%) |
The percentage of page views for which a content error was detected within service test (real-user) traffic. |
User Traffic User Violation Page Views |
The total number of content notifications and client aborts detected with service test (real-user) traffic. |
User Traffic Web Site Error Page Views (%) |
The percentage of page views within service test (real-user) traffic for which a Web site error was determined. |
User Violation Calls |
The number of webservice calls for which content notifications and client aborts were detected within service test (real-user) traffic. |
User Violation Calls (%) |
The percentage of webservice calls for which content notifications and client aborts were detected within service test (real-user) traffic. |
User Violation Ended Flows(%) |
The percentage of page views for which content notifications and client aborts were detected within service test (real-user) traffic during userflow activity. |
User Violation Page Views |
The number of page views for which content notifications and client aborts were detected within service test (real-user) traffic. |
User Violation Page Views |
The total number of page views for which content notifications and client aborts were detected within service test (real-user) traffic during a session. |
User Violation Page Views (%) |
The percentage of page views for which content notifications and client aborts were detected within service test (real-user) traffic. |
User Violations Ended Flows |
The number of page views for which content notifications and client aborts were detected within service test (real-user) traffic during userflow activity. |
User Visit Time |
The session time (in seconds) within service test (real-user) traffic. |
Views on First Step |
The number of page views on the first user flow step. |
Views on Last Step |
The number of page views on the last user flow step. |
Views on Step |
The number of page views on the user flow step. |
Violation Calls |
The total number of content notifications, client aborts, poor webservice calls and Web site, network, server, and content errors detected. |
Violation Calls (%) |
The percentage of webservice calls for which content notifications, client aborts, poor page views and Web site, network, server, and content errors were detected. |
Violation Ended Flows(%) |
The percentage of content notifications, client aborts, poor page views and Web site, network, server, and content errors detected during userflow activity. |
Violation Page Views |
The total number of content notifications, client aborts, poor page views and Web site, network, server, and content errors detected during a session. |
Violation Page Views |
The total number of content notifications, client aborts, poor page views and Web site, network, server, and content errors detected. |
Violation Page Views (%) |
The percentage of page views for which content notifications, client aborts, poor page views and Web site, network, server, and content errors were detected. |
Violations Ended Flows |
The total number of content notifications, client aborts, poor page views and Web site, network, server, and content errors detected during userflow activity. |
Visit Time per (Started) User Flow |
The average visit time per (started) user flow. |
Visit Time per Step |
The average visit time (in minutes) per user flow step. |
Visit Time per Transition |
The average visit time (in minutes) per transition. |
Visit Time per User Flow |
The user flow visit time (in minutes). |
Web Site Error Application Hits |
The number of objects within service test (real-user) traffic for which a Web site error was determined. |
Web Site Error Application Hits (%) |
The percentage of objects within service test (real-user) traffic for which a Web site error was determined. |
Web Site Error Calls |
The number of times a Web site error was determined during a service function call. |
Web Site Error Calls (%) |
The percentage of service function calls during which a network Web site error occurred. |
Web Site Error Ended Flows(%) |
The percentage of page views during which a network Web site error occurred during userflow activity. |
Web Site Error Page Views |
The number of times a Web site error was determined upon page display. |
Web Site Error Page Views |
The total number of times a Web site error was determined upon page display during a session. |
Web Site Error Page Views (%) |
The percentage of page views during which a network Web site error occurred. |
Web Site Error Views (%) |
The percentage of page views during which a network Web site error occurred. |
Web Site Errors |
Web site errors are hits that result in an HTTP error code 400-499. |
Web Site Errors Ended Flows |
The number of times a Web site error was determined upon page display during userflow activity. |
Web Site Errors per Session |
The average number of times a Web site error was determined upon page display during a session. |
The KPI metrics available within RUEI are described in Table E-2.
Table E-2 KPI Metrics
Metric | Description |
---|---|
Apdex-per-call |
Apdex is a method for calculating and reporting a metric of transactional application response time in the form of an index with a value of 0 to 1. This number is calculated as an average per call, where failure or poor satisfaction is reported as 0, OK satisfaction as 0.5 and good satisfaction as 1. |
Application Violations |
The number of poor page views or web site, network, server, and content errors detected. |
Browser Busy Time |
The average delay time per hit due to browser activity at the client end. This is the period during which the client TCP window size is indicated as 0. |
Browser Exceptions |
The number of browser exceptions measured by the Browser JS Library. |
Browser Hits |
The number of objects on a page as being measured by the Browser JS Library. |
Browser Time |
The amount of time the browser spent rendering the page. |
Cancelled User Flows |
The number of stopped user flows (either due to abortion or session timeout). |
Client Aborts |
The number of times the client aborted the transfer because the client closed the connection while the function or page was still loading. |
Collection Errors |
There was an error during data collection, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Error Calls |
The number of service calls where a data collection error was encountered, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Error Calls (%) |
The percentage of service calls where a data collection error was encountered, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Error Hits |
The number of hits where a data collection error was encountered, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Error Hits (%) |
The percentage of hits where a data collection error was encountered, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Error on Step |
The number of steps where a data collection error was encountered (considering only step activities), possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Error Page |
Views The number of page views where a data collection error was encountered, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector |
Collection Error Page Views (%) |
The percentage of page views where a data collection error was encountered, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Error Views (%) |
The percentage of views where a data collection error was encountered, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Collection Errors Ended User Flows |
The number of times a data collection error was encountered while analyzing a userflow activity. |
Collection Errors Ended Flows (%) |
The percentage of times a data collection error was encountered while analyzing a userflow activity. |
Collection Error Page Views |
The total number of page views where a data collection error was encountered, possibly because of problems in physical network hardware, due to which packets are lost between the tap or span port and the collector. |
Completed User Flows |
The number of user flows that were successfully completed. |
Concurrent Sessions |
The number of currently active sessions at calculation. |
Content Errors |
The number of content errors determined during a service function call or page view. |
Content Notifications |
The service function calls or page views for which a content notification was determined. |
Content Size |
The size of the object content (excluding headers). |
Database Process Time |
The time per page view taken by the database server to process an action. |
Download Time |
The download time per page. This is the elapsed time from the first object until the last object for the page has been delivered. |
Ended User Flows |
User flows that have ended. |
Errors |
The function calls or page views that for any reason were not successfully invoked/displayed. |
Flow Transitions |
The number of flow transitions. |
Header Size |
The size of the object header (excluding the content). |
Hits |
The number of hits. |
Inactive User Flows |
User flows that were inactive at time of calculation. |
Load Time |
The load time of this page view or function call. |
Network Errors |
The number of network errors determined for this function call or page. |
Network Throughput |
The average object size per network time. |
Network Time |
The network transfer time, as percentage of the total download time. |
Network Timeouts |
The number of network timeouts measured. |
Page-apdex |
Apdex is a method for calculating and reporting a metric of transactional application response time in the form of an index with a value of 0 to 1. This number is calculated as an average per page, where failure or poor satisfaction is reported as 0, OK satisfaction as 0.5 and good satisfaction as 1. |
Read Time |
The time between a page (and all its objects) being loaded, and the next page request, that is, the time available for the visitor to read the page. |
Reply Content Size |
The size of the reply content. |
Reply Header Size |
The size of the reply header. |
Reply Size |
The size of the reply (content + header). |
Request Content Size |
The size of the request content. |
Request Header Size |
The size of the request header. |
Request Size |
The size of the request (content + header). |
Satisfaction Good |
The number of function calls / page views for which the loading time was within the defined satisfaction threshold. |
Satisfaction Ok |
The number of function calls / page views for which the loading time was greater than the defined satisfaction threshold, but less than four times this threshold. |
Satisfaction Poor |
The number of function calls / page views for which the loading time was greater than four times the define satisfaction threshold. |
Server Aborts |
The number of times the server aborted the transfer because it closed the connection while the function or page was still loading. |
Server Errors |
The number of server errors determined during a service function call or page view. |
Server Time |
The server response time, as percentage of the total download time, for a service function call or page view. |
Server Timeouts |
The number of server side timeouts determined during a function call or page view. |
Size |
The size of traffic per function call / page view |
Started User Flows |
The number of user flows that started. |
Step Changes |
The number of actions that brought the end-user one step further/back in the user flow, including start and complete. |
Stopped User Flows |
The number of user flows that ended due to session timeout. |
Transfer Time |
The time taken for a service function call or page view to reach the client after reply from the server. |
Test Traffic Collection Error Page Views (%) |
The percentage of page views where a data collection error was encountered while analyzing a service test (beacon) traffic. |
Total Collection Error |
Percentage on Abort Percentage of collection errors on aborted user flows. |
Total Collection Error on Abort |
Total number of collection errors on aborted user flows. |
Total Collection Error Percentage on Completed |
Percentage of completed user flows that contained collection errors. |
Total Collection Error on Completed |
Total number of collection errors on completed user flows. |
Total Collection Error Percentage on Stopped |
User Flows The percentage of collection errors seen on session timeout. |
Total Collection Error on Stopped User Flows |
Total number of collection errors seen at session timeout. |
Total Collection Error Percentage on Cancel |
Percentage of collection errors on stopped user flows. |
Total Collection Error on Cancel |
Total number of collection errors on stopped user flows. |
User Traffic Collection Error Page Views (%) |
The percentage of page views for which a collection error was detected within service test (real-user) traffic. |
User Violations |
The number of content notifications and client aborts detected. |
View/Actions |
The number of user flow views or actions. This includes page views and function calls. |
Violations |
The total number of content notifications, client aborts, poor webservice calls, and Web site, network, server, and content errors detected. |
Web Site Errors |
The number of service function calls or page view during which a network web site error occurred. |
Calculating Reported Averages
Data items shown in Table E-2 that include the description per, are calculated by dividing a relevant summed total by the item specified after the per part of the description. For example, the download time per page is derived by dividing the total number of pages by the download time for all pages.
The dimensions reported within RUEI are described in Table E-3.
Table E-3 Dimensions
Dimension | Description |
---|---|
5 Minute |
5-minute (and hour). |
Action |
The name of the action. |
Adf Page Download Time (%) |
The download time reported by ADF framework |
Apdex |
Apdex is a method for calculating and reporting a metric of transactional application response time in the form of an index with a value of 0 to 1. This number is calculated as an average per page / call, where a failed / poor satisfaction is reported as 0, a OK satisfaction as 0.5 and a good as 1. |
Application |
The name of the suite, application, or service. |
Application Language |
The application language. |
Application Territory |
The application territory. |
Application Violations |
The number of application violations during start and end of the user flow |
BTM Service |
BTM service name |
BTM Service Operation |
BTM service operation |
Client Browser |
The name of the client browser. |
Client Browser Version |
The name and version of the client browser. |
Client City |
The client city (based on the city specified in the provider's DNS record). (Derived from the MaxMind directory). |
Client Country |
The client country (based on the country specified in the provider's DNS record). (Derived from the MaxMind directory). |
Client Device |
The device class name. |
Client Device Brand |
The brand name of the device. |
Client Device Model |
The brand name and model of the device. |
Client ID |
The ID of the service client. |
Client ID Group |
The group name of the client ID ("users" if set, empty otherwise). |
Client IP |
The IP address of the client. |
Client Language |
The language of the client PC. |
Client Network |
The client network name (based on the registered IP address range). See Defining Named Client Groups. |
Client OS |
The client operating system class name used to visit the Web site. |
Client OS Version |
The complete operating system name used to visit the Web site. |
Client Provider |
The client provider's name (based on the country specified in the provider's DNS record). |
Client Region |
The client region (based on the city specified in the provider's DNS record). |
Content Errors |
The number of error strings found in content |
Content Notifications |
The number of notification strings found in content |
Cookie OK |
The number of pageviews tracked based on cookie (rather than IP or browser/network) |
Day |
Day (and month). |
Day percentage |
SLA set day percentage at time of measurement |
Delayed log ratio |
The number of logfiles that were expected but not received as percentage of expected number of logfiles in a minute. |
Denominator |
Denominator for KPI calculation |
Domain |
The domain part of the requested URL. |
Duration |
The time between going out of boundaries, and getting inside set boundaries again or vice-versa |
ECID |
The ECID of an object. |
Error User Group |
The group name of the user ID ("users" if set, empty otherwise) of erroneous sessions. |
Error User ID |
The user ID of the user (if logged on to your Web site) of erroneous sessions. |
Failed Minutes |
The total number of minutes the KPI was failing inside the selected period |
Frustrated Pageviews |
The number of poor pageviews encountered between start and end of the user flow |
Function |
The service function name. |
Function Group |
The service function group. |
Fusion Login Family |
The number of unique sessions where a fusion family was encountered the first time |
Fusion Login Product |
The number of unique sessions where a fusion product was encountered the first time |
Good Pageviews |
The total number of good pageviews encountered between start and end of the user flow |
Hour |
Hour (and day). |
KPI Entity |
The number of KPI calculations |
Lower Threshold |
The lower threshold/boundary for the KPI at time of measurement |
Maximum Time Stamp |
The maximum time stamp value |
Minimum Time Stamp |
The minimum time stamp value |
Month |
Month (and year). |
Month Percentage |
SLA set month percentage at time of measurement |
Named Client |
The name assigned to the client IP address or range. See Defining Named Client Groups. |
Named Client Group |
The group name assigned to the client IP address or range. See Defining Named Client Groups. |
Named Server |
The name of the Web server. See Defining Named Web Server Groups. |
Named Server Group |
The group name of the Web server. See Defining Named Web Server Groups. |
Network time (%) |
The total network time of all activities between start and end of user flow |
Numerator |
Numerator for KPI calculation |
Object Class |
The classification of the object (for example, image, video, and so on). |
Object Delivery |
Indication of whether object delivery was successful. If not, the category of error (Web site, network, or server) or other reason. |
Object Delivery Detail |
Either successful delivery or the response code or reason why the object failed. |
Object Extension |
The file extension of the object. |
Object Type |
The object type (static or dynamic). |
Object URI |
The protocol, domain, path and parameters of the object's URI |
Object URL |
Path of the object's URL. |
Object URL Top Directory |
First directory of the path of the object's URL. |
Ok Minutes |
The total number of minutes the KPI was OK inside the selected period |
Ok Pageviews |
The total number of ok pageviews encountered between start and end of the user flow |
Page |
The application page name. |
Page Delivery |
If not successfully delivered, the category of error (Web site, network, server, or content) or other reason. |
Page Delivery Detail |
Either successful delivery or the response code or reason why the page failed. |
Page Group |
The application page group. |
Page Load Time |
The total page load time of all activities between start and end of user flow |
Page Sequence Number |
A number that represents the number of pages seen in the session up-till the reported page |
Page URI |
The protocol, domain, path and parameters of the pages's URI. |
Page URL |
Path of the pages's URL. |
Page URL Top Directory |
First directory of the path of the page's URL. |
Physical Client IP |
The physical IP address or range of the client. |
Poor Hits |
The number of ok hits |
Poor Hits |
The number of poor hits |
Prerequisite Failures |
The total number of minutes the KPI was failing inside the selected period because requisite conditions were not met |
Referrer Domain |
The domain of the referrer URL. |
Referrer URL |
The full referrer URL. That is, the domain, directories, and parameters. |
SLA Entity |
The number of SLA calculations |
SSL Connection Size (%) |
The number of bytes that were used to setup the SSL connection for this hit. The SSL connection size is only added to the first hit in the ssl-session |
SSL Connection Time (%) |
The number of milliseconds required to setup the SSL connection for this hit. The SSL connection time is only added to the first hit in the ssl-session |
Satisfied Hits |
The number of good hits |
Server IP |
The IP address of the Web server. |
Server Time (%) |
The total server time of all activities between start and end of user flow |
Service Delivery |
If not successfully delivered, the category of error (Web site, network, server, or content) or other reason. |
Service Delivery Detail |
If not successfully delivered, the return code or reason why the function failed. |
Service Function |
The service function name. |
Service Function Group |
The service function group. |
Service Language |
The service language. |
Service Territory |
The service territory. |
Session Client Browser |
The name of the client browser. If multiple values were observed for this session, the first value seen is used. |
Session Client Browser Version |
The name and version of the client browser. If multiple values were observed for this session, the first value seen is used. |
Session Client City |
The client city (based on the city specified in the provider's DNS record). (Derived from the MaxMind directory). If multiple values were observed for this session, the first value seen is used. |
Session Client Country |
The client country (based on the country specified in the provider's DNS record). (Derived from the MaxMind directory). If multiple values were observed for this session, the first value seen is used. |
Session Client Device |
The device class name. If multiple values were observed for this session, the first value seen is used. |
Session Client Device Brand |
The brand name of the device. If multiple values were observed for this session, the first value seen is used. |
Session Client Device Model |
The brand name and model of the device. If multiple values were observed for this session, the first value seen is used. |
Session Client IP |
The IP address of the client. If multiple values were observed for this session, the first value seen is used. |
Session Client Language |
The language of the client PC. If multiple values were observed for this session, the first value seen is used. |
Session Client Network |
The client network name (based on the registered IP address range). See Defining Named Client Groups. If multiple values were observed for this session, the first value seen is used. |
Session Client OS |
The client operating system class name used to visit the Web site. If multiple values were observed for this session, the first value seen is used. |
Session Client OS Version |
The complete operating system name used to visit the Web site. If multiple values were observed for this session, the first value seen is used. |
Session Client Provider |
The client provider's name (based on the country specified in the provider's DNS record). If multiple values were observed for this session, the first value seen is used. |
Session Client Region |
The client region (based on the city specified in the provider's DNS record). If multiple values were observed for this session, the first value seen is used. |
Session Sequence Number |
A internal identifier that indicates the number of session breaks (due to logout conditions and timeouts) in a technical session |
Transaction |
The name of the transaction. |
Transaction Group |
The group of the transaction. |
Transaction Step |
The step name of the transaction. |
Upper Threshold |
The upper threshold/boundary for the KPI at time of measurement |
User Flow |
The name of the user flow. |
User Flow Group |
The category of the user flow. |
User Flow Start Time |
The start time of the User Flow in EPOCH time |
User Flow Step |
The step name in the user flow. |
User Flow Step Count |
The total number of User Flow activities |
User Flow Step Number |
The step number in the flow |
User Group |
The group name of the user ID ("users" if set, empty otherwise). |
User ID |
The ID of the user (if logged onto your Web site). |
User Violations |
The number of user violations during start and end of the user flow |
Violations |
The number of violations during start and end of the user flow |
Week |
Week (and year). |
Week Percentage |
SLA set week percentage at time of measurement |
Year |
Year. |
Year Percentage |
SLA set year percentage at time of measurement |
When an object is requested by a visitor, RUEI sees the request and measures the time the web server requires to present the visitor with the requested object. At this point, RUEI knows who requested the page (the client IP), which object was requested, and from which server the object was requested (server IP). This is shown in Figure E-1.
When the web server responds and sends the requested object to the visitor, RUEI sees that response. At this point, RUEI can see whether there is a response from the server, whether this response is correct, how much time the web server required to generate the requested object, and the size of the object.
In addition, RUEI can also see whether the object was completely received by the visitor, or if the visitor aborted the download (that is, proof of delivery). Hence, RUEI can determine the time taken for the object to traverse the Internet to the visitor, and calculate the Internet throughput between the visitor and the server (that is, the connection speed of the visitor).
Objects requested from a server are either dynamic or static. Dynamic objects are generated live by the server, and are identified by file extensions such as php, php3, php4, asp, aspx, and so on. Static objects are already available for download with no further server action required. These are generally graphic, video, or document files. Note that dynamically-generated objects are typically much more server intensive than static objects. Table E-4 shows a complete list of the object file extensions that are recorded as static.
Table E-4 Static Object File Extensions
Extension | Extension | Extension |
---|---|---|
.7z |
.aac |
.aaf |
.ace |
.ani |
.arc |
.arj |
.atom |
.au |
.avi |
.bmp |
.bz2 |
.cab |
.class |
.css |
.cur |
.dat |
.deb |
.divx |
.docx |
.dot |
.dotx |
.dtd |
.flv |
.gif |
.gz |
.htm |
.html |
.ico |
.iso |
.jar |
.java |
.jpeg |
.jpg |
.js |
.lzh |
.m4a |
.m4p |
.mid |
.mpe |
.mpeg |
.mpg |
.mov |
.mp4 |
.ogg |
.par |
.par2 |
|
.ppt |
.properties |
.ra |
.rar |
.rm |
.rss |
.rtf |
.svg |
.swa |
.swf |
.tar |
.tar |
.tiff |
.tgz |
.ttf |
.txt |
.wav |
.wma |
.wma |
.xhtm |
.xhtml |
.xls |
.xml |
.xsl |
.xslt |
.z |
.zip |
Note that Table E-2 only applies to objects used within a GET or a POST. Otherwise, they are reported as dynamic objects.
Table E-5 shows a complete list of the object file extensions that are explicitly recorded as dynamic. Note that all object file extensions not listed in Table E-4 are also recorded as dynamic.
Table E-5 Dynamic Object File Extensions
Extension | Extension | Extension |
---|---|---|
.asp |
.aspx |
.cfm |
|
.jsp |
.php |
.php3 |
.php4 |
.php5 |
.phtml |
.pl |
|
Note the correlation of pages and hits is performed on a time basis, and a page and its hits can never have a time difference longer than 15 seconds. A hit gap of longer than 15 seconds means that the hit is no longer considered part of its associated page. In addition, the system recognizes redirects, and correlates this data to the next page view.
Be aware that any download (such as a PDF or large graphics file) that takes longer than 5 minutes to be completed is discarded by RUEI, and not reported. This is regardless of whether or not the download was successful.
The time taken for a requested object to arrive at the client side is called the end-to-end (or e2e) time. It comprises two parts:
Server time: the time taken by the server to generate the response.
Network time: the time taken required for the response to travel from the server to the client.
It is important to understand the precise definition of page load time and end-to-end time because they are closely related and influenced by the way the server interacts with the client browser. Figure E-2 shows a page view that consists of three hits.
Figure E-2 Page View Consisting of One Page Hit and Two Object Hits
Each hit has three arrows associated with it:
The request from the client browser to the server.
The reply from the server to the client browser.
The acknowledgement from the client browser to the server.
The server time is based on the time between receiving the request, and the moment the server starts to reply to the request. The network time is based on the time between the reply being sent to the client, and the acknowledgement of the reply by the client browser. The end-to-end time reported by RUEI is always the sum of the network time and the server time.
The page download time is calculated as the time between the start of the page request and acknowledgement of the last object. The page browser time is the time taken after receipt, for a page to be loaded by client browser. Page browser time out-of-the-box does only work for ADF and Fusion, for other suites / generic applications it needs to be instrumented manually with JS library support. For more information, see Defining Browser JS Library Settings.
Examining the page view network and server times shown in Figure E-2, it appears that the sum of network and server times for all hits is longer than the page loading time. This is caused by the fact that the last two hits (green and blue) are processed in parallel. For calculation of the network and server times, these are processed as two individual hits with their own timing.
The "UserActivityInfo" class in ADF/ Fusion holds information about a user action, and is used to monitor end user activity such as start time and end time for a user action initiated from the client-side.
RUEI uses the "UserActivityInfo" information from ADF/Fusion to identify the page requests and to calculate the page browser time. RUEI calculates the loading time as observed by ADF/Fusion using the difference between client start time (the moment the user clicks) and the client end time (the moment the page is loaded).The difference between the RUEI download time is called the page browser time.
For more information, refer https://docs.oracle.com/middleware/12212/adf/api-reference-faces/oracle/adf/view/rich/monitoring/UserActivityInfo.html
.
As each object within a requested page is received at the client browser, there is sometimes a delay before the browser can start to process and load it. This is known as the browser load time (not to be confused with the page browser time as shown above). Once all objects have been loaded, the page is displayed in the client browser. The time from this moment until the next page request is known as the page read (or idle) time. It is the time the client users to review the requested page, and is set to a maximum of two minutes.
Be aware that the reported number of page views for a specific or hour can differ depending on the Data Browser group you are using. The structure of the information available within the Data Browser is explained in Understanding the Data Structure. In particular, it is calculated slightly differently between the All sessions group and the All pages group. This is illustrated in Table E-6:
Table E-6 Page View Reporting in the All Pages and All Sessions Groups
Time | Visited pages | Reported no. of page views | ||
---|---|---|---|---|
Visitor 1 | Visitor 2 | All pages | All sessions | |
00:00 |
A, B |
A, B, C |
5 (Visitor 1: A,B,A) Visitor 2: B,C) |
0 |
00:15 |
C, D |
A |
3 (Visitor 1: C,D) (Visitor 2: A) |
0 |
00:30 |
E |
B |
2 (Visitor: 1E) (Visitor 2: B) |
0 |
00:45 |
F |
C |
2 (Visitor: F) (Visitor: C) |
0 |
01:00 |
- |
D |
1 (Visitor 2: D) |
6 (Visitor 1: A,B,C,D,E,F) |
01:15 |
D |
- |
1 (Visitor 1: D) |
7 (Visitor 2: A,B,C,A,B,C,D) |
01:30 |
F |
A |
2 (Visitor 1: F) (Visitor 2: A) |
0 |
01:45 |
- |
- |
- |
3 (Visitor 1: D,F) (Visitor 2: A) |
8 |
8 |
16 |
16 |
Table E-6 shows the visited page history of two users. As both visitors browse the monitored web site, the number of pages they have visited are immediately recorded in the All pages group. For example, between 00:00 and 00:15 they had visited five pages. However, because these sessions are still active, they are not yet recorded within the All sessions group. That happens between 01:00 and 01:15, together with the other pages visited in that session.
As the two visitors' sessions progress, the number of visited pages is preserved. Because the All sessions group waits until each is regarded as finished, the related page history is recorded against a later time interval than in the All pages group. However, as can be seen in the totals at the bottom of Table E-6, after both sessions have finished, the total number of page visits reported in each group is the same.
Typically, the All pages group is used for functional analysis, (such as performance monitoring), while the All sessions group is used to identify issues are impacting users.
Finally, be aware that the page views for a session are recorded for the current day when they arrive at least 30 minutes before 12 PM. Thereafter, they are treated as belonging to a new session. Therefore, small differences can arise between reported page views in real-time data (such as the dashboard) and session-based groups.
All dimension level values are limited to 255 characters. If a value is longer than this, it is automatically truncated. Note that truncated data is indicated by ending with an ellipse (…). This restrictions does not apply within session diagnostics on object level, or to posted form content.
RUEI can monitor compressed network traffic. Currently, it supports the DEFLATE (zlib) and gzip compression algorithms. Be aware that information about error messages encountered by users is written to the Session diagnostics replay facility (see Working With the Session Diagnostics Feature) "as is", and are not decompressed until requested to be viewed. The ability to correctly display such information depends on your browser's capabilities. While Internet Explorer and Mozilla Firefox are fully supported for this purpose, the use of other (unsupported) browsers may present difficulties.
Aggregation is an important data management mechanism for controlling the database size used by RUEI. Aggregation works by removing irrelevant or redundant details from database tables. For example, the tracking of individual user IDs is not relevant when wanting to see the number of visitors per day over a month period. By removing this information, and adding useful counters, the amount of information that can be reported is easily increased. Consider the database table shown in Table E-8.
Table E-7 Page Views
Page.Group | Page.Name | User.Group | User.Name | Page Views | Hits |
---|---|---|---|---|---|
Homepage |
Homepage |
Users |
Jan |
4 |
44 |
Product |
Product » Details |
Users |
Jan |
5 |
50 |
Homepage |
Homepage |
"(no value)" |
"(no value)" |
1 |
8 |
About-Us |
About-Us » Contact |
"(no value)" |
"(no value)" |
10 |
30 |
About-Us |
About-Us » FAQs |
"(no value)" |
"(no value)" |
2 |
13 |
When the Page.Name level is removed, the table shown in Table E-9 is created. Note that the number of rows is reduced from five to four.
Table E-8 Page Views
Page.Group | User.Group | User.Name | Page Views | Hits |
---|---|---|---|---|
Homepage |
Users |
Jan |
4 |
44 |
Product |
Users |
Jan |
5 |
50 |
Homepage |
"(no value)" |
"(no value)" |
1 |
8 |
About-Us |
"(no value)" |
"(no value)" |
2 |
43 |
However, if the User.Name level is removed instead, the table shown in Table E-9 is created. Note that in this case it does not result in a reduced number of rows.
Table E-9 Page Views
Page.Group | Page.Name | User.Group | Page Views | Hits |
---|---|---|---|---|
Homepage |
Homepage |
Users |
4 |
44 |
Product |
Product » Details |
Users |
5 |
50 |
Homepage |
Homepage |
"(no value)" |
1 |
8 |
About-Us |
About-Us » Contact |
"(no value)" |
10 |
30 |
About-Us |
About-Us » FAQs |
"(no value)" |
2 |
13 |