Application health examination method based on standard interface support expansion

Abstract

The invention discloses an application health examination method based on standard interface support expansion. The method comprises the following steps: defining a standard interface component; health examination of the open-source public component is realized; and temporarily storing health examination information. Various open source components can be easily integrated into their systems without worrying about the problem of mismatching of interfaces or inconsistent data formats. And according to own requirements and business logic, health examination functions are flexibly expanded and customized, so that the system can better adapt to continuously changing business requirements and technical environments.

Description

Technical Field

[0001] The present invention relates to the field of cloud technology and microservice technology, and in particular to an application health check method based on standard interface support extension. Background Art

[0002] In today's rapidly developing information technology field, with the widespread application of cloud computing and microservice architecture, application health.

[0003] The solutions of the prior art include:

[0004] Process detection and port activity detection strategies: Process detection is a crucial component of application health monitoring, focusing on the application's operational status. During process detection, the monitoring system periodically queries the operating system's process list to check whether the target application's process exists. If the target process does not exist or terminates abnormally, the monitoring system records the event and may trigger appropriate alerts or recovery mechanisms. Furthermore, process detection includes monitoring process resource usage, such as CPU and memory utilization, to assess application performance.

[0005] Port probing is another common application health monitoring method. It assesses application health by checking the availability of network services. During port probing, the monitoring system attempts to send probe packets to the target service's listening port and uses the response to determine whether the service is operating normally. For example, for an HTTP service, the system sends an HTTP request and checks the returned status code to determine service health. If the service fails to respond or returns an error status code, this indicates a potential problem.

[0006] Integrated health component monitoring strategy

[0007] Applications using this strategy, through the introduction of health check packages, record key status information at startup, including class loading status and memory usage. This information is a valuable data source for monitoring systems, helping system administrators fully understand the application's operating status.

[0008] When a monitoring system begins monitoring an application, it periodically requests health data from the application's server. This process is typically automated and can be configured to different intervals to suit different monitoring needs. This way, the monitoring system can continuously obtain the latest application health information, allowing it to promptly identify and address potential issues.

[0009] Policies not only improve system reliability and stability but also reduce the workload of system administrators. By monitoring the data provided by the system, they can quickly identify problems and take appropriate measures to ensure the continued stable operation of applications. Therefore, integrated health check packages have become an indispensable part of modern application development. Summary of the Invention

[0010] In view of the above problems, the present invention is proposed to provide an application health check method based on standard interface support extension that overcomes the above problems or at least partially solves the above problems.

[0011] According to one aspect of the present invention, a method for application health check based on standard interface support extension is provided, the method comprising:

[0012] Define standard interface components;

[0013] Implementation of health checks for open source public components;

[0014] Health check information is temporarily stored.

[0015] Optionally, the definition of the standard interface component specifically includes:

[0016] Define common fields based on key public information of health checks;

[0017] Define the standard interface to be queried, the interface for reporting health information, and the automatic scanning interface to achieve automatic integration of middleware components for application integration.

[0018] Optionally, the defined common fields specifically include: application name, application integration component name, corresponding health status, service name and service health status.

[0019] Optionally, the health check implementation of the open source public component specifically includes:

[0020] Integrate open source components of current applications based on defined standard interfaces;

[0021] Organize the standard health check information of components into information of standard interfaces.

[0022] Optionally, organizing the standard health check information of the component into information of the standard interface specifically includes: implementing component check functions commonly used in database health check and web server health check.

[0023] Optionally, the temporary storage of health check information specifically includes:

[0024] After the system is integrated and started by the application, the health check component follows the scheduled tasks;

[0025] Automatically scan the application and its integrated components. If developers customize business-related health check policies based on the interface, they will be automatically executed.

[0026] Collect and aggregate relevant indicator information into the cache, and then pull it to the monitoring system or apply it for regular reporting.

[0027] Optionally, the health check implementation of the open source public component specifically includes:

