CN112395126A - Fault log processing method and device, electronic equipment and storage medium - Google Patents
Fault log processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112395126A CN112395126A CN202011308953.6A CN202011308953A CN112395126A CN 112395126 A CN112395126 A CN 112395126A CN 202011308953 A CN202011308953 A CN 202011308953A CN 112395126 A CN112395126 A CN 112395126A
- Authority
- CN
- China
- Prior art keywords
- fault
- logs
- machine
- information
- module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 23
- 238000000034 method Methods 0.000 claims abstract description 22
- 238000012545 processing Methods 0.000 claims abstract description 20
- 230000004044 response Effects 0.000 claims abstract description 8
- 230000015654 memory Effects 0.000 claims description 20
- 238000012163 sequencing technique Methods 0.000 claims description 4
- 238000012423 maintenance Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 238000004590 computer program Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 230000004807 localization Effects 0.000 description 2
- 238000012827 research and development Methods 0.000 description 2
- 238000012216 screening Methods 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3452—Performance evaluation by statistical analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Computer Hardware Design (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Probability & Statistics with Applications (AREA)
- Evolutionary Biology (AREA)
- Bioinformatics & Computational Biology (AREA)
- Life Sciences & Earth Sciences (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a fault log processing method, a fault log processing device, electronic equipment and a storage medium, and relates to the technical field of network fault processing, wherein the method comprises the following steps: sending a fault log acquisition request to a client of a fault machine; receiving N groups of fault logs of the fault machine sent by the client in response to the fault log acquisition request, wherein the N groups of fault logs comprise all logs generated by calling N requests by each module of the fault machine, and N is an integer greater than or equal to 1; and determining fault source module information and corresponding fault type information of the fault machine according to the N groups of fault logs. The fault source module of the fault machine can be determined efficiently, and therefore fault positioning is achieved efficiently.
Description
Technical Field
The present application relates to the field of network technologies, in particular to a network fault processing technology, and in particular, to a fault log processing method and apparatus, an electronic device, and a storage medium.
Background
In order to maintain system stability, fault logs need to be collected and analyzed to troubleshoot system faults. Along with the increase of the service complexity, the complexity of modules in the system can be gradually increased, the number of the modules can be increased, and different modules can output different logs. In conventional fault log collection, logs of each module are usually collected separately, which makes fault location difficult.
Disclosure of Invention
The application provides a fault log processing method and device, electronic equipment and a storage medium.
According to a first aspect, the present application provides a fault log processing method, including:
sending a fault log acquisition request to a client of a fault machine;
receiving N groups of fault logs of the fault machine sent by the client in response to the fault log acquisition request, wherein the N groups of fault logs comprise all logs generated by calling N requests by each module of the fault machine, and N is an integer greater than or equal to 1;
and determining fault source module information and corresponding fault type information of the fault machine according to the N groups of fault logs.
According to a second aspect, the present application provides a fault log processing apparatus, comprising:
the sending module is used for sending a fault log collecting request to a client of a fault machine;
a receiving module, configured to receive N groups of fault logs of the fault machine sent by the client in response to the fault log collection request, where the N groups of fault logs include all logs generated by invoking N requests by each module of the fault machine, and N is an integer greater than or equal to 1;
and the determining module is used for determining the fault source module information and the corresponding fault type information of the fault machine according to the N groups of fault logs.
According to a third aspect, the present application provides an electronic device comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform any one of the methods of the first aspect.
According to a fourth aspect, the present application provides a non-transitory computer readable storage medium having stored thereon computer instructions for causing a computer to perform any of the methods of the first aspect.
According to the technology of the application, the N groups of collected fault logs are all logs generated by calling N requests for each module of the fault machine, so that the fault source module of the fault machine can be determined efficiently according to the N groups of fault logs, and fault positioning is achieved efficiently.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present application, nor do they limit the scope of the present application. Other features of the present application will become apparent from the following description.
Drawings
The drawings are included to provide a better understanding of the present solution and are not intended to limit the present application. Wherein:
FIG. 1 is a schematic block diagram of a fault log processing system according to a first embodiment of the present application;
FIG. 2 is a flowchart illustrating a fault log processing method according to a first embodiment of the present application;
fig. 3 is a schematic structural diagram of a fault log processing apparatus according to a second embodiment of the present application;
fig. 4 is a block diagram of an electronic device for implementing the fault log processing method according to the embodiment of the present application.
Detailed Description
The following description of the exemplary embodiments of the present application, taken in conjunction with the accompanying drawings, includes various details of the embodiments of the application for the understanding of the same, which are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
The fault log is generated by a fault machine when a call request is made, and particularly, a machine (machine) is provided with a plurality of modules, and when a certain module in the machine fails, the machine can be called as a fault machine. When a request enters a machine, the request goes through a plurality of modules in sequence, each module outputs own log, and when the machine fails, each module of the machine calls the log generated by any request to be understood as a fault log.
In the prior art, fault log tracking is generally constructed in a server-client (client) mode, and the following scheme is generally adopted: the method comprises the steps that a log collection tool is deployed for each machine, a client side continuously reads each row of logs collected by the log collection tool according to configuration, and reports the logs to a server in a full-quantity mode or in a screening mode, and the data quantity needing to be processed by the log collection client side is continuously increased along with the increase of flow, so that the system resources occupied by the log collection client side are too high, and even if a screening mechanism is adopted, the number of logs stored in the back end is huge. Moreover, as the complexity of the service increases, the complexity of the modules in the machine gradually increases, the number of the modules also increases, different modules output different logs, and the log collection client usually separately collects log information of each module, which easily causes log confusion, so that fault location is difficult.
In order to solve the technical problems in the prior art, the present application provides a fault log processing method, a fault log processing apparatus, an electronic device, and a storage medium.
In the present application, the fault log processing mode may still adopt a server-client mode, and may be implemented by the fault log processing system shown in fig. 1. In fig. 1, each machine 11 corresponds to a respective client 12, the client 12 of each machine 11 is connected to a server 13, the server 13 is further connected to an alarm component 14, and the alarm component 14 is further connected to each machine 11. The client 12 may be configured to collect logs generated by the machine 11, the alarm component 14 may be configured to monitor an operating state of the machine 11, when the machine 11 fails, the alarm component 14 may send a failure alarm signal, the server 13 may obtain failure information of the machine 11 through the alarm component 14, and the server 13 and the client 12 may perform interactive communication, for example, the server 13 may send a failure log collection request to the client 12 and receive a failure log sent by the client 12.
In this application, the collection of the fault log may be understood as obtaining the fault log from the fault machine 11, and the collection end of the fault log may be the client 12 of the fault machine 11. The localization of the fault may include the determination of the source module of the fault and the determination of the type of the fault, and in this application, the localization of the fault may be implemented by the server 13.
Exemplary embodiments of the present application are described below.
As shown in fig. 2, the fault log processing method includes the following steps:
step 201: sending a fault log acquisition request to a client of a fault machine;
step 202: receiving N groups of fault logs of the fault machine sent by the client in response to the fault log acquisition request, wherein the N groups of fault logs comprise all logs generated by calling N requests by each module of the fault machine, and N is an integer greater than or equal to 1;
step 203: and determining fault source module information and corresponding fault type information of the fault machine according to the N groups of fault logs.
The fault log processing method according to the embodiment of the present application may be executed by a fault log processing apparatus, which may be the server 13 in fig. 1.
In the embodiment of the application, the acquisition of the fault log is not performed by the client actively and reported to the server, but the client waits for the notification of the server to acquire the fault log. Specifically, in step 201, when the server obtains the fault signal, the server may send a fault log collection request to the client of the fault machine.
If the client receives a fault log collection request sent by the server, the client can respond to the fault log collection request to collect logs of the machine. If the server does not send a fault log collection request to the client, the client does not actively collect the log of the machine. Therefore, the problem of resource waste caused by a traditional log collection mode can be effectively solved, the resource loss of a machine where the client is located and the waste of network bandwidth can be saved, and the whole log processing system can process the fault log on the premise of occupying small resources.
The server can acquire the fault signal in various ways, for example, the server scans or grabs the fault signal from the alarm component at regular time to confirm whether the fault occurs; for another example, when the alarm component monitors that a fault occurs, it actively reports a fault signal to the server. The server can determine the failed machine (i.e., the failed machine) by the failure signal.
In the embodiment of the application, once a fault is found to occur, the server can initiate a fault log acquisition request to a client of a fault machine according to configuration, and the server can carry acquisition requirements of a fault log in the fault log acquisition request.
In step 202, the server may receive N sets of fault logs of the fault machine sent by the client in response to the fault log collection request, where the N sets of fault logs include all logs generated by modules of the fault machine calling N requests. Here, each set of fault logs may again be understood as a complete log generated by each request being invoked by a faulty machine. Each set of fault logs may be considered a complete log, and each complete log may include multiple logs resulting from multiple module calls for the same request.
The N groups of fault logs can be partial fault logs of the fault machine or all fault logs of the fault machine, and the client can randomly collect the N groups of fault logs and send the N groups of fault logs to the server.
Since the N groups of fault logs are complete logs generated by the N requests called by the fault machine, in step 203, the server may trace and locate the fault according to the N groups of fault logs, that is, determine the fault source module information of the fault machine, and in addition, the server may determine the corresponding fault type information according to the fault logs.
In the embodiment of the application, when the fault logs are collected, all logs generated by N requests are called by N groups of collected fault logs for each module of the fault machine, so that the fault source module of the fault machine can be determined efficiently according to the N groups of fault logs, and fault positioning is realized efficiently. When the machine breaks down, the fault log collection and fault positioning can be realized through the embodiment of the application, and convenience can be provided for operation and maintenance personnel to efficiently troubleshoot the fault machine.
Optionally, the fault log collection request includes collection quantity information of the fault logs, and the value of N is matched with the collection quantity information of the fault logs.
The information on the collection number of fault logs in the fault log collection request may be understood as the number of complete logs, for example, each fault machine may be configured to collect at most 10 complete logs.
In the embodiment, the log collection quantity of each fault machine is limited by the fault log collection request, so that the quantity of the collected logs of the client can be effectively limited, fault logs of small quantity levels cannot be leaked, excessive and repeated fault logs cannot be collected when large-scale faults are triggered, the occupation of excessive resources of the client and the machine can be further avoided, and the light-weight fault log collection is realized.
Optionally, the determining, according to the N groups of fault logs, fault source module information of the fault machine includes:
and sequencing each group of fault logs of the N groups of fault logs according to the calling sequence of each request of the N requests in the fault machine, searching each group of fault logs in sequence, and determining the fault source module information of each group of fault logs.
After a request enters the agent module through load balancing, the request sequentially passes through a plurality of modules of the machine, and each module outputs a log of the request. The server can sort each group of fault logs according to the module access sequence and search the fault logs of each module in sequence, so that the fault source module information of the fault logs is determined.
According to the implementation mode, each group of fault logs are sequenced according to the calling sequence of the requests in the fault machine, so that the server can quickly trace and investigate the fault source, and the fault can be positioned efficiently. In addition, the server can search each group of fault logs in sequence, so that the sequence of transmitting the fault logs by the client is not required to be limited, and the complexity of transmitting the fault logs by the client can be reduced.
Optionally, the N requests are respectively preconfigured with identification information corresponding to each request, and all logs generated when each request of the N requests is called by each module of the fault machine carry the identification information corresponding to the request.
In this embodiment, in order to improve the correlation between logs, a proxy module may be created in advance, when a request enters the backend, the request may be controlled by the proxy module, corresponding identification information is created for the request, and the identification information is output in the log in each subsequent module call, thereby improving the correlation between logs.
Therefore, when the client collects the fault log of the fault machine, the collected fault log can be ensured to be a complete log according to the identification information carried in the log.
Optionally, the sending a fault log collection request to a client of a fault machine includes:
and sending fault log acquisition requests to clients of a preset number of fault machines, wherein the preset number is less than the total number of the fault machines.
In the embodiment of the application, the number of collected logs of each fault machine can be limited, and the number of collected machines can be limited. For example, when a large-scale fault occurs, the number of the faulty devices is large, and the fault causes of most faulty devices may be the same, so that it is not necessary to collect too many and repeated fault logs, and it is not necessary to collect fault logs for each faulty device. In view of this, when the total number of the faulty machines is large, the server may send a fault log collection request to the clients of a preset number of the faulty machines. For example, the preset number may be 10, that is, when the total number of the faulty machines is greater than 10, the server may send a fault log collection request to the clients of any 10 faulty machines.
In the embodiment, the number of the collected machines is limited, so that the occupation of excessive resources of the client and the machines can be further avoided, and the lightweight fault log collection is further realized.
Optionally, after determining the fault source module information and the corresponding fault type information of the faulty machine according to the N sets of fault logs, the method further includes:
and generating fault statistical data, wherein the fault statistical data comprises the proportion information of the fault source module and the corresponding fault type information.
After determining the fault source module information and the corresponding fault type information of the fault machine, the server may directly display the fault source module information and the corresponding fault type information at the front end, or directly report the fault source module information and the corresponding fault type information to research, development, operation and maintenance personnel in a message pushing manner.
In view of the fact that the fault source module information and the corresponding fault type information are relatively complicated, in order to enable research and development and operation and maintenance personnel to directly, clearly and conveniently know the main fault source and the fault type, the server can summarize the fault reason of each log according to the determined fault source module information and the fault type information and generate fault statistical data. The fault statistics may include fraction information of the fault source module and corresponding fault type information. For example, the failure statistics may be, for example, "70% module a, connection DB failed, 30% module B, network abnormal".
Even if the server generates the fault statistical data, the server can continuously store detailed fault logs, fault source module information and corresponding fault type information for research and development and operation and maintenance personnel to check at any time.
In addition, with the development of the cloud technology, modules can be continuously optimized, decoupled and increased, so that in consideration of the expandability of the system, configuration files can be designed for the server, and each module in the configuration can be configured with 0 to n dependent modules. When the server is started, the modules to be combed can be sequenced, and for the modules which are irrelevant, a plurality of coroutines (coroutines) can be started for processing, so that the processing efficiency is improved.
It should be noted that, the various optional embodiments in the fault log processing method in the present application may be implemented in combination with each other or implemented separately, and the present application is not limited to this.
The above embodiments of the present application have at least the following advantages or benefits:
in the embodiment of the application, when the fault logs are collected, all logs generated by N requests are called by N groups of collected fault logs for each module of the fault machine, so that the fault source module of the fault machine can be determined efficiently according to the N groups of fault logs, and fault positioning is realized efficiently. When the machine breaks down, the fault log collection and fault positioning can be realized through the embodiment of the application, and convenience can be provided for operation and maintenance personnel to efficiently troubleshoot the fault machine.
As shown in fig. 3, the present application provides a fault log processing apparatus 300, including:
a sending module 301, configured to send a fault log collection request to a client of a fault machine;
a receiving module 302, configured to receive N groups of fault logs of the fault machine sent by the client in response to the fault log collection request, where the N groups of fault logs include all logs generated by invoking N requests by each module of the fault machine, and N is an integer greater than or equal to 1;
a determining module 303, configured to determine, according to the N groups of fault logs, fault source module information and corresponding fault type information of the fault machine.
Optionally, the determining module 303 is specifically configured to:
and sequencing each group of fault logs of the N groups of fault logs according to the calling sequence of each request of the N requests in the fault machine, searching each group of fault logs in sequence, and determining fault source module information and corresponding fault type information of each group of fault logs.
Optionally, the fault log processing apparatus 300 further includes:
and the generation module is used for generating fault statistical data, and the fault statistical data comprises the proportion information of the fault source module and the corresponding fault type information.
Optionally, the N requests are respectively preconfigured with identification information corresponding to each request, and all logs generated when each request of the N requests is called by each module of the fault machine carry the identification information corresponding to the request.
Optionally, the fault log collection request includes collection quantity information of the fault logs, and the value of N is matched with the collection quantity information of the fault logs.
Optionally, the sending module 301 is specifically configured to:
and sending fault log acquisition requests to clients of a preset number of fault machines, wherein the preset number is less than the total number of the fault machines.
The fault log processing apparatus 300 provided in the present application can implement each process in the above-described fault log processing method embodiment, and can achieve the same beneficial effects, and for avoiding repetition, details are not repeated here.
According to an embodiment of the present application, an electronic device and a readable storage medium are also provided.
Fig. 4 is a block diagram of an electronic device according to the fault log processing method of the embodiment of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application that are described and/or claimed herein.
As shown in fig. 4, the electronic apparatus includes: one or more processors 401, memory 402, and interfaces for connecting the various components, including high-speed interfaces and low-speed interfaces. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions for execution within the electronic device, including instructions stored in or on the memory to display graphical information of a GUI on an external input/output apparatus (such as a display device coupled to the interface). In other embodiments, multiple processors and/or multiple buses may be used, along with multiple memories and multiple memories, as desired. Also, multiple electronic devices may be connected, with each device providing portions of the necessary operations (e.g., as a server array, a group of blade servers, or a multi-processor system). In fig. 4, one processor 401 is taken as an example.
The memory 402, which is a non-transitory computer readable storage medium, may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules (e.g., the transmitting module 301, the receiving module 302, and the determining module 303 shown in fig. 3) corresponding to the fault log processing method in the embodiment of the present application. The processor 401 executes various functional applications and data processing of the fault log processing apparatus by running non-transitory software programs, instructions and modules stored in the memory 402, that is, implements the fault log processing method in the above-described method embodiment.
The memory 402 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of the electronic device of the fault log processing method, and the like. Further, the memory 402 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 402 may optionally include a memory remotely located from the processor 401, and these remote memories may be connected to the electronic device of the fault log processing method through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The electronic device of the fault log processing method may further include: an input device 403 and an output device 404. The processor 401, the memory 402, the input device 403 and the output device 404 may be connected by a bus or other means, and fig. 4 illustrates an example of a connection by a bus.
The input device 403 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the electronic apparatus of the fault log processing method, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, a pointing stick, one or more mouse buttons, a track ball, a joystick, or other input devices. The output devices 404 may include a display device, auxiliary lighting devices (e.g., LEDs), and haptic feedback devices (e.g., vibrating motors), among others. The display device may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some implementations, the display device can be a touch screen.
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
These computer programs (also known as programs, software applications, or code) include machine instructions for a programmable processor, and may be implemented using high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), the internet, and blockchain networks.
The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The Server may be a cloud Server, which is also called a cloud computing Server or a cloud host, and is a host product in a cloud computing service system, so as to solve the defects of high management difficulty and weak service extensibility in the conventional physical host and Virtual Private Server (VPS) service.
According to the technical scheme of the embodiment of the application, when the fault logs are collected, all logs generated by N requests are called by N groups of collected fault logs for each module of the fault machine, so that the fault source module of the fault machine can be determined efficiently according to the N groups of fault logs, and fault positioning is achieved efficiently. When the machine breaks down, the fault log collection and fault positioning can be realized through the embodiment of the application, and convenience can be provided for operation and maintenance personnel to efficiently troubleshoot the fault machine.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present application may be executed in parallel, sequentially, or in different orders, and the present invention is not limited thereto as long as the desired results of the technical solutions disclosed in the present application can be achieved.
The above-described embodiments should not be construed as limiting the scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (14)
1. A fault log processing method, the method comprising:
sending a fault log acquisition request to a client of a fault machine;
receiving N groups of fault logs of the fault machine sent by the client in response to the fault log acquisition request, wherein the N groups of fault logs comprise all logs generated by calling N requests by each module of the fault machine, and N is an integer greater than or equal to 1;
and determining fault source module information and corresponding fault type information of the fault machine according to the N groups of fault logs.
2. The method of claim 1, wherein said determining fault source module information for the faulty machine from the N sets of fault logs comprises:
and sequencing each group of fault logs of the N groups of fault logs according to the calling sequence of each request of the N requests in the fault machine, searching each group of fault logs in sequence, and determining the fault source module information of each group of fault logs.
3. The method of claim 1, wherein after said determining fault source module information and corresponding fault type information for the faulty machine from the N sets of fault logs, the method further comprises:
and generating fault statistical data, wherein the fault statistical data comprises the proportion information of the fault source module and the corresponding fault type information.
4. The method according to claim 1, wherein the N requests are respectively preconfigured with respective corresponding identification information, and all logs generated when each request of the N requests is called by each module of the faulty machine carry the identification information corresponding to the request.
5. The method of claim 1, wherein the fault log collection request includes collected quantity information of fault logs, and the value of N matches the collected quantity information of fault logs.
6. The method of claim 1, wherein the sending a fault log collection request to a client of a faulty machine comprises:
and sending fault log acquisition requests to clients of a preset number of fault machines, wherein the preset number is less than the total number of the fault machines.
7. A fault log processing apparatus comprising:
the sending module is used for sending a fault log collecting request to a client of a fault machine;
a receiving module, configured to receive N groups of fault logs of the fault machine sent by the client in response to the fault log collection request, where the N groups of fault logs include all logs generated by invoking N requests by each module of the fault machine, and N is an integer greater than or equal to 1;
and the determining module is used for determining the fault source module information and the corresponding fault type information of the fault machine according to the N groups of fault logs.
8. The apparatus of claim 7, wherein the determining module is specifically configured to:
and sequencing each group of fault logs of the N groups of fault logs according to the calling sequence of each request of the N requests in the fault machine, searching each group of fault logs in sequence, and determining the fault source module information of each group of fault logs.
9. The apparatus of claim 7, further comprising:
and the generation module is used for generating fault statistical data, and the fault statistical data comprises the proportion information of the fault source module and the corresponding fault type information.
10. The apparatus according to claim 7, wherein the N requests are respectively preconfigured with respective corresponding identification information, and all logs generated when each of the N requests is called by each module of the faulty machine carry the identification information corresponding to the request.
11. The apparatus of claim 7, wherein the fault log collection request includes collected quantity information of fault logs, and the value of N matches the collected quantity information of fault logs.
12. The apparatus of claim 7, wherein the sending module is specifically configured to:
and sending fault log acquisition requests to clients of a preset number of fault machines, wherein the preset number is less than the total number of the fault machines.
13. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1 to 6.
14. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011308953.6A CN112395126A (en) | 2020-11-20 | 2020-11-20 | Fault log processing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011308953.6A CN112395126A (en) | 2020-11-20 | 2020-11-20 | Fault log processing method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112395126A true CN112395126A (en) | 2021-02-23 |
Family
ID=74607667
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011308953.6A Pending CN112395126A (en) | 2020-11-20 | 2020-11-20 | Fault log processing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112395126A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113630288A (en) * | 2021-07-09 | 2021-11-09 | 济南浪潮数据技术有限公司 | Intelligent network card fault information collection method, device, terminal and storage medium |
| CN115396282A (en) * | 2022-07-20 | 2022-11-25 | 北京奇艺世纪科技有限公司 | Information processing method, system and device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103905223A (en) * | 2012-12-26 | 2014-07-02 | 腾讯科技（北京）有限公司 | Data packet acquisition method, system and device |
| CN105868040A (en) * | 2016-03-29 | 2016-08-17 | Tcl通力电子（惠州）有限公司 | Log collection method and collection terminal |
| CN106100879A (en) * | 2016-06-07 | 2016-11-09 | 青岛海信移动通信技术股份有限公司 | Mobile terminal journal obtaining method and device |
| CN109240846A (en) * | 2018-09-19 | 2019-01-18 | 郑州云海信息技术有限公司 | A kind of power failure diagnosing method, apparatus and server |
| CN109426578A (en) * | 2017-09-04 | 2019-03-05 | 优酷网络技术（北京）有限公司 | The method and apparatus for handling client failure |
| CN109710490A (en) * | 2018-12-20 | 2019-05-03 | 网易（杭州）网络有限公司 | Acquisition method, device, storage medium and the electronic equipment of client log |
| CN111143185A (en) * | 2019-12-30 | 2020-05-12 | 珠海金山网络游戏科技有限公司 | Log-based fault analysis method and device |
-
2020
- 2020-11-20 CN CN202011308953.6A patent/CN112395126A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103905223A (en) * | 2012-12-26 | 2014-07-02 | 腾讯科技（北京）有限公司 | Data packet acquisition method, system and device |
| CN105868040A (en) * | 2016-03-29 | 2016-08-17 | Tcl通力电子（惠州）有限公司 | Log collection method and collection terminal |
| CN106100879A (en) * | 2016-06-07 | 2016-11-09 | 青岛海信移动通信技术股份有限公司 | Mobile terminal journal obtaining method and device |
| CN109426578A (en) * | 2017-09-04 | 2019-03-05 | 优酷网络技术（北京）有限公司 | The method and apparatus for handling client failure |
| CN109240846A (en) * | 2018-09-19 | 2019-01-18 | 郑州云海信息技术有限公司 | A kind of power failure diagnosing method, apparatus and server |
| CN109710490A (en) * | 2018-12-20 | 2019-05-03 | 网易（杭州）网络有限公司 | Acquisition method, device, storage medium and the electronic equipment of client log |
| CN111143185A (en) * | 2019-12-30 | 2020-05-12 | 珠海金山网络游戏科技有限公司 | Log-based fault analysis method and device |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113630288A (en) * | 2021-07-09 | 2021-11-09 | 济南浪潮数据技术有限公司 | Intelligent network card fault information collection method, device, terminal and storage medium |
| CN115396282A (en) * | 2022-07-20 | 2022-11-25 | 北京奇艺世纪科技有限公司 | Information processing method, system and device |
| CN115396282B (en) * | 2022-07-20 | 2024-03-15 | 北京奇艺世纪科技有限公司 | Information processing method, system and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2021129367A1 (en) | Method and apparatus for monitoring distributed storage system | |
| CN112486820B (en) | Method, apparatus, device and storage medium for testing code | |
| CN111639027B (en) | Test method and device and electronic equipment | |
| CN112181683A (en) | Concurrent consumption method and device for message middleware | |
| CN111694646A (en) | Resource scheduling method and device, electronic equipment and computer readable storage medium | |
| CN112395126A (en) | Fault log processing method and device, electronic equipment and storage medium | |
| CN111586128A (en) | Method, device and equipment for acquiring applet data and storage medium | |
| CN112491617B (en) | Link tracking method, device, electronic equipment and medium | |
| KR102488582B1 (en) | Method and apparatus for verifying operation state of application | |
| CN113051043A (en) | Micro-service anomaly compensation method and device | |
| CN111740859B (en) | Test environment deployment method and device, electronic equipment and storage medium | |
| CN111049690B (en) | Equipment fault monitoring processing method, device, equipment and storage medium | |
| CN112486645A (en) | Timed task monitoring method and device, electronic equipment and medium | |
| CN112540914A (en) | Execution method, execution device, server and storage medium for unit test | |
| CN112202746A (en) | RPC member information acquisition method and device, electronic equipment and storage medium | |
| CN112491858B (en) | Method, device, equipment and storage medium for detecting abnormal information | |
| CN111966471B (en) | Access method, device, electronic equipment and computer storage medium | |
| CN114217996A (en) | Sound mixing method and device | |
| CN111694686B (en) | Processing method and device for abnormal service, electronic equipment and storage medium | |
| EP3866399A1 (en) | Method and apparatus for adjusting network flow | |
| CN111597026B (en) | Method and device for acquiring information | |
| CN111835857B (en) | Method and apparatus for accessing data | |
| US10949232B2 (en) | Managing virtualized computing resources in a cloud computing environment | |
| CN113032209A (en) | Operation monitoring method, device, server and medium | |
| CN110768855B (en) | Method and device for testing linkmzation performance |
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 |