Abstract:
A system automatically determines end user timing across multiple platforms and network browsers. End user timing data may be captured using one or more techniques. The techniques may include utilizing a navigation timing standard and handler call back functionality. The end user timing data may be analyzed to identify which technique's data is most accurate, and the most accurate end user timing data is then reported.
Abstract:
A system monitors a client request and a backend business transaction performed in response to the request and correlates the data generated from monitoring the request and business transaction. A request may be monitored in detail to determine several metrics. The metrics may include sever connection time, response receipt completion time, document download time, document processing time, and page rendering time. The metrics may be determined for an entire content page as well as individual page elements, such as Iframes and elements constructed from AJAX techniques.
Abstract:
Code intended to operate in an operating system without an isolation mechanism is executed in isolation. The present system enables synthetic transactions to be executed in isolation without affecting other client data and files. Isolation may be outsourced to a separate set of servers that have an operating system which does support isolation. A handshake or other protocol is utilized to maintain secure data and communication. Untrusted script code provided by a customer is isolated in one or more remote servers. To execute the script on a client machine, a key is provided to access this script. A machine at which the script is to be run is provided with the key and the address of the script code on the remote server. A secure connection is established between the client machine and the script code server and script is executed on the client machine.
Abstract:
Distributed applications are monitored and page composition metrics are reported in terms of a plurality of phases of a page loading lifecycle. The phases may include first byte received, page rendering time, onload time, post page load time, and other phases. For each phase, data regarding different types of requests may be reported. Data regarding AJAX and iFrame requests may be reported for each phase in a page load, providing more information regarding what is loaded and when. The data may be provided in a graphical ‘cascade’ format based on the phase. Information for AJAX, iFrame and other requests may include the number of such requests occurring in each phase, the average execution time of the requests, and other data. The requests and phases can be determined for multiple types of browsers based on data collection techniques compatible for each particular browser.