CN117955807A

CN117955807A - System detection method, device, electronic equipment and computer readable storage medium

Info

Publication number: CN117955807A
Application number: CN202311814282.4A
Authority: CN
Inventors: 何金丹
Original assignee: Mashang Xiaofei Finance Co Ltd
Current assignee: Mashang Xiaofei Finance Co Ltd
Priority date: 2023-12-26
Filing date: 2023-12-26
Publication date: 2024-04-30

Abstract

The application provides a system detection method, a system detection device, electronic equipment and a computer readable storage medium; the method comprises the following steps: network analysis is carried out on the call system to be detected, and when the obtained network analysis result is that the network is not abnormal, an abnormal operation request which is sent by the client and has failed response is obtained; routing the abnormal operation request to the idle node device; and acquiring operation response data sent by the idle node equipment, and determining a response failure reason of the abnormal operation request according to the operation response data. According to the application, the no-load node which is not connected with any client flow is used for responding to the abnormal operation request, so that operation response data can be generated only for the abnormal operation request, and the system detection efficiency is improved.

Description

System detection method, device, electronic equipment and computer readable storage medium

Technical Field

The present application relates to the field of data processing technologies, and in particular, to a system detection method, a device, an electronic apparatus, and a computer readable storage medium.

Background

Along with the increasing size and complexity of the call center system, the direction of checking when the request of the agents is abnormal is also quite large, for example, the network of the agents is abnormal, the server is abnormal, and the abnormal situation of the specific agents is difficult to check due to the fact that the number of the agents is quite large. For the network anomaly at the agent end, the site reliability engineer (Site Reliability Engineer, SRE) typically notifies the agent to execute the network operation command to check the network condition, and for the anomaly at the service end, the SRE typically locates the link data condition of the anomaly by log analysis, full link analysis tool analysis, and the like.

Disclosure of Invention

The embodiment of the application provides a system detection method, a system detection device and a computer readable storage medium, which can respond to an abnormal operation request through a no-load node which is not accessed with traffic, so that operation response data can be generated only for the abnormal operation request, and further the system detection efficiency is improved.

The technical scheme of the embodiment of the application is realized as follows:

The embodiment of the application provides a system detection method, which comprises the following steps: network analysis is carried out on the call system to be detected, and when the obtained network analysis result is that the network is not abnormal, an abnormal operation request which is sent by the client and has failed response is obtained; routing the abnormal operation request to an idle node device; and acquiring operation response data sent by the idle node equipment, and determining a response failure reason of the abnormal operation request according to the operation response data.

The embodiment of the application provides a system detection device, which comprises: the acquisition module is used for carrying out network analysis on the call system to be detected, and acquiring an abnormal operation request which is sent by the client and fails to respond when the obtained network analysis result is that the network is not abnormal; the routing module is used for routing the abnormal operation request to the idle node equipment; and the determining module is used for acquiring the operation response data sent by the idle node equipment and determining the response failure reason of the abnormal operation request according to the operation response data.

An embodiment of the present application provides an electronic device, including: a memory for storing computer executable instructions; and the processor is used for realizing the system detection method provided by the embodiment of the application when executing the computer executable instructions stored in the memory.

The embodiment of the application provides a computer readable storage medium which stores computer executable instructions for realizing the system detection method provided by the embodiment of the application when being executed by a processor.

Embodiments of the present application provide a computer program product comprising executable instructions stored in a computer readable storage medium; the processor of the electronic device reads the executable instructions from the computer readable storage medium and executes the executable instructions to implement the system detection method provided by the embodiment of the application.

The embodiment of the application has the following beneficial effects:

On the one hand, when the network analysis result shows that the network is not abnormal, an abnormal operation request of the client side when the system of the call system to be detected is abnormal is acquired, the abnormal operation request is routed to the idle node equipment, and the idle node equipment responds to the abnormal operation request. Therefore, because the idle node device is an idle node which is not connected with any client flow before the abnormal operation request is routed, after the abnormal operation request is routed to the idle node device, the operation response data generated after the idle node device responds to the abnormal operation request does not contain response data of other normal requests except the abnormal operation request, that is, the data volume in the operation response data obtained after the idle node device responds to the abnormal operation request is smaller, so that relevant logs of system abnormality can be rapidly positioned based on the operation response data obtained after the idle node device responds to the abnormal operation request, and the abnormality detection of the system can be rapidly carried out, thereby improving the detection efficiency of the system.

On the other hand, the abnormal operation request is routed to the idle node equipment, namely, the idle node equipment does not need to respond to other normal requests except the abnormal operation request, and the idle node equipment only pays attention to the related operation and the request of the client side when the abnormal condition occurs, so that the idle node equipment can accurately capture the related log information when the abnormal condition occurs, and the accuracy of the abnormal detection can be greatly improved based on the log information.

Drawings

Fig. 1 is a flow chart of a related art system detection method according to an embodiment of the present application;

fig. 2 is a schematic diagram of a result of screening log information according to the related art provided in the embodiment of the present application;

FIG. 3 is a schematic diagram of a result of screening abnormal operation request points according to the related art according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a system detection system according to an embodiment of the present application;

FIG. 5 is a schematic flow chart of an alternative system detection method according to an embodiment of the present application;

FIG. 6 is a schematic flow chart of another alternative system detection method according to an embodiment of the present application;

fig. 7 is a schematic diagram of an implementation flow for performing abnormality detection on a system abnormality of a call system to be detected based on operation response data according to an embodiment of the present application;

Fig. 8 is a schematic diagram of an implementation flow for quickly locating a cause of an abnormality in a system according to an embodiment of the present application;

fig. 9 is a schematic diagram of an implementation flow for obtaining a network analysis result according to an embodiment of the present application;

FIG. 10 is a flowchart of a system detection method for determining a specific cookie according to an embodiment of the present application;

FIG. 11 is a schematic diagram of a system detection device according to an embodiment of the present application;

fig. 12 is a schematic diagram of a composition structure of an electronic device according to an embodiment of the present application.

Detailed Description

The present application will be further described in detail with reference to the accompanying drawings, for the purpose of making the objects, technical solutions and advantages of the present application more apparent, and the described embodiments should not be construed as limiting the present application, and all other embodiments obtained by those skilled in the art without making any inventive effort are within the scope of the present application.

In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is to be understood that "some embodiments" can be the same subset or different subsets of all possible embodiments and can be combined with one another without conflict.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used in the embodiments of the application is for the purpose of describing embodiments of the application only and is not intended to be limiting of the application.

