CN108390770B - Information generation method and device and server - Google Patents
Information generation method and device and server Download PDFInfo
- Publication number
- CN108390770B CN108390770B CN201810043695.XA CN201810043695A CN108390770B CN 108390770 B CN108390770 B CN 108390770B CN 201810043695 A CN201810043695 A CN 201810043695A CN 108390770 B CN108390770 B CN 108390770B
- Authority
- CN
- China
- Prior art keywords
- service
- log
- server
- service request
- target
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5003—Managing SLA; Interaction between SLA and QoS
- H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
- H04L41/5012—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF] determining service availability, e.g. which services are available at a certain point in time
- H04L41/5016—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF] determining service availability, e.g. which services are available at a certain point in time based on statistics of service availability, e.g. in percentage or over a given time
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
- H04L41/064—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis involving time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5003—Managing SLA; Interaction between SLA and QoS
- H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- Probability & Statistics with Applications (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention provides an information generation method, an information generation device and a server, wherein the information generation method comprises the following steps: obtaining a first log corresponding to a first service request, wherein the first service request is: a service request requesting a service failure; determining a service requested by the first service request as a target service; determining a business logic of the target service as a first business logic; searching log data which is not matched with the service configuration item of the first service logic in the log data contained in the first log as target log data; and generating a reason for the service failure of the first service request according to the target log data. By the technical scheme provided by the embodiment of the invention, the problem that the workload of developers is large due to the fact that a large number of analysis tools need to be written can be avoided, and the workload of the developers can be reduced.
Description
Technical Field
The present invention relates to the field of internet application technologies, and in particular, to an information generating method, an information generating apparatus, and a server.
Background
With the rapid development of internet applications, a server can provide various services to clients by performing business logic of the various services. Specifically, when a client needs to request a service from a server, a service request for the requested service is sent to the server, and after receiving the service request sent by the client, the server executes the service logic of the service requested by the client, so that the service required by the client is provided for the client.
However, the inventor finds that the prior art has at least the following problems in the process of implementing the invention:
when a client requests a service from a server, there may be a case where the request service fails due to a network connection failure, response timeout, and the like. In order to know the reason of the request service failure, the server generally calls an analysis tool written in advance by a developer to analyze the condition of the request service failure. However, since the types of services are many and each service has different characteristics, developers generally write an analysis tool for each service, which results in a large workload.
Disclosure of Invention
The embodiment of the invention aims to provide an information generation method, an information generation device and a server, so as to avoid the problem that the workload of developers is large due to the fact that a large number of analysis tools need to be written. The specific technical scheme is as follows:
in a first aspect, an embodiment of the present invention provides an information generating method, which is applied to a server, and the method includes:
obtaining a first log corresponding to a first service request, wherein the first service request is: a service request requesting a service failure;
determining a service requested by the first service request as a target service;
determining a business logic of the target service as a first business logic;
searching log data which is not matched with the service configuration item of the first service logic in the log data contained in the first log as target log data;
and generating a reason for the service failure of the first service request according to the target log data.
Optionally, the obtaining the first log corresponding to the first service request includes:
acquiring a target log generated by a first client as a first log, wherein the first client is as follows: a client sending the first service request to the server, wherein the target log is: a log generated by the first client in the process of requesting the target service;
and/or the presence of a gas in the gas,
obtaining a log generated by a first service terminal in the process of responding to the first service request as a first log, wherein the first service terminal is as follows: and responding to the server side of the first service request.
Optionally, the method further includes:
acquiring a second log corresponding to a second service request, wherein the second service request is as follows: a service request requesting a successful service;
according to the first log and the second log, state data of a server responding to the first service request and the second service request are generated, wherein the state data of one server comprises: the running state data of the server and the service state data of the service provided by the server.
Optionally, the operation status data of one server includes at least one of the following data:
the number of received service requests in a preset time, the success probability of responding to the service requests in the preset time, the failure probability of responding to the service requests in the preset time, the time ratio of responding to the service requests, the number of service requests responded per second, the number of relying parties, the success rate and the failure rate of the relying parties.
Optionally, after generating the status data of the server side responding to the first service request and the second service request according to the first log and the second log, the method further includes:
displaying the generated state data of the server;
and/or the presence of a gas in the gas,
sending the generated state data and/or prompt information of the server to a preset electronic device, wherein the prompt information is: and generating information for prompting the state of the server according to the generated state data of the server.
Optionally, the prompt information is generated according to the following manner:
selecting state data which accord with preset abnormal conditions corresponding to each state data from the generated state data of the server;
and generating the prompt information according to the selected state data.
In a second aspect, an embodiment of the present invention further provides an information generating apparatus, which is applied to a server, where the apparatus includes:
a first log obtaining module, configured to obtain a first log corresponding to a first service request, where the first service request is: a service request requesting a service failure;
a target service determination module, configured to determine, as a target service, a service requested by the first service request;
a business logic determining module, configured to determine a business logic of the target service, as a first business logic;
a target log data searching module, configured to search, in log data included in the first log, log data that does not match a service configuration item of the first service logic, as target log data; and the information generation module is used for generating the reason of the service failure of the first service request according to the target log data.
Optionally, the first log obtaining module is specifically configured to:
acquiring a target log generated by a first client as a first log, wherein the first client is as follows: a client sending the first service request to the server, wherein the target log is: a log generated by the first client in the process of requesting the target service;
and/or the presence of a gas in the gas,
obtaining a log generated by a first service terminal in the process of responding to the first service request as a first log, wherein the first service terminal is as follows: and responding to the server side of the first service request.
Optionally, the apparatus further comprises:
a second log obtaining module, configured to obtain a second log corresponding to a second service request, where the second service request is: a service request requesting a successful service;
a status data generating module, configured to generate, according to the first log and the second log, status data of a server responding to the first service request and the second service request, where the status data of one server includes: the running state data of the server and the service state data of the service provided by the server.
Optionally, the operation status data of one server includes at least one of the following data:
the number of received service requests in a preset time, the success probability of responding to the service requests in the preset time, the failure probability of responding to the service requests in the preset time, the time ratio of responding to the service requests, the number of service requests responded per second, the number of relying parties, the success rate and the failure rate of the relying parties.
Optionally, the apparatus further comprises:
the state data display module is used for displaying the generated state data of the server after generating the state data of the server responding to the first service request and the second service request according to the first log and the second log;
and/or the presence of a gas in the gas,
an information sending module, configured to send the generated state data and/or prompt information of the server to a preset electronic device after generating, according to the first log and the second log, state data of the server that responds to the first service request and the second service request, where the prompt information is: and generating information for prompting the state of the server according to the generated state data of the server.
Optionally, the prompt information is generated according to the following manner:
selecting state data which accord with preset abnormal conditions corresponding to each state data from the generated state data of the server;
and generating the prompt information according to the selected state data.
In a third aspect, an embodiment of the present invention further provides an electronic device, including a processor, a communication interface, a memory, and a communication bus, where the processor, the communication interface, and the memory complete mutual communication through the communication bus;
a memory for storing a computer program;
a processor configured to implement any of the information generating methods according to the first aspect described above when executing a program stored in the memory.
In yet another aspect of the present invention, there is also provided a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to execute any one of the information generating methods described above in the first aspect.
In another aspect of the present invention, an embodiment of the present invention further provides a computer program product containing instructions, which when run on a computer, causes the computer to execute any one of the information generating methods described in the first aspect.
Compared with the prior art, according to the technical scheme provided by the embodiment of the invention, when the server analyzes the reason of the service failure, the server firstly acquires the first log corresponding to the first service request, wherein the first service request is as follows: a service request requesting a service failure; then determining a target service requested by the first service request, and determining a business logic of the target service as a first business logic; finally, log data which are not matched with the service configuration item of the first service logic are searched in the log data contained in the first log and serve as target log data; and generating a reason for the service failure of the first service request according to the target log data.
Therefore, according to the technical scheme provided by the embodiment of the invention, when the server analyzes the reason of the service request failure, the server obtains the log corresponding to the service request of the service request failure, determines the service logic of the target service requested by the service request of the service request failure, searches the target log data which is not matched with the service logic of the target service in the obtained log, and can generate the reason of the service request failure according to the target log data. Unlike the prior art, when the server analyzes the reason of the requested service failure, the server needs to call an analysis tool corresponding to the requested service to analyze the reason of the requested service failure. Therefore, through the technical scheme provided by the embodiment of the invention, the problem that the workload of developers is large due to the fact that a large number of analysis tools need to be written can be avoided, and the workload of the developers can be reduced.
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.
Fig. 1 is a flowchart of an information obtaining method according to an embodiment of the present invention;
fig. 2 is a flowchart of another information obtaining method according to an embodiment of the present invention;
fig. 3 is a flowchart of another information obtaining method according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of an information acquisition apparatus according to an embodiment of the present invention;
fig. 5 is another schematic structural diagram of an information acquisition apparatus according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a server according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention.
In order to solve the problem of the prior art, embodiments of the present invention provide an information generating method, an information generating device, and a server, so as to avoid a large workload of developers due to the need to write a large number of analysis tools.
In a first aspect, an information generating method provided in an embodiment of the present invention will be described.
As shown in fig. 1, an information generating method provided in an embodiment of the present invention includes the following steps:
s110, obtain a first log corresponding to a first service request, where the first service request is: a service request requesting a service failure;
s120, determining the service requested by the first service request as a target service;
s130, determining the business logic of the target service as a first business logic;
s140, searching log data which is not matched with the service configuration item of the first service logic in the log data contained in the first log as target log data;
s150, according to the target log data, generating a reason of the service failure of the first service request.
It can be seen that, in the technical solution provided in the embodiment of the present invention, when analyzing the reason for requesting the service failure, the server obtains the log corresponding to the service request for requesting the service failure, determines the service logic of the target service requested by the service request for requesting the service failure, searches for target log data that is not matched with the service logic of the target service in the obtained log, and can generate the reason for requesting the service failure according to the target log data. Unlike the prior art, when the server analyzes the reason of the requested service failure, the server needs to call an analysis tool corresponding to the requested service to analyze the reason of the requested service failure. Therefore, through the technical scheme provided by the embodiment of the invention, the problem that the workload of developers is large due to the fact that a large number of analysis tools need to be written can be avoided, and the workload of the developers can be reduced.
The information generation method provided by the embodiment shown in fig. 1 will be described in detail below.
S110, obtain a first log corresponding to a first service request, where the first service request is: a service request requesting a service failure;
when analyzing the reason of the service request failure, the server first obtains a log corresponding to the service request with the service request failure, that is, obtains a first log corresponding to the first service request.
The first log may be a log generated by a client sending a first service request to a server in a process of requesting a service; the service end responding to the first service request can also be a log generated in the process of responding to the first service request.
When the first log is generated in the process of requesting the service by a client sending a first service request to the server, the server acquires the first log in two ways, wherein the first way is as follows: the client sending the first service request sends a first log to the server; the second way is: the server sends a request for acquiring a first log to the client sending the first service request, and the client sending the first service request sends the first log to the server after receiving the request.
When the first log is a log generated by the server side responding to the first service request in the process of responding to the first service request, the manner of the server acquiring the first log may be: and searching a first log generated by the server in the process of responding to the first service request in the log system.
It is understood that the server side responding to the first service request may be the execution main server itself, or may be other servers capable of responding to the first service request.
S120, determining the service requested by the first service request as a target service;
in general, different services requested by different service requests are different, and service logics executed by the server when providing different services for the client are different, so that, in order to know the service logics of the services requested by the first service request in subsequent steps, the server needs to determine the service requested by the first service request, that is, a target service needs to be determined.
S130, determining the business logic of the target service as a first business logic;
in general, business logics corresponding to different services are different, and therefore, after a target service is determined, the business logic of the target service, that is, a first business logic needs to be determined.
S140, searching log data which is not matched with the service configuration item of the first service logic in the log data contained in the first log as target log data;
the service configuration item of the first service logic is a parameter which needs to be satisfied by executing the first service logic when the service end successfully provides service for the client. The first log is a log corresponding to a service request which fails to request the service, and therefore log data which is not matched with the service configuration item of the first service logic exists in the log data included in the first log. In order to analyze the reason of the request service failure in the subsequent steps, log data which does not match with the service configuration item of the first service logic needs to be searched in the log data contained in the first log as target log data.
For example, the response time included in the first log is 20 seconds, and when the server successfully provides the service to the client, the maximum response time for executing the first service logic is as follows: 10 seconds, that is, the maximum response time in the service configuration item of the first service logic is: for 10 seconds, the target log data is: the response time was 20 seconds. S150, according to the target log data, generating a reason of the service failure of the first service request.
The first log is a log generated by a client sending a first service request to the server in the process of requesting the service; or a log generated by the server side responding to the first service request in the process of responding to the first service request. Therefore, after the target log data which is not matched with the service configuration item of the first service logic is found in the log data contained in the first log, the server can generate the reason of the failure of the first service request and generate the reason of the failure of the first service request.
For example, the first log includes a response time of 20 seconds, and the maximum response time in the service configuration item of the first service logic is: 10 seconds, the target log data is: if the response time is 20 seconds, the reason for the failure of the first service request generated according to the target log data may be: the response times out.
Compared with the prior art, according to the technical scheme provided by the embodiment of the invention, when the server analyzes the reason of the service failure, the server firstly acquires the first log corresponding to the first service request, wherein the first service request is as follows: a service request requesting a service failure; then determining a target service requested by the first service request, and determining a business logic of the target service as a first business logic; finally, log data which are not matched with the service configuration item of the first service logic are searched in the log data contained in the first log and serve as target log data; and generating a reason for the service failure of the first service request according to the target log data.
Therefore, according to the technical scheme provided by the embodiment of the invention, when the server analyzes the reason of the service request failure, the server obtains the log corresponding to the service request of the service request failure, determines the service logic of the target service requested by the service request of the service request failure, searches the target log data which is not matched with the service logic of the target service in the obtained log, and can generate the reason of the service request failure according to the target log data. Unlike the prior art, when the server analyzes the reason of the requested service failure, the server needs to call an analysis tool corresponding to the requested service to analyze the reason of the requested service failure. Therefore, through the technical scheme provided by the embodiment of the invention, the problem that the workload of developers is large due to the fact that a large number of analysis tools need to be written can be avoided, and the workload of the developers can be reduced.
Another information generating method provided in the embodiment of the present invention is described below.
As shown in fig. 2, an information generating method provided in an embodiment of the present invention may include the following steps:
s210, obtain a first log corresponding to a first service request, where the first service request is: a service request requesting a service failure;
s220, determining the service requested by the first service request as a target service;
s230, determining the business logic of the target service as a first business logic;
s240, searching the log data which is not matched with the service configuration item of the first service logic in the log data contained in the first log as target log data;
s250, generating a reason for the service failure of the first service request according to the target log data;
s260, obtaining a second log corresponding to a second service request, where the second service request is: a service request requesting a successful service;
s270, generating status data of the service end responding to the first service request and the second service request according to the first log and the second log, where the status data of one service end includes: the running state data of the server and the service state data of the service provided by the server.
In this embodiment, steps S210 to S250 are the same as steps S110 to S150, and since steps S110 to S150 have already been described in detail in the embodiment shown in fig. 1, no further description is given in this embodiment.
The steps S260 and S270 will be explained in detail below.
S260, obtaining a second log corresponding to a second service request, where the second service request is: a service request requesting a successful service;
in steps S210 to S250, the server acquires a service request for which the requested service failed, and analyzes the reason for the requested service failure. In order to further analyze the status data of each server responding to the service request, it is further required to obtain a log corresponding to the service request requesting the successful service, that is, to obtain a second log.
The second log may be a log generated by a client sending a second service request to the server in a process of requesting a service; the service end responding to the second service request can also be a log generated in the process of responding to the second service request.
When the second log is generated by a client sending a second service request to the server in the process of requesting the service, the server acquires the second log in two ways, wherein the first way is as follows: the client sending the second service request sends the second log to the server; the second way is: and the server sends a request for acquiring a second log to the client sending the second service request, and the client sending the second service request sends the second log to the server after receiving the request.
When the second log is a log generated by the server responding to the second service request in the process of responding to the second service request, the manner of the server acquiring the second log may be: and searching a second log generated by the server in the process of responding to the second service request in the log system.
It is understood that the server responding to the second service request may be the execution main server itself, or may be other servers capable of responding to the second service request.
S270, generating status data of the service end responding to the first service request and the second service request according to the first log and the second log, where the status data of one service end includes: the running state data of the server and the service state data of the service provided by the server.
After the server acquires the first log and the second log, the server analyzes the first log and the second log to obtain state data of the server side responding to the first service request and the second service request.
It should be noted that the state data of the server may include: the running state data of the server and the service state data of the service provided by the server.
The operation state data of the server may include the following data:
1. the server receives the number of service requests within a preset time period.
Specifically, the number of the service requests may be a total number of the first service requests and the second service requests received by the server within a preset time period, where the preset time period may be 1 second, 10 seconds, 1 minute, 1 hour, and the like, and the size of the preset time period is not specifically limited in the embodiment of the present invention.
2. The success probability of the server responding to the service request within the preset time length.
Specifically, since the second service request is a service request that requests a successful service, the success probability of responding to the service request within the preset duration may be calculated as follows: the number of the second service requests received by the server in the preset time length is divided by the number of the service requests received by the server in the preset time length, so that the success probability of the server responding to the service requests in the preset time length can be calculated. It can be understood that the preset duration may be larger or smaller, and the size of the preset duration is not specifically limited in the embodiment of the present invention.
3. And the failure probability of the server responding to the service request within the preset time length.
Specifically, since the first service request is a service request that requests a service failure, the failure probability of responding to the service request within a preset duration may be calculated as follows: the number of the first service requests received by the server in the preset time length is divided by the number of the service requests received by the server in the preset time length, so that the success probability of the server responding to the service requests in the preset time length can be calculated. It can be understood that the preset duration may be larger or smaller, and the size of the preset duration is not specifically limited in the embodiment of the present invention.
It can be understood that, after the success probability of the server responding to the service request within the preset time is calculated, the success probability of the server responding to the service request within the preset time is subtracted from 1, so that the failure probability of the server responding to the service request within the preset time can be obtained.
4. The time of the server side responding to the service request is in proportion;
after the server acquires the first log corresponding to the first service request and the second log corresponding to the second service request, the time consumed by the server for responding to each service request can be obtained, and the time ratio of the server for responding to the service request can be calculated.
For example, there are 10 service requests, and the time consumed by the server to respond to the 10 service requests is sequentially: 1 second, 2 seconds, 3 seconds, 4 seconds, 5 seconds, 7 seconds, 8 seconds, 9 seconds, the server calculates the time ratio consumed by the server to respond to the service request, and the time ratio can be: the content of the compound is 20% in less than 3 seconds, and the content of the compound is 50% in 3 to 5 seconds. The ratio of 6 seconds to 10 seconds is as follows: 30 percent.
5. The number of service requests the server responds to per second.
Specifically, after the server acquires the first log corresponding to the first service request and the second log corresponding to the second service request, the server may acquire a time corresponding to a response to the first service request from the first log and acquire a time corresponding to a response to the second service request from the second log, so that the server may calculate the number of times of service requests responded per second by the server responding to the first service request and the second service request.
6. The number of relying parties;
the number of relying parties is the total number of relying services. For example, when the service a is provided, the service B and the service C are invoked, and then the service B and the service C are dependent services.
7. The success rate and failure rate of the relying party.
The success rate of the relying party is: probability of success of the invocation dependent service. For example, the total number of the dependent services is 10, the number of times of successful invocation of the dependent services is 8, and then the success rate of the dependent party is 80%;
accordingly, the success rate of the relying party is: probability of failure of the invocation dependent service. For example, the total number of dependent services is 10, the number of times the dependent service is invoked fails is 2, and then the failure rate of the dependent party is 20%.
It should be noted that the service state data of the service provided by the server may be the number of successful services, the number of failed services, the success probability, the failure probability, and so on provided by the server.
Compared with the prior art, when analyzing the reason of the service request failure, the server obtains the log corresponding to the service request of the service request failure, determines the service logic of the target service requested by the service request of the service request failure, searches the target log data which is not matched with the service logic of the target service in the obtained log, and can generate the reason of the service request failure according to the target log data; and acquiring a second log corresponding to the service request which requests the service to be successful, and generating state data of the server side responding to the first service request and the second service request according to the first log and the second log. Therefore, according to the technical scheme provided by the embodiment of the invention, the problem that the workload of developers is large due to the fact that a large number of analysis tools need to be written can be avoided, namely, the workload of the developers can be reduced, and the state data of the service end responding to the service request can be automatically generated according to the first log and the second log.
Another information generating method provided in the embodiment of the present invention is described below.
As shown in fig. 3, an information generating method provided in an embodiment of the present invention may include the following steps:
s310, obtain a first log corresponding to a first service request, where the first service request is: a service request requesting a service failure;
s320, determining the service requested by the first service request as a target service;
s330, determining the business logic of the target service as a first business logic;
s340, searching log data which is not matched with the service configuration item of the first service logic in the log data contained in the first log as target log data;
s350, generating a reason for the service failure of the first service request according to the target log data;
s360, a second log corresponding to a second service request is obtained, wherein the second service request is as follows: a service request requesting a successful service;
s370, generating status data of the service end responding to the first service request and the second service request according to the first log and the second log, wherein the status data of one service end includes: the running state data of the server and the service state data of the service provided by the server;
s380, displaying the generated state data of the server;
and/or the presence of a gas in the gas,
sending the generated state data and/or prompt information of the server to a preset electronic device, wherein the prompt information is: and generating information for prompting the state of the server according to the generated state data of the server.
In this embodiment, steps S310 to S350 are the same as steps S110 to S150, and since steps S110 to S150 have already been described in detail in the embodiment shown in fig. 1, no further description is given in this embodiment; steps S360 to S370 are the same as steps S260 to S270, and since steps S2600 to S270 have already been described in detail in the embodiment illustrated in fig. 2, no further description is given in this embodiment.
Step S380 will be described in detail below.
S380, displaying the generated state data of the server;
and/or the presence of a gas in the gas,
sending the generated state data and/or prompt information of the server to a preset electronic device, wherein the prompt information is: and generating information for prompting the state of the server according to the generated state data of the server.
After the server generates the state data of the service end, in order to enable the user to know the state of each service end responding to the first service request and the second service request, the generated state data of each service end responding to the first service request and the second service request is displayed. In order to enable a user to quickly know the state of each server. The generated status data of the server can be made into a chart form by using a graphical tool such as echarts, and the chart form can be a report form, a line graph, a bar graph, a region graph, a bar graph, a scatter graph, a bubble graph, a K line graph, a pie graph, a ring graph and the like.
It should be noted that the server can display the generated state data of the server in real time, so that the user can know the state of each server at any time; the user may also preset a time interval according to the user's own needs, and display the generated state data of the server according to the preset time interval, for example, the preset time interval may be one day, one week, one month, and the like. It can be understood that, in order to save memory, the server will automatically delete the state data that has been exposed, and only save the performance data that has not been exposed.
In addition, in order to enable the user to know the state data of the server in time, after the server generates the state data of the server, the generated state data of the server can be sent to the preset electronic equipment, so that the user does not need to check the server every time to know the state data of the server; or after the server generates the state data of the server, the server may prompt the preset electronic device for information, where the prompt information is: and generating information for prompting the state of the server according to the generated state data of the server. For example, when the failure rate of the server side responding to the service request is high, the prompt message may be: and (5) alarming information. Of course, it is reasonable that the server may send the generated status data of the server and the prompt information to the preset electronic device at the same time.
In one implementation, the prompt information may be generated as follows:
selecting state data which accord with preset abnormal conditions corresponding to each state data from the generated state data of the server; and generating prompt information according to the selected state data.
For example, the failure probability of responding to the service request within the preset duration is as follows: 2%, namely the preset abnormal condition corresponding to the failure probability of responding to the service request within the preset duration is as follows: if the probability of failure of responding to the service request within the preset time is 3%, the prompt message generated by the server may be: the probability of failure in responding to a service request is abnormal, the probability of failure in responding to a service request is high, and the like.
It should be noted that there are various ways to send the generated status data and/or prompt information of the server to the preset electronic device. For example, the method can be used for sending a short message, a mail, a QQ message or a WeChat message to a preset electronic device; the specific content of the presentation information may be information for presenting only the occurrence of an abnormality, or may be detailed information of status data in which an abnormality has occurred. The present invention is not limited to the manner of sending the prompt message, the form of the prompt message, and the specific content of the prompt message.
Compared with the prior art, after the server generates the state data of the server side responding to the first service request and the second service request, the server can display the generated state data, or send the generated state data and/or prompt information of the server side to the preset electronic equipment, so that the user can know the state of each server side in time, and can find and process the state data of the server side in time when the state data of the server side is abnormal.
In a second aspect, an embodiment of the present invention further provides an information generating apparatus, which is applied to a server, and as shown in fig. 4, the apparatus includes:
a first log obtaining module 410, configured to obtain a first log corresponding to a first service request, where the first service request is: a service request requesting a service failure;
a target service determination module 420, configured to determine a service requested by the first service request as a target service;
a business logic determining module 430, configured to determine a business logic of the target service as a first business logic;
a target log data searching module 440, configured to search, in the log data included in the first log, log data that does not match the service configuration item of the first service logic, as target log data;
the information generating module 450 is configured to generate a reason for the service failure of the first service request according to the target log data.
Optionally, the first log obtaining module is specifically configured to:
acquiring a target log generated by a first client as a first log, wherein the first client is as follows: a client sending the first service request to the server, wherein the target log is: a log generated by the first client in the process of requesting the target service;
and/or the presence of a gas in the gas,
obtaining a log generated by a first service terminal in the process of responding to the first service request as a first log, wherein the first service terminal is as follows: and responding to the server side of the first service request.
Compared with the prior art, according to the technical scheme provided by the embodiment of the invention, when the server analyzes the reason of the service failure, the server firstly acquires the first log corresponding to the first service request, wherein the first service request is as follows: a service request requesting a service failure; then determining a target service requested by the first service request, and determining a business logic of the target service as a first business logic; finally, log data which are not matched with the service configuration item of the first service logic are searched in the log data contained in the first log and serve as target log data; and generating a reason for the service failure of the first service request according to the target log data.
Therefore, according to the technical scheme provided by the embodiment of the invention, when the server analyzes the reason of the service request failure, the server obtains the log corresponding to the service request of the service request failure, determines the service logic of the target service requested by the service request of the service request failure, searches the target log data which is not matched with the service logic of the target service in the obtained log, and can generate the reason of the service request failure according to the target log data. Unlike the prior art, when the server analyzes the reason of the requested service failure, the server needs to call an analysis tool corresponding to the requested service to analyze the reason of the requested service failure. Therefore, through the technical scheme provided by the embodiment of the invention, the problem that the workload of developers is large due to the fact that a large number of analysis tools need to be written can be avoided, and the workload of the developers can be reduced.
An embodiment of the present invention further provides an information generating apparatus, which is applied to a server, and as shown in fig. 5, the apparatus includes:
a first log obtaining module 510, configured to obtain a first log corresponding to a first service request, where the first service request is: a service request requesting a service failure;
a target service determination module 520, configured to determine a service requested by the first service request as a target service;
a business logic determining module 530, configured to determine a business logic of the target service as a first business logic;
a target log data searching module 540, configured to search, in the log data included in the first log, log data that does not match the service configuration item of the first service logic, as target log data;
an information generating module 550, configured to generate a reason for the service failure of the first service request according to the target log data;
a second log obtaining module 560, configured to obtain a second log corresponding to a second service request, where the second service request is: a service request requesting a successful service;
a status data generating module 570, configured to generate, according to the first log and the second log, status data of a server responding to the first service request and the second service request, where the status data of one server includes: the running state data of the server and the service state data of the service provided by the server.
Optionally, the operation status data of one server includes at least one of the following data:
the number of received service requests in a preset time, the success probability of responding to the service requests in the preset time, the failure probability of responding to the service requests in the preset time, the time ratio of responding to the service requests, the number of service requests responded per second, the number of relying parties, the success rate and the failure rate of the relying parties.
Compared with the prior art, when analyzing the reason of the service request failure, the server obtains the log corresponding to the service request of the service request failure, determines the service logic of the target service requested by the service request of the service request failure, searches the target log data which is not matched with the service logic of the target service in the obtained log, and can generate the reason of the service request failure according to the target log data; and acquiring a second log corresponding to the service request which requests the service to be successful, and generating state data of the server side responding to the first service request and the second service request according to the first log and the second log. Therefore, according to the technical scheme provided by the embodiment of the invention, the problem that the workload of developers is large due to the fact that a large number of analysis tools need to be written can be avoided, namely, the workload of the developers can be reduced, and the state data of the service end responding to the service request can be automatically generated according to the first log and the second log.
Optionally, on the basis of the embodiment shown in fig. 5, the information acquiring apparatus may further include:
the state data display module is used for displaying the generated state data of the server after generating the state data of the server responding to the first service request and the second service request according to the first log and the second log;
and/or the presence of a gas in the gas,
an information sending module, configured to send the generated state data and/or prompt information of the server to a preset electronic device after generating, according to the first log and the second log, state data of the server that responds to the first service request and the second service request, where the prompt information is: and generating information for prompting the state of the server according to the generated state data of the server.
In one embodiment, the prompt may be generated as follows:
selecting state data which accord with preset abnormal conditions corresponding to each state data from the generated state data of the server;
and generating the prompt information according to the selected state data.
Compared with the prior art, after the server generates the state data of the server side responding to the first service request and the second service request, the server can display the generated state data, or send the generated state data and/or prompt information of the server side to the preset electronic equipment, so that the user can know the state of each server side in time, and can find and process the state data of the server side in time when the state data of the server side is abnormal.
The embodiment of the present invention further provides a server, as shown in fig. 6, including a processor 601, a communication interface 602, a memory 603, and a communication bus 604, where the processor 601, the communication interface 602, and the memory 603 complete mutual communication through the communication bus 604,
a memory 603 for storing a computer program;
the processor 601 is configured to implement any of the information generating methods described in the method embodiments of the first aspect when executing the program stored in the memory 603.
The communication bus mentioned in the electronic device may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface is used for communication between the electronic equipment and other equipment.
The Memory may include a Random Access Memory (RAM) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a network Processor (Ne word Processor, NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component.
Compared with the prior art, according to the technical scheme provided by the embodiment of the invention, when the server analyzes the reason of the service failure, the server firstly acquires the first log corresponding to the first service request, wherein the first service request is as follows: a service request requesting a service failure; then determining a target service requested by the first service request, and determining a business logic of the target service as a first business logic; finally, log data which are not matched with the service configuration item of the first service logic are searched in the log data contained in the first log and serve as target log data; and generating a reason for the service failure of the first service request according to the target log data.
Therefore, according to the technical scheme provided by the embodiment of the invention, when the server analyzes the reason of the service request failure, the server obtains the log corresponding to the service request of the service request failure, determines the service logic of the target service requested by the service request of the service request failure, searches the target log data which is not matched with the service logic of the target service in the obtained log, and can generate the reason of the service request failure according to the target log data. Unlike the prior art, when the server analyzes the reason of the requested service failure, the server needs to call an analysis tool corresponding to the requested service to analyze the reason of the requested service failure. Therefore, through the technical scheme provided by the embodiment of the invention, the problem that the workload of developers is large due to the fact that a large number of analysis tools need to be written can be avoided, and the workload of the developers can be reduced.
In yet another embodiment of the present invention, a computer-readable storage medium is further provided, which stores instructions that, when executed on a computer, cause the computer to execute the information generating method described in any of the above embodiments.
Compared with the prior art, according to the technical scheme provided by the embodiment of the invention, when the server analyzes the reason of the service failure, the server firstly acquires the first log corresponding to the first service request, wherein the first service request is as follows: a service request requesting a service failure; then determining a target service requested by the first service request, and determining a business logic of the target service as a first business logic; finally, log data which are not matched with the service configuration item of the first service logic are searched in the log data contained in the first log and serve as target log data; and generating a reason for the service failure of the first service request according to the target log data.
Therefore, according to the technical scheme provided by the embodiment of the invention, when the server analyzes the reason of the service request failure, the server obtains the log corresponding to the service request of the service request failure, determines the service logic of the target service requested by the service request of the service request failure, searches the target log data which is not matched with the service logic of the target service in the obtained log, and can generate the reason of the service request failure according to the target log data. Unlike the prior art, when the server analyzes the reason of the requested service failure, the server needs to call an analysis tool corresponding to the requested service to analyze the reason of the requested service failure. Therefore, through the technical scheme provided by the embodiment of the invention, the problem that the workload of developers is large due to the fact that a large number of analysis tools need to be written can be avoided, and the workload of the developers can be reduced.
In yet another embodiment, the present invention further provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the information generating method described in any of the above embodiments.
Compared with the prior art, according to the technical scheme provided by the embodiment of the invention, when the server analyzes the reason of the service failure, the server firstly acquires the first log corresponding to the first service request, wherein the first service request is as follows: a service request requesting a service failure; then determining a target service requested by the first service request, and determining a business logic of the target service as a first business logic; finally, log data which are not matched with the service configuration item of the first service logic are searched in the log data contained in the first log and serve as target log data; and generating a reason for the service failure of the first service request according to the target log data.
Therefore, according to the technical scheme provided by the embodiment of the invention, when the server analyzes the reason of the service request failure, the server obtains the log corresponding to the service request of the service request failure, determines the service logic of the target service requested by the service request of the service request failure, searches the target log data which is not matched with the service logic of the target service in the obtained log, and can generate the reason of the service request failure according to the target log data. Unlike the prior art, when the server analyzes the reason of the requested service failure, the server needs to call an analysis tool corresponding to the requested service to analyze the reason of the requested service failure. Therefore, through the technical scheme provided by the embodiment of the invention, the problem that the workload of developers is large due to the fact that a large number of analysis tools need to be written can be avoided, and the workload of the developers can be reduced.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for embodiments of the apparatus, the server, and the like, since they are substantially similar to the method embodiments, the description is relatively simple, and for relevant points, reference may be made to part of the description of the method embodiments.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (9)
1. An information generation method applied to a server, the method comprising:
obtaining a first log corresponding to a first service request, wherein the first service request is: a service request requesting a service failure; the first log is a log generated by a server side responding to the first service request in the process of responding to the first service request;
determining a service requested by the first service request as a target service;
determining a business logic of the target service as a first business logic;
searching log data which is not matched with a service configuration item of the first service logic in the log data contained in the first log as target log data, wherein the service configuration item of the first service logic is a parameter which needs to be met when a service end successfully provides service for a client side, and the service configuration item of the first service logic is executed;
generating a reason for service failure of the first service request according to the target log data;
acquiring a second log corresponding to a second service request, wherein the second service request is as follows: a service request requesting a successful service;
according to the first log and the second log, state data of a server responding to the first service request and the second service request are generated, wherein the state data of one server comprises: the running state data of the server and the service state data of the service provided by the server;
the operation state data of one server comprises at least one of the following data:
the number of received service requests in a preset time, the success probability of responding to the service requests in the preset time, the failure probability of responding to the service requests in the preset time, the time ratio of responding to the service requests, the number of service requests responded per second, the number of relying parties, the success rate and the failure rate of the relying parties.
2. The method of claim 1, wherein obtaining the first log corresponding to the first service request comprises:
acquiring a target log generated by a first client as a first log, wherein the first client is as follows: a client sending the first service request to the server, wherein the target log is: a log generated by the first client in the process of requesting the target service;
and/or the presence of a gas in the gas,
obtaining a log generated by a first service terminal in the process of responding to the first service request as a first log, wherein the first service terminal is as follows: and responding to the server side of the first service request.
3. The method of claim 1, wherein after generating the status data of the server side responding to the first service request and the second service request according to the first log and the second log, the method further comprises:
displaying the generated state data of the server;
and/or the presence of a gas in the gas,
sending the generated state data and/or prompt information of the server to a preset electronic device, wherein the prompt information is: and generating information for prompting the state of the server according to the generated state data of the server.
4. The method of claim 3, wherein the hint information is generated by:
selecting state data which accord with preset abnormal conditions corresponding to each state data from the generated state data of the server;
and generating the prompt information according to the selected state data.
5. An information generating apparatus, applied to a server, the apparatus comprising:
a first log obtaining module, configured to obtain a first log corresponding to a first service request, where the first service request is: a service request requesting a service failure; the first log is a log generated by a server side responding to the first service request in the process of responding to the first service request;
a target service determination module, configured to determine, as a target service, a service requested by the first service request;
a business logic determining module, configured to determine a business logic of the target service, as a first business logic;
a target log data searching module, configured to search, in log data included in the first log, log data that does not match a service configuration item of the first service logic, as target log data, where the service configuration item of the first service logic is a parameter that needs to be satisfied by executing the first service logic when a service end successfully provides a service for a client;
the information generating module is used for generating the reason of the service failure of the first service request according to the target log data;
a second log obtaining module, configured to obtain a second log corresponding to a second service request, where the second service request is: a service request requesting a successful service;
a status data generating module, configured to generate, according to the first log and the second log, status data of a server responding to the first service request and the second service request, where the status data of one server includes: the running state data of the server and the service state data of the service provided by the server;
the operation state data of one server comprises at least one of the following data:
the number of received service requests in a preset time, the success probability of responding to the service requests in the preset time, the failure probability of responding to the service requests in the preset time, the time ratio of responding to the service requests, the number of service requests responded per second, the number of relying parties, the success rate and the failure rate of the relying parties.
6. The apparatus of claim 5, wherein the first log obtaining module is specifically configured to:
acquiring a target log generated by a first client as a first log, wherein the first client is as follows: a client sending the first service request to the server, wherein the target log is: a log generated by the first client in the process of requesting the target service;
and/or the presence of a gas in the gas,
obtaining a log generated by a first service terminal in the process of responding to the first service request as a first log, wherein the first service terminal is as follows: and responding to the server side of the first service request.
7. The apparatus of claim 5, further comprising:
the state data display module is used for displaying the generated state data of the server after generating the state data of the server responding to the first service request and the second service request according to the first log and the second log;
and/or the presence of a gas in the gas,
an information sending module, configured to send the generated state data and/or prompt information of the server to a preset electronic device after generating, according to the first log and the second log, state data of the server that responds to the first service request and the second service request, where the prompt information is: and generating information for prompting the state of the server according to the generated state data of the server.
8. The apparatus of claim 7, wherein the hint information is generated by:
selecting state data which accord with preset abnormal conditions corresponding to each state data from the generated state data of the server;
and generating the prompt information according to the selected state data.
9. A server is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing the communication between the processor and the memory through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of any of claims 1 to 4 when executing a program stored in the memory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810043695.XA CN108390770B (en) | 2018-01-17 | 2018-01-17 | Information generation method and device and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810043695.XA CN108390770B (en) | 2018-01-17 | 2018-01-17 | Information generation method and device and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108390770A CN108390770A (en) | 2018-08-10 |
| CN108390770B true CN108390770B (en) | 2022-03-04 |
Family
ID=63077037
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810043695.XA Active CN108390770B (en) | 2018-01-17 | 2018-01-17 | Information generation method and device and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108390770B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111177428B (en) * | 2018-11-12 | 2023-06-30 | 马上消费金融股份有限公司 | Business exception processing method and related device |
| CN113438294A (en) * | 2021-06-22 | 2021-09-24 | 康键信息技术（深圳）有限公司 | Service request processing method, device, equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101198105A (en) * | 2007-12-25 | 2008-06-11 | 北京亿阳信通软件研究院有限公司 | Mobile communication service handling method and device |
| CN101753344A (en) * | 2008-12-12 | 2010-06-23 | 华为技术有限公司 | Method, device and system for logging |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9218211B2 (en) * | 2009-01-02 | 2015-12-22 | International Business Machines Corporation | Priority promotion for service requests |
| CN106411970B (en) * | 2015-07-28 | 2019-10-11 | 阿里巴巴集团控股有限公司 | A kind of fault handling method based on service call, device and system |
-
2018
- 2018-01-17 CN CN201810043695.XA patent/CN108390770B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101198105A (en) * | 2007-12-25 | 2008-06-11 | 北京亿阳信通软件研究院有限公司 | Mobile communication service handling method and device |
| CN101753344A (en) * | 2008-12-12 | 2010-06-23 | 华为技术有限公司 | Method, device and system for logging |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108390770A (en) | 2018-08-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108153670B (en) | Interface testing method and device and electronic equipment | |
| US9384114B2 (en) | Group server performance correction via actions to server subset | |
| EP2871574A1 (en) | Analytics for application programming interfaces | |
| CN111245900B (en) | Distributed message sending processing system and processing method thereof | |
| US10452469B2 (en) | Server performance correction using remote server actions | |
| US20150281035A1 (en) | Monitoring of Node.JS Applications | |
| US20160323160A1 (en) | Detection of node.js memory leaks | |
| CN111522711A (en) | Data monitoring processing system, method, execution end, monitoring end and electronic equipment | |
| US10599505B1 (en) | Event handling system with escalation suppression | |
| CN108390770B (en) | Information generation method and device and server | |
| CN110430070B (en) | Service state analysis method, device, server, data analysis equipment and medium | |
| CN112866062B (en) | Distributed pressure test system, method, device, equipment and storage medium | |
| US10191844B2 (en) | Automatic garbage collection thrashing monitoring | |
| CN112653736B (en) | Parallel source returning method and device and electronic equipment | |
| CN114153703A (en) | Micro-service exception positioning method and device, electronic equipment and program product | |
| CN116545905A (en) | Service health detection method and device, electronic equipment and storage medium | |
| CN110633165A (en) | Fault processing method, device, system server and computer readable storage medium | |
| CN112286778B (en) | Service chain call analysis method and device | |
| CN112445597B (en) | Timing task scheduling method and device | |
| CN112416731B (en) | Stability monitoring method and device applied to block chain system | |
| CN114356713A (en) | Thread pool monitoring method and device, electronic equipment and storage medium | |
| CN112860770B (en) | Report generation method, report generation device, electronic equipment and storage medium | |
| CN114090268A (en) | Container management method and container management system | |
| CN110362464B (en) | Software analysis method and equipment | |
| CN109063206B (en) | Article monitoring method and device |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |