IP Library Granted Patent US 12,724,854
Granted Patent B2
US 12,724,854 · App. 18/229,983 · Granted Sep 1, 2026

Onboarding of monitoring tools

Inventors: Mohamed Seck (Aubrey, TX); Louis Buell (Chevy Chase, MD)
Assignee: Capital One Services, LLC
G06F21/105G06F3/0482G06F9/547G06F11/3065G06F11/3409G06F11/3466G06F21/121H04L67/025G06F11/008G06F16/951G06F21/1073
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,724,854
App. No.
18/229,983
Granted
Sep 1, 2026
Kind
B2
Abstract

A system, process, and computer-readable medium for configuring agents for monitoring deployed applications is described. A system, process, and computer-readable medium for configuring monitoring user interfaces, e.g., monitoring dashboards, that use information made available from the agents is also described. Through using application data available during creation of the agents, the agents may be configured using the user interface as modified by selections and displaying subsequent choices from the received application data. Using knowledge of the generated agents, monitoring dashboards may be generated via developers interacting with a user interface providing a list of available metrics accessible by the generated agents. Using the one or more user interfaces, developers may generate agents and/or monitoring dashboards with greater efficiency.

Claims (104)

1 . A computer-implemented method comprising:

receiving a dataset for deployed applications, wherein the dataset comprises application identifiers and profiling information;

generating, based on the received dataset, a first user interface;

receiving, via the first user interface, one or more user selections, wherein the one or more user selections comprises:

an application identifier, of a deployed application;

profiling information associated with the deployed application; and

an agent type;

generating, based on the application identifier, based on the profiling information, and based on the agent type, a software agent configured to expose operations, of the deployed application as metrics, wherein the metrics are configured to be addressable, via an application programming interface (API);

generating, based on the software agent and the metrics, a second user interface comprising a plurality of regions configured to receive the application identifier and a selection of one or more of the metrics; and

causing, based on user interactions via the second user interface and based on the selection of the one or more metrics, a monitoring application to include the application identifier and the one or more metrics associated with the deployed application.

2 . The computer-implemented method of claim 1 , wherein:

the generating the second user interface is based on installation of the software agent, and

the monitoring application comprises a dashboard user interface comprising graphical representations of operations of the one or more metrics.

3 . The computer-implemented method of claim 1 , further comprising:

determining, based on second user interactions via the first user interface, a language identification of the deployed application and an operating system identification indicating an operating system of the deployed application, and

wherein the programming language for the software agent corresponds to the operating system of the deployed application.

4 . The computer-implemented method of claim 1 , further comprising:

determining, based on second user interactions via the first user interface, an application name associated with the deployed application and an environment identifier,

wherein the generating the software agent is further based on the application name and the environment identifier.

5 . The computer-implemented method of claim 1 , further comprising:

determining, based on second user interactions via the first user interface, a license key,

wherein the generating the software agent is further based on the license key.

6 . The computer-implemented method of claim 1 , wherein the one or more metrics comprise:

throughput statistics;

response time statistics;

slow performing transaction statistics;

average response times per transaction type statistics;

transaction count comparison statistics; or

a combination of the throughput statistics, response time statistics, the slow performing transaction statistics, the average response times per transaction type statistics, or the transaction count comparison statistics.

7 . The computer-implemented method of claim 1 , wherein the one or more metrics comprise:

error code statistics;

recent error code statistics;

error codes by code type statistics;

error counts statistics; or

a combination of the error code statistics, the recent error code statistics, the error codes by error code type statistics, or the error counts statistics.

8 . The computer-implemented method of claim 1 , wherein the one or more metrics comprise:

unique session statistics;

page views based on device type statistics;

session counts per platform statistics;

unique sessions per time window statistics;

average page rendering duration statistics;

sessions by device type statistics;

average document object model (DOM) processing duration statistics;

page popularity statistics;

average page views per session statistics; or

a combination of the unique session statistics, the page views based on device type statistics, the session counts per platform statistics, the unique sessions per time window statistics, the average page rendering duration statistics, the sessions by device type statistics, the average DOM processing duration statistics, the page popularity statistics, or the average page views per session statistics.

9 . The computer-implemented method of claim 1 , further comprising:

receiving, for the deployed application, a deployment environment identification identifying a deployment environment of the deployed application as a production environment or a non-production environment,

wherein the generating the software agent is further based on the received deployment environment identification.

10 . The computer-implemented method of claim 1 , further comprising:

generating, based on second user interactions via the second user interface, a modified monitoring application displaying a second selection of the one or more metrics; and

causing the modified monitoring application to monitor, via the API, the deployed application via the second selection of the one or more metrics.

11 . The computer-implemented method of claim 1 , further comprising:

receiving an operating system identification associated with an operating system of the deployed application; and

receiving operating system-specific instructions for generating the software agent,

wherein generating the software agent is further based on the received operating system-specific instructions.

12 . The computer-implemented method of claim 1 , wherein the agent type indicates a programming language for the software agent.

13 . An apparatus comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the apparatus to:

receive a dataset for deployed applications, wherein the dataset comprises application identifiers and profiling information;

generate, based on the received dataset, a first user interface;

receive, via the first user interface, one or more user selections, wherein the one or more user selections comprises:

an application name;

an application identifier, of a deployed application;

profiling information associated with the deployed application; and

an agent type;

generate, based on the application name, based on the application identifier, based on the profiling information, and based on the agent type, a software agent configured to expose operations, of the deployed application as metrics, wherein the metrics are configured to be addressable, via an application programming interface (API);