The flow chart of the related art is shown in fig. 1, and the specific flow chart is as follows: s01, when an agent feeds back an abnormality when using the system, the agent feeds back the abnormality to the SRE, for example, clicking to report errors or no abnormality such as data display; s02, the SRE prompts the seat to execute operations such as ping and telnet; s03, feeding back ping and telnet network execution results to the SRE by the agent; s04, SRE analyzes the feedback of the seat and checks whether the network is abnormal; s05, if the network is abnormal, the SRE contacts with the network management to process the network or replace the network; s06, if the network is not abnormal, the SRE continuously analyzes the reason of the abnormality through the log and the request flow; s07, searching an abnormal request of a specific agent from a large number of requests by the SRE, analyzing logs based on the abnormal request, searching the abnormal logs from the large number of logs, and checking whether the logs have related errors or not; s08, SRE positioning abnormality is solved. Thus, the SRE analyzes the request situation of a specific agent through the log to see if an abnormality can be found from the log, however, finding the log of the specific agent from a large number of logs is difficult. The abnormal request of the specific agent is found from a large number of request flows, then the request link of the specific agent is analyzed, the condition containing the upstream and downstream data flows is analyzed, and the reason of the abnormal request of the agent is positioned.

However, most of agent computers and networks have insufficient knowledge, so that network operation commands like ping, telnet and the like cannot be accurately executed, and an execution result of the network operation commands cannot be accurately returned, so that the SRE cannot accurately judge the network condition of the agent end; and the abnormal description information provided by the agent is often simpler, so that when screening is performed on massive log information, the abnormal operation request flow needs to be identified and judged from the information. As shown in fig. 2, when filtering can be performed only according to account information provided by the agent, thousands of pieces of log information may be screened out, but to accurately find out an abnormal operation request flow meeting the agent description in the logs, special techniques and abundant experience need to be used for distinguishing and analyzing, so that difficulty is great. SR E uses a full-link analysis tool to perform deep analysis on the request flow of the application program, but due to the limitation of the analysis tool, the abnormal operation request of a specific agent is often mixed with the requests of a large number of normal agents, which makes it very difficult for the SRE to accurately locate the abnormal operation request. As shown in fig. 3, there are more than 7 tens of thousands of requests in a minute, each small point representing a request, from which 7 tens of thousands of points, the abnormal request point is found, which cannot be manually screened.

Based on at least one problem existing in the related art, the embodiment of the application aims at system abnormality, firstly, abnormality detection is carried out on a network, a network analysis result is generated by executing network analysis operation, and an abnormal operation request carrying identification information after system abnormality re-operation is obtained under the condition that the network analysis result is that the network is not abnormal; then, routing the abnormal operation request to idle node equipment of an idle node which is not connected with any client flow, acquiring operation response data obtained after the idle node equipment responds to the abnormal operation request, determining a response link of the abnormal operation request in the whole request response process based on a scatter diagram in the operation response data, and screening an abnormal log; and finally, determining the abnormality type of the system abnormality based on the abnormality log, thereby realizing abnormality detection of the system abnormality. Therefore, by judging whether the abnormal operation request after the abnormal heavy operation of the system carries the identification information or not and routing the abnormal operation request carrying the identification information to the idle node equipment, the idle node equipment has only the flow access of the abnormal operation request, so that the abnormal problem of the system can be rapidly positioned in the system detection process without being influenced by other normal requests, and the system detection rate is improved.

Referring to fig. 4, fig. 4 is a schematic structural diagram of a system detection system 100 architecture according to an embodiment of the present application, in order to support a system detection application, a terminal 400 is connected to a server 200 through a network 300, where the network 300 may be a wide area network or a local area network, or a combination of the two.

The terminal 400 is configured to send an abnormality detection request to the server 200, and the server 200 is configured to send an operation alert message to the terminal 400 in response to the abnormality detection request, to alert the target object to perform a network analysis operation through the terminal 400; the terminal 400 generates a network analysis result of the call system to be detected in response to the network analysis operation and transmits the network analysis result to the server 200; the server 200 obtains a network analysis result, and obtains an abnormal operation request of the terminal 400 when a system abnormality occurs in the call system to be detected under the condition that the network analysis result is that the network is not abnormal; the server 200 routes the abnormal operation request to the idle node device; the server 200 obtains operation response data obtained after the idle node device responds to the abnormal operation request, performs abnormality detection on system abnormality of the call system to be detected based on the operation response data, obtains an abnormality detection result, namely a response failure reason of the abnormal operation request, and returns the abnormality detection result to the terminal 400 so as to display the abnormality detection result at the terminal 400.

In some embodiments, the server 200 may be a stand-alone physical server, a server cluster or a distributed system formed by a plurality of physical servers, or may be a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, a content delivery network (Content Delivery Network, CDN), and basic cloud computing services such as big data and an artificial intelligence platform, where the server 200 may also belong to an SRE engineer and may be operated by the SRE engineer. The terminal 400 may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, a vehicle-mounted terminal, etc., and the terminal 400 may be an agent client, but is not limited thereto. The terminal 400 and the server 200 may be directly or indirectly connected through wired or wireless communication, which is not limited in the embodiment of the present application.

The system detection method provided by the embodiments of the present application may be performed by an electronic device, where the electronic device may be a server or a terminal, that is, the system detection method of the embodiments of the present application may be performed by the server or the terminal, or may be performed by interaction between the server and the terminal.

Referring to fig. 5, fig. 5 is a schematic flowchart of an alternative system detection method according to an embodiment of the present application, which will be described with reference to the steps shown in fig. 5, and the method includes the following steps S101 to S103, where an execution subject of the system detection method is taken as an example of a server:

Step S101, network analysis is carried out on the call system to be detected, and when the obtained network analysis result is that the network is not abnormal, an abnormal operation request which is sent by the client and has failed in response is obtained.

In the embodiment of the application, the call system to be detected is a system in which a system abnormality occurs in a process that a target object uses the system or performs a certain operation, when the system abnormality occurs, the target object sends an abnormality detection request to a server through a client, the server responds to the abnormality detection request sent by the client and sends an operation reminding message to the client, and a network analysis result of the call system to be detected, which is generated after the client responds to network analysis operation, is obtained.

The client is an application program corresponding to the server and providing local services for the user, for example, the client can be an agent client, the agent client is suitable for each service industry, and the agent can provide each service (for example, consultation service, business handling service and the like) for the user through the agent client. The abnormality detection request refers to a request for abnormality detection of a system when a target object performs a certain operation, and the target object sends a request to a server through a client, for example, the abnormality of the system may be a system abnormality such as a click error report when user information is modified, and no data presentation when a system file is accessed. At the client, corresponding abnormality detection requests can be generated aiming at any system abnormality, and the abnormality detection requests are sent to the server.

The operation reminding message is used for reminding the target object to execute network analysis operation through the client, the network analysis operation is an operation for detecting whether a network between the client and the server is abnormal or not by utilizing a network operation command, for example, detecting whether a network connection is normal or not, detecting whether a network port is normal or not, and the like, and the network operation command can be a ping, telnet and other execution command. That is, when an abnormality occurs in the system, the client transmits the generated abnormality detection request to the server, and the server first alerts the target object to detect whether there is a network abnormality in response to the abnormality detection request, that is, may alert the target object (for example, an agent or customer service) to perform network abnormality detection by performing a network analysis operation through the client, generates an operation alert message, and transmits the operation alert message to the client.

