Application health monitoring and reporting system

Patent metadata

Field	Value
Publication number	US-2023195603-A1
Application number	US-202218084668-A
Country	US
Kind code	A1
Filing date	Dec 20, 2022
Priority date	Dec 20, 2021
Publication date	Jun 22, 2023
Grant date	—

Abstract

An application health monitoring and reporting system is disclosed herein that allows managers of an application to have real-time visibility to the health of the application and which reports any issues associated with the application. The system is able to identify the issue(s) of why a particular service or micro-services, an icon, a picture or image or any item that is presented on a webpage as part of the application, as well as the failure, status of the failure, estimated time for resolving the failure, along with a hyperlink to view the full details of the failure which contains a summary of the overall health of the services. This system may help to monitor and report the issues in the production of applications, networks, underlying hardware/software components, and any other components.

First claim

1 . A method of health monitoring for an application, comprising:
receiving component data from a plurality of components associated with the application; retrieving, from a database, a component dependency list indicative of dependencies of the plurality of components associated with the application; determining a component status for each of the plurality of components in the component dependency list based on the received component data; and generating an application status notification indicating the determined component statuses for one or more of the of the plurality of components in the component dependency list.

2 . The method of claim 1 , further comprising:
transmitting the application status notification to an application manager through a portal.

3 . The method of claim 2 , further comprising:
receiving subscription parameters from the application manager through the portal, the subscription parameters indicating one or more application events that the application manager has subscribed to; and transmitting the application status notification to the application manager when the determined component statuses correspond to an application event of the one or more application events that the application manager has subscribed to.

4 . The method of claim 1 , further comprising:
transmitting the application status notification to a user of the application through the application.

5 . The method of claim 4 , wherein the application status notification comprises information allowing the user of the application to take a corrective action.

6 . The method of claim 1 , wherein the application status notification indicates a failed component of the plurality of components in the component dependency list, and the application status notification further indicates an estimated time to fix the failed component.

7 . The method of claim 1 , wherein each component of the plurality of components comprises a unique identifier that is used to identify the respective component.

8 . The method of claim 7 , wherein the component data is received as log data from the plurality of components, each log comprising the unique identifier for the respective component.

9 . The method of claim 8 , further comprising:
determining the component status from the component data based on whether a component state of the component has changed.

10 . The method of claim 9 , further comprising:
performing testing of one or more of the plurality of components.

11 . The method of claim 1 , further comprising:
applying pre-defined rules to the component data, wherein a component status is determined to have failed if a rule has been violated.

12 . The method of claim 11 , further comprising:
transmitting the application status notification if a rule has been violated.

13 . The method of claim 11 , further comprising:
retrieving a KPI for the component data; and determining that an anomaly has occurred based on the KPI when the component data did not violate a rule, wherein the component status may be determined based on the anomaly.

14 . The method of claim 1 , wherein the component dependency list is defined manually by an application manager.

15 . The method of claim 1 , further comprising:
determining, from the received component data, the plurality of components associated with the application and their dependencies; generating, based on the determined dependencies, the component dependency list; and storing the component dependency list.

16 . The method of claim 1 , wherein the plurality of components comprise any one or more of: hardware components, software components, service components, and micro-service components.

17 . A system for health monitoring for an application, comprising:
a processor; and a memory operably coupled with the processor, the memory having computer-executable instructions stored thereon, which when executed by the processor configure the processor to:
receive component data from a plurality of components associated with the application;
retrieve, from a database, a component dependency list indicative of dependencies of the plurality of components associated with the application;
determine a component status for each of the plurality of components in the component dependency list based on the received component data; and
generate an application status notification indicating the determined component statuses for one or more of the of the plurality of components in the component dependency list.

18 . A non-transitory computer-readable medium having computer-executable instructions stored thereon, which when executed by a computer configure the computer to perform a method comprising:
receiving component data from a plurality of components associated with the application; retrieving, from a database, a component dependency list indicative of dependencies of the plurality of components associated with the application; determining a component status for each of the plurality of components in the component dependency list based on the received component data; and generating an application status notification indicating the determined component statuses for one or more of the of the plurality of components in the component dependency list.

Assignees

• Bce Inc

Inventors

• Kang Jin
• Lu Guang
• Li Chuan Kevin
• Fan Xiaopeng
• Ali Ismaeel Ahmad
• Mahida Hitendrasinh
• Bhinder Manpreet

Classifications

• G06F11/3664 Primary

  Physics · mapped topic

• G06F11/3698 Primary

  Environments for analysis, debugging or testing of software · CPC title