Discovery crawler for application dependency discovery, reporting, and management tool

Patent metadata

Field	Value
Publication number	US-11620211-B2
Application number	US-202217833557-A
Country	US
Kind code	B2
Filing date	Jun 6, 2022
Priority date	Jun 27, 2019
Publication date	Apr 4, 2023
Grant date	Apr 4, 2023

Abstract

Techniques for monitoring operating statuses of an application and its dependencies are provided. A monitoring application may collect and report the operating status of the monitored application and each dependency. Through use of existing monitoring interfaces, the monitoring application can collect operating status without requiring modification of the underlying monitored application or dependencies. The monitoring application may determine a problem service that is a root cause of an unhealthy state of the monitored application. Dependency analyzer and discovery crawler techniques may automatically configure and update the monitoring application. Machine learning techniques may be used to determine patterns of performance based on system state information associated with performance events and provide health reports relative to a baseline status of the monitored application. Also provided are techniques for testing a response of the monitored application through modifications to API calls. Such tests may be used to train the machine learning model.

First claim

What is claimed is:

1. A computer-implemented method comprising:
receiving a request to on-board a first application for monitoring by a monitoring application;
determining a plurality of dependencies associated with the first application;
querying a monitoring interface application to determine a set of monitoring interfaces associated with the plurality of dependencies;
identifying one or more first monitoring interfaces of the set of monitoring interfaces based on at least a first monitoring dashboard provided by the monitoring interface application and associated with a first dependency of the plurality of dependencies, wherein the first monitoring dashboard is associated with a second application that also depends on the first dependency;
determining, based on the first monitoring dashboard, a first unhealthy operating status threshold associated with the first dependency;
configuring the monitoring application to monitor the first dependency using the one or more first monitoring interfaces and based on the determined first unhealthy operating status threshold;
detecting, by the monitoring application, that the operating status of the first dependency satisfies the first unhealthy operating status threshold; and
generating, by the monitoring application and based on the detecting, an alert indicating:
that the first application depends on the first dependency, and
that the first dependency has an unhealthy operating status.

2. The method of claim 1 , wherein the first monitoring dashboard was created by a user associated with the second application prior to receiving the request to on-board the first application.

3. The method of claim 1 , wherein the first unhealthy operating status threshold is an attribute of the first monitoring dashboard corresponding to an alert threshold configured by a user of the second application.

4. The method of claim 1 , wherein the first monitoring dashboard comprises an attribute corresponding to an alert threshold configured by a user of the second application,
wherein the first unhealthy operating status threshold is determined based on the alert threshold of the first monitoring dashboard.

5. The method of claim 1 , wherein the plurality of dependencies comprises:
one or more immediate dependencies associated with the first application; and
one or more sub-dependencies associated with the first application, wherein each sub-dependency of the one or more sub-dependencies corresponds to a dependency of a respective immediate dependency or sub-dependency associated with the first application.

6. The method of claim 1 , wherein the first dependency is at least one of:
an Application Programming Interface (API) associated with a resource utilized by the first application and the second application,
a platform utilized by the first application and the second application, or
a network utilized by the first application to communicate with another dependency and the second application.

7. The method of claim 1 , further comprising:
determining the operating status of a given dependency based on determining one or more of:
whether a resource associated with the given dependency is accessible;
a response latency associated with requests to the given dependency;
an error rate associated with requests to the given dependency; or
an error state or error message provided by the given dependency.

8. The method of claim 1 , wherein configuring the monitoring application to monitor the first dependency using the one or more first monitoring interfaces comprises:
configuring the monitoring application to utilize the one or more first monitoring interfaces through at least one monitoring query associated with the monitoring interface application.

9. The method of claim 1 , further comprising:
re-configuring the monitoring application to monitor the first dependency at a second time, after originally configuring the monitoring application to monitor the first dependency, by:
determining, based on the first monitoring dashboard, an updated second unhealthy operating status threshold associated with the first dependency; and
re-configuring the monitoring application to monitor the first dependency using the one or more first monitoring interfaces and based on the updated second unhealthy operating status threshold.

10. The method of claim 1 , further comprising:
re-configuring the monitoring application to monitor the first dependency at a second time, after originally configuring the monitoring application to monitor the first dependency, by:
querying the monitoring interface application to determine an updated set of monitoring interfaces associated with the first dependency at the second time;
determining that the updated set of monitoring interfaces indicates the addition, update, or removal of a modified monitoring interface; and
re-configuring the monitoring application to add, update, or remove the modified monitoring interface for monitoring the first dependency.

11. A monitoring device comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processors, causes the monitoring device to perform steps comprising:
receive a request to on-board a first application for monitoring by a monitoring application;
determine a plurality of dependencies associated with the first application;
query a monitoring interface application to determine a set of monitoring interfaces associated with the plurality of dependencies;
identify one or more first monitoring interfaces of the set of monitoring interfaces based on at least a first monitoring dashboard provided by the monitoring interface application and associated with a first dependency of the plurality of dependencies, wherein the first monitoring dashboard is associated with a second application that also depends on the first dependency;
determine, based on the first monitoring dashboard, a first unhealthy operating status threshold associated with the first dependency;
configure the monitoring application to monitor the first dependency using the one or more first monitoring interfaces and based on the determined first unhealthy operating status threshold;
detect, by the monitoring application, that the operating status of the first dependency satisfies the first unhealthy operating status threshold; and
generate, by the monitoring application and based on the detecting, an alert indicating:
that the first application depends on the first dependency, and
that the first dependency has an unhealthy operating status.

12. The monitoring device of claim 11 , wherein the first monitoring dashboard was created by a user associated with the second application prior to receiving the request to on-board the first application.

13. The monitoring device of claim 11 , wherein the first unhealthy operating status threshold is an attribute of the first monitoring dashboard corresponding to an alert threshold configured by a user of the second application.

14. The monitoring device of claim 11 , wherein the instructions further cause the monitoring device to:
re-configure the monitoring application to monitor the first dependency at a second time, after originally configuring the monitoring application to monitor the first dependency, by causing the monitoring device to:
determine, based on the first monitoring dashboard, an updated second unhealthy operating status threshold associated with the first dependency; and
re-configure the monitoring application to monitor the first dependency using the one or more first monitoring interfaces and based on the updated second u

Assignees

• Capital One Services Llc

Inventors

• Balasubramanian Muralidharan
• Barnum Eric K
• Dallen Julie
• Watson David

Classifications

• G06F2201/86

  Event-based monitoring · CPC title

• G06F11/3409

  for performance assessment · CPC title

• G06N20/00

  Machine learning · CPC title

• G06F11/0754

  by exceeding limits · CPC title

• G06F11/3672 Primary

  Test management · CPC title