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

Patent metadata

Field	Value
Publication number	US-11966324-B2
Application number	US-202217833689-A
Country	US
Kind code	B2
Filing date	Jun 6, 2022
Priority date	Jun 27, 2019
Publication date	Apr 23, 2024
Grant date	Apr 23, 2024

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:
determining a plurality of dependencies associated with a first application;
configuring a monitoring application to monitor the plurality of dependencies using a plurality of monitoring interfaces, wherein configuring the monitoring application to monitor a first dependency of the plurality of dependencies comprises:
querying a monitoring interface application to determine a set of monitoring interfaces associated with the first dependency;
identifying one or more first monitoring interfaces of the set of monitoring interfaces based on at least one monitoring dashboard associated with the first dependency and provided by the monitoring interface application, wherein the at least one monitoring dashboard is associated with at least one second application that also depends on the first dependency; and
configuring the monitoring application to monitor the first dependency using the one or more first monitoring interfaces of the set of monitoring interfaces; and

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 an update to the one or more first monitoring interfaces; and
re-configuring the monitoring application based on the update to the one or more first monitoring interfaces.

2. The method of claim 1 , wherein querying the monitoring interface application to determine an updated set of monitoring interfaces associated with the first dependency at the second time comprises:
identifying one or more second monitoring interfaces of the set of monitoring interfaces based on the at least one monitoring dashboard associated with the first dependency.

3. The method of claim 2 , wherein determining that the updated set of monitoring interfaces indicates an update to the one or more first monitoring interfaces comprises at least one of:
determining that a new monitoring interface associated with the first dependency has been added to the at least one monitoring dashboard; or
determining that an old monitoring interface associated with the first dependency has been removed from the at least one monitoring dashboard.

4. The method of claim 2 , wherein determining that the updated set of monitoring interfaces indicates an update to the one or more first monitoring interfaces comprises:
determining that an operating status threshold associated with a first monitoring interface associated with the first dependency has been modified on the at least one monitoring dashboard.

5. The method of claim 1 , wherein:
determining that the updated set of monitoring interfaces indicates an update to the one or more first monitoring interfaces comprises determining that a new monitoring interface is present in the updated set of monitoring interfaces, and
re-configuring the monitoring application based on the update to the one or more first monitoring interfaces comprises re-configuring the monitoring application to monitor the first dependency using the new monitoring interface.

6. The method of claim 1 , wherein:
determining that the updated set of monitoring interfaces indicates an update to the one or more first monitoring interfaces comprises determining that at least one modified monitoring interface, comprising an updated version of a corresponding monitoring interface in the one or more first monitoring interfaces, is present in the updated set of monitoring interfaces, and
re-configuring the monitoring application based on the update to the one or more first monitoring interfaces comprises re-configuring the monitoring application to monitor the first dependency using the modified monitoring interface.

7. The method of claim 1 , wherein:
determining that the updated set of monitoring interfaces indicates an update to the one or more first monitoring interfaces comprises determining that at least one old monitoring interface, of the one or more first monitoring interfaces, is not present in the updated set of monitoring interfaces, and
re-configuring the monitoring application based on the update to the one or more first monitoring interfaces comprises re-configuring the monitoring application to no longer monitor the first dependency using the old monitoring interface.

8. The method of claim 1 , wherein configuring the monitoring application to monitor the first dependency further comprises:
determining, based on the at least one monitoring dashboard, a first unhealthy operating status threshold associated with the first dependency,
wherein the monitoring application is configured to monitor the first dependency using the first unhealthy operating status threshold.

9. The method of claim 8 , wherein re-configuring the monitoring application to monitor the first dependency further comprises:
determining, based on the at least one monitoring dashboard, an updated second unhealthy operating status threshold associated with the first dependency,
wherein the monitoring application is re-configured to monitor the first dependency using the updated second unhealthy operating status threshold.

10. The method of claim 8 , 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 at least one second application.

11. The method of claim 8 , 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.

12. 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.

13. 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.

14. 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.

15. A monitoring device comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processors, cause the monitoring device to perform steps comprising:
determine a plurality of dependencies associated with a first application;
configure a monitoring application to monitor the plurality of dependencies using a plurality of monitoring interfaces, wherein the instructions cause the monitoring device to configure the monitoring application to monitor a first dependency of the plural

Assignees

• Capital One Services Llc

Inventors

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

Classifications

• G06F11/3672 Primary

  Test management · CPC title

• G06F16/90335

  Query processing · CPC title

• G06N20/00

  Machine learning · CPC title

• G06F11/302 Primary

  where the computing system component is a software system · CPC title

• G06F2201/865

  Monitoring of software · CPC title