generate, based on the software agent and the metrics, a second user interface comprising a plurality of regions configured to receive the application identifier and a selection of one or more of the metrics; and

cause, based on user interactions with the second user interface and based on the selection of the one or more metrics, a monitoring application to include the application name and the one or more metrics associated with the deployed application.

14 . The apparatus of claim 13 , wherein the monitoring application comprises a dashboard user interface comprising graphical representations of the one or more metrics.

15 . The apparatus of claim 13 , wherein the instructions, when executed by the one or more processors, cause the apparatus to:

determine, based on second user interactions via the first user interface, a language identification of the deployed application and an operating system identification of the operating system of the deployed application, and

generate the software agent based on a software agent template configured to monitor, in the operating system, the deployed application written in the identified language.

16 . The apparatus of claim 13 , wherein the instructions, when executed by the one or more processors, cause the apparatus to:

determine, based on second user interactions via the first user interface, an environment identifier and a license key; and

generate the software agent based on the environment identifier and based on the license key.

17 . The apparatus of claim 13 , wherein the one or more metrics comprise:

throughput statistics;

response time statistics;

slow performing transaction statistics;

average response times per transaction type statistics;

transaction count comparison statistics; or

a combination of the throughput statistics, response time statistics, the slow performing transaction statistics, the average response times per transaction type statistics, or the transaction count comparison statistics.

18 . The apparatus of claim 13 , wherein the one or more metrics comprise:

error code statistics;

recent error code statistics;

error codes by code type statistics;

error counts statistics; or

a combination of the error code statistics, the recent error code statistics, the error codes by error code type statistics, or the error counts statistics.

19 . The apparatus of claim 13 , wherein the instructions, when executed by the one or more processors, cause the apparatus to:

receive, for the deployed application, a deployment environment identification indicating a deployment environment of the deployed application as a production environment or a non-production environment; and

generate the software agent based on the received deployment environment identification.

20 . One or more non-transitory media storing instructions that, when executed by one or more processors, cause the one or more processors to perform steps comprising:

receiving a dataset for deployed applications, wherein the dataset comprises application identifiers and profiling information;

generating, based on the received dataset, a first user interface;

receiving, via the first user interface, one or more user selections, wherein the one or more selections comprises:

an application name;

an application identifier, of a deployed application;

profiling information associated with the deployed application; and

an agent type;

generating, based on the application name, based on the application identifier, based on the profiling information, and based on the agent type, a software agent configured to expose operations, of the deployed application as metrics, wherein the metrics are configured to be addressable, via an application programming interface (API);

generating, based on the software agent and the metrics, a second user interface comprising a plurality of regions configured to receive the application identifier and a selection of one or more of the metrics; and

causing, based on user interactions via the second user interface and based on the selection of the one or more metrics, a monitoring application to include the application name and the one or more metrics associated with the deployed application.

Continuity (2)
Continuation 17362403 · Jun 29, 2021
Related Publication 20240004966A1 · Jan 4, 2024
References Cited (29)
US 6505246B1 · Land · 2003 [cited by examiner]
US 9274758B1 · Qin · 2016 [cited by examiner]
US 10073837B2 · Setayesh et al. · 2018 [cited by applicant]
US 10230601B1 · Qin · 2019 [cited by examiner]
US 10394802B1 · Porath et al. · 2019 [cited by applicant]
US 10467633B2 · Hsu et al. · 2019 [cited by applicant]
US 10509794B2 · Filippi et al. · 2019 [cited by applicant]
US 10547521B1 · Roy · 2020 [cited by examiner]
US 20100280962A1 · Chan · 2010 [cited by applicant]
US 20110126111A1 · Gill et al. · 2011 [cited by applicant]
US 20120284291A1 · Brown · 2012 [cited by examiner]
US 20130124807A1 · Nielsen · 2013 [cited by examiner]
US 20140089901A1 · Hadar · 2014 [cited by examiner]
US 20170286449A1 · Strube et al. · 2017 [cited by applicant]
US 20180082232A1 · Howard et al. · 2018 [cited by applicant]
US 20180089288A1 · Haggie et al. · 2018 [cited by applicant]
US 20180189344A1 · Akwule et al. · 2018 [cited by applicant]
US 20190190803A1 · Joshi et al. · 2019 [cited by applicant]
US 20200118030A1 · Sainani et al. · 2020 [cited by applicant]
US 20200320212A1 · Kaminski et al. · 2020 [cited by applicant]
US 20200387550A1 · Cappetta et al. · 2020 [cited by applicant]
US 20200409825A1 · Balasubramanian et al. · 2020 [cited by applicant]
US 20210126977A1 · Ruflin · 2021 [cited by examiner]
US 20210227351A1 · Mei · 2021 [cited by examiner]
US 20220245476A1 · Acharya · 2022 [cited by examiner]
WO WO2014088398A1 · 2014 [cited by examiner]
Aversa, Rocco, Luca Tasquier, and Salvatore Venticinque. “Management of cloud infrastructures through agents.” 2012 Third International Conference on Emerging Intelligent Data and Web Technologies. IEEE, 2012. (Year: 20… [cited by examiner]
Moustafa, Saadeldin, et al. “Slam: SLA monitoring framework for federated cloud services.” 2015 IEEE/ACM 8th International Conference on Utility and Cloud Computing (UCC). IEEE, 2015. (Year: 2015). [cited by examiner]
Nov. 24, 2022—(EP) Extended European Search Report—App No. 22181769. [cited by applicant]