The network analysis result refers to an analysis result obtained after the target object executes the network analysis operation through the client, and is used for analyzing whether the network is abnormal or not. The network analysis results include two different analysis results: network presence anomalies and network absence anomalies. After the target object executes the network analysis operation through the client, a corresponding network analysis result is generated at the client, the target object can directly check the network analysis result through the client to determine whether the network of the call system to be detected is abnormal, or the client can directly send the network analysis result to the server, and the server can further determine whether the network of the call system to be detected is abnormal through detecting the network analysis result fed back by the client.

In the embodiment of the application, the abnormal operation request refers to an abnormal operation request sent by the client in response to failure when the target object directly checks the network analysis result through the client to indicate that the network is not abnormal. Or the server may send a system abnormal re-operation request to the client when detecting that the network analysis result fed back by the client is that the network is not abnormal, so that the target object re-executes the corresponding operation when the system abnormality occurs to generate a request. When the target object determines that the network is not abnormal through the client, re-executing the operation corresponding to the system abnormality at the client, generating an abnormal operation request by the client based on the operation, and sending the generated abnormal operation request to the server, so that the subsequent server routes the abnormal operation request to the idle node equipment.

In some embodiments, when the target object checks the network analysis result through the client to find that the network is abnormal, the target object may notify a professional serviceman (for example, a network administrator) to repair the network abnormality, or the target object may perform a network replacement operation, so that normal use of the system is realized after the network replacement. Or under the condition that the server detects that the network analysis result fed back by the client side is that the network is abnormal, the server can send a network abnormal maintenance prompt to the client side of the professional maintenance personnel to remind the professional maintenance personnel to carry out network abnormal maintenance, or the server can also send a network replacement prompt to the client side of the target object to remind the target object to replace network connection, so that the problem of network abnormality is solved, and normal use of the system is realized.

Step S102, routing the abnormal operation request to the idle node device.

In the embodiment of the application, the idle node equipment is an idle node which is not connected with any client traffic before the abnormal operation request is routed, and the idle node equipment can be understood as a server node which is idle at ordinary times and is not connected with the request for processing any client, namely is not connected with the client traffic. Before the server routes the abnormal operation request to the idle node device, a server node which is not accessed with the client flow is selected in advance to serve as the idle node device. The no-load node equipment is not connected with the client flow at ordinary times, and only the server accesses the client flow corresponding to the abnormal operation request to the no-load node equipment under the condition that the server determines that the network analysis result is that the network is not abnormal and receives the abnormal operation request of the client when the system of the call to be detected is abnormal, namely, the abnormal operation request is routed to the no-load node equipment, so that the no-load node equipment does not contain other client flows except the client flow corresponding to the abnormal operation request when the system of the call is abnormal, the interference of normal requests corresponding to normal operations of other users on the client is avoided, the normal requests are not required to be excluded from a large number of requests to find the abnormal operation request, and the time for carrying out the abnormal detection on the system of the call system to be detected based on the operation response data of the no-load node equipment can be greatly shortened.

Step S103, operation response data sent by the idle node equipment are obtained, and response failure reasons of abnormal operation requests are determined according to the operation response data.

In the embodiment of the application, the operation response data is response data generated after the idle node equipment executes the abnormal operation request. Since the server only routes the abnormal operation request to the idle node device, it is not interfered by other normal requests. For example, when the server receives an abnormal operation request, it may receive thousands of normal requests generated by all clients at the same time, and in general, the server needs to find the abnormal operation request from all the requests including the abnormal operation request and a large number of normal requests, so as to locate a system abnormality problem of the call system to be detected. However, after the server routes the abnormal operation request to the idle node device, the idle node device will respond to the abnormal operation request and generate operation response data, where the operation response data does not include response data of other normal requests except the abnormal operation request.

The operation response data comprises a scatter diagram obtained after the idle node equipment responds to the abnormal operation request, wherein the scatter diagram is a request response scatter diagram generated by executing a detail checking function through a full-link analysis tool when the idle node equipment responds to the abnormal operation request, the scatter diagram is used for displaying abnormal operation request counting and response time in a time dimension, and the corresponding abnormal operation request can be selected and the executing detail can be checked by dragging the diagram. The idle node equipment sends the scatter diagram to a server, the server can select all the scatter diagrams contained in the scatter diagram in a framing way, an abnormal link called in the system by the serial abnormal operation request and a related log of the abnormal operation request are obtained, and the abnormal link and the related log are analyzed to realize the rapid detection of the system abnormality of the call system to be detected and rapidly determine the response failure reason of the abnormal operation request.

According to the system detection method provided by the embodiment of the application, the operation reminding message is sent to the client in response to the abnormality detection request sent by the client, the target object is reminded to execute the network analysis operation through the client, and meanwhile, the network analysis result generated after the client executes the network analysis operation is obtained. And under the condition that the network analysis result shows that the network is not abnormal, acquiring an abnormal operation request of the client when the system is abnormal, routing the abnormal operation request to the idle node equipment, acquiring operation response data obtained after the idle node equipment responds to the abnormal operation request, and detecting the system abnormality based on the operation response data. Therefore, because the idle node equipment is an idle node which is not connected with any client flow before the abnormal operation request is routed, after the abnormal operation request is routed to the idle node equipment, the abnormal operation of the call system to be detected can be rapidly detected according to the operation response data obtained by the idle node equipment, and the abnormal system rate of the call system to be detected is improved and positioned.

For example, the system detection method provided by the embodiment of the application can be applied to the following scenes: in the process that the agent modifies loan information for a user through the agent client, the agent client clicks and reports errors, the agent feeds back the system errors to the server, for example, the system detection application interface of the agent client inputs an abnormality detection operation, the agent client generates an abnormality detection request based on the abnormality detection operation and sends the abnormality detection request to the server, and the server reminds the agent client to click on the agent client network analysis application by one key after receiving the abnormality detection request information, so that a network analysis result is implemented by utilizing a network operation command, namely, the server sends an operation reminding message to the client. The client returns the network analysis result to the server to determine whether the network problem causes the click error reporting abnormality.

When the network problem is not determined to exist, the server sends the specific website address with the cookie to the seat client, the seat is reminded to access the website address through the seat client, and the operation of clicking and reporting errors just in the process of modifying the loan information is re-executed. The server judges whether the received abnormal operation request carries the cookie or not, if yes, the abnormal operation request is routed to a specific server node (namely the idle node equipment) which does not have any agent client flow access at ordinary times, so that the specific server node only responds to the abnormal operation request of the agent client, and the abnormal detection process is not interfered by other normal requests. The server may select a specific server node through the full link analysis tool pinpoint, and frame and select all the scattered points in the node scattered point, where each scattered point includes a plurality of pieces of log information, for example, the modified user name request point, the modified loan time request point, the modified user contact information request point, and the like in the scattered point corresponding to the modified loan information abnormal operation request, and the modified loan time request point includes a plurality of pieces of log information such as obtaining loan initial time log information, obtaining loan ending time log information, and the like, and through these log information, paths called by the abnormal operation request in the system may be connected in series, so as to obtain a response link of the abnormal operation request in the whole request response process. The response link comprises a state characteristic identifier corresponding to each piece of log information, wherein the state characteristic identifier comprises different color identifiers, such as a red identifier and a black identifier, and when the state characteristic identifier is the red identifier, the log information is indicated to be abnormal log information. Therefore, the abnormal log information can be screened from all log information according to the state characteristic identification, the abnormal type of the system abnormality is determined based on the abnormal log information, the response failure reason of the abnormal operation request is determined based on the abnormal type, and the system detection of the abnormal system is realized.

