Methods and systems for measuring user and system metrics

Patent metadata

Field	Value
Publication number	US-11630756-B2
Application number	US-202117391065-A
Country	US
Kind code	B2
Filing date	Aug 2, 2021
Priority date	Aug 17, 2018
Publication date	Apr 18, 2023
Grant date	Apr 18, 2023

Abstract

A method including receiving, from a user device, a user request to access data associated with a web page; generating, by a processor, a first transaction identification; collecting transaction information, the transaction information comprising server-side metrics; integrating, by the processor, the first transaction identification with the transaction information; transmitting, by the processor, the first transaction identification to the user device; receiving, from the user device, client-side data associated with a second transaction identification; integrating, by the processor, the server-side metrics and the client-side data; and analyzing, by the processor, the integrated server-side metrics and the client-side data.

First claim

What is claimed is:

1. A method for measuring user metrics and system metrics, the method comprising:
receiving, with a transceiver of a computing device, a first request from a user device to access data associated with a web page;
generating, by one or more processors of the computing device, a first transaction identification;
determining, by the one or more processors, current server-side metrics present during a user session initiated based on the first request;
associating, by the one or more processors, the first transaction identification with the current server-side metrics;
receiving, with the transceiver, current client-side data associated with a second transaction identification from the user device; and
integrating, by the processor, the current server-side metrics and the current client-side data.

2. The method of claim 1 , further comprising:
receiving, with the transceiver, a failed status of the first request from the user device;
identifying, by the one or more processors, a source of the failed status based on the integrated current server-side metrics and the current client-side data; and
storing the source of the failed status, and the current client-side data and the current server-side metrics.

3. The method of claim 2 , further comprising:
receiving, with the transceiver, a second request from the user device;
identifying, by the one or more processors, at least one server needed to fulfill the second request;
comparing, by the one or more processors, the at least one server to the source of the failed status to determine a partial match; and
routing, by the one or more processors, the second request away from the at least one server, wherein the second request is routed to prevent a re-occurrence of the failed status.

4. The method of claim 2 , further comprising:
generating, by the one or more processors, a graphical user interface that displays a visual representation of the source of the failed status.

5. The method of claim 1 , further comprising:
generating, by the one or more processors, a graphical user interface that displays a visual representation of the current client-side data and the current server-side metrics present during the user session associated with the first request.

6. The method of claim 5 , further comprising:
receiving, at the graphical user interface, a user input; and
identifying, by the one or more processors, a source of a failed status based on the user input.

7. The method of claim 1 , wherein integrating the current server-side metrics and the current client-side data comprises:
determining, by the one or more processors, the second transaction identification associated with the current client-side data;
comparing, by the one or more processors, the first transaction identification and the second transaction identification to determine a match; and
generating, by the one or more processors, a user session dataset comprising the current server-side metrics and the current client-side data.

8. The method of claim 7 , further comprising:
receiving, with the transceiver, a failed status of the first request from the user device;
identifying, by the one or more processors, a source of the failed status by:
comparing, by the one or more processors, the user session dataset to a historic user session dataset, the historic user session dataset comprising previous client-side data and previous server-side metrics of previous user sessions that resulted in a failed status;
determining, by the one or more processors, that a correlation exists between the user session dataset and the historic user session dataset, wherein the correlation is at least one of:
one or more current server-side metrics or one or more client-side data;

setting, by the one or more processors, the correlation as the source of the failed status; and
preventing future occurrences of the failed status by eliminating the correlation.

9. The method of claim 1 , wherein determining the current server-side metrics present during the user session comprises:
determining, by the one or more processors, one or more servers accessed during the user session;
recording, by the one or processors, a central processing unit (CPU) utilization percentage for each of the one or more servers accessed during the user session; and
associating, by the one or more processors, each CPU utilization percentage recorded with the current server-side metrics.

10. The method of claim 1 , wherein determining the current server-side metrics present during the user session comprises:
determining, by the one or more processors, an amount of time to return the data associated with the web page to the user device; and
associating the amount of time to return the data associated with the web page with the current server-side metrics.

11. The method of claim 1 , wherein the current client-side data comprises at least one of a customer identification, a browser type, an operating system type, a web page load time, a graphical user interface (GUI) identification, or a user geographical location.

12. A method for measuring user metrics and system metrics, the method comprising:
receiving, with a transceiver of a user device, a transaction identification from a web server;
generating, by one or more processors, a client-side dataset comprising client-side metrics and the transaction identification;
sending, with the transceiver, the client-side dataset to the web server;
determining, by the one or more processors, a status of a first user request, the first user request associated with a first user requesting access to data associated with a web page, wherein the status of the first user request is successful or failed; and
sending, with the transceiver, the status of the first user request to the web server.

13. The method of claim 12 , wherein the client-side metrics comprises at least one of a customer identification, a browser type, an operating system type, a web page load time, a graphical user interface (GUI) identification, or a user geographical location.

14. The method of claim 12 , wherein the status of the first user request is successful, and the method further comprises:
receiving, with the transceiver, web page data associated with the first user request.

15. The method of claim 12 , wherein the status of the first user request is failed, and the method further comprises:
sending, with the transceiver of the user device, a user request to access data associated with the web page to the web server, wherein the web server selectively routes the user request based at least in part on the client-side metrics.

16. A system for measuring user metrics and system metrics, the system comprising:
one or more processors;
a transceiver;
a memory in communication with the one or more processors, and the transceiver, and storing instructions that, when executed by the one or more processors, are configured to cause the system to:
receive, with the transceiver, a user request to access data associated with a web page from a user device;
generate, by the one or more processors, a first transaction identification;
determine, by the one or more processors, current server-side metrics present during a user session established based on the user request;
associate, by the one or more processors, the first transaction identification with the current server-side metrics;
receive, with the transceiver, current client-side data present during the user session and a second transaction identification from the user device; and
integrate, by the one or mor

Assignees

• Capital One Services Llc

Inventors

• Mandali Venkata
• Mamidala Sateesh
• Natarajan Arunkumar
• Kanniyappan Kadhiresan

Classifications

• G06F11/3495 Primary

  for systems · CPC title

• G06F2201/875

  Monitoring of systems including the internet · CPC title

• H04L67/535

  Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34) · CPC title

• G06F2201/87

  Monitoring of transactions · CPC title

• G06F16/9577

  Optimising the visualization of content, e.g. distillation of HTML documents · CPC title