System and method for determining end user timing

US9935856B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9935856-B2
Application numberUS-201414245938-A
CountryUS
Kind codeB2
Filing dateApr 4, 2014
Priority dateApr 4, 2014
Publication dateApr 3, 2018
Grant dateApr 3, 2018

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

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.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for monitoring a business transaction, comprising: capturing, by agents installed on client computing devices in communication with a remote server over a network, a first set of metrics using handler objects in different network browsers executing on the client computing devices, the first set of metrics associated with a request by a corresponding one of the different network browsers and each agent is inserted into a content page displayed by the corresponding one of the different network browsers at a corresponding one of the client computing devices; comparing, by each agent on the corresponding one of the client computing devices, the first set of metrics with a second set of metrics retrieved from a browser interface at the corresponding one of the client computing devices to determine whether the first set of metrics or the second set of metrics are most accurate, the second set of metrics associated with the request, wherein the most accurate set of metrics of the first set of metrics and the second set of metrics is determined based on whether data points are in an expected order or whether data times are within a particular threshold; and reporting to the remote server by the agents on the client computing devices the first set of metrics or the second set of metrics depending upon which is most accurate. 2. The method of claim 1 , further comprising associating, by each agent at the corresponding one of the client computing devices, a first call back to one of the handler objects. 3. The method of claim 2 , further comprising storing, by each agent at the corresponding one of the client computing devices, timing data upon receiving a call of the associated call back. 4. The method of claim 3 , further comprising associating a second call back to a particular handler object upon receiving the call of the associated call back, wherein the associating the first and second call backs are based on a list of handler objects that are suitable for associating with call backs. 5. The method of claim 1 , further comprising normalizing the first set of metrics and the second set of metrics. 6. The method of claim 1 , further comprising receiving, by each agent at the corresponding one of the client computing devices, a first call back upon execution of a first one of the handler objects associated with a first network browser platform and a second call back with a second one of the handler objects associated with a second network browser platform. 7. The method of claim 1 , further comprising placing a most recently received call back to a bottom of a list. 8. The method of claim 1 , wherein the second set of metrics is retrieved using a navigation timing interface. 9. A non-transitory computer readable storage medium having embodied thereon a program, the program being executable by a processor to perform operations for monitoring a business transaction, the operations comprising: capturing, by agents installed on client computing devices in communication with a remote server over a network, a first set of metrics using handler objects in different network browsers executing on the client computing devices, the first set of metrics associated with a request by a corresponding one of the different network browsers and each agent is inserted into a content page displayed by the corresponding one of the different network browsers at a corresponding one of the client computing devices; comparing, by each agent on the corresponding one of the client computing devices, the first set of metrics with a second set of metrics retrieved from a browser interface at the corresponding one of the client computing devices to determine whether the first set of metrics or the second set of metrics are most accurate, the second set of metrics associated with the request, wherein the most accurate set of metrics of the first set of metrics and the second set of metrics is determined based on whether data points are in an expected order or whether data times are within a particular threshold; and reporting to the remote server by the agents on the client computing devices, the first set of metrics or the second set of metrics depending upon which is most accurate. 10. The non-transitory computer readable storage medium of claim 9 , wherein the operations include associating, by each agent at the corresponding one of the client computing devices, a first call back to one of the handler objects. 11. The non-transitory computer readable storage medium of claim 10 , wherein the operations include storing, by each agent at the corresponding one of the client computing devices, timing data upon receiving a call of the associated call back. 12. The non-transitory computer readable storage medium of claim 11 , wherein the operations include associating a second call back to a particular handler object upon receiving the call of the associated call back, wherein the associating the first and second call backs are based on a list of handler objects that are suitable for associating with call backs. 13. The non-transitory computer readable storage medium of claim 9 , wherein the operations include normalizing the first set of metrics and the second set of metrics. 14. The non-transitory computer readable storage medium of claim 9 , wherein the operations include receiving, by each agent at the corresponding one of the client computing devices, a first call back upon execution of a first one of the handler objects associated with a first network browser platform and a second call back with a second one of the handler objects associated with a second network browser platform. 15. The non-transitory computer readable storage medium of claim 9 , wherein the operations include placing a most recently received call back to a bottom of a list. 16. The non-transitory computer readable storage medium of claim 9 , wherein the second set of metrics is retrieved using a navigation timing interface. 17. A system for monitoring a business transaction, comprising: a processor; a memory; and one or more modules stored in memory and executable by a processor to perform operations including: capture, by agents installed on client computing devices in communication with a remote server over a network, a first set of metrics using handler objects in different network browsers executing on the client computing devices, the first set of metrics associated with a request by a corresponding one of the different network browsers and each agent is inserted into a content page displayed by the corresponding one of the different network browsers at a corresponding one of the client computing devices; compare, by each agent on the corresponding one of the client computing devices, the first set of metrics with a second set of metrics retrieved from a browser interface at the corresponding one of the client computing devices to determine whether the first set of metrics or the second set of metrics are most accurate, the second set of metrics associated with the request, wherein the most accurate set of metrics of the first set of metrics and the second set of metrics is determined based on whether data points are in an expected order or whether data times are within a particular threshold; and report to the remote server by the agents on the client computing devices, the first set of metrics or the second set of metrics depending upon which is most accurate. 18. The system of claim 17 , wherein the operations include associate, by each agent at the corresponding one of the client computi

Assignees

Inventors

Classifications

  • Electricity · mapped topic

  • Strategic management or analysis, e.g. setting a goal or target of an organisation; Planning actions based on goals; Analysis or evaluation of effectiveness of goals · CPC title

  • Processing captured monitoring data, e.g. for logfile generation · CPC title

  • Electricity · mapped topic

  • H04L43/08Primary

    Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9935856B2 cover?
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 timi…
Who is the assignee on this patent?
Appdynamics Llc, Cisco Tech Inc
What technology area does this patent fall under?
Primary CPC classification G06Q10/0637. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Apr 03 2018 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).