The system detection method in the embodiment of the present application will be described below in connection with an interaction procedure between a server and a terminal (i.e., the above-mentioned client) in a system detection system. It should be noted that, the system detection method is a system detection method implemented by interaction between a server and a terminal, which is substantially the same as the system detection method executed by the server in the above embodiment, except that in the embodiment of the present application, actions executed by the terminal during execution of the system detection method are also described, and some steps may be executed by the terminal or the server, so, for the steps in the embodiment that are the same as those in the above embodiment but different in execution subject, the embodiment is only an exemplary illustration, and may be executed by any one execution subject in the implementation process, and the embodiment of the present application is not limited thereto.

Referring to fig. 6, fig. 6 is another optional flowchart of a system detection method according to an embodiment of the present application, as shown in fig. 6, the method includes the following steps S201 to S222:

in step S201, the terminal receives an abnormality detection operation input by the user.

In the embodiment of the application, a user can input the abnormality detection operation of the call system to be detected at the client of the abnormality detection application, in the abnormality detection application, an abnormality detection function can be provided, and the user (can be an abnormality detection engineer or a developer of the abnormality detection application) can input the abnormality detection operation at the abnormality detection function page.

In some embodiments, when the abnormality detection operation is input, a network operation command may be simultaneously input to perform a network analysis operation; and a preset resource positioning identifier can be input so as to realize the interactive operation of the resource positioning identifier.

In step S202, the terminal generates an abnormality detection request in response to the abnormality detection operation.

In the embodiment of the application, the data input by the user can be packaged into the abnormality detection request. For example, a network operation command input by a user may be encapsulated into an anomaly detection request, or a preset resource location identifier input by the user may be encapsulated into the anomaly detection request.

In step S203, the terminal transmits an abnormality detection request to the server.

In step S204, the server generates an operation alert message in response to the abnormality detection request.

In the embodiment of the application, when the server receives the abnormality detection request sent by the terminal, if the network operation command is encapsulated in the abnormality detection request, the abnormality detection request can be analyzed to obtain the network operation command in the abnormality detection request, and an operation reminding message is generated based on the network operation command to remind a target object to execute network analysis operation by using the network operation command at the client side so as to carry out subsequent system detection.

In step S205, the server sends an operation reminding message to the terminal.

Step S206, the terminal displays the operation reminding message on the current interface, receives the network analysis operation executed by the target object based on the operation reminding message, and generates a network analysis result.

In the embodiment of the application, when the terminal receives the operation reminding message sent by the server, the operation reminding message is displayed on the current interface, and the network analysis operation executed by the target object based on the operation reminding message is received. The network analysis operation may be that the target object completes the network analysis operation by executing the network operation command included in the operation reminding message, for example, the target object may perform ping in the cmd command window to detect whether the network connection is normal or not, and may also perform telnet to detect whether the port of the network is normal or not. The network analysis operation may also be that the target object performs network problem detection by clicking on a network analysis application of the terminal and using a network analysis platform associated with the network analysis application, so that a network analysis result is directly obtained by the network analysis platform.

And obtaining a corresponding network analysis result based on the network analysis operation of the target object, and determining whether the network of the call system to be detected is abnormal or not based on the network analysis result. When the network is abnormal, namely the terminal displays the network abnormality, the user can inform a network manager to solve the network problem, and can also solve the network problem by replacing the connecting network. When the network is not abnormal, the network abnormality problem is eliminated, and other possible system abnormality problems are continuously detected.

In step S207, the terminal transmits the network analysis result to the server.

Step S208, the server responds to the network analysis result, and obtains a preset resource positioning identifier under the condition that the network analysis result is that the network is not abnormal.

In the embodiment of the application, if the network analysis result shows that the network is not abnormal, if the abnormality detection request is packaged with the preset resource positioning identifier, the preset resource positioning identifier can be obtained by analyzing the abnormality detection request, and the subsequent interactive operation of the user on the resource positioning identifier through the terminal is completed based on the resource positioning identifier.

In some embodiments, an expiration time is set for the resource location identifier; and if the expiration time is reached, the resource positioning identifier is adjusted from the effective state to the failure state, wherein if the resource positioning identifier is in the failure state, the target object cannot execute interactive operation on the resource positioning identifier through the client. That is, an expiration time can be set for the resource positioning identifier, when the resource positioning identifier does not reach the expiration time, the resource positioning identifier is in a valid state, and the resource positioning identifier is indicated to be in a usable time range, so that a subsequent server is allowed to respond to the interaction operation of the target object to the resource positioning identifier through the terminal; when the resource positioning identifier reaches the expiration time, the server adjusts the resource positioning identifier from the effective state to the failure state, and the server indicates that the resource positioning identifier is not in the usable time range, and the subsequent server is forbidden to respond to the interactive operation of the target object on the resource positioning identifier through the terminal.

Step S209, the server sends the resource positioning identification to the terminal.

Step S210, the terminal sends the interactive operation of the target object to the resource positioning identification through the terminal to the server.

In the embodiment of the application, the resource location identifier, namely the uniform resource locator, is a mechanism used by the browser to search any resource published on the website, and is also the address of the unique resource given by the server on the website. Each valid resource location identity points to a unique resource, which may be identity information corresponding to the terminal. The interactive operation of the user on the resource positioning identifier by the terminal refers to the access operation of the user on the resource positioning identifier by clicking the resource positioning identifier on a browser, after the interactive operation is completed, the terminal sends the interactive operation to the server, and then the resource positioning identifier points to the identifier information which is uniquely corresponding to the terminal by the interactive operation.

In step S211, the server sets the identification information of the terminal when detecting that the client performs the interactive operation on the resource location identifier.

In the embodiment of the application, the identification information can be a cookie, for example, and is used for identifying the data information of the terminal, storing the information returned to the terminal by the server, and storing the information in the terminal. The automatic login of the cookie is utilized, the functions of browsing history, identity verification and the like are saved, when the website is accessed next time, the terminal sends the saved cookie to the server, and the server utilizes the cookie to perform subsequent abnormality detection operation. That is, when the server receives the interaction operation of the terminal on the resource positioning identifier by the target object sent by the terminal, the server obtains the identifier information pointed by the resource positioning identifier and uniquely corresponding to the terminal. The server may set a cookie corresponding to the terminal in the browser, for example, sp-debug: true, which indicates that the name of the cookie is sp-debug, and the value carried by the cookie is true, so that an abnormal operation request carrying identification information is generated at the terminal.

