CN110908855A - Micro-service operation maintenance device and method and electronic equipment - Google Patents
Micro-service operation maintenance device and method and electronic equipment Download PDFInfo
- Publication number
- CN110908855A CN110908855A CN201811089768.5A CN201811089768A CN110908855A CN 110908855 A CN110908855 A CN 110908855A CN 201811089768 A CN201811089768 A CN 201811089768A CN 110908855 A CN110908855 A CN 110908855A
- Authority
- CN
- China
- Prior art keywords
- abnormal
- micro
- service
- maintenance
- abnormal event
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a micro-service operation maintenance device and method and electronic equipment, which comprises the steps of monitoring the operation state of micro-service, determining abnormal micro-service and restarting the abnormal micro-service; determining an abnormal event according to the abnormal micro-service, determining the generation reason of the abnormal event according to the abnormal event positioning, and analyzing and determining a maintenance scheme according to the generation reason; searching a database according to the abnormal event, judging whether the abnormal event exists in the database or not, and if the abnormal event does not exist, saving the abnormal event, the generation reason of the abnormal event and a maintenance scheme in the database; if the abnormal events stored in the database are the same as the determined generation reasons, the abnormal events, the generation reasons and the maintenance schemes are stored in the database, if the abnormal events are not the same as the determined generation reasons, the abnormal events, the generation reasons and the maintenance schemes are stored in the database, if the abnormal events are the same as the determined maintenance schemes, the abnormal events, the generation reasons and the maintenance schemes are stored in the database, and if the abnormal events, the generation reasons and the maintenance schemes are not the same as the determined maintenance schemes.
Description
Technical Field
The present invention relates to the field of micro service technologies, and in particular, to a micro service operation maintenance device and method, and an electronic device.
Background
The platform realized based on the micro-service architecture depends on the normal operation of a plurality of background micro-services, and if some micro-services are abnormally operated, some functions are abnormal, even the normal operation of the whole platform is influenced. Therefore, the real-time operation status of each micro-service needs to be dynamically monitored, so as to ensure the normal operation of each micro-service, and simultaneously, quickly locate the reason for the abnormal operation of the abnormal micro-service.
Disclosure of Invention
In view of the above, the present invention provides a micro-service operation maintenance device and method, and an electronic device, which can dynamically monitor the operation state of each micro-service, restart an abnormal micro-service in time, ensure the normal operation of a platform, and quickly locate and solve the problem of the abnormal micro-service.
Based on the above purpose, the present invention provides a micro-service operation and maintenance device, which comprises:
the monitoring and restarting module is used for monitoring the running state of each micro-service, determining the micro-service which runs abnormally as the abnormal micro-service and restarting the abnormal micro-service;
the positioning and analyzing module is used for determining an abnormal event of the abnormal micro-service according to the abnormal micro-service, determining the generation reason of the abnormal event according to the abnormal event positioning, and analyzing and determining a maintenance scheme according to the generation reason;
the database is used for storing the abnormal events corresponding to the abnormal micro-services, the corresponding generation reasons and the corresponding maintenance schemes;
the classification module is used for searching whether the abnormal event exists in the database according to the abnormal event determined by the positioning and analyzing module, and if the abnormal event does not exist, the abnormal event determined by the positioning and analyzing module, the corresponding generation reason and the maintenance scheme are stored in the database; if the abnormal event exists, judging whether the generation reason corresponding to the abnormal event stored in the database is the same as the generation reason determined by the positioning and analyzing module, if the generation reasons are not the same, storing the abnormal event determined by the positioning and analyzing module and the corresponding generation reason and maintenance scheme in the database, if the generation reasons are the same, judging whether the maintenance scheme corresponding to the abnormal event stored in the database is the same as the maintenance scheme determined by the positioning and analyzing module, if the maintenance schemes are not the same, storing the abnormal event determined by the positioning and analyzing module and the corresponding generation reason and maintenance scheme in the database, and if the maintenance schemes are the same, not updating the database.
Optionally, the monitoring and restarting module includes:
the process detection restarting submodule is used for detecting whether each micro-service process exists or not at regular time, using the nonexistent micro-service process as the abnormal micro-service and restarting the abnormal micro-service;
and the heartbeat detection and restart submodule is used for regularly detecting whether the network heartbeat information of each micro service exists, taking the micro service without the network heartbeat information as the abnormal micro service, and restarting the abnormal micro service.
Optionally, the positioning and analyzing module determines an abnormal event of the abnormal micro service by using an abnormal detection tool, determines a cause of the abnormal event by using a program abnormal analysis tool according to the abnormal event, and analyzes and determines the maintenance scheme according to the cause.
Optionally, the micro-service operation and maintenance device further includes:
the modification marking module is used for determining corresponding modification strength and operation environment according to the maintenance scheme;
and the database is used for storing the abnormal events corresponding to the abnormal micro-services and the corresponding generation reasons, maintenance schemes, modification force and operating environment.
Optionally, the micro-service operation and maintenance device further includes:
and the information pushing module is used for pushing corresponding abnormal micro-service information to the user according to the user permission.
The embodiment of the invention also provides a micro-service operation maintenance method, which comprises the following steps:
s20: monitoring the running state of each micro-service, determining the micro-service with abnormal running as an abnormal micro-service, and restarting the abnormal micro-service;
s21: determining an abnormal event according to the abnormal micro-service, determining the generation reason of the abnormal event according to the abnormal event positioning, and analyzing and determining a maintenance scheme according to the generation reason;
s22: searching a database according to the abnormal event, judging whether the abnormal event exists in the database, and if so, executing S23; if not, executing S25;
s23: judging whether the generation reason corresponding to the abnormal event stored in the database is the same as the determined generation reason or not, and if so, executing step S24; if not, go to step S25;
s24: judging whether the maintenance scheme corresponding to the abnormal event stored in the database is the same as the maintenance scheme determined by analysis, if so, not updating the database, and ending the method; if not, go to step S25;
s25: and storing the abnormal event, the generation reason and the maintenance scheme thereof in the database.
Optionally, in step S20, the method for monitoring the operating state of each microservice includes:
and according to the type of the micro service, regularly monitoring whether the micro service process normally operates through a watching process, or regularly monitoring the network heartbeat information of the micro service, judging whether the micro service normally operates, and determining the micro service which quits operation or abnormally operates as the abnormal micro service.
Optionally, in step S21, according to the abnormal micro service, an abnormal event of the abnormal micro service is determined by using an abnormal detection tool, according to the abnormal event, a cause of the abnormal event is determined by using a program abnormality analysis tool, and according to the cause, the maintenance plan is analyzed and determined.
Optionally, the microservice operation maintenance method further includes: and determining corresponding modification force and operation environment according to the maintenance scheme, and storing the abnormal event corresponding to the abnormal micro-service, the corresponding generation reason, the maintenance scheme, the modification force and the operation environment in the database.
Optionally, the microservice operation maintenance method further includes: and pushing corresponding abnormal micro-service information to the user according to the user authority.
The embodiment of the invention also provides electronic equipment which comprises a memory, a processor and a computer program which is stored on the memory and can be operated on the processor, wherein the micro-service operation maintenance method is realized when the processor executes the program.
From the above, the micro-service operation maintenance device, the micro-service operation maintenance method and the electronic device provided by the invention can determine the abnormal micro-service by monitoring the operation state of the micro-service, restart the micro-service in time to ensure the normal operation of the platform, determine the abnormal event and the generation reason and the maintenance scheme thereof according to the abnormal micro-service, and continuously update and store various abnormal events, various generation reasons corresponding to the abnormal events, various maintenance schemes corresponding to different generation reasons, modification strength and operation environment corresponding to the maintenance schemes in a database, thereby providing maintenance basis for developers to quickly position and solve the problem of the abnormal micro-service.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a schematic diagram of the apparatus of the present invention;
FIG. 2 is a schematic flow chart of a method according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to specific embodiments and the accompanying drawings.
It should be noted that all expressions using "first" and "second" in the embodiments of the present invention are used for distinguishing two entities with the same name but different names or different parameters, and it should be noted that "first" and "second" are merely for convenience of description and should not be construed as limitations of the embodiments of the present invention, and they are not described in any more detail in the following embodiments.
FIG. 1 is a schematic diagram of an apparatus according to an embodiment of the present invention. As shown in the drawings, the micro-service operation and maintenance device provided in the embodiment of the present invention includes:
the monitoring and restarting module is used for monitoring the running state of each micro-service, determining the micro-service which runs abnormally as an abnormal micro-service and restarting the abnormal micro-service;
the positioning and analyzing module is used for determining an abnormal event of the abnormal micro-service, determining the generation reason of the abnormal event according to the abnormal event positioning, and analyzing and determining a maintenance scheme according to the generation reason;
the database is used for storing abnormal events corresponding to the abnormal micro-services, corresponding generation reasons and maintenance schemes;
the classification module is used for searching whether the abnormal event exists in the database according to the determined abnormal event, and if the abnormal event does not exist, the abnormal event determined by the positioning and analyzing module, the corresponding generation reason and the maintenance scheme are stored in the database; if the abnormal event exists, further judging whether the generation reason corresponding to the abnormal event stored in the database is the same as the generation reason determined by the positioning and analyzing module, if the generation reasons are not the same, storing the abnormal event determined by the positioning and analyzing module and the corresponding generation reason and maintenance scheme in the database, if the generation reasons are the same, further judging whether the maintenance scheme corresponding to the abnormal event stored in the database is the same as the maintenance scheme determined by the positioning and analyzing module, if the maintenance schemes are not the same, storing the abnormal event determined by the positioning and analyzing module and the corresponding generation reason and maintenance scheme in the database, and if the maintenance schemes are the same, not updating the database.
In the embodiment of the invention, the monitoring and restarting module comprises:
the process monitoring and restarting submodule is used for regularly monitoring whether each micro-service process exists or not, marking the nonexistent micro-service process as abnormal micro-service and restarting the abnormal micro-service;
and the heartbeat monitoring and restarting submodule is used for regularly monitoring whether the network heartbeat information of each micro service exists, marking the micro service without the network heartbeat information as an abnormal micro service, and restarting the abnormal micro service.
In the embodiment of the invention, the positioning and analyzing module is used for determining the abnormal event of the abnormal micro-service, determining the generation reason of the abnormal event according to the abnormal event positioning, and analyzing and determining the maintenance scheme according to the generation reason. Firstly, according to the abnormal micro-service determined by the monitoring and restarting module, determining an abnormal event of the abnormal micro-service by using an abnormal detection tool; then, according to the abnormal event, a program abnormal analysis tool is used for determining the generation reason of the abnormal event, and then, according to the generation reason of the abnormal event, a maintenance scheme is analyzed and determined.
The exception detection tool can utilize a program exception capture mechanism (system tool-event viewer) of the windows system to preliminarily locate an exception event when the exception micro service is abnormal. The program abnormity analysis tool can analyze and determine the cause of the program abnormity by positioning the position of the abnormal code, the program abnormity analysis tool can configure an abnormal log capture script, once the program is abnormal, the abnormal log capture script generates an abnormal log file, and the abnormal code position is directly positioned by looking up the abnormal log file.
In the embodiment of the invention, an interactive teaching platform is taken as an example, and the normal operation of the platform depends on micro services such as public micro service, screenshot micro service, live micro service and interactive teaching background service. The abnormal events of abnormal quitting of the live micro service stored in the database and the corresponding reasons for generation and maintenance are as follows:
TABLE 1
In the embodiment of the present invention, the micro-service operation maintenance apparatus further includes:
the modification marking module is used for determining corresponding modification strength and operation environment according to the maintenance scheme;
and the database is used for storing the abnormal events corresponding to the abnormal micro-services and the corresponding generation reasons, maintenance schemes, modification force and operation environment.
In the embodiment of the present invention, the micro-service operation maintenance apparatus further includes:
and the information pushing module is used for pushing the abnormal micro-service information to the user according to the user permission.
According to the user authority, the abnormal micro-service information of different contents can be pushed to the user. For example, for an administrator, pushing abnormal micro-service information including abnormal events of abnormal micro-services, generation reasons of the abnormal events, modification schemes and the like; and for a general user, pushing abnormal micro-services and abnormal micro-service information restarted by the abnormal micro-services.
FIG. 2 is a schematic flow chart of a method according to an embodiment of the present invention. As shown in the figure, the micro-service operation maintenance method disclosed by the invention comprises the following steps:
s20: monitoring the running state of each micro-service, determining the micro-service with abnormal running as an abnormal micro-service, and restarting the abnormal micro-service;
and according to the type of the micro-service, regularly monitoring whether the micro-service process normally operates through a watching process, or regularly monitoring network heartbeat information of the micro-service to judge whether the micro-service normally operates, and determining the micro-service which quits operation or abnormally operates as the abnormal micro-service.
After the abnormal micro-service is monitored, the abnormal micro-service is restarted to ensure the normal operation of the platform.
S21: determining an abnormal event of the abnormal micro-service by using an abnormal detection tool according to the abnormal micro-service; determining the generation reason of the abnormal event by using a program abnormal analysis tool according to the abnormal event, and analyzing and determining a maintenance scheme;
according to the determined abnormal micro-service, an abnormal event of the abnormal micro-service is positioned and determined by an abnormal detection tool; and analyzing and determining the reason of the abnormal event by using a program abnormal analysis tool according to the abnormal event, and further analyzing and determining a maintenance scheme for solving the abnormality.
Taking table 1 as an example, it is determined that the live microservice is an abnormal microservice, an abnormal event is preliminarily located by using an abnormality detection tool as program integrity failure, and the program abnormality analysis tool is further used to analyze and determine the generation cause of the program integrity failure as missing of the configuration file, so as to determine a maintenance scheme as comparing and checking the integrity of the configuration file, and completely supplementing the missing configuration file.
S22: searching a database according to the abnormal event, judging whether the abnormal event exists in the database, and executing S23 if the abnormal event exists; if not, executing S25;
s23: if the abnormal event already exists in the database, determining whether the generation reason corresponding to the abnormal event stored in the database is the same as the determined generation reason, and if so, executing step S24; if not, go to step S25;
s24: judging whether the maintenance scheme corresponding to the abnormal event stored in the database is the same as the maintenance scheme determined by analysis, if so, not updating the database, and ending; if not, go to step S25;
it should be noted here that, for the same abnormal event, although the cause is the same, the specific maintenance scheme may be different. Taking table 1 as an example, if the generation cause is missing of the configuration files, the integrity of each configuration file may be checked first, if the configuration files are incomplete, the maintenance scheme is to supplement the missing configuration files, if the configuration files are complete, further analysis is performed to determine whether a plurality of configuration items of each configuration file are complete, if the configuration items of a specific configuration file are incomplete, the maintenance scheme is to supplement the configuration items of the specific configuration file completely, and the like.
In the embodiment of the invention, different modification strengths and operation environments can be marked aiming at different maintenance schemes. For example, for a configuration file whose maintenance scheme is to supplement missing, a first modification strength is marked, and a current operating environment (an operating system, software configuration, hardware configuration, a network environment, etc.) of the microservice is marked, for a maintenance scheme, a configuration item of a specific configuration file is supplemented completely, a second modification strength is marked, a corresponding operating environment is marked, and then the maintenance scheme, the modification strength corresponding to the maintenance scheme, and the operating environment are stored in a database.
Therefore, by utilizing the device and the method of the invention, various abnormal events of abnormal micro-services, various generation reasons corresponding to the abnormal events, various maintenance schemes corresponding to different generation reasons, modification strength and operating environment corresponding to the maintenance schemes are continuously updated and stored in the database, the database can be continuously enriched, and maintenance basis is provided for developers to quickly position and solve the problems of the abnormal micro-services.
S25: and storing the abnormal event, the generation reason and the maintenance scheme thereof in a database.
In the embodiment of the invention, after the abnormal event of the abnormal micro-service, the generation reason and the maintenance scheme are determined according to the method, the updating micro-service is upgraded, and the micro-service is reloaded, so that the robustness of the micro-service operation is improved.
In the embodiment of the invention, the abnormal micro-service information can be pushed to different users according to the user authority. For example, a message that the abnormal micro service generates an abnormality and restarts the abnormal micro service is pushed to a general user, and an abnormal event of the abnormal micro service, a generation reason of the abnormal micro service and a maintenance scheme are pushed to an administrator user.
Based on the above purpose, an embodiment of an apparatus for executing the micro-service operation maintenance method is further provided in the embodiments of the present invention. The device comprises:
one or more processors, and a memory.
The apparatus for executing the micro-service operation maintenance method may further include: an input device and an output device.
The processor, memory, input device, and output device may be connected by a bus or other means.
The memory, which is a non-volatile computer-readable storage medium, may be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as program instructions/modules corresponding to the micro service operation maintenance method in the embodiment of the present invention (for example, the monitoring restart module, the locating and analyzing module, and the classifying module shown in fig. 1). The processor executes various functional applications and data processing of the server by running the nonvolatile software program, instructions and modules stored in the memory, namely, the micro-service operation and maintenance method of the above method embodiment is realized.
The memory may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of an apparatus that performs the micro-service operation maintenance method, and the like. Further, the memory may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some embodiments, the memory optionally includes memory remotely located from the processor, and these remote memories may be connected to the member user behavior monitoring device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device may receive input numeric or character information and generate key signal inputs related to user settings and function control of the device performing the micro-service operation maintenance method. The output device may include a display device such as a display screen.
The one or more modules are stored in the memory and, when executed by the one or more processors, perform the microservice operation maintenance method of any of the above method embodiments. The technical effect of the embodiment of the device for executing the micro-service operation maintenance method is the same as or similar to that of any method embodiment.
The embodiment of the invention also provides a non-transitory computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions can execute the processing method of the list item operation in any method embodiment. Embodiments of the non-transitory computer storage medium may be the same or similar in technical effect to any of the method embodiments described above.
Finally, it should be noted that, as will be understood by those skilled in the art, all or part of the processes in the methods of the above embodiments may be implemented by a computer program that can be stored in a computer-readable storage medium and that, when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like. The technical effect of the embodiment of the computer program is the same as or similar to that of any of the method embodiments described above.
Furthermore, the apparatuses, devices, etc. described in the present disclosure may be various electronic terminal devices, such as a mobile phone, a Personal Digital Assistant (PDA), a tablet computer (PAD), a smart television, etc., and may also be large terminal devices, such as a server, etc., and therefore the scope of protection of the present disclosure should not be limited to a specific type of apparatus, device. The client disclosed by the present disclosure may be applied to any one of the above electronic terminal devices in the form of electronic hardware, computer software, or a combination of both.
Furthermore, the method according to the present disclosure may also be implemented as a computer program executed by a CPU, which may be stored in a computer-readable storage medium. The computer program, when executed by the CPU, performs the above-described functions defined in the method of the present disclosure.
Further, the above method steps and system elements may also be implemented using a controller and a computer readable storage medium for storing a computer program for causing the controller to implement the functions of the above steps or elements.
Further, it should be appreciated that the computer-readable storage media (e.g., memory) described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. By way of example, and not limitation, nonvolatile memory can include Read Only Memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM), which can act as external cache memory. By way of example and not limitation, RAM is available in a variety of forms such as synchronous RAM (DRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The storage devices of the disclosed aspects are intended to comprise, without being limited to, these and other suitable types of memory.
The apparatus of the foregoing embodiment is used to implement the corresponding method in the foregoing embodiment, and has the beneficial effects of the corresponding method embodiment, which are not described herein again.
Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant to be exemplary only, and is not intended to intimate that the scope of the disclosure, including the claims, is limited to these examples; within the idea of the invention, also features in the above embodiments or in different embodiments may be combined, steps may be implemented in any order, and there are many other variations of the different aspects of the invention as described above, which are not provided in detail for the sake of brevity.
In addition, well known power/ground connections to Integrated Circuit (IC) chips and other components may or may not be shown within the provided figures for simplicity of illustration and discussion, and so as not to obscure the invention. Furthermore, devices may be shown in block diagram form in order to avoid obscuring the invention, and also in view of the fact that specifics with respect to implementation of such block diagram devices are highly dependent upon the platform within which the present invention is to be implemented (i.e., specifics should be well within purview of one skilled in the art). Where specific details (e.g., circuits) are set forth in order to describe example embodiments of the invention, it should be apparent to one skilled in the art that the invention can be practiced without, or with variation of, these specific details. Accordingly, the description is to be regarded as illustrative instead of restrictive.
While the present invention has been described in conjunction with specific embodiments thereof, many alternatives, modifications, and variations of these embodiments will be apparent to those of ordinary skill in the art in light of the foregoing description. For example, other memory architectures (e.g., dynamic ram (dram)) may use the discussed embodiments.
The embodiments of the invention are intended to embrace all such alternatives, modifications and variances that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, substitutions, improvements and the like that may be made without departing from the spirit and principles of the invention are intended to be included within the scope of the invention.
Claims (11)
1. A microservice operation maintenance device, comprising:
the monitoring and restarting module is used for monitoring the running state of each micro-service, determining the micro-service which runs abnormally as the abnormal micro-service and restarting the abnormal micro-service;
the positioning and analyzing module is used for determining an abnormal event of the abnormal micro-service according to the abnormal micro-service, determining the generation reason of the abnormal event according to the abnormal event positioning, and analyzing and determining a maintenance scheme according to the generation reason;
the database is used for storing the abnormal events corresponding to the abnormal micro-services, the corresponding generation reasons and the corresponding maintenance schemes;
the classification module is used for searching whether the abnormal event exists in the database according to the abnormal event determined by the positioning and analyzing module, and if the abnormal event does not exist, the abnormal event determined by the positioning and analyzing module, the corresponding generation reason and the maintenance scheme are stored in the database; if the abnormal event exists, judging whether the generation reason corresponding to the abnormal event stored in the database is the same as the generation reason determined by the positioning and analyzing module, if the generation reasons are not the same, storing the abnormal event determined by the positioning and analyzing module and the corresponding generation reason and maintenance scheme in the database, if the generation reasons are the same, judging whether the maintenance scheme corresponding to the abnormal event stored in the database is the same as the maintenance scheme determined by the positioning and analyzing module, if the maintenance schemes are not the same, storing the abnormal event determined by the positioning and analyzing module and the corresponding generation reason and maintenance scheme in the database, and if the maintenance schemes are the same, not updating the database.
2. The microservice operation and maintenance device of claim 1, wherein the monitoring and restarting module comprises:
the process detection restarting submodule is used for detecting whether each micro-service process exists or not at regular time, using the nonexistent micro-service process as the abnormal micro-service and restarting the abnormal micro-service;
and the heartbeat detection and restart submodule is used for regularly detecting whether the network heartbeat information of each micro service exists, taking the micro service without the network heartbeat information as the abnormal micro service, and restarting the abnormal micro service.
3. The microservice operation and maintenance device of claim 1, wherein the location and analysis module determines the abnormal event of the abnormal microservice by using an abnormal detection tool, determines the cause of the abnormal event by using a program abnormal analysis tool according to the abnormal event, and analyzes and determines the maintenance scheme according to the cause of the abnormal event.
4. The microservice operational maintenance device of claim 1, further comprising:
the modification marking module is used for determining corresponding modification strength and operation environment according to the maintenance scheme;
and the database is used for storing the abnormal events corresponding to the abnormal micro-services and the corresponding generation reasons, maintenance schemes, modification force and operating environment.
5. The microservice operational maintenance device of claim 1, further comprising:
and the information pushing module is used for pushing corresponding abnormal micro-service information to the user according to the user permission.
6. A micro-service operation maintenance method is characterized by comprising the following steps:
s20: monitoring the running state of each micro-service, determining the micro-service with abnormal running as an abnormal micro-service, and restarting the abnormal micro-service;
s21: determining an abnormal event according to the abnormal micro-service, determining the generation reason of the abnormal event according to the abnormal event positioning, and analyzing and determining a maintenance scheme according to the generation reason;
s22: searching a database according to the abnormal event, judging whether the abnormal event exists in the database, and if so, executing S23; if not, executing S25;
s23: judging whether the generation reason corresponding to the abnormal event stored in the database is the same as the determined generation reason or not, and if so, executing step S24; if not, go to step S25;
s24: judging whether the maintenance scheme corresponding to the abnormal event stored in the database is the same as the maintenance scheme determined by analysis, if so, not updating the database, and ending the method; if not, go to step S25;
s25: and storing the abnormal event, the generation reason and the maintenance scheme thereof in the database.
7. The method for micro-service operation and maintenance according to claim 6, wherein in step S20, the method for monitoring the operation status of each micro-service is as follows:
and according to the type of the micro service, regularly monitoring whether the micro service process normally operates through a watching process, or regularly monitoring the network heartbeat information of the micro service, judging whether the micro service normally operates, and determining the micro service which quits operation or abnormally operates as the abnormal micro service.
8. The method for operating and maintaining microservice according to claim 6, wherein in step S21, an abnormal event of the abnormal microservice is determined by an abnormal detection tool according to the abnormal microservice, a cause of the abnormal event is determined by a program abnormal analysis tool according to the abnormal event, and the maintenance plan is analyzed and determined according to the cause of the abnormal event.
9. The microservice operation maintenance method of claim 6, further comprising: and determining corresponding modification force and operation environment according to the maintenance scheme, and storing the abnormal event corresponding to the abnormal micro-service, the corresponding generation reason, the maintenance scheme, the modification force and the operation environment in the database.
10. The microservice operation maintenance method of claim 6, further comprising: and pushing corresponding abnormal micro-service information to the user according to the user authority.
11. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 6 to 10 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811089768.5A CN110908855A (en) | 2018-09-18 | 2018-09-18 | Micro-service operation maintenance device and method and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811089768.5A CN110908855A (en) | 2018-09-18 | 2018-09-18 | Micro-service operation maintenance device and method and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110908855A true CN110908855A (en) | 2020-03-24 |
Family
ID=69812891
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811089768.5A Pending CN110908855A (en) | 2018-09-18 | 2018-09-18 | Micro-service operation maintenance device and method and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110908855A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112053521A (en) * | 2020-08-12 | 2020-12-08 | 长沙理工大学 | An edge fingerprint database judgment system for leakage current of residential buildings |
| CN112187511A (en) * | 2020-08-28 | 2021-01-05 | 苏州浪潮智能科技有限公司 | Method, system, equipment and medium for positioning micro-service fusing abnormity |
| CN112306749A (en) * | 2020-10-26 | 2021-02-02 | 珠海格力电器股份有限公司 | Method and device for processing service in control system, and control system |
| CN113867129A (en) * | 2021-10-27 | 2021-12-31 | 珠海格力电器股份有限公司 | Redundancy control method, device and system, computer equipment and storage medium |
| CN114760441A (en) * | 2022-03-28 | 2022-07-15 | 北京优酷科技有限公司 | LED digital background shooting monitoring method and device |
| CN116366356A (en) * | 2023-04-10 | 2023-06-30 | 杭州安恒信息技术股份有限公司 | A device abnormality detection method, system, device and network protection device |
| CN118354345A (en) * | 2024-03-27 | 2024-07-16 | 北京唯得科技有限公司 | Alarm management method and system for 5G MIMO frequency-shifted dual-path system |
| JP7522369B2 (en) | 2021-01-08 | 2024-07-25 | 日本電信電話株式会社 | Control device, control method, and program |
| JP7522368B2 (en) | 2021-01-08 | 2024-07-25 | 日本電信電話株式会社 | Analysis device, analysis method, and program |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102866930A (en) * | 2012-08-22 | 2013-01-09 | 北京奇虎科技有限公司 | Blue screen repairing method, device and system |
| US20140244822A1 (en) * | 2013-02-27 | 2014-08-28 | Samsung Electronics Co., Ltd | Management apparatus and method of managing server node |
| CN106202535A (en) * | 2016-07-25 | 2016-12-07 | 浪潮(北京)电子信息产业有限公司 | A kind of method and system of the detection of RRD data base |
| CN107341068A (en) * | 2017-06-28 | 2017-11-10 | 北京优特捷信息技术有限公司 | The method and apparatus that O＆M troubleshooting is carried out by natural language processing |
| CN108173911A (en) * | 2017-12-18 | 2018-06-15 | 中国科学院声学研究所 | A microservice fault detection and processing method and device |
-
2018
- 2018-09-18 CN CN201811089768.5A patent/CN110908855A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102866930A (en) * | 2012-08-22 | 2013-01-09 | 北京奇虎科技有限公司 | Blue screen repairing method, device and system |
| US20140244822A1 (en) * | 2013-02-27 | 2014-08-28 | Samsung Electronics Co., Ltd | Management apparatus and method of managing server node |
| CN106202535A (en) * | 2016-07-25 | 2016-12-07 | 浪潮(北京)电子信息产业有限公司 | A kind of method and system of the detection of RRD data base |
| CN107341068A (en) * | 2017-06-28 | 2017-11-10 | 北京优特捷信息技术有限公司 | The method and apparatus that O＆M troubleshooting is carried out by natural language processing |
| CN108173911A (en) * | 2017-12-18 | 2018-06-15 | 中国科学院声学研究所 | A microservice fault detection and processing method and device |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112053521A (en) * | 2020-08-12 | 2020-12-08 | 长沙理工大学 | An edge fingerprint database judgment system for leakage current of residential buildings |
| CN112187511A (en) * | 2020-08-28 | 2021-01-05 | 苏州浪潮智能科技有限公司 | Method, system, equipment and medium for positioning micro-service fusing abnormity |
| US12149411B2 (en) | 2020-08-28 | 2024-11-19 | Inspur Suzhou Intelligent Technology Co., Ltd. | Method and system for locating micro-service fusing anomaly, device and medium |
| CN112306749A (en) * | 2020-10-26 | 2021-02-02 | 珠海格力电器股份有限公司 | Method and device for processing service in control system, and control system |
| JP7522369B2 (en) | 2021-01-08 | 2024-07-25 | 日本電信電話株式会社 | Control device, control method, and program |
| JP7522368B2 (en) | 2021-01-08 | 2024-07-25 | 日本電信電話株式会社 | Analysis device, analysis method, and program |
| CN113867129A (en) * | 2021-10-27 | 2021-12-31 | 珠海格力电器股份有限公司 | Redundancy control method, device and system, computer equipment and storage medium |
| CN114760441A (en) * | 2022-03-28 | 2022-07-15 | 北京优酷科技有限公司 | LED digital background shooting monitoring method and device |
| CN114760441B (en) * | 2022-03-28 | 2026-03-24 | 神力视界(深圳)文化科技有限公司 | LED Digital Background Shooting Monitoring Method and Device |
| CN116366356A (en) * | 2023-04-10 | 2023-06-30 | 杭州安恒信息技术股份有限公司 | A device abnormality detection method, system, device and network protection device |
| CN116366356B (en) * | 2023-04-10 | 2025-11-18 | 杭州安恒信息技术股份有限公司 | A method, system, device, and network protection equipment for detecting equipment malfunctions. |
| CN118354345A (en) * | 2024-03-27 | 2024-07-16 | 北京唯得科技有限公司 | Alarm management method and system for 5G MIMO frequency-shifted dual-path system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110908855A (en) | Micro-service operation maintenance device and method and electronic equipment | |
| CN110647471B (en) | Interface test case generation method, electronic device and storage medium | |
| US9612936B2 (en) | Correlation of source code with system dump information | |
| US9569325B2 (en) | Method and system for automated test and result comparison | |
| CN111930472B (en) | Code debugging method and device, electronic equipment and storage medium | |
| CN111193609B (en) | Application abnormity feedback method and device and application abnormity monitoring system | |
| CN107085549B (en) | Method and device for generating fault information | |
| CN111416836B (en) | Nginx-based server maintenance method and device, computer equipment and storage medium | |
| CN103309761B (en) | A kind of method and system of automatic error-correcting based on online service | |
| CN112597828B (en) | Webpage recognition model training method and device and webpage recognition method | |
| CN110838929B (en) | System error checking method and system error checking device | |
| CN110287093A (en) | Mobile terminal, data interface test method and storage medium | |
| CN104579830A (en) | Service monitoring method and device | |
| CN110737562A (en) | method and system for monitoring process and electronic equipment | |
| US11055416B2 (en) | Detecting vulnerabilities in applications during execution | |
| CN115333923B (en) | Fault point tracing analysis method, device, equipment and medium | |
| CN110601879B (en) | Method and device for forming Zabbix alarm process information and storage medium | |
| CN111142982B (en) | Event execution method and device, and electronic device | |
| CN111382415A (en) | A unified login method and device, and electronic equipment | |
| US10726069B2 (en) | Classification of log entry types | |
| CN111381849B (en) | Software updating method and device and electronic equipment | |
| US11888817B2 (en) | Filtering data logs from disparate data sources for processing by a security engine | |
| CN116661936A (en) | Page data processing method and device, computer equipment and storage medium | |
| KR101415270B1 (en) | Network system monitoring application installed on computing device | |
| CN112671615A (en) | Method, system and storage medium for collecting operation behavior data of front-end user |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200324 |