CN108650123B - Fault information recording method, device, equipment and storage medium - Google Patents
Fault information recording method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN108650123B CN108650123B CN201810434527.3A CN201810434527A CN108650123B CN 108650123 B CN108650123 B CN 108650123B CN 201810434527 A CN201810434527 A CN 201810434527A CN 108650123 B CN108650123 B CN 108650123B
- Authority
- CN
- China
- Prior art keywords
- execution result
- current node
- recording
- node
- fault
- 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/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/0677—Localisation of faults
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a fault information recording method, which comprises the following steps: acquiring an execution result of a current operation node in the service system in the operation process of the service system; judging whether the execution result of the current node meets the corresponding tracking condition or not, wherein each node in the service system is provided with the corresponding tracking condition; and if the execution result of the current node meets the corresponding tracking condition, judging that the current node fails, and recording the execution result of the current node. The invention also discloses a fault information recording device, equipment and a computer readable storage medium. The invention can find the corresponding information in the request information record base when the system has a fault, thereby being capable of quickly positioning and facilitating problem analysis and statistics.
Description
Technical Field
The present invention relates to the field of communications security, and in particular, to a method, an apparatus, a device, and a storage medium for recording fault information.
Background
With the development of the internet, the information interaction amount among various service systems is increasing, and in order to ensure high availability and high performance, when a server product relates to specific applications, no matter in tracking test or actual application, performance data needs to be collected and analyzed, so that the operation condition of the whole system is monitored, and problems are found as soon as possible. Especially, when the application performance of the system is reduced and problems occur, performance data needs to be collected, so that the problems are found and solved.
At present, many systems can track and position the system through a working log, so that the working process of the system can be conveniently seen, and specific problem points are positioned when problems occur.
Disclosure of Invention
The invention mainly aims to provide a fault information recording method, a fault information recording device, fault information recording equipment and a fault information recording storage medium, and aims to solve the technical problem that the existing working log cannot meet the requirement of quickly positioning a fault node.
In order to achieve the above object, the present invention provides a fault information recording method, including the steps of:
acquiring an execution result of a current operation node in a service system in the operation process of the service system;
judging whether the execution result of the current node meets the corresponding tracking condition or not, wherein each node in the service system is provided with the corresponding tracking condition;
and if the execution result of the current node meets the corresponding tracking condition, judging that the current node has a fault, and recording the execution result of the current node.
Preferably, after determining that the current node fails and recording an execution result of the current node, the method further includes:
when a fault occurs, searching an execution result of the fault node according to a page or functional information of the current fault;
and carrying out fault location according to the searched execution result and a preset function comparison table. .
Preferably, after performing fault location according to the searched execution result and a preset function comparison table, the method further includes:
carrying out classified statistics according to fault results obtained by fault positioning;
and analyzing the results of the classification statistics in a preset time period to determine the occurrence frequency of the faults of each class, and sending corresponding prompt information to corresponding technicians when the occurrence frequency of the faults exceeds the preset frequency.
Preferably, the first and second electrodes are formed of a metal,
the obtaining of the execution result of the currently operating node in the service system in the operation process of the service system includes:
in the operation process of the service system, obtaining the execution results of current execution nodes in a service unit and a public operation unit, wherein the service system comprises the public unit and the service unit, the service unit receives a user operation instruction and calls the public unit to execute a corresponding function according to the user operation instruction, and corresponding tracking conditions are respectively set at each node in the public unit and the service unit.
Preferably, the determining whether the execution result of the current node meets the corresponding tracking condition includes:
step a, obtaining the switch state of the current node, judging whether the switch state is on, if the current switch is on, executing the following steps: recording the execution result of the current node, otherwise entering the step b;
b, judging whether to perform degradation processing according to the execution result of the current node, and if the system performs degradation processing, performing the following steps: recording the execution result of the current node, otherwise entering the step c;
step c, judging whether the user agent information in the user operation instruction is correct, if so, encrypting the operation instruction, and entering the step d, otherwise, executing the step: recording an execution result of the current node;
step d, judging whether to pass through IP blacklist control according to the user name information in the user operation instruction, entering step e if the user name information passes through the IP blacklist control, and otherwise executing the step: recording an execution result of the current node;
step e, judging whether the access frequency of the access equipment is greater than a preset frequency or not according to the access equipment in the user operation instruction, if the access frequency of the access equipment is greater than the preset frequency, recording the execution result of the current node, otherwise, executing the step: entering step f;
step f, judging whether the platform version passes according to the platform version of the user operation application, if so, entering step g, otherwise, executing the steps: recording an execution result of the current node;
step g, judging login state verification according to the login state in the user operation instruction, if the login state verification is passed, carrying out specific service, otherwise, executing the step: and recording the execution result of the current node.
Preferably, the step of determining whether to perform the degradation processing according to the execution result of the current node, and if the system performs the degradation processing, performing the following steps: recording the execution result of the current node, including:
and if the execution result of the current node indicates that the access amount exceeds the preset access amount, judging that the service system performs degradation processing, and recording the execution result of the current node.
Preferably, the step of determining whether to perform the degradation processing according to the execution result of the current node, and if the system performs the degradation processing, performing the steps of: recording the execution result of the current node comprises:
and if the execution result of the current node indicates no response, the response time exceeds the preset time, or the response result is unavailable, judging that the service system performs degradation processing, and recording the execution result of the current node.
Further, to achieve the above object, the present invention also provides a failure information recording apparatus comprising:
the acquisition module is used for acquiring the execution result of the current operation node in the service system in the operation process of the service system;
the judging module is used for judging whether the execution result of the current node meets the corresponding tracking condition or not, and each node in the service system is provided with the corresponding tracking condition;
and the recording module is used for judging that the current node has a fault if the execution result of the current node meets the corresponding tracking condition, and recording the execution result of the current node.
Further, to achieve the above object, the present invention also provides a failure information recording apparatus including: a memory, a processor and a fault information recording program stored on the memory and executable on the processor, the fault information recording program implementing the steps of the method as described above when executed by the processor.
Further, in order to achieve the above object, the present invention provides a computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a failure information recording program that, when executed by a processor, implements the steps of the failure information recording method as described above.
In the invention, in order to quickly locate, analyze and count problems by a method for recording fault information, a tracking node mode is set in each bottom layer node required in the operation process of a service system, a tracking condition is set in the current operation node in the service system, when the execution result meets the tracking condition, the execution of the current operation node is failed, the tracking information is correspondingly recorded at the moment, and each piece of tracking information is associated with the corresponding node. Therefore, in the using process of a user, if a fault occurs, the positioning can be quickly carried out according to the recorded execution result.
Drawings
Fig. 1 is a schematic terminal structure diagram of a hardware operating environment of a fault information recording device according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a fault information recording method according to a first embodiment of the present invention;
FIG. 3 is a flowchart illustrating a fault information recording method according to a second embodiment of the present invention;
fig. 4 is a flowchart illustrating a fault information recording method according to a third embodiment of the present invention.
The implementation, functional features and advantages of the present invention will be further described with reference to the accompanying drawings.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
As shown in fig. 1, fig. 1 is a schematic structural diagram of a hardware operating environment of a fault information recording apparatus according to an embodiment of the present invention.
The fault information recording device of the embodiment of the invention can be a PC host, a server and other devices, and can also be other types of electronic terminal devices.
As shown in fig. 1, the fault information recording apparatus may include: a processor 1001, such as a CPU, a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., a WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a memory device separate from the processor 1001 described above.
Those skilled in the art will appreciate that the hardware configuration of the fault information recording device shown in fig. 1 does not constitute a limitation of the fault information recording device, and may include more or less components than those shown, or combine some components, or a different arrangement of components.
As shown in fig. 1, a memory 1005, which is a kind of computer-readable storage medium, may include therein an operating system, a network communication module, a user interface module, and a failure information recording program. The operating system is a program for managing and controlling the fault information recording equipment and software resources, and supports the operation of the network communication module, the user interface module, the fault information recording program and other programs or software; the network communication module is used for managing and controlling the network interface 1002; the user interface module is used to manage and control the user interface 1003.
In the hardware structure of the fault information recording device shown in fig. 1, the network interface 1004 is mainly used for connecting to a system background and performing data communication with the system background; the user interface 1003 is mainly used for connecting a client (user side) and performing data communication with the client; the failure information recording apparatus calls the failure information recording program stored in the memory 1005 by the processor 1001, and performs the following operations:
in the operation process of the service system, acquiring an execution result of a current operation node in the service system;
judging whether the execution result of the current node meets the corresponding tracking condition or not, wherein each node in the service system is provided with the corresponding tracking condition;
and if the execution result of the current node meets the corresponding tracking condition, judging that the current node fails, and recording the execution result of the current node.
Further, the processor 1001 may call the failure information recording program stored in the memory 1005, and also perform the following operations:
searching an execution result of a fault node according to a page or functional information of the current fault;
and carrying out fault location according to the searched execution result and a preset function comparison table.
Further, the processor 1001 may call the failure information recording program stored in the memory 1005, and also perform the following operations:
carrying out classified statistics according to fault results obtained by fault positioning;
and analyzing the results of the classification statistics in a preset time period to determine the occurrence frequency of the faults of each class, and sending corresponding prompt information to corresponding technicians when the occurrence frequency of the faults exceeds the preset frequency.
Further, the processor 1001 may call the failure information recording program stored in the memory 1005, and also perform the following operations:
in the operation process of the service system, obtaining the execution results of current execution nodes in a service unit and a public operation unit, wherein the service system comprises the public unit and the service unit, the service unit receives a user operation instruction and calls the public unit to execute a corresponding function according to the user operation instruction, and corresponding tracking conditions are respectively set at each node in the public unit and the service unit.
Further, the processor 1001 may call the failure information recording program stored in the memory 1005, and also perform the following operations:
step a, obtaining the switch state of the current node, judging whether the switch state is off, if the current switch is off, executing the following steps: recording the execution result of the current node, otherwise entering the step b;
b, judging whether to perform degradation processing according to the execution result of the current node, and if the system performs degradation processing, performing the following steps: recording the execution result of the current node, otherwise entering the step c;
step c, judging whether the user agent information in the user operation instruction is correct, if so, encrypting the operation instruction, and entering the step d, otherwise, executing the step: recording an execution result of the current node;
step d, judging whether to pass through IP blacklist control according to the user name information in the user operation instruction, entering step e if the user name information passes through the IP blacklist control, and otherwise executing the step: recording an execution result of the current node;
step e, judging whether the access frequency of the access equipment is greater than a preset frequency or not according to the access equipment in the user operation instruction, if the access frequency of the access equipment is greater than the preset frequency, recording the execution result of the current node, otherwise, executing the step: entering step f;
step f, judging whether the platform version passes according to the platform version of the user operation application, if so, entering step g, otherwise, executing the steps: recording an execution result of the current node;
step g, judging login state verification according to the login state in the user operation instruction, if the login state verification is passed, carrying out specific service, otherwise, executing the step: and recording the execution result of the current node.
Further, the processor 1001 may call the failure information recording program stored in the memory 1005, and also perform the following operations:
and if the execution result of the current node indicates that the access amount exceeds the preset access amount, judging that the service system performs degradation processing, and recording the execution result of the current node.
Further, the processor 1001 may call the failure information recording program stored in the memory 1005, and also perform the following operations:
and if the execution result of the current node indicates no response, the response time exceeds the preset time, or the response result is unavailable, judging that the service system performs degradation processing, and recording the execution result of the current node.
Based on the above hardware structure, various embodiments of the fault information recording method of the present invention are proposed.
Referring to fig. 2, fig. 2 is a flowchart illustrating a fault information recording method according to a first embodiment of the present invention.
In this embodiment, the fault information recording method includes the following steps:
step S10, in the operation process of the service system, obtaining an execution result of the currently operating node in the service system.
In an embodiment of the present invention, the fault information recording method may be applied to a plurality of business systems for financial, medical, health, entertainment, social, e-commerce and the like that provide online products or services and the like, and the business processing system may include: a front end and a server. The invention can be applied to a front end and/or a server, as an implementation mode: the method is applied to the front end and the server, when business occurs, the front end and the server can execute corresponding functional nodes, for example, the front end provides operation for a user, verifies user information, carries out data corresponding to a communication request with the server after the verification is passed, and simultaneously displays the content fed back by the server to equipment of the user; the server is used for storing data, receiving and processing the operation request of the front-end party, executing the corresponding function and simultaneously feeding back the corresponding execution data to the front-end. As another example: the invention may be applied in a front-end or a server, where the difference with the previous embodiment is that all functions are performed in the front-end or the server, such as the authentication function of the login information in the front-end/the server.
In order to record corresponding information and quickly position when a system fails or has problems, the invention pre-embeds corresponding tracking conditions in each functional node in a service system, wherein the tracking conditions are corresponding tracking conditions when the system fails/has problems.
The present invention will be specifically described by taking a fault information recording method of a terminal service function in the field of financial products or service provision as an example and combining a service system, and a front end in the present invention may be a device as shown in fig. 1.
The operation request may be: a user sends a request operation instruction; the related information at least comprises: address information of a function or service of which operation request is triggered, such as URL (uniform resource locator) information.
In the operation of the service system, as an embodiment, a user may trigger a service request through a front-end device, for example, access a home e credit interface, the front-end receives the service request of the user, and sends the service request to a server, when receiving the service request, the server will sequentially execute corresponding functional nodes, and when executing the corresponding functional nodes each time, obtain an execution result of a currently executed node.
The sequentially executed functional nodes may include, but are not limited to: the method comprises the following steps that whether the on-off state, the degradation control and the verification pass or not is judged, wherein the on-off state specifically refers to that corresponding on-off information is searched from a database through a uniform resource identifier (URL) according to the content of a current operation page of a user; system degradation refers specifically to one way to ensure that the current service is available; whether the verification is passed means whether the user name, system version, platform version and the like used by the user in the service operation process are the same as those of the server in the service system.
Step S20, judging whether the execution result of the current node meets the corresponding tracking condition;
in this embodiment, during the operation of each functional node, a corresponding execution result, such as an execution log, is generated, during the execution of the service system, according to the execution result of the current node obtained in step S10, the tracking condition of the node is searched in all preset tracking conditions, and a judgment is made according to the tracking condition of the current node and the execution result of the current node, so as to judge whether the execution result meets the corresponding tracking condition.
Specifically, the process of searching for the tracking condition of the node in all the preset tracking conditions may be to set an identifier for each functional node in advance, associate the corresponding tracking condition with the identifier, and search for the tracking condition in all the preset tracking conditions according to the identifier of the currently executed node in the service execution process. Of course, the execution result and all the tracking conditions may be directly searched.
Step S30, if the execution result of the current node meets the corresponding tracking condition, determining that the current node has a fault, and recording the execution result of the current node.
In the operation process of the service flow, the current execution node can execute normally, and according to the judgment result obtained in the step S20, if the judgment result is that the current execution node is normal, the next step can be performed without recording the execution result; and if the judgment result is that the current node has a fault/problem, recording the execution result.
Further, in this embodiment, an information record library may be provided, and the recorded execution result may be stored.
In the invention, in order to quickly locate, analyze and count problems by a method for recording fault information, a tracking node mode is set in each bottom layer node required in the operation process of a service system, a tracking condition is set in the current operation node in the service system, when the execution result meets the tracking condition, the tracking information is recorded correspondingly, for example, when the step execution of a certain node has an error, the tracking information is correspondingly recorded, and each tracking information is associated with the corresponding node. Therefore, in the using process of a user, if a fault occurs, the positioning can be quickly carried out according to the recorded execution result.
Referring to fig. 3, fig. 3 is a flowchart illustrating a fault information recording method according to a second embodiment of the present invention.
Based on the first embodiment of the fault information recording method of the present invention, the fault information recording method further includes:
step S40, searching the execution result of the fault node according to the current fault page or function information;
and step S50, fault location is carried out according to the searched execution result and a preset function comparison table.
In this embodiment, in order to perform positioning quickly, a function comparison table is preset, where the function comparison table includes an execution result generated when each function node may have a fault/problem during execution.
In this embodiment, when an execution node fails, the time when the failure occurs is recorded, in this embodiment, according to the time when the failure occurs, the recorded execution information may be searched for an execution result that is the same as or closest to the time when the failure occurs, where the execution result also includes the recorded time, and then the searched execution result is matched with a preset function comparison table, so as to perform failure location.
Of course, when the executing node fails, the time of the failure may not be recorded, and when the failure occurs, the latest recorded executing result is searched in the recorded executing information as the executing result of the current failure, and then the searched executing result is matched with the preset function comparison table, so as to perform the failure location.
Further, the fault information recording method further includes:
step S60, according to the fault result obtained by fault positioning, carrying out classification statistics;
and step S70, analyzing the results of the classification statistics in a preset time period to determine the occurrence frequency of each class of faults, and sending corresponding prompt information to corresponding technicians when the occurrence frequency of the faults exceeds the preset frequency.
After the fault location, determining a fault result corresponding to each recorded information according to the fault location, and performing classification statistics according to a preset statistical strategy, for example, performing classification statistics of fault types according to a numerical value of a fault result occurring in a week, where the fault types may include but are not limited to: machine faults, software faults, and system faults, wherein software faults may include, but are not limited to, system logic errors, verification errors, and the like. The statistical strategy can be set by the user according to the requirement.
Furthermore, when the system fails, some problems are accidental events, some problems are caused by technical imperfection, in order to accurately know the running state of the system, after classification statistics is completed, classification statistical results are analyzed, the frequency of occurrence of various faults is determined, and when faults with the frequency exceeding the preset frequency occur within the preset time, prompt information is generated and sent to corresponding technicians, so that the technicians can improve the fault. Such as presetting the number of failed events to be greater than or equal to 20 times. When the occurrence frequency of the fault exceeds the preset frequency, the system sends a prompt message that the current page cannot be displayed, and prompts the corresponding technician of the current position information of the fault to carry out fault repair.
The fault positioning speed reflects the high efficiency of system service and the good service state of the system, and has very important significance for user use and systems.
Referring to fig. 4, fig. 4 is a flowchart illustrating a fault information recording method according to a third embodiment of the present invention.
Based on the first embodiment of the method for recording fault information in the present invention, in this embodiment, in order to facilitate collecting fault information generated by a system and reduce repeated development of a plurality of functional systems having the same basis, in this embodiment, the same basic function is set as a common unit, and when a plurality of service systems run, codes of the functional units can be copied for use, or a group in which the common unit is located is called for basic verification, specifically, the service system includes: the service unit is used for receiving a user operation instruction and processing according to the user operation instruction so as to call the public unit to execute a corresponding function, and each node in the public unit and the service unit is respectively provided with a corresponding tracking condition;
accordingly, step S10 is replaced by: step S11, in the operation process of the service system, obtaining the execution result of the current execution node in the service unit and the common operation unit.
In this embodiment, a corresponding tracing condition is pre-embedded in each functional node in the service unit and the common operation unit, where the functional points of the common operation unit may include but are not limited to: obtaining the switch state, controlling whether the system is degraded or not, controlling whether the user agent information is correct or not, preventing hacker attack, controlling an IP blacklist, controlling the equipment access frequency, verifying a platform version equipment identifier and the like, verifying a login state and the like.
Specifically, the determining whether the execution result of the current node meets the corresponding tracking condition includes: step a, obtaining the switch state of the current node, judging whether the switch state is off, if the current switch is off, executing the following steps: recording the execution result of the current node, otherwise entering the step b;
when a user request is received, determining an object operated by the user, such as an access i-credit webpage, according to the user request, and after the user operation object is determined, obtaining a switch state corresponding to the object, in this embodiment, uniformly storing switch information of all objects in a database for uniform management, so as to avoid a situation that in the prior art, when the object is given with a switch function in a development process, a function code needs to be written separately, when the switch state corresponding to the object is obtained, searching for corresponding switch information from the database through a uniform resource identifier (URL), if a corresponding function switch is off, judging that an execution result of a current node meets a preset condition, and if the execution result is an access failure, the execution step records an execution result of the current node; and if the corresponding function switch is on, judging that the execution result of the current node does not accord with the preset condition, and entering the step b.
B, judging whether to perform degradation processing according to the execution result of the current node, and if the system performs degradation processing, performing the following steps: recording the execution result of the current node, otherwise entering the step c;
after the step a, whether to perform degradation processing is determined according to an execution result of the current node, where system degradation is a means for ensuring that the current service is available, for example, when a number of requests for a service at the same time is large, a problem occurs in the system or the service becomes slow, that is, if an access concurrency exceeds a threshold, the system does not respond to a user request or responds very slowly, for an actual demand, it is often necessary to perform degradation processing on traffic exceeding the threshold by adopting a plurality of different manners of determining that the threshold is exceeded and limiting the flow according to different service interface requests, so that the service remains available. If the execution result is detected to indicate that the system performs degradation processing, executing the following steps: and c, recording the execution result of the current node, otherwise, entering the step c.
Specifically, step b may include:
and if the execution result of the current node indicates that the access quantity exceeds the preset access quantity, judging to perform degradation processing on the search service system, and recording the execution result of the current node.
In this step, the preset access amount is specifically used for reflecting the number of times that the user requests access, so that whether the system accessed by the user is maliciously attacked or not and the network is busy can be conveniently known.
If the execution result of the current node indicates that the current access amount exceeds a preset access threshold, alarm information can be sent to a system management end, degradation processing is carried out, the execution result of the current node is recorded, and if the execution result does not exceed the preset access amount, the following steps are executed: the returned results are available.
Further step b may further comprise:
and if the execution result of the current node indicates no response, the response time exceeds the preset time, or the response result is unavailable, judging that the service system performs degradation processing, and recording the execution result of the current node.
Specifically, the response time in the execution result is specifically used for reflecting the efficiency of the system for processing the fault, so that the efficiency of the system for processing the fault is optimized conveniently. Judging through the execution result of the execution node, if the execution result of the current node indicates no response, the response time exceeds the preset time, or the response result is unavailable, which indicates that the system processing efficiency is low, and in order to ensure that the service is available, the system can perform corresponding degradation processing; and if the preset response time is not exceeded, executing according to a normal flow.
After step b, if the execution result indicates that the system performs the degradation process, the process may also proceed to step c.
Step c, judging whether the user agent information in the user operation instruction is correct, if so, encrypting the operation instruction, and entering the step d, otherwise, executing the step: recording an execution result of the current node;
after the step b, whether user agent (user agent) information in the user operation instruction is correct is further judged, wherein the user agent information is a special character string head and is used for identifying an operating system and version, a CPU (Central processing Unit) type, a browser and version, a browser rendering engine, a browser language, a browser plug-in and the like used by a client. If the user agent information in the user operation instruction is correct, encrypting the operation instruction to prevent the information from being intercepted and stolen, and entering the step d, if the user agent information in the user operation instruction is incorrect, executing the steps of: and recording the execution result of the current node, and recording the current execution result.
Step d, judging whether to pass through IP blacklist control according to the user name information in the user operation instruction, entering step e if the IP blacklist control passes, and otherwise executing the step: recording an execution result of the current node;
after the step c, the user is indicated to operate on regular equipment, however, illegal personnel may operate on the regular equipment, so that whether the user name information is controlled through an IP blacklist is judged according to the user operation instruction, specifically, an IP blacklist is prestored according to historical data, the IP blacklist can be added in real time according to a blacklist rule, if the user name information in the user operation instruction is judged to be controlled through the IP blacklist, the step e is entered, otherwise, the step is executed: and recording the execution result of the current node.
Step e, judging whether the access frequency of the access equipment is greater than a preset frequency or not according to the access equipment in the user operation instruction, if the access frequency of the access equipment is greater than the preset frequency, recording the execution result of the current node, otherwise, executing the step: entering step f;
in order to avoid using different user names in the same device to perform operations, thereby affecting system operation and avoiding potential hazards, in this embodiment, the corresponding access device is further determined according to a user operation instruction, whether the access frequency of the same access device is greater than a preset frequency is determined, if the device access frequency is greater than the preset frequency, it is indicated that the access frequency of the same device is too high, at this time, an execution result of a current node is recorded, otherwise, the steps are executed: entering step f;
f, judging whether the platform version passes according to the platform version of the user operation application, if so, entering the step g, otherwise, executing the step: recording an execution result of the current node;
after step e, determining whether the platform version of the user operation application is consistent with that of the server according to the user operation instruction, namely verifying whether the platform version of the user operation application is the latest version, if so, entering step g, otherwise, executing the following steps: recording an execution result of the current node;
step g, judging login state verification according to the login state in the user operation instruction, if the login state verification is passed, carrying out specific service, otherwise, executing the step: and recording the execution result of the current node.
If the platform version equipment identification and the like pass the verification, performing login state verification; and if the verification of the login state is passed, performing specific business, such as accessing a loan interface.
Further, an information recording library is provided in the present embodiment, and is used for recording the execution result of the node.
The function points of the service unit may include, but are not limited to: and accessing a webpage interface, recording webpage execution steps, judging whether the execution flow is normal, and the like.
Specifically, for example, when a user requests to access a loan interface, a service unit skips to the loan interface according to an instruction information page sent by the user when receiving a request access instruction sent by the user; recording loan execution steps, namely recording steps executed during user operation according to the service required to be completed by the user, and prompting the user to perform corresponding operation; in the operation process, acquiring an execution result of an execution node according to the execution node corresponding to the user operation instruction, and prompting a user to perform the operation of the next step if the execution result shows that the current flow is not abnormal; if the current execution result shows that the execution result is abnormal, recording abnormal information into an information recording library; when the user processes the service, the flow is abnormal, the user is prompted that the service is successfully transacted, and the information of successful execution is stored in the information recording library; when the user successfully processes the service, the system feeds back the node code number successfully processed to the user through the operation interface, and stores the node code number successfully processed to the information record base.
In this embodiment, in order to quickly locate, analyze, and count a problem by a method of recording fault information, a tracking node mode is set in each bottom node required in the operation process of the service system, and a tracking node is set in a currently operating node in the service system, so that when an error occurs in the step execution of each node, tracking information is correspondingly recorded, and each tracking information is associated with the corresponding node. Therefore, in the using process of a user, if a fault occurs, the information record base can be read, and the corresponding node is found from the tracking node function comparison table according to the tracking node function comparison table associated with the node with the fault in the user operation page, so that the problem is quickly positioned and solved.
In addition, an embodiment of the present invention further provides a fault information recording apparatus, including:
an obtaining module 100, configured to receive an execution request of a user operation in an operation process of the service system, and obtain a current execution result;
a judging module 200, configured to judge whether an execution result of a current node meets a corresponding tracking condition, where each node in the service system is provided with a corresponding tracking condition;
the recording module 300 is configured to determine that the current node fails if the execution result of the current node meets the corresponding tracking condition, and record the execution result of the current node.
The obtaining module 100, the determining module 200, and the recording module 300 are virtual modules obtained by the processor 1001 in fig. 1 reading corresponding codes in the fault information recording program in the memory, and the functions implemented by each module during execution may refer to each embodiment of the fault information recording method of the present invention, which is not described herein again.
In addition, the embodiment of the invention also provides a computer readable storage medium.
The computer-readable storage medium of the present invention stores thereon a failure information recording program that realizes the steps of the failure information recording method as described above when executed by a processor.
The method implemented when the fault information recording program running on the processor is executed may refer to each embodiment of the fault information recording method of the present invention, and is not described herein again.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system 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 system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention, and all equivalent structures or equivalent processes performed by the present invention or directly or indirectly applied to other related technical fields are also included in the scope of the present invention.
Claims (9)
1. A fault information recording method, comprising:
in the operation process of a service system, acquiring an execution result of a current operation node in the service system;
judging whether the execution result of the current node meets the corresponding tracking condition or not, wherein each node in the service system is provided with the corresponding tracking condition;
if the execution result of the current node meets the corresponding tracking condition, judging that the current node fails, and recording the execution result of the current node;
the judging whether the execution result of the current node meets the corresponding tracking condition includes:
step a, obtaining the switch state of the current node, judging whether the switch state is off, if the current switch is off, executing the following steps: recording the execution result of the current node, otherwise entering the step b;
b, judging whether to perform degradation processing according to the execution result of the current node, and if the system performs degradation processing, performing the following steps: recording the execution result of the current node, otherwise entering the step c;
step c, judging whether the user agent information in the user operation instruction is correct, if so, encrypting the operation instruction, and entering the step d, otherwise, executing the step: recording an execution result of the current node;
step d, judging whether to pass through IP blacklist control according to the user name information in the user operation instruction, entering step e if the user name information passes through the IP blacklist control, and otherwise executing the step: recording an execution result of the current node;
step e, judging whether the access frequency of the access equipment is greater than a preset frequency or not according to the access equipment in the user operation instruction, if the access frequency of the access equipment is greater than the preset frequency, recording the execution result of the current node, otherwise, executing the step: entering step f;
step f, judging whether the platform version passes according to the platform version of the user operation application, if so, entering step g, otherwise, executing the steps: recording an execution result of the current node;
step g, judging login state verification according to the login state in the user operation instruction, if the login state verification is passed, carrying out specific service, otherwise, executing the step: and recording the execution result of the current node.
2. The fault information recording method according to claim 1, wherein after determining that the current node has a fault and recording the execution result of the current node, further comprising:
searching an execution result of a fault node according to a page or functional information of the current fault;
and carrying out fault location according to the searched execution result and a preset function comparison table.
3. The method according to claim 2, wherein after performing fault location according to the searched execution result and a preset function comparison table, the method further comprises:
carrying out classified statistics according to fault results obtained by fault positioning;
and analyzing the results of the classification statistics in a preset time period to determine the occurrence frequency of the faults of each class, and sending corresponding prompt information to corresponding technicians when the occurrence frequency of the faults exceeds the preset frequency.
4. The method for recording fault information according to claim 1, wherein the obtaining, during the operation of the service system, the execution result of the currently operating node in the service system includes:
in the operation process of the service system, obtaining the execution results of current execution nodes in a service unit and a public operation unit, wherein the service system comprises the public operation unit and the service unit, the service unit receives a user operation instruction and calls the public operation unit to execute a corresponding function according to the user operation instruction, each node in the public operation unit and the service unit is respectively provided with a corresponding tracking condition, and the function of the public operation unit comprises: acquiring a switch state, controlling whether system degradation is performed or not, controlling whether user agent information is correct or not, preventing hacker attack, controlling an IP blacklist, controlling equipment access frequency, verifying a platform version and equipment identification, and verifying a login state.
5. The method for recording fault information according to claim 1, wherein the step of determining whether to perform the degradation processing according to the execution result of the current node, and if the system performs the degradation processing, the step of: recording the execution result of the current node, including:
and if the execution result of the current node indicates that the access amount exceeds the preset access amount, judging that the service system performs degradation processing, and recording the execution result of the current node.
6. The method for recording fault information according to claim 1, wherein the determining whether to perform degradation processing is performed according to the execution result of the current node, and if the system performs degradation, performing the steps of: recording the execution result of the current node comprises:
and if the execution result of the current node indicates no response, the response time exceeds the preset time, or the response result is unavailable, judging that the service system performs degradation processing, and recording the execution result of the current node.
7. A fault information recording apparatus, wherein the fault information recording apparatus is applied to a service system in which each node is provided with a corresponding tracking condition, the fault information recording apparatus comprising:
the acquisition module is used for acquiring the execution result of the current operation node in the service system in the operation process of the service system;
the judging module is used for judging whether the execution result of the current node meets the corresponding tracking condition or not, and each node in the service system is provided with the corresponding tracking condition;
the recording module is used for judging that the current node has a fault if the execution result of the current node meets the corresponding tracking condition and recording the execution result of the current node;
wherein, the judging whether the execution result of the current node meets the corresponding tracking condition includes:
step a, obtaining the switch state of the current node, judging whether the switch state is off, if the current switch is off, executing the following steps: recording the execution result of the current node, otherwise entering the step b;
b, judging whether to perform degradation processing according to the execution result of the current node, and if the system performs degradation processing, performing the following steps: recording the execution result of the current node, otherwise entering the step c;
step c, judging whether the user agent information in the user operation instruction is correct, if so, encrypting the operation instruction, and entering the step d, otherwise, executing the step: recording an execution result of the current node;
step d, judging whether to pass through IP blacklist control according to the user name information in the user operation instruction, entering step e if the user name information passes through the IP blacklist control, and otherwise executing the step: recording an execution result of the current node;
step e, judging whether the access frequency of the access equipment is greater than a preset frequency or not according to the access equipment in the user operation instruction, if the access frequency of the access equipment is greater than the preset frequency, recording the execution result of the current node, otherwise, executing the step: entering step f;
step f, judging whether the platform version passes according to the platform version of the user operation application, if so, entering step g, otherwise, executing the steps: recording an execution result of the current node;
step g, judging login state verification according to the login state in the user operation instruction, if the login state verification is passed, carrying out specific service, otherwise, executing the step: and recording the execution result of the current node.
8. A failure information recording apparatus characterized by comprising: memory, a processor and a fault information recording program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the method according to any of claims 1 to 6.
9. A computer-readable storage medium, characterized in that a failure information recording program is stored thereon, which when executed by a processor implements the steps of the failure information recording method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810434527.3A CN108650123B (en) | 2018-05-08 | 2018-05-08 | Fault information recording method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810434527.3A CN108650123B (en) | 2018-05-08 | 2018-05-08 | Fault information recording method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108650123A CN108650123A (en) | 2018-10-12 |
| CN108650123B true CN108650123B (en) | 2022-09-06 |
Family
ID=63749600
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810434527.3A Active CN108650123B (en) | 2018-05-08 | 2018-05-08 | Fault information recording method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108650123B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110609538B (en) * | 2019-09-30 | 2021-04-16 | 潍柴动力股份有限公司 | Fault processing method, device, equipment and storage medium |
| CN111124771B (en) * | 2019-11-13 | 2023-01-06 | 苏州浪潮智能科技有限公司 | Method, equipment and medium for positioning fault |
| CN113988789A (en) * | 2021-10-25 | 2022-01-28 | 重庆允成互联网科技有限公司 | Method, system, equipment and storage medium for automatically screening data based on process |
| CN114116285B (en) * | 2021-11-22 | 2025-02-18 | 深圳市杉岩数据技术有限公司 | A method, device and medium for processing file gateway failure switching |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104657637A (en) * | 2015-01-29 | 2015-05-27 | 深信服网络科技（深圳）有限公司 | Document information embedding and tracking methods and systems and proxy service equipment |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4920391B2 (en) * | 2006-01-06 | 2012-04-18 | 株式会社日立製作所 | Computer system management method, management server, computer system and program |
| KR100840129B1 (en) * | 2006-11-16 | 2008-06-20 | 삼성에스디에스 주식회사 | Performance failure management system and its method using statistical analysis |
| GB2487355B (en) * | 2011-01-13 | 2020-03-25 | Advanced Risc Mach Ltd | Processing apparatus, trace unit and diagnostic apparatus |
| US9336073B1 (en) * | 2014-02-27 | 2016-05-10 | Seagate Technology Llc | Write fault modulation |
| CN107102795A (en) * | 2017-05-31 | 2017-08-29 | 努比亚技术有限公司 | A kind of log recording method, mobile terminal and computer-readable recording medium |
| CN107678933A (en) * | 2017-09-28 | 2018-02-09 | 中国平安人寿保险股份有限公司 | Daily record generation management method, device, equipment and computer-readable recording medium |
| CN107769963B (en) * | 2017-09-29 | 2019-01-25 | 贵州白山云科技股份有限公司 | A kind of content distributing network Fault Locating Method and device |
| CN107908695A (en) * | 2017-10-31 | 2018-04-13 | 平安普惠企业管理有限公司 | Operation system operation method, device, system and readable storage medium storing program for executing |
-
2018
- 2018-05-08 CN CN201810434527.3A patent/CN108650123B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104657637A (en) * | 2015-01-29 | 2015-05-27 | 深信服网络科技（深圳）有限公司 | Document information embedding and tracking methods and systems and proxy service equipment |
Non-Patent Citations (1)
| Title |
|---|
| 匿名即时通信监控技术研究;赵煜等;《计算机应用研究》;20080615(第06期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108650123A (en) | 2018-10-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113489713B (en) | Network attack detection method, device, equipment and storage medium | |
| CN108650123B (en) | Fault information recording method, device, equipment and storage medium | |
| CN107451040B (en) | Method and device for positioning fault reason and computer readable storage medium | |
| CN110267215B (en) | Data detection method, equipment and storage medium | |
| CN110650126A (en) | Method and device for preventing website traffic attack, intelligent terminal and storage medium | |
| CN109684863B (en) | Data leakage prevention method, device, equipment and storage medium | |
| CN108509322B (en) | Method, electronic device, and computer-readable storage medium for avoiding excessive return visits | |
| CN117272308A (en) | Software security test method, device, equipment, storage medium and program product | |
| CN111371645B (en) | Method, system, computer equipment and storage medium for testing service connectivity | |
| CN110597662B (en) | Backup data automatic verification method and device, user equipment and storage medium | |
| CN115145816A (en) | Test method, device, storage medium and equipment for data reporting | |
| CN111756594B (en) | Control method of pressure test, computer device and computer readable storage medium | |
| CN113285915A (en) | Registration management method and device and private cloud control server | |
| CN112817816A (en) | Embedded point processing method and device, computer equipment and storage medium | |
| CN110162982B (en) | Method and device for detecting illegal rights, storage medium and electronic equipment | |
| CN113452533A (en) | Charging self-inspection and self-healing method and device, computer equipment and storage medium | |
| CN111651356A (en) | Application program testing method, device and system | |
| CN117009202A (en) | Buried data processing method, buried data processing device, buried data processing equipment and storage medium | |
| CN110019262B (en) | Data updating method and device | |
| CN108257011B (en) | Drop list processing method and device | |
| CN111737129B (en) | Service control method, device, computer readable medium and electronic equipment | |
| CN111241547A (en) | Detection method, device and system for unauthorized vulnerability | |
| CN110362464B (en) | Software analysis method and equipment | |
| CN113923190A (en) | Method and device for identifying equipment identification jump, server and storage medium | |
| CN113778800A (en) | Error reporting information processing method, device, system, equipment and storage medium |
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 |