Step S212, the server sends identification information and a system abnormal re-operation request to the terminal.

In step S213, the terminal receives the abnormal heavy operation of the system of the target object in response to the abnormal heavy operation request of the system.

In the embodiment of the application, the system abnormal re-operation request is used for requesting the target object to re-operate the abnormal operation request with the system abnormality through the terminal. When the target object re-operates the abnormal operation request with the abnormal system through the terminal, the terminal receives the abnormal re-operation of the system of the target object.

In step S214, the terminal responds to the abnormal heavy operation of the system to generate an abnormal operation request for heavy operation, and adds the identification information into the abnormal operation request for heavy operation, so as to obtain an abnormal operation request carrying the identification information after the abnormal heavy operation of the system.

In the embodiment of the application, when the terminal receives the abnormal heavy operation of the system of the target object, the terminal responds to the abnormal heavy operation of the system to generate a heavy operation abnormal operation request, and adds the identification information sent by the server to the heavy operation abnormal operation request, namely, the heavy operation abnormal operation request, so that the abnormal operation request after the abnormal heavy operation of the system carries the identification information, and the abnormal operation request carrying the identification information after the abnormal heavy operation of the system is obtained.

And the request information in the abnormal operation request and the identification information are subjected to association operation to obtain association request information, and the association request information is packaged into the re-operation abnormal operation request, so that the abnormal operation request after the system is abnormally re-operated carries the request information and the identification information associated with the request information, and the abnormal operation request carrying the identification information after the system is abnormally re-operated is obtained.

In step S215, the terminal transmits an abnormal operation request to the server.

Step S216, the server acquires an abnormal operation request with failed response sent by the terminal, and analyzes the abnormal operation request to obtain an analysis result.

In the embodiment of the application, because the association request information in the abnormal operation request is encapsulated in the abnormal operation request carrying the identification information after the abnormal re-operation of the system is acquired, the abnormal operation request can be analyzed, and an analysis result, namely the association request information in the abnormal operation request, is obtained.

In step S217, the server determines whether the abnormal operation request carries the identification information of the terminal according to the analysis result.

In the embodiment of the application, the identification information is used for identifying that the call system accessed by the client does not have network abnormality. Because the abnormal operation request carrying the identification information after the abnormal re-operation of the system is obtained is also encapsulated with the association request information, the abnormal operation request can be analyzed to obtain an analysis result, namely the association request information in the abnormal operation request, and the association request information comprises the request information and the identification information associated with the request information. Therefore, according to the analysis result, whether the abnormal operation request carries the identification information for identifying the terminal or not can be determined, and whether the abnormal operation request is routed or not can be determined in the subsequent step.

Step S218, under the condition that the abnormal operation request carries the identification information, the server acquires the idle node equipment identification from a preset node equipment identification list.

In the embodiment of the application, when the identification information carried in the abnormal operation request is determined based on the request information, the subsequent routing of the abnormal operation request to the idle node equipment is indicated, so that the idle node equipment identification of the idle node equipment is firstly acquired. The preset node equipment identifier list may store all the idle node equipment identifiers in advance, where the idle node equipment identifiers are obtained from the preset node equipment identifier list, and may be one idle node equipment identifier that is not currently used for routing other abnormal operation requests is randomly selected in the node equipment identifier list. The preset node equipment identification list may also store all the idle node equipment identifications of other abnormal operation requests which are not routed currently in advance, where the idle node equipment identifications are obtained from the preset node equipment identification list, or may be a random selection of an idle node equipment identification in the node equipment identification list.

In some embodiments, when the identification information is not carried in other normal requests than the abnormal operation request, then the request is not subsequently routed to the idle node device. Thus, other normal requests are not routed to the idle node device, i.e., requests routed to the idle node device are abnormal operation requests.

In step S219, the server determines an idle node device according to the idle node device identifier, and routes the abnormal operation request to the idle node device.

In the embodiment of the application, the idle node equipment identifier is unique identifier information corresponding to the idle node equipment, and based on the idle node equipment identifier, the server can know which idle node equipment the abnormal operation request should be routed to. The idle node device is an idle node which is not accessed with the terminal traffic before the abnormal operation request is routed, when the abnormal operation request is routed to the idle node device, the corresponding terminal traffic is accessed to the idle node, so that the idle node device completely receives the abnormal operation request, and the idle node device can also contain the service request related to the abnormal operation request besides the abnormal operation request.

For example, in the existing five server nodes, the idle node device identifiers are A, B, C, D, E, and only the server node with the idle node device identifier B is the idle node that has not accessed the terminal traffic before the abnormal operation request is routed, the server determines the server node with the idle node device identifier B as the idle node device, acquires the idle node device identifier B of the idle node device, and routes the abnormal operation request to the idle node device with the idle node device identifier B based on the idle node device identifier B.

Step S220, the server acquires operation response data sent by the idle node equipment, and determines a response failure reason of the abnormal operation request according to the operation response data.

In the embodiment of the application, after the empty load node equipment receives the abnormal operation request, the empty load node equipment responds to the abnormal operation request, generates operation response data and sends the operation response data to the server.

In some embodiments, the operation response data includes a scatter plot obtained after the idle node device responds to the abnormal operation request; referring to fig. 7, fig. 7 shows that in step S220, determining the response failure cause of the abnormal operation request according to the operation response data can be achieved by the following steps S2201 to S2205:

Step S2201, based on the scatter diagrams, acquires pieces of log information generated by the idle node device after responding to the sub-operation request of each scatter.

In the embodiment of the application, the abnormal operation request comprises a plurality of sub-operation requests, and the scatter diagram comprises a plurality of scatter points, wherein each scatter point is a scatter point of each sub-operation request in the abnormal operation request in the scatter diagram, namely, each scatter point corresponds to one sub-operation request. The log information is a file for recording various important information in the running process of the system, is created and recorded by each process in the running process of the system, can be used for recording the normal running process of the system and abnormal information generated in the running process, and provides detailed information for rapidly positioning problems occurring in the running process of the system and program debugging problems in the developing process. The idle node equipment responds to the sub-operation request of each scatter point to obtain the scatter point corresponding to the sub-operation request in the scatter point diagram, and then obtains a plurality of pieces of log information corresponding to each sub-operation request according to the mapping relation between each scatter point in the scatter diagram and the log information.

For example, assuming that the abnormal operation request is an abnormal operation request generated by an abnormality occurring when an agent modifies a loan amount for a user, the abnormal operation request includes a sub-operation request for searching the user, a sub-operation request for inquiring the user's original loan amount, a sub-operation request for modifying the loan amount, and the like. After the idle node equipment responds to all sub-operation requests in the abnormal operation requests, sub-response data, namely all scattered points in a scattered point diagram, are generated, wherein each scattered point comprises scattered points for searching the sub-operation requests of a user, scattered points for searching the sub-operation requests of the original loan amount of the user, scattered points for modifying the sub-operation requests of the loan amount and the like, and each scattered point corresponds to a plurality of pieces of log information. At this time, by looking up the scattered points in the scattered points, a plurality of pieces of log information generated by the idle node device after responding to the sub-operation request of each scattered point can be obtained.

