CN113010365A - System running state monitoring method, system running state detection device, electronic equipment and storage medium - Google Patents
System running state monitoring method, system running state detection device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN113010365A CN113010365A CN201911328753.4A CN201911328753A CN113010365A CN 113010365 A CN113010365 A CN 113010365A CN 201911328753 A CN201911328753 A CN 201911328753A CN 113010365 A CN113010365 A CN 113010365A
- Authority
- CN
- China
- Prior art keywords
- service
- request
- calling
- called
- called service
- 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
- 238000000034 method Methods 0.000 title claims abstract description 94
- 238000012544 monitoring process Methods 0.000 title claims abstract description 39
- 238000003860 storage Methods 0.000 title claims abstract description 22
- 238000001514 detection method Methods 0.000 title claims description 19
- 230000002159 abnormal effect Effects 0.000 claims abstract description 59
- 230000008569 process Effects 0.000 claims abstract description 35
- 238000004590 computer program Methods 0.000 claims description 10
- 238000012806 monitoring device Methods 0.000 claims 1
- 230000009286 beneficial effect Effects 0.000 abstract 1
- 238000010586 diagram Methods 0.000 description 18
- 238000012795 verification Methods 0.000 description 12
- 230000005856 abnormality Effects 0.000 description 10
- 238000012545 processing Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 230000005540 biological transmission Effects 0.000 description 4
- 230000003993 interaction Effects 0.000 description 3
- 239000000835 fiber Substances 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000001902 propagating effect Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 1
- 229910052802 copper Inorganic materials 0.000 description 1
- 239000010949 copper Substances 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003238 somatosensory effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3055—Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a method for monitoring system running state, a method and a device for detecting system running abnormity, electronic equipment and a computer readable storage medium. The monitoring method comprises the following steps: receiving a service request; generating a request identifier corresponding to the service request, and adding the request identifier to the service request; determining at least one invoked service based on the service request; sending a service request containing the request identifier to the at least one called service, wherein each called service records the request identifier and calling information in the process of executing the service request, and the calling information at least comprises: the ID of the called service. The invention can monitor the running state of the current system and is beneficial to positioning the abnormal running problem in the system.
Description
Technical Field
The present invention relates to the field of monitoring software technologies, and in particular, to a method and an apparatus for monitoring a system operating status, a method and an apparatus for detecting system operating anomalies, an electronic device, and a storage medium.
Background
The state of monitoring software in a production environment is always the most concerned problem of each company, and the current operation state of a system and a module is generally judged through the numerical value of each index (access amount, payment amount, auditing amount and the like).
The method is a mode for indirectly monitoring the operation condition of the system by judging the operation state of the current system through each important index. As the result value of each index is the result of system operation, once a certain link has a problem, the final result can be influenced, and the system state can be indirectly reflected. But the running state is judged by the index, and whether the existing system or module has a problem or not can be only determined. Therefore, the existing monitoring means is too rough to accurately reflect the problem.
Disclosure of Invention
The invention aims to provide a method and a device for monitoring the running state of a system, electronic equipment and a storage medium, so as to determine the running state of the current system and help to locate the running abnormal problem in the system.
According to a first aspect of the present invention, there is provided a method for monitoring an operation state of a system, executed on a server side, including:
receiving a service request;
generating a request identifier corresponding to the service request, and adding the request identifier to the service request;
determining at least one invoked service based on the service request;
sending the service request containing the request identifier to the called service, wherein each request identifier and calling information are recorded by the at least one called service in the process of executing the service request, and the calling information at least comprises: the ID of the called service.
Optionally, the calling information further includes: one or more of a call start time, a call end time, a call parameter of the called service, a call result return value of the called service, and call exception information.
Optionally, in the process of executing the service request, recording the request identifier and the invocation information by each invoked service includes:
and when the called service starts to execute the service request, recording the request identification, the ID of the called service, the calling parameter of the called service and calling start time.
Optionally, in the process of executing the service request, recording the request identifier and the invocation information by each invoked service includes:
and when the called service finishes executing the service request, recording the request identification, the ID of the called service, the calling result return value of the called service and calling end time.
Optionally, in the process of executing the service request, the recording the request identifier and the call information by the called service includes:
when the called service is abnormal in the process of executing the service request, recording the request identification, the ID of the called service and calling abnormal information; the calling exception information comprises calling exception time and calling exception content.
According to a second aspect of the present invention, there is provided a method for detecting system operation abnormality, including:
obtaining an anomaly detection request, wherein the anomaly detection request comprises a request identifier according to the first aspect of the invention;
determining a service request containing the request identification and a called service for executing the service request according to the request identification;
and acquiring the calling information which is recorded in the called service and is associated with the request identifier according to the request identifier.
And determining the called service with abnormal operation according to the calling information.
According to a third aspect of the present invention, there is provided a system operation state monitoring apparatus, comprising:
the receiving module is used for receiving the service request;
the identification module is used for generating a request identification corresponding to the service request and adding the request identification to the service request;
a first determining module for determining at least one invoked service based on the service request;
a sending module, configured to send a service request including the request identifier to the called service, where each called service records the request identifier and calling information in a process of executing the service request, where the calling information at least includes: the ID of the called service.
Optionally, the calling information further includes: one or more of a call start time, a call end time, a call parameter of the called service, a call result return value of the called service, and call exception information.
Optionally, in the process of executing the service request, recording the request identifier and the invocation information by each invoked service includes:
and when the called service starts to execute the service request, recording the request identification, the ID of the called service, the calling parameter of the called service and calling start time.
Optionally, in the process of executing the service request, recording the request identifier and the invocation information by each invoked service includes:
and when the called service finishes executing the service request, recording the request identification, the ID of the called service, the calling result return value of the called service and calling end time.
Optionally, in the process of executing the service request, the recording the request identifier and the call information by the called service includes:
when the called service is abnormal in the process of executing the service request, recording the request identification, the ID of the called service and calling abnormal information; the calling exception information comprises calling exception time and calling exception content.
According to a fourth aspect of the present invention, there is provided a system operation abnormality detection apparatus, comprising:
a first obtaining module, configured to obtain an anomaly detection request, where the anomaly detection request includes a request identifier according to a first method of the present invention;
the first determining module is used for determining the service request containing the request identification and the called service for executing the service request according to the request identification;
and the second acquisition module is used for acquiring the calling information which is recorded in the called service and is associated with the request identifier according to the request identifier.
And the second determination module is used for determining the called service with abnormal operation according to the calling information.
Optionally, the determining, by the second determining module, the called service with abnormal operation according to the calling information includes:
and determining whether the called service is abnormal according to the difference between the calling start time and the calling end time of the called service.
Optionally, the determining, by the second determining module, the called service with abnormal operation according to the calling information includes:
determining a called service with abnormal operation according to the calling abnormal information;
and determining the operation position of the abnormal situation according to the calling abnormal content.
According to a fifth aspect of the present invention, there is provided an electronic apparatus comprising:
the apparatus according to the third or fourth aspect of the invention; alternatively, the first and second electrodes may be,
a processor and a memory for storing executable instructions for controlling the processor to perform the method according to the first or second aspect of the invention.
According to a sixth aspect of the present invention, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method according to the first or second aspect of the present invention.
According to the embodiment of the invention, the corresponding request identifier is added to the received service request, and in the execution process of the service request, the corresponding calling information and the corresponding request identifier are recorded by the called service of each executed service request, so that the running state of the current system can be directly determined.
Other features of the present invention and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention.
Fig. 1 is a block diagram of a hardware configuration structure of an electronic device that can be used to implement an embodiment of the present invention.
Fig. 2 is a flowchart of steps of a method for monitoring a system operating state according to an embodiment of the present invention.
Fig. 3 is a first exemplary flowchart of the recording steps of the monitoring method for the system operation state according to the present invention.
Fig. 4 is a second exemplary flowchart of the recording steps of the monitoring method for the system operation state according to the present invention.
Fig. 5 is a flowchart illustrating a method for detecting system operation abnormality according to an embodiment of the present invention.
Fig. 6 is a block diagram of a system operation state monitoring apparatus according to an embodiment of the present invention.
Fig. 7 is a block diagram showing a configuration of a system operation abnormality detection apparatus according to an embodiment of the present invention.
Fig. 8 is a block diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
Various exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, the numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present invention unless specifically stated otherwise.
The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the invention, its application, or uses.
Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.
In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.
Fig. 1 is a block diagram showing a configuration of hardware of an electronic apparatus 1000 that can implement an embodiment of the present invention.
The electronic device 1000 may be a laptop, desktop, cell phone, tablet, server, etc.
The server device may be a unitary server or a distributed server across multiple computers or computer data centers. The server may be of various types, such as, but not limited to, a node device of a content distribution network, a storage server of a distributed storage system, a cloud database server, a cloud computing server, a cloud management server, a web server, a news server, a mail server, a message server, an advertisement server, a file server, an application server, an interaction server, a storage server, a database server, a proxy server, or the like. In some embodiments, each server may include hardware, software, or embedded logic components or a combination of two or more such components for performing the appropriate functions supported or implemented by the server. For example, a server, such as a blade server, a cloud server, etc., or may be a server group consisting of a plurality of servers, which may include one or more of the above types of servers, etc.
As shown in fig. 1, the electronic device 1000 may include a processor 1100, a memory 1200, an interface device 1300, a communication device 1400, or may further include a display device 1500, an input device 1600, a speaker 1700, a microphone 1800, and the like. The processor 1100 may be a central processing unit CPU, a microprocessor MCU, or the like, and is configured to execute a computer program. The computer program may be written in an instruction set of an architecture such as x86, Arm, RISC, MIPS, SSE, etc. The memory 1200 includes, for example, a ROM (read only memory), a RAM (random access memory), a nonvolatile memory such as a hard disk, and the like. The interface device 1300 includes, for example, a USB interface, a headphone interface, and the like. The communication device 1400 is capable of wired communication using an optical fiber or a cable, or wireless communication, for example, and may specifically include WiFi communication, bluetooth communication, 2G/3G/4G/5G communication, and the like. The display device 1500 is, for example, a liquid crystal display panel, a touch panel, or the like. The input device 1600 may include, for example, a touch screen, a keyboard, a somatosensory input, and the like. A user can input/output voice information through the speaker 1700 and the microphone 1800.
The electronic device shown in fig. 1 is merely illustrative and is in no way meant to limit the invention, its application, or uses. In an embodiment of the present invention, the memory 1200 of the electronic device 1000 is configured to store instructions for controlling the processor 1100 to operate so as to perform any one of the monitoring methods for the system operating status provided by the embodiment of the present invention. It will be appreciated by those skilled in the art that although a plurality of means are shown for the electronic device 1000 in fig. 1, the present invention may relate to only some of the means therein, e.g. the electronic device 1000 may relate to only the processor 1100 and the storage means 1200. The skilled person can design the instructions according to the disclosed solution. How the instructions control the operation of the processor is well known in the art and will not be described in detail herein.
In one embodiment of the present invention, a method for monitoring an operating state of a system is provided, and is executed at a server.
Referring to fig. 2, which is a flowchart illustrating steps of a system operation status monitoring method according to an embodiment of the present invention, the monitoring method may be implemented by an electronic device, such as the electronic device 1000 shown in fig. 1.
As shown in fig. 2, the method for monitoring the system operating state according to the embodiment of the present invention includes the following steps:
first, in step 102, a service request sent by a client is received, and then a request identifier corresponding to the service request is generated and added to the corresponding service request (step 104), for example, a request identifier of a universally unique identifier is added to the received service request, that is, a UUID (universally unique identifier, whose key is not repeated) is generated, so as to add a request identifier to each service request.
In step 106, at least one invoked service is determined based on the service request, the at least one invoked service being a service for executing the service request. Specifically, the invoked service may be determined according to the service request type or according to the request parameters in the service request. For example: and if the service request type is authentication, the called service is authentication service.
The service request including the request identification is then sent to the invoked service (step 108). Each called service records the request identification and calling information in the process of executing the service request, wherein the calling information at least comprises: the ID of the called service.
In one example, the invocation information further includes one or more of an invocation start time, an invocation end time, invocation parameters of the invoked service, invocation result return values of the invoked service, and invocation exception information.
The called service for executing the service request includes at least one service, and according to different service request types or request parameters in the service request, it is determined to call the corresponding service to execute the service request, which will be specifically developed later with reference to examples.
In one example, each invoked service records the request identification, the ID of the invoked service, the invocation parameters of the invoked service, and the invocation start time when beginning to execute the business request.
In one example, each called service also records the request identification, the ID of the called service, the calling result return value of the called service and the calling end time when finishing executing the service request.
In an example, the called service for executing the service request may include at least one service, which is determined according to a service to be called, and therefore the call information recorded correspondingly is also the call information corresponding to each service. The following will explain the monitoring method for the system operation state in detail with reference to the examples of fig. 3 to fig. 4, where fig. 3 is a first exemplary flowchart of the recording step of the monitoring method for the system operation state in the invention, and fig. 4 is a second exemplary flowchart of the recording step of the monitoring method for the system operation state in the invention.
Referring first to fig. 3, in the present example, a service request is executed between a front-end page (client) and one of back-end services (server), and the method for monitoring the operating status of the system of the present invention is executed on the server. Referring to fig. 3, an example of an interaction flow between a client and a server executing the monitoring method for the system operation state of the present invention is shown in fig. 3, which includes the following steps:
step 202, firstly, generating a service request based on a request parameter input by a user on a front-end page of a client;
step 204, the front-end page sends a service request to a back-end service;
in step 206, the UUID adding module of the back-end service generates a request identifier of the unique request identifier UUID according to the service request sent by the front-end page, and then sends the request identifier UUID. The UUID request identification is added to the corresponding service request. Taking a service request sent by a front-end page as an example of a login website, the front-end page sends a login request to a back-end service, and a UUID adding module of the back-end service generates a request identifier of a UUID for the login request after receiving the login request.
And step 208, the UUID adding module sends the generated service request with the UUID to a called service corresponding to the back-end service for processing the service request.
Step 210, after receiving the service request, the called service starts to execute the corresponding service request, and records the request identifier and the corresponding calling information in the process of executing the service request. Specifically, when the called service starts to execute the service request, the UUID corresponding to the service request, the ID of the called service, the call parameter, and the call start time (i.e., the time when the service request starts to be executed) are recorded.
Similarly, for example, when the client requests login authentication, the recorded call parameters include a login user name and a password sent by the client, and the call information may further include service key description, for example, the content of the service is a user name and a password for authenticating a login website.
And the called service also records corresponding calling information in the process of executing the login information verification request.
In step 212, when the called service finishes executing the login information verification request, the ID, the service key description, the UUID request identifier, the call result return value, and the call end time (i.e., the time when the called service stops executing the service request) of the called service are recorded again.
Step 214, after the called service finishes executing the service, the called service sends a feedback request response result to the front-end page of the client. And according to different results of the called service executing the service request, the calling result return values are different. For example, when the login user name and the password are verified to be correct, the calling result returned value sent to the front-end page of the client is verified to be passed, so that the user can normally login the website on the front-end page of the client. When the login user name or the password is verified to be incorrect, the calling result returned value sent to the front-end page of the client is a login error, so that the user cannot normally login the website on the front-end page of the client.
As described in the above example, during the process of the service request of the called service performing login information verification, the corresponding UUID request identification and the calling information are recorded. In this way, during the execution of the service request, the request identifier, the calling service ID, the calling start time, the calling end time, the calling parameter, and the calling result return value of the service request are recorded for the important steps (request arrival, request return) of the called service, so that the running state of the current system can be determined.
When the called service is abnormal in the process of executing the service request, recording a request identifier, the ID of the called service and calling abnormal information; the calling exception information comprises calling exception time and calling exception content. And further detecting the running position of the system with abnormal running according to the recorded request identifier, the calling information and the calling abnormal information. Regarding detecting the system operation exception by combining the request identifier, the calling information and the calling exception information, the following detailed description is made by combining the method for detecting the system operation exception of the present invention, and details are not repeated here.
Now, please refer to fig. 4, which is a second exemplary flowchart of the recording steps of the monitoring method for the system operation state according to the present invention, in this example, a service request is executed between a front-end page (client) and two services A, B of a back-end service (server), where a service a calls a service B during the execution of the service request, and the monitoring method for the system operation state according to the present invention is executed on the server.
Referring to fig. 4, an example of an interaction flow between a client and a server executing the monitoring method for the system operation state of the present invention is shown in fig. 4, which includes the following steps:
In step 308, the UUID adding module sends the generated first service request with the UUID to the called service a corresponding to the backend service processing the service request.
Step 310, after receiving the first service request, the called service a starts to execute the corresponding service request, and records the request identifier and the corresponding calling information in the process of executing the first service request. Specifically, when the called service a starts to execute the first service request, the UUID corresponding to the first service request, the ID of the called service a, the service key description, the calling parameter, and the calling start time (i.e., the time when the called service a starts to execute the first service request) are recorded.
And in the process of executing the request by the called service A, corresponding calling information is also recorded.
In step 312, the called service a needs to call the service B when executing the first service request. At this point, service a sends a second service request with UUID to invoked service B. And jointly executing the first service request sent by the front-end page of the client by calling the service B.
For example, the first service request sent by the front-end page is personal authority verification, the personal authority verification comprises login verification and authority verification, the called service a firstly processes login verification service of the personal authority verification after receiving the first service request, and after the login verification passes, the authority verification of the personal authority verification is called to be executed by the service B.
In step 314, after receiving the second service request, the called service B starts to execute the second service request, and records the UUID request identifier, the ID of the called service B, the service key description, the calling parameter of the called service B, and the calling start time (i.e., the time when the called service B starts to execute the second service request) in the process of executing the service request.
And the called service B also records corresponding calling information in the process of executing the second service request.
In step 316, when the called service B finishes executing the second service request, the ID, the service key description, the UUID request identifier, the call result return value corresponding to the called service B, and the call end time (that is, the time when the called service B finishes executing the second service request) of the called service B are recorded.
In step 318, the called service B sends the corresponding call result return value to the called service a to continue executing the corresponding request.
In step 320, when the called service a finishes executing the first service request, the ID, the service key description, the UUID request identifier, the call result return value, and the call end time of the called service a are recorded.
Step 322, the called service a feeds back the response result of the first service request to the front-end page.
As described in the above example, during the execution of the service request, the corresponding request identifier and the call information are recorded. In the process of executing the service request, the calling time, the calling parameters and the calling result of the service request are recorded aiming at the important steps (request arrival and request return) of each called service to be called, so that the running state of the current system can be determined.
And each called service sequentially records the UUID, the calling time, the calling parameters and the calling result return value corresponding to the current called service, so that the running state of the current system can be determined, and the running state of the system does not need to be judged through key indexes.
It should be noted that although fig. 4 shows two services a and B performing the service request, and the service a calls the service B, the present invention is not limited to this specific embodiment, and in other embodiments, the system operation status monitoring method of the present invention may be performed on at least one called service. When the number of the called services is at least two, the called services may have a calling relationship or have no calling relationship, that is, the service request of the user is sent to two or more called services respectively to execute corresponding services respectively, the two or more called services independently execute corresponding services respectively, and no calling relationship exists. Or the service request of the existing user is respectively sent to two or more than two called services, part of the called services independently execute corresponding services, and part of the called services have calling relations to execute corresponding services.
In another embodiment of the present invention, a method for detecting system operation abnormality is provided, as shown in fig. 5, which is a flowchart illustrating a method for detecting system operation abnormality according to an embodiment of the present invention.
As shown in fig. 5, the method for detecting system operation abnormality includes the following steps:
and 308, determining the called service with abnormal operation according to the calling information.
In step 308, determining a called service with abnormal operation according to the calling information, including: and determining whether the called service is abnormal according to the difference between the calling start time and the calling end time of the called service.
Or, in step 308, determining a called service with abnormal operation according to the calling information, including: and determining the called service with abnormal operation according to the calling abnormal information, and determining the operation position where the abnormal operation occurs according to the calling abnormal content.
As shown above, according to the method for monitoring the system running state in the embodiment of the present invention, in the process of executing the service request, the called service records the request identifier corresponding to the service request and records the call information corresponding to the called service executing the service request, if the called service has an abnormal system running in the process of executing the service request, the execution of the service request is interrupted, and meanwhile, the call abnormal information of the service request is further recorded and written into the log, and the call abnormal information includes the call abnormal time and the call abnormal content.
Specifically, the operation position where the exception occurs is determined according to the recorded calling information and the recorded calling exception information, a service request including the request identification is determined according to the request identification of the calling exception information, the calling exception time can be obtained according to the calling exception time of the calling exception information and the calling exception time corresponding to the calling exception information, the calling exception time is up, the calling information of the called service record corresponding to the service request is recorded, and then the operation position where the exception occurs is determined according to the calling exception content.
The method for detecting the system operation abnormity can determine the service request containing the request identifier and the called service corresponding to the service request by acquiring the request identifier of the service request when the system operation is abnormal, and further determine the called service with abnormal operation according to the calling information by acquiring the calling information which is recorded in the called service and is associated with the request identifier. Therefore, the record data is traced through the request identifier generated corresponding to the service request, so that the called service with the abnormal condition is found. Further, the operation position of the abnormal occurrence can be determined by the calling abnormal content in the calling information.
In addition, the system runs abnormal contents such as service request type mismatch, database connection timeout or request parameter null, etc. And when the system is abnormal in operation, the current system operation service is interrupted. Although the above embodiment of the method for monitoring the system running state describes the corresponding call information when the called service starts executing the service request and the corresponding call information when the called service finishes executing the service request, the above record is only used to illustrate that the running state of the system can be clarified by recording the call information.
If the system has an exception, the corresponding service request execution process is interrupted when the exception occurs, for example, the exception occurs after the called service starts executing the service request and before the called service finishes executing the request, in this case, the recorded calling information does not include the calling information for finishing executing the service request.
The calling information of the called service in the process of executing the service request is recorded, so that the stage to which the running state of the current system reaches can be directly known, and the running state of the system does not need to be judged through key indexes. And combining the recorded calling exception information, the position of the system operation exception can be determined when the system exception occurs.
When the system operation is abnormal in the process of executing the service request, the called service further records the calling abnormal information of the service request and writes the calling abnormal information into a log. The recorded calling information in the process of executing the service request can directly know which stage the running state of the current system reaches, which called service has a problem, and what problem occurs correspondingly to finally cause the index to be abnormal, so that the positioning of a problem module or the called service can be facilitated.
In another embodiment of the present invention, a system operation state monitoring apparatus 2000 is further provided, as shown in fig. 6, and fig. 6 is a block diagram illustrating a structure of the system operation state monitoring apparatus according to the embodiment of the present invention.
The monitoring apparatus 2000 includes a receiving module 2200, an identifying module 2400, a first determining module 2600, and a sending module 2800, where the receiving module 2200 is configured to receive a service request, and the identifying module 2400 is configured to generate a request identifier corresponding to the service request, and add the request identifier to the service request. A first determining module 2600 configured to determine at least one called service based on the service request, wherein the sending module 2800 is configured to send the service request including the request identifier to the at least one called service, and each called service records the request identifier and calling information during execution of the service request, where the calling information at least includes: the ID of the called service.
In one example, the calling information further includes: one or more of a call start time, a call end time, a call parameter of the called service, a call result return value of the called service, and call exception information. In one example, during the process of executing the service request, the recording the request identifier and the calling information by each called service includes: and when the called service starts to execute the service request, recording the request identification, the ID of the called service, the calling parameter of the called service and calling start time. In one example, each called service records the request identification, the ID of the called service, the calling result return value of the called service and the calling end time when finishing executing the service request.
In one example, when an exception occurs in the process of executing the service request, the called service records the request identifier, the ID of the called service and calling exception information; the calling exception information comprises calling exception time and calling exception content.
According to still another embodiment of the present invention, there is further provided a system operation abnormality detection apparatus 4000, as shown in fig. 7, and fig. 7 is a block diagram illustrating a structure of the system operation abnormality detection apparatus according to the embodiment of the present invention.
As shown in the drawing, the apparatus 4000 for detecting system operation abnormality includes:
a first obtaining module 4200, configured to obtain an anomaly detection request, where the anomaly detection request includes a request identifier according to a first method of the present invention;
a first determining module 4400, configured to determine, according to the request identification, a service request including the request identification and a called service for executing the service request;
a second obtaining module 4600, configured to obtain, according to the request identifier, the invocation information associated with the request identifier, which is recorded in the invoked service.
A second determining module 4800, configured to determine, according to the call information, a called service that runs abnormally.
In one example, the second determining module 4800 determines whether the called service is abnormal according to a difference between a call start time and a call end time of the called service.
Or, the second determining module 4800 determines the called service with abnormal operation according to the calling abnormal information; and determining the operation position of the abnormal situation according to the calling abnormal content.
According to still another embodiment of the present invention, there is also provided an electronic apparatus, and the electronic apparatus 3000 may be the electronic apparatus 1000 shown in fig. 1. Fig. 8 is a block diagram of an electronic device according to an embodiment of the present invention.
In one aspect, the electronic device 3000 may include the foregoing system operation status monitoring apparatus, which is used to implement the system operation status monitoring method according to any embodiment of the present invention.
On the other hand, as shown in fig. 8, the electronic device 3000 may include a memory 3200 and a processor 3400, the memory 3200 being for storing executable instructions; the instruction is used to control the processor 3400 to perform the foregoing method for monitoring the system operation state.
In this embodiment, the electronic device 3000 may be any electronic product having the memory 3200 and the processor 3400, such as a mobile phone, a tablet computer, a palmtop computer, a desktop computer, a notebook computer, a workstation, a game machine, a server, and the like.
Finally, according to yet another embodiment of the present invention, there is also provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method for monitoring the operational status of a system according to any embodiment of the present invention.
The present invention may be a system, method and/or computer program product. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied therewith for causing a processor to implement various aspects of the present invention.
The computer readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted through electrical wires.
The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or to an external computer or external storage device via a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.
The computer program instructions for carrying out operations of the present invention may be assembler instructions, Instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, aspects of the present invention are implemented by personalizing an electronic circuit, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA), with state information of computer-readable program instructions, which can execute the computer-readable program instructions.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.
These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. It is well known to those skilled in the art that implementation by hardware, implementation by software, and implementation by a combination of software and hardware are equivalent.
Having described embodiments of the present invention, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen in order to best explain the principles of the embodiments, the practical application, or improvements made to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein. The scope of the invention is defined by the appended claims.
Claims (12)
1. A method for monitoring the operation state of a system is characterized by comprising the following steps:
receiving a service request;
generating a request identifier corresponding to the service request, and adding the request identifier to the service request;
determining at least one invoked service based on the service request;
and sending the service request containing the request identifier to the at least one called service, wherein each called service records the request identifier and calling information in the process of executing the service request, and the calling information at least comprises the ID of the called service.
2. The method of claim 1, wherein the invocation information further includes: one or more of a call start time, a call end time, a call parameter of the called service, a call result return value of the called service, and call exception information.
3. The method of claim 1, wherein each called service records the request identifier and calling information during the execution of the service request, and comprises:
and when the called service starts to execute the service request, recording the request identification, the ID of the called service, the calling parameter of the called service and calling start time.
4. The method of claim 1, wherein the called service recording the request identifier and calling information during the execution of the service request comprises:
and when the called service finishes executing the service request, recording the request identification, the ID of the called service, the calling result return value of the called service and calling end time.
5. The method of claim 1, wherein the called service recording the request identifier and calling information during the execution of the service request comprises:
when the called service is abnormal in the process of executing the service request, recording the request identification, the ID of the called service and calling abnormal information; the calling exception information comprises calling exception time and calling exception content.
6. A method for detecting system operation abnormity is characterized by comprising the following steps:
obtaining an anomaly detection request, wherein the anomaly detection request comprises a request identifier of any one of claims 1-5;
determining a service request containing the request identification and a called service for executing the service request according to the request identification;
and acquiring the calling information which is recorded in the called service and is associated with the request identifier according to the request identifier.
And determining the called service with abnormal operation according to the calling information.
7. The method of claim 6, wherein the determining the called service with abnormal operation according to the calling information comprises:
and determining whether the called service is abnormal according to the difference between the calling start time and the calling end time of the called service.
8. The method of claim 6, wherein the determining the called service with abnormal operation according to the calling information comprises:
determining a called service with abnormal operation according to the calling abnormal information;
and determining the operation position of the abnormal situation according to the calling abnormal content.
9. A system operation status monitoring device, comprising:
the receiving module is used for receiving the service request;
the identification module is used for generating a request identification corresponding to the service request and adding the request identification to the service request;
a first determining module for determining at least one invoked service based on the service request;
a sending module, configured to send a service request including the request identifier to the called service, where each called service records the request identifier and calling information in a process of executing the service request, where the calling information at least includes: the ID of the called service.
10. A system anomaly detection device, comprising:
a first obtaining module, configured to obtain an anomaly detection request, where the anomaly detection request includes a request identifier according to any one of claims 1 to 5;
the first determining module is used for determining the service request containing the request identification and the called service for executing the service request according to the request identification;
and the second acquisition module is used for acquiring the calling information which is recorded in the called service and is associated with the request identifier according to the request identifier.
And the second determination module is used for determining the called service with abnormal operation according to the calling information.
11. An electronic device, comprising:
the apparatus of claim 9 or 10; alternatively, the first and second electrodes may be,
a processor and a memory for storing executable instructions for controlling the processor to perform the method of any of claims 1 to 8.
12. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911328753.4A CN113010365A (en) | 2019-12-20 | 2019-12-20 | System running state monitoring method, system running state detection device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911328753.4A CN113010365A (en) | 2019-12-20 | 2019-12-20 | System running state monitoring method, system running state detection device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113010365A true CN113010365A (en) | 2021-06-22 |
Family
ID=76382092
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911328753.4A Pending CN113010365A (en) | 2019-12-20 | 2019-12-20 | System running state monitoring method, system running state detection device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113010365A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113778736A (en) * | 2021-09-14 | 2021-12-10 | 北京房江湖科技有限公司 | Method and device for positioning error information |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5247676A (en) * | 1989-06-29 | 1993-09-21 | Digital Equipment Corporation | RPC based computer system using transparent callback and associated method |
| CN108462750A (en) * | 2018-03-22 | 2018-08-28 | 平安好房（上海）电子商务有限公司 | Distribution calls method for tracing, operation system, monitoring system and storage medium |
| CN109672741A (en) * | 2018-12-25 | 2019-04-23 | 鼎信信息科技有限责任公司 | Micro services monitoring method, device, computer equipment and storage medium |
| CN109873717A (en) * | 2019-01-18 | 2019-06-11 | 深圳壹账通智能科技有限公司 | Monitoring method, device, computer equipment and storage medium |
-
2019
- 2019-12-20 CN CN201911328753.4A patent/CN113010365A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5247676A (en) * | 1989-06-29 | 1993-09-21 | Digital Equipment Corporation | RPC based computer system using transparent callback and associated method |
| CN108462750A (en) * | 2018-03-22 | 2018-08-28 | 平安好房（上海）电子商务有限公司 | Distribution calls method for tracing, operation system, monitoring system and storage medium |
| CN109672741A (en) * | 2018-12-25 | 2019-04-23 | 鼎信信息科技有限责任公司 | Micro services monitoring method, device, computer equipment and storage medium |
| CN109873717A (en) * | 2019-01-18 | 2019-06-11 | 深圳壹账通智能科技有限公司 | Monitoring method, device, computer equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113778736A (en) * | 2021-09-14 | 2021-12-10 | 北京房江湖科技有限公司 | Method and device for positioning error information |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10832254B2 (en) | Mapping user actions to historical paths to determine a predicted endpoint | |
| US11533330B2 (en) | Determining risk metrics for access requests in network environments using multivariate modeling | |
| US10362046B1 (en) | Runtime behavior of computing resources of a distributed environment | |
| US10171315B2 (en) | Orchestration process template for generation of orchestration process to tolerate errors | |
| US10614208B1 (en) | Management of login information affected by a data breach | |
| US11153236B2 (en) | Real-time integration of machine intelligence into client messaging platforms | |
| CN112567709B (en) | Enhancing security using anomaly detection | |
| US10095608B2 (en) | Application test automation transmitting data via phone/voice calls | |
| US10152400B2 (en) | Method and system for dynamically unblocking customers in critical workflows by pushing community contributed solutions just-in-time when an error is encountered | |
| US20230350769A1 (en) | Method and apparatus for generating log data having increased filterability | |
| US11275640B2 (en) | Computer error prevention and reduction | |
| CN111586177B (en) | Cluster session loss prevention method and system | |
| US11625237B2 (en) | Autonomous contextual software support anomaly detection and playbook automation | |
| CN113010365A (en) | System running state monitoring method, system running state detection device, electronic equipment and storage medium | |
| CN117557206A (en) | Flow processing method and device, electronic equipment and readable storage medium | |
| US11627206B2 (en) | System and methods for providing user analytics and performance feedback for web applications | |
| CN115203671A (en) | Account login method, device, equipment and storage medium | |
| CN113672885A (en) | Application authorization method and device and electronic equipment | |
| US20160277269A1 (en) | Dynamic community support | |
| CN113190812A (en) | Login method, system, electronic equipment and storage medium | |
| US20200202230A1 (en) | Cognitive device support for potentially affected devices | |
| CN113900895B (en) | Information processing method, information processing apparatus, storage medium, and electronic device | |
| US11645071B1 (en) | Intelligent installation for client systems | |
| CN113612756B (en) | Shared login method and device, computer readable storage medium and electronic equipment | |
| US20230038689A1 (en) | Systems and methods for providing user guidance via a workspace score |
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 |