# US 10,481,995 B1 · Methods and systems for measuring user and system metrics > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,481,995 B1 - Document ID: US10481995B1 - Status: Granted - Kind: B1 - Application number: 16/233,432 - Filed: 2018-12-27 - Granted: 2019-11-19 - Earliest claimed: 2018-08-17 - Assignees: Capital One Services, LLC - Applicants: Capital One Services, LLC - Inventors: Venkata Mandali; Sateesh Mamidala; Arunkumar Natarajan; Kadhiresan Kanniyappan - Web page: https://patentgrep.com/patent/US10481995B1 ## CPC - G06F 11/3419: {by assessing time} - G06F 11/3495: {for systems} - G06F 11/079: {Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36)} - G06F 11/3423: {where the assessed time is active or idle time} - G06F 11/3476: {Data logging (G06F11/14, G06F11/2205 take precedence)} - G06F 16/9577: {Optimising the visualization of content, e.g. distillation of HTML documents} - H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)} - G06F 2201/87: Monitoring of transactions - G06F 2201/875: Monitoring of systems including the internet - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## 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. ## Claims ### Claim 1 A method for measuring user and system metrics, the method comprising: receiving, from a user device, a first user request to access data associated with a web page; generating, by a processor, a first transaction identification; collecting transaction information generated in response to the first user request, 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; analyzing, by the processor, the integrated server-side metrics and the client-side data; receiving, from the user device, a second request; and selectively re-routing the second user request based at least in part on the analyzed integrated server-side metrics and the client-side data. ### Claim 2 (depends on 1) The method of claim 1 further comprising: determining one or more servers accessed in response to the first user request; recording each internet protocol (IP) address corresponding to the one or more servers accessed in response to the first user request; and associating each IP address recorded with the server-side metrics. ### Claim 3 (depends on 1) The method of claim 1 further comprising: determining one or more servers accessed in response to the first user request; recording a central processing unit (CPU) utilization percentage for each of the one or more servers accessed in response to the first user request; and associating each CPU utilization percentage recorded with the server-side metrics. ### Claim 4 (depends on 1) The method of claim 1 further comprising: determining an amount of time to return, to the user device, the data associated with the web page; and associating the amount of time to return the data associated with the web page with the server-side metrics. ### Claim 5 (depends on 1) The method of claim 1, wherein the 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, and a user geographical location. ### Claim 6 (depends on 1) The method of claim 1 further comprising: determining, by the processor, the second transaction identification associated with the client-side data; comparing, by the processor and to determine a match, the first transaction identification and the second transaction identification; and in response to finding a match, generating, by the processor, a dataset comprising the server-side metrics and the client-side data. ### Claim 7 (depends on 1) The method of claim 1, wherein the transaction information is stored on a first storage device. ### Claim 8 (depends on 1) The method of claim 1, wherein the client-side data is stored on a second storage device. ### Claim 9 (depends on 1) The method of claim 1 further comprising: receiving, from the user device, an indication of a status of the user request, the indication comprising a successful status indication or a failed status indication. ### Claim 10 (depends on 9) The method of claim 9 further comprising: responsive to receiving the failed status indication, identifying a source of the failed status indication; and storing the source of the failed status indication, and the client-side data and the server-side metrics corresponding to the first transaction identification, wherein the second user request is re-routed to prevent the re-occurrence of the client-side data and the server-side metrics corresponding to the first transaction identification. ### Claim 11 (depends on 10) The method of claim 10 further comprising responsive to receiving the failed status indication: comparing, the client-side data and the server-side metrics to historic data, to identify whether a correlation between the client-side data and the server-side metrics exists leading to the failed status indication; and in response to identifying that the correlation exists, preventing future occurrences of the failed status indication by eliminating the correlation. ### Claim 12 (depends on 11) The method of claim 11, wherein the historic data comprises a plurality of client-side data and a plurality of server-side metrics. ### Claim 13 A system for measuring user and system metrics, the system comprising: one or more processors; and a memory in communication with the one or more processors and storing instructions that, when executed by the one or more processors, are configured to cause the system to: receive, from a user device, a user request to access data associated with a web page; generate a first transaction identification; collect transaction information, the transaction information comprising server-side metrics; integrate the first transaction identification with the transaction information; transmit the first transaction identification to the user device; receive, from the user device, client-side data associated with a second transaction identification; integrate the server-side metrics and the client-side data; and analyze the integrated server-side metrics and the client-side data. ### Claim 14 (depends on 13) The system of claim 13 further comprising: receiving, from the user device, an indication of a status of the user request, the user request comprising a successful status indication or a failed status indication. ### Claim 15 (depends on 14) The system of claim 14 further comprising: responsive to receiving the failed status indication: comparing, the client-side data and the server-side metrics to historic data, to identify whether a correlation between the client-side data and the server-side metrics exists leading to the failed status indication; and in response to identifying that the correlation exists, preventing future occurrences of the failed status indication by eliminating the correlation.