Step S2202, the abnormal log information is selected from the plurality of logs.

In the embodiment of the application, firstly, a response link of an abnormal operation request in the whole request response process can be determined based on a plurality of pieces of log information. Based on the obtained multiple pieces of log information, paths called in the system by one user request can be connected in series, so that the paths called in the system by the abnormal operation request can be connected in series based on the log information associated with each sub-operation request in the abnormal operation request, and a response link of the abnormal operation request in the whole request response process can be obtained.

Then, based on the state characteristic identification, abnormal points are screened from all log identification points. The response link comprises a log identification point corresponding to each piece of log information, the log identification point is provided with a state characteristic identification, the state characteristic identification is used for identifying whether the log identification point is an abnormal point, for example, when the log identification point is an abnormal point, the state characteristic identification is displayed in red; when the identification log identification point is not an outlier, the status feature identification may be displayed in black. And through the color displayed by the state characteristic identification, whether the log identification points are abnormal points or not can be sequentially determined, and the abnormal points are screened from all the log identification points.

And finally, determining the log information corresponding to the abnormal point as abnormal log information. The log information corresponding to the abnormal points is different, and when the abnormal points are screened out from all the log identification points, each screened abnormal point corresponds to the unique log information, the log information corresponding to the abnormal point can be determined to be the abnormal log information.

In step S2203, attribute parameters in the anomaly log information are acquired.

In the embodiment of the application, each log has corresponding attribute parameters, wherein the attribute parameters comprise log name, log level, date and time, source, event ID, task category and the like, for example, the log level can represent the severity of the log, and the abnormal problem of the system can be positioned according to the specific event ID. For the abnormal log information, the abnormal type of the abnormal log information can be judged according to the attribute parameters, for example, the severity of the abnormal log recorded when the abnormal system occurs can be determined based on the attribute parameters, and the abnormal problem of the system can be positioned by judging whether the abnormal log information is the log information related to the service codes or the client data, namely, the abnormal type of the abnormal system is determined based on the attribute parameters, so that the response failure reason of the abnormal operation request is determined according to the abnormal type of the abnormal log information.

In step S2204, in the case where it is determined that the abnormal log information is the log information related to the service code based on the attribute parameter, it is determined that the response failure of the abnormal operation request is due to the service code abnormality.

In the embodiment of the application, the abnormal service code refers to the error of the code associated with the service corresponding to the abnormal operation request, and when the abnormal log information is the log information related to the service code, the abnormal system is indicated to be the error of the service code, namely the response failure of the abnormal operation request is caused by the abnormal service code.

In some embodiments, in the case that the response failure cause of the abnormal operation request is abnormal in the service code, determining a service source code corresponding to the abnormal operation request, and acquiring an update code corresponding to the service source code; and updating the service source code by adopting the updating code. When the service code is abnormal, it is first necessary to determine the service code in which an error has occurred, that is, the service source code corresponding to the abnormal operation request. Then, searching for a new code version corresponding to the service source code by searching and searching for the new code version to check whether the existing new code version replaces the service source code corresponding to the abnormal operation request; the server can also generate a code update prompt message and send the message to a developer of the terminal so as to remind the developer of repairing the service source code, namely updating the service source code and obtaining an update code corresponding to the service source code. And finally, updating the service source code by using the updating code, so as to realize the rapid repair of the system abnormality when the service code is abnormal.

In step S2205, in the case where it is determined that the abnormal log information is the log information related to the client data based on the attribute parameter, it is determined that the response failure cause of the abnormal operation request is the client data abnormality.

In the embodiment of the application, the abnormal client data refers to that errors occur in the data associated with the abnormal operation request of the client, for example, the loan amount of the user is wrongly reduced in the process of upgrading the loan amount of the user by the seat of the client, so that a system abnormal prompt is generated in the subsequent business handling process. When the abnormal log information is the log information related to the client data, the abnormal log information indicates that the system abnormality is the error of the client data, namely the response failure cause of the abnormal operation request is the abnormality of the client data.

In some embodiments, in the case that the response failure cause of the abnormal operation request is that the client data is abnormal, a data abnormality prompt message is sent to the client. The data abnormality prompting message sent to the client can prompt the user of the client that the reason of the response failure of the seat is data abnormality, prompt the user of the seat where the data of the client is wrong, prompt the user of how to change the data of the client, and the like, so as to realize the rapid repair of the data abnormality of the client to the system abnormality.

In step S221, the server transmits the response failure cause to the terminal.

In step S222, the terminal outputs a response failure reason.

In the embodiment of the application, aiming at system abnormality, firstly, abnormality detection is carried out on a network, a network analysis result is generated by executing network analysis operation, and an abnormal operation request carrying identification information after system abnormality re-operation is obtained under the condition that the network analysis result is that the network is not abnormal; then, routing the abnormal operation request to idle node equipment of an idle node which is not connected with any client flow, acquiring operation response data obtained after the idle node equipment responds to the abnormal operation request, determining a response link of the abnormal operation request in the whole request response process based on a scatter diagram in the operation response data, and screening out abnormal log information; finally, determining the abnormal type of the system abnormality based on the abnormal log information, thereby determining the response failure reason of the abnormal operation request. Therefore, by judging whether the abnormal operation request after the abnormal heavy operation of the system carries the identification information or not and routing the abnormal operation request carrying the identification information to the idle node equipment, the idle node equipment has only the flow access of the abnormal operation request, so that the abnormal problem of the system can be rapidly positioned in the system detection process without being influenced by other normal requests, and the system detection rate is improved.

In the following, an exemplary application of the embodiment of the present application in a practical application scenario will be described.

The embodiment of the application provides a system detection method, in the case that an agent feeds back a certain operation abnormality, a server firstly detects an agent end network problem by informing the agent of network analysis operation executed at an agent client (namely the client), when the agent end network is not abnormal, the agent accesses a specific website URL (namely the URL) with a specific cookie (namely the identification information) at the agent client, and the operation under the abnormal condition is re-executed, so that an abnormal operation request is generated, the server routes the abnormal operation request to a specific server node (namely the idle node equipment), and the system detection is carried out on the abnormal operation request at the specific server node, so that the quick positioning of the cause of the system abnormality is realized.