[0028] By defining standard interfaces and combining them with the open source components of current applications, we can organize component standard health check information.

[0029] During the implementation process, we studied and analyzed each open source component to obtain its working principles, performance indicators, and common fault types;

[0030] The corresponding health check standards are defined based on the information and converted into the form of standard interfaces.

[0031] Optionally, the temporary storage of health check information specifically includes:

[0032] After the system is started, the health check component automatically scans the application and all integrated components according to the preset scheduled tasks;

[0033] If developers customize business-related health check strategies based on interfaces;

[0034] During the health check process, metric information is collected and aggregated into a cache.

[0035] Optionally, the indicator information includes key performance indicators such as CPU usage, memory usage, and network latency.

[0036] This invention provides an application health check method based on standard interface support extensions. The method includes: defining standard interface components; implementing health checks on open-source public components; and temporarily storing health check information. This method allows users to easily integrate various open-source components into their systems without worrying about interface mismatches or inconsistent data formats. Health check functionality can be flexibly expanded and customized based on their needs and business logic, better adapting to evolving business requirements and technical environments.

[0037] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are specifically listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0039] Figure 1 A flowchart of an application health check method based on standard interface support extension provided by an embodiment of the present invention;

[0040] Figure 2 A flowchart of defining a standard interface component provided by an embodiment of the present invention;

[0041] Figure 3 A flowchart of the implementation of health check of open source public components provided by an embodiment of the present invention;

[0042] Figure 4 This is a flowchart of temporarily storing health check information provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0043] Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0044] The terms "comprises" and "comprising" and any variations thereof in the description, embodiments, claims and drawings of the present invention are intended to cover non-exclusive inclusions, for example, including a series of steps or units.

[0045] The technical solution of the present invention is further described in detail below with reference to the accompanying drawings and embodiments.

[0046] like Figure 1 As shown, the present invention provides an application health check method based on standard interface support extension, including: defining standard interface components; implementing health checks on open source public components; and temporarily storing health check information.

[0047] Define standard interface components: Based on the key public information of health checks, this software defines the following public fields: application name, application integration component name, corresponding health status, business name, business health status, etc., and defines standard interfaces to be queried, interfaces for reporting health information, and automatic scanning interfaces to realize the automatic integration of middleware components for application integration.

[0048] Implementation of health checks for open source public components: Based on the defined standard interfaces and the currently used open source components, the standard health check information of the components is organized into information on the standard interfaces. For example, common component check functions such as database health checks and web server health checks are implemented.

[0049] Temporary storage of health check information: After the system is integrated and started by the application, the health check component automatically scans the application and integrated components based on scheduled tasks. If the developer has customized business-related health check policies based on the interface, these policies will also be automatically executed, and relevant indicator information will be collected and aggregated into the cache, to be pulled to the monitoring system or reported by the application on a scheduled basis.

[0050] like Figure 2 As shown, define the standard interface components:

[0051] Based on the key public information of health checks, a series of common fields are defined, including application name, application integration component name, corresponding health status, business name, and business health status. These fields provide a standardized health data structure for the system, ensuring the consistency and traceability of various health information.

[0052] To enable automated integration of middleware components for application integration, the software defines three key interfaces: a standard query interface, a health information reporting interface, and an automatic scanning interface. The standard query interface allows users or the system to retrieve specific health data based on pre-set standard query criteria. The health information reporting interface allows each component to proactively report its own health status, ensuring real-time monitoring and management of the system. Finally, the automatic scanning interface performs regular or on-demand health scans of various components in the system, promptly identifying and addressing potential issues.

[0053] like Figure 3 As shown, the health check of open source public components is implemented as follows:

[0054] By defining a standard interface and integrating it with currently used open-source components, we have achieved the organization of standardized component health check information. This standard interface not only covers common component check functions, such as database and web server health checks, but also provides extensibility for custom components. This ensures that health check information between different components is transmitted and processed in a unified, standardized format, improving the maintainability and scalability of the entire system.

[0055] During the implementation process, we first conducted in-depth research and analysis of each open source component to understand its operating principles, performance indicators, and common failure types. Based on this information, we defined corresponding health check standards and converted these standards into standard interfaces. Regardless of which open source component a developer uses, they can check its health by calling these standard interfaces.

[0056] like Figure 4 As shown, the health check information is temporarily stored:

[0057] After the system starts, the health check component automatically scans the application and all integrated components according to the preset scheduled tasks. This automated scanning mechanism ensures that the system can continuously monitor the health of each component in real time, and promptly identify and address potential problems.

[0058] If developers customize business-related health check policies based on the interface, these policies are automatically executed. The system not only performs general health check tasks but also offers customized checks based on specific business needs. This flexibility allows the system to better adapt to diverse application scenarios and business requirements, improving its adaptability and reliability.

[0059] During the health check, relevant metrics are collected and aggregated into a cache. These metrics include key performance indicators (KPIs) such as CPU usage, memory usage, and network latency. These metrics are periodically pulled by the monitored system or reported by the application.

[0060] Beneficial effects:

[0061] Standardization: Standardized interfaces ensure compatibility and interoperability between different components. This design enables developers to easily integrate various open source components into their systems without worrying about interface mismatches or inconsistent data formats.

[0062] Flexibility and Convenience: Support for developers to customize health check components provides greater flexibility and convenience. Developers can flexibly expand and customize health check functions according to their own needs and business logic, better adapting to changing business needs and technical environments.

[0063] The above specific implementation methods further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific implementation methods of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for application health check based on standard interface support extension, characterized in that: The application health check method includes: Define standard interface components; Implementation of health check for open source public components; Health check information is temporarily stored.

2. The application health check method based on standard interface support extension according to claim 1, characterized in that: The definition of the standard interface component specifically includes: Define common fields based on key public information of health checks; Define the standard interface to be queried, the interface for reporting health information, and the automatic scanning interface to achieve automatic integration of middleware components for application integration.

3. The application health check method based on standard interface support extension according to claim 2, characterized in that: The defined common fields specifically include: application name, application integration component name, corresponding health status, service name and service health status.

4. The application health check method based on standard interface support extension according to claim 1, characterized in that: The health check implementation of the open source public components specifically includes: Integrate open source components of current applications based on defined standard interfaces; Organize the standard health check information of components into information of standard interfaces.

5. The application health check method based on standard interface support extension according to claim 4 is characterized in that: The said arranging the standard health check information of the component into the information of the standard interface specifically includes: realizing the commonly used component check functions such as database health check and web server health check.

6. The application health check method based on standard interface support extension according to claim 1, characterized in that: The temporary storage of health check information specifically includes: After the system is integrated and started by the application, the health check component follows the scheduled tasks; Automatically scan the application and its integrated components. If developers customize business-related health check policies based on the interface, they will be automatically executed. Collect and aggregate relevant indicator information into the cache, and then pull it to the monitoring system or apply it for regular reporting.

7. The application health check method based on standard interface support extension according to claim 1, characterized in that: The health check implementation of the open source public components specifically includes: By defining standard interfaces and combining them with the open source components of current applications, we can organize component standard health check information. During the implementation process, we studied and analyzed each open source component to obtain its working principles, performance indicators, and common fault types; The corresponding health check standards are defined based on the information and converted into the form of standard interfaces.

8. The application health check method based on standard interface support extension according to claim 1, characterized in that: The temporary storage of health check information specifically includes: After the system is started, the health check component automatically scans the application and all integrated components according to the preset scheduled tasks; If developers customize business-related health check strategies based on interfaces; During the health check process, metric information is collected and aggregated into a cache.

9. The application health check method based on standard interface support extension according to claim 8, characterized in that: The indicator information includes key performance indicators such as CPU usage, memory usage, and network latency.

Images