Referring to fig. 8, fig. 8 is a schematic diagram of an implementation flow of a fast positioning system abnormality cause provided in an embodiment of the present application, where the implementation flow is: s10, the agent feeds back abnormality to the server; s11, the server informs the seat to operate and click the one-click network analysis client; s12, the network analysis client uploads an analysis result to an analysis platform; s13, the server analyzes and checks whether the network problem is caused by the analysis platform; s14, if the network is abnormal, the server informs the network manager to process the network or replace the network; s15, if the network is not abnormal, the server continues to analyze the reason of the abnormality through the log and pinpoint; s16, the server informs the agent to visit a specific URL; s17, after the agent accesses the URL, a specific cookie such as sp-debug is produced in the browser; s18, the server informs the seat of executing the just abnormal request again; s19, after the Nginx receives the request, judging that sp-debug request exists in the request, and routing the request to a back-end node (namely the idle node equipment) without traffic at ordinary times; s20, the server firstly selects a scatter diagram of the back-end node through a pinpoint page; s21, the server frames all scattered points of the back-end node, and the scattered point requests come from the just-specific agents; s22, the server checks all logs of the rear end node, wherein the logs are from the just-specific agents; s23, combining the analysis of the log and pinpoint, and locating and solving the system abnormality cause.

Specifically, when the agent feeds back an operation abnormality or cannot complete a job, the server notifies the agent to execute the network analysis operation of the agent client on one hand, for example, click on the network analysis agent client by one click, the agent client analyzes an analysis task (mainly, some network operation commands such as ping, telnet, curl, etc.) of the network analysis platform, executes a corresponding network analysis operation, and returns a network analysis result to the network analysis platform. The server checks and analyzes whether the network from the agent end to the server is normal or not through the network analysis platform, and if the network is abnormal, the server contacts with the agent side network manager to solve the network problem or replace the network, otherwise, the server notifies the agent of a request for operating abnormality again. On the other hand, the server informs the agent to access a specific URL, which places a specific cookie, for example, sp-debug, in the browser of the agent client: true, set time 2 minutes expired.

As shown in fig. 9, the network analysis platform needs to set an analysis task of the agent client application, for example, set a domain name needing to be pinned and a domain name and a port needing to be telnet, and provide an interface to output task data, and the agent client application performs automatic detection according to the received task data. In addition, the network analysis platform needs to provide an interface for the agent client to upload, and returns the network analysis result to the network analysis platform.

After the agent re-operates the just abnormal request, as the agent accesses the specific URL before and places the cookie, as shown in fig. 10, S1001 and nglnx determine whether there is an sp-debug cookie, and if there is no sp-debug cookie, S1002 is executed to normally route the agent request (i.e. the abnormal operation request) to the back-end server node; if there is a cookie of sp-debug to true, S1003 is executed, where the request of the agent is routed to a special server node (i.e. the above-mentioned no-load node device), where the special server node does not access other agent traffic at ordinary times, and after the abnormal traffic of the agent is accessed, the special server node receives the request of the specific agent completely, and when analyzing the problem, the special server node will not interfere with other normal requests, i.e. other agents will not be affected by this, and will normally request the server node. The server can locate the problem with the agent at that particular server node simply by pinpoint and log analysis.

After the program is introduced pinpoint, each request stream is associated with one traceid when generating a log, and is used for concatenating all paths called in the system by a certain request, while detailed calling link information can be queried in pinpoint through traceid, so that the knowledge of the front and rear environments of the whole request stream is facilitated. After the server obtains traceid and related logs of the agent abnormal operation request, these information are used to detect and determine the corresponding link (i.e. the response link of the abnormal operation request in the whole request response process) in pinpoint. And checking abnormal points on the link, and comprehensively analyzing the acquired log information prompt.

Classifying and positioning the abnormal type aiming at the abnormal problem, for example, if the analysis results in that the abnormality is a specific code error, the code needs to be checked and the online repair is needed; if the data of the agent is wrong, repair processing and the like are required for the data of the agent. In summary, corresponding solutions are adopted for different problem categories.

In the embodiment of the application, the agent does not need complex computer network knowledge, and can upload network analysis results by mainly operating one button of the agent client, so that the agent is prevented from opening a cmd command window to execute network analysis operations such as ping, telnet and the like; the abnormal operation request of the agent is routed to a specific server node, the abnormal operation request is not influenced by other normal requests, the server can screen corresponding logs according to the event ID, and the server can simply and completely see all log information of the specific agent without screening needed log information from a large amount of log information; the server can directly select specific nodes on pinpoint pages, frame and select all the requests of the nodes, directly analyze abnormal operation request links, and can improve the abnormal speed of the positioning system without finding out required abnormal operation request links in a large number of requests.

Continuing with the description below of an exemplary architecture of the system detection device 455 implemented as a software module provided by embodiments of the present application, in some embodiments, as shown in fig. 11, the software modules stored in the system detection device 455 of the memory may include: the acquisition module 4551 is configured to perform network analysis on the call system to be detected, and acquire an abnormal operation request sent by the client and having failed in response when the obtained network analysis result indicates that the network is not abnormal; a routing module 4552 configured to route the abnormal operation request to an idle node device; and the determining module 4553 is configured to obtain operation response data sent by the idle node device, and determine a response failure reason of the abnormal operation request according to the operation response data.

In some embodiments, the routing module 4552 is further to: analyzing the abnormal operation request, and determining whether the abnormal operation request carries identification information of the client according to an analysis result, wherein the identification information is used for identifying that the call system accessed by the client has no network abnormality; under the condition that the abnormal operation request carries the identification information, acquiring an idle node equipment identification from a preset node equipment identification list; and determining the idle node equipment according to the idle node equipment identifier, and routing the abnormal operation request to the idle node equipment.

In some embodiments, the acquisition module 4551 is further to: acquiring a preset resource positioning identifier and sending the resource positioning identifier to the client under the condition that the network analysis result shows that the network is not abnormal; under the condition that the client side is detected to execute interactive operation on the resource positioning identification, setting the identification information of the client side, and sending the identification information and a system abnormal heavy operation request to the client side; and acquiring an abnormal operation request which is sent by the client and is generated after the response of the client to the system abnormal heavy operation request, wherein the abnormal operation request carries the identification information.

In some embodiments, the apparatus further comprises: the setting module is used for setting the expiration time for the resource positioning identifier; and if the expiration time is reached, the resource positioning identifier is adjusted from an effective state to a failure state, wherein if the resource positioning identifier is in the failure state, the target object cannot execute the interactive operation on the resource positioning identifier through the client.

In some embodiments, the operation response data includes a scatter diagram obtained after the idle node device responds to the abnormal operation request, the abnormal operation request includes a plurality of sub-operation requests, and the scatter diagram includes a plurality of scatter points, and each scatter point corresponds to one sub-operation request; the determining module 4553 is further configured to: based on the scatter diagram, acquiring a plurality of pieces of log information generated by the idle node equipment after responding to a sub-operation request of each scatter diagram; screening abnormal log information from the plurality of logs; and determining the response failure reason of the abnormal operation request based on the screened abnormal log information.

In some embodiments, the determining module 4553 is further to: acquiring attribute parameters in the abnormal log information; determining that the response failure of the abnormal operation request is caused by abnormal service codes under the condition that the abnormal log information is determined to be the log information related to the service codes based on the attribute parameters; and determining that the response failure cause of the abnormal operation request is abnormal of the client data under the condition that the abnormal log information is determined to be the log information related to the client data based on the attribute parameters.

In some embodiments, the apparatus further comprises: the updating module is used for determining a service source code corresponding to the abnormal operation request and acquiring an updating code corresponding to the service source code under the condition that the response failure cause of the abnormal operation request is abnormal; updating the service source code by adopting the updating code; and sending a data abnormality prompt message to the client under the condition that the response failure reason of the abnormal operation request is that the data of the client is abnormal.

It should be noted that, the description of the apparatus according to the embodiment of the present application is similar to the description of the embodiment of the method described above, and has similar beneficial effects as the embodiment of the method, so that a detailed description is omitted. For technical details not disclosed in the present apparatus embodiment, please refer to the description of the method embodiment of the present application for understanding.

Correspondingly, an embodiment of the present application provides an electronic device, fig. 12 is a schematic diagram of a composition structure of the electronic device provided by the embodiment of the present application, and as shown in fig. 12, the electronic device 1200 at least includes: a processor 1201, a communication interface 1202, and a storage medium 1203 configured to store executable instructions, wherein: the processor 1201 generally controls the overall operation of the electronic device 1200.

Communication interface 1202 may enable an electronic device to communicate with other terminals or servers over a network.

The storage medium 1203 is configured to store instructions and applications executable by the processor 1201, and may also cache data to be processed or processed by each module in the processor 1201 and the electronic device 1200, and may be implemented by a FLASH memory (FLASH) or a random access memory (Random Access Memory, RAM).

Embodiments of the present application provide a computer-readable storage medium having stored therein computer-executable instructions that, when executed by a processor, cause the processor to perform a system detection method provided by embodiments of the present application, for example, a system detection method as shown in fig. 5.

Embodiments of the present application provide a computer program product comprising computer-executable instructions stored in a computer-readable storage medium. The processor of the electronic device reads the computer executable instructions from the computer readable storage medium, and the processor executes the computer executable instructions, so that the electronic device executes the system detection method according to the embodiment of the application.

In some embodiments, the computer readable storage medium may be RAM, ROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; but may be a variety of devices including one or any combination of the above memories.

In some embodiments, computer-executable instructions may be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, in the form of programs, software modules, scripts, or code, and they may be deployed in any form, including as stand-alone programs or as modules, components, subroutines, or other units suitable for use in a computing environment.

As an example, computer-executable instructions may, but need not, correspond to files in a file system, may be stored in a portion of a file that holds other programs or data, such as in one or more scripts in a hypertext markup language (Hyper Text Markup Language, HTML) document, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code).

As an example, computer-executable instructions may be deployed to be executed on one electronic device or on multiple electronic devices located at one site or distributed across multiple sites and interconnected by a communication network.

The foregoing is merely exemplary embodiments of the present application and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and scope of the present application are included in the protection scope of the present application.

Claims

1. A system detection method, the method comprising:

Network analysis is carried out on the call system to be detected, and when the obtained network analysis result is that the network is not abnormal, an abnormal operation request which is sent by the client and has failed response is obtained;

routing the abnormal operation request to an idle node device;

And acquiring operation response data sent by the idle node equipment, and determining a response failure reason of the abnormal operation request according to the operation response data.

2. The method of claim 1, wherein the routing the abnormal operation request to an idle node device comprises:

Analyzing the abnormal operation request, and determining whether the abnormal operation request carries identification information of the client according to an analysis result, wherein the identification information is used for identifying that a call system accessed by the client is not abnormal in network;

under the condition that the abnormal operation request carries the identification information, acquiring an idle node equipment identification from a preset node equipment identification list;

and determining the idle node equipment according to the idle node equipment identifier, and routing the abnormal operation request to the idle node equipment.

3. The method according to claim 2, wherein, when the obtained network analysis result is that there is no abnormality in the network, the obtaining the abnormal operation request sent by the client and having failed in the response includes:

acquiring a preset resource positioning identifier and sending the resource positioning identifier to the client under the condition that the network analysis result shows that the network is not abnormal;

Under the condition that the client side is detected to execute interactive operation on the resource positioning identification, setting the identification information of the client side, and sending the identification information and a system abnormal heavy operation request to the client side;

and acquiring an abnormal operation request which is sent by the client and has failed in response, wherein the abnormal operation request is a request generated after the client responds to the system abnormal heavy operation request, and the abnormal operation request carries the identification information.

4. A method according to claim 3, characterized in that the method further comprises:

Setting an expiration time for the resource location identifier;

And if the expiration time is reached, the resource positioning identifier is adjusted from an effective state to a failure state, wherein if the resource positioning identifier is in the failure state, the target object cannot execute the interactive operation on the resource positioning identifier through the client.

5. The method according to any one of claims 1 to 4, wherein the operation response data includes a scatter plot generated by the idle node device in response to the abnormal operation request, the abnormal operation request including a plurality of sub-operation requests, the scatter plot including a plurality of scatter points, each scatter point corresponding to one sub-operation request;

the determining a response failure reason of the abnormal operation request according to the operation response data comprises the following steps:

based on the scatter diagram, acquiring a plurality of pieces of log information generated by the idle node equipment after responding to a sub-operation request of each scatter diagram;

Screening abnormal log information from the plurality of pieces of log information;

And determining the response failure reason of the abnormal operation request based on the screened abnormal log information.

6. The method of claim 5, wherein determining a response failure cause of the abnormal operation request based on the screened abnormal log information comprises:

acquiring attribute parameters in the abnormal log information;

Determining that the response failure of the abnormal operation request is caused by abnormal service codes under the condition that the abnormal log information is determined to be the log information related to the service codes based on the attribute parameters;

And determining that the response failure cause of the abnormal operation request is abnormal of the client data under the condition that the abnormal log information is determined to be the log information related to the client data based on the attribute parameters.

7. The method of claim 6, wherein the method further comprises:

Under the condition that the response failure of the abnormal operation request is caused by abnormal service codes, determining a service source code corresponding to the abnormal operation request, and acquiring an update code corresponding to the service source code; updating the service source code by adopting the updating code;

And sending a data abnormality prompt message to the client under the condition that the response failure reason of the abnormal operation request is that the data of the client is abnormal.

8. A system detection device, the device comprising:

The acquisition module is used for carrying out network analysis on the call system to be detected, and acquiring an abnormal operation request which is sent by the client and fails to respond when the obtained network analysis result is that the network is not abnormal;

The routing module is used for routing the abnormal operation request to the idle node equipment;

And the determining module is used for acquiring the operation response data sent by the idle node equipment and determining the response failure reason of the abnormal operation request according to the operation response data.

9. An electronic device, comprising:

A memory for storing computer executable instructions;

a processor for implementing the system detection method of any one of claims 1 to 7 when executing computer-executable instructions stored in the memory.

10. A computer readable storage medium, characterized in that computer executable instructions are stored, which when executed by a processor, implement the system detection method of any of claims 1 to 7.