CN113220493A

CN113220493A - Fault data processing method and device, storage medium and electronic equipment

Info

Publication number: CN113220493A
Application number: CN202010079612.XA
Authority: CN
Inventors: 李开君; 张兴龙
Original assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Jingdong Shangke Information Technology Co Ltd
Current assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Jingdong Shangke Information Technology Co Ltd
Priority date: 2020-02-04
Filing date: 2020-02-04
Publication date: 2021-08-06

Abstract

The present disclosure relates to the field of data processing technologies, and in particular, to a fault data processing method, a fault data processing apparatus, a computer-readable storage medium, and an electronic device, where the method includes: reading target alarm data in the fault alarm data pool, and determining a corresponding equipment tag according to the target alarm data; calling a corresponding data collection interface according to the equipment label to collect data, and storing the collected target fault data in a preset storage space; generating a storage path corresponding to the target fault data according to the position of the target fault data in a preset storage space; and determining a corresponding processing party according to the equipment tag, and sending the storage path to the processing party so that the processing party reads the target fault data through the storage path. According to the technical scheme, the target fault data required by the equipment can be automatically collected by the data collection interface corresponding to the equipment label, and the problem of low fault processing efficiency caused by manual collection is solved.

Description

Fault data processing method and device, storage medium and electronic equipment

Technical Field

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

Background

A data center is a globally collaborative network of devices that is used to communicate, accelerate, present, compute, store data information over an internet network infrastructure. In general, a baseboard management interface (BMC) of a data center server accesses a data center network through its own network interface, and a technician can remotely maintain, configure, and manage the data center server through the BMC. When equipment of each manufacturer (namely a fault data processing party) has a fault, technicians can access the BMC of the data center through the network to diagnose and collect fault data of each equipment in the data center, and then can report the fault data to different processing parties.

When hardware faults occur, because different processing parties have different requirements on fault data required by maintenance and different collection modes, in the prior art, technical personnel often perform manual collection and the collected data are transmitted to the processing parties through a network after the manual collection is finished. However, when the data center is large in size, the number of servers in the data center is also large, and hundreds of hardware failures may occur every day. In this case, a technician manually collects the failure data and manually uploads the failure data after the collection is completed, and this manual execution may take a longer time, thereby causing a problem of inefficient failure processing.

It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.

Disclosure of Invention

The present disclosure is directed to a fault data processing method, a fault data processing apparatus, a computer-readable storage medium, and an electronic device, so as to overcome, at least to a certain extent, the problem of low fault processing efficiency caused by long time consumption for manually collecting fault data.

Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.

According to a first aspect of the present disclosure, there is provided a fault data processing method, the method including:

reading target alarm data in a fault alarm data pool, and determining a corresponding equipment tag according to the target alarm data;

calling a corresponding data collection interface according to the equipment label to collect data, and storing the collected target fault data in a preset storage space;

generating a storage path corresponding to the target fault data according to the position of the target fault data in the preset storage space;

and determining a corresponding processing party according to the equipment tag, and sending the storage path to the processing party so that the processing party reads the target fault data through the storage path.

Optionally, based on the foregoing scheme, before performing data collection, the method further includes:

determining target equipment according to the equipment label, and calling an account and a password corresponding to the target equipment in a preset password library through a password calling interface;

and establishing a communication connection between the data collection interface and the target device through the account and the password.

Optionally, based on the foregoing scheme, the invoking a corresponding data collection interface according to the device tag to collect data includes:

and reading a processing party label contained in the equipment label, calling a corresponding data collection interface according to the processing party label, and collecting data through the data collection interface.

Optionally, based on the foregoing scheme, the method further includes:

and determining fault component information in the target equipment according to the target alarm data, and sending the fault component information to the processing party.

Optionally, based on the foregoing scheme, the storing the collected target fault data in a preset storage space includes:

and establishing a folder in the preset storage space by taking the equipment tag and the current time as names, and storing the target fault data in the folder.

Optionally, based on the foregoing solution, after the target fault data is stored in the folder, the method further includes:

and compressing the folder to control the size of the target fault data.

Optionally, based on the foregoing scheme, before reading the target alarm data in the fault alarm data pool, the method further includes:

and receiving fault alarm data sent by equipment, and writing the fault alarm data into the fault alarm data pool.

According to an aspect of the present disclosure, there is provided a fault data processing apparatus including:

the tag acquisition module is used for reading target alarm data in the fault alarm data pool and determining a corresponding equipment tag according to the target alarm data;

the data collection module is used for calling a corresponding data collection interface according to the equipment label to collect data and storing the collected target fault data in a preset storage space;

the path generation module is used for generating a storage path corresponding to the target fault data according to the position of the target fault data in the preset storage space;

and the data sending module is used for determining a corresponding processing party according to the equipment tag and sending the storage path to the processing party so that the processing party reads the target fault data through the storage path.

According to an aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a fault data processing method as described in any one of the above.

According to an aspect of the present disclosure, there is provided an electronic device including:

a processor; and

memory for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement a fault data processing method as claimed in any one of the preceding claims.

The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects:

in the fault data processing method provided by an embodiment of the disclosure, on one hand, a plurality of equipment faults occurring at the same time can be processed in parallel by setting a fault alarm data pool, so that the problem that misjudgment faults are caused by serial processing and further fault data are transmitted in error is avoided; on the other hand, the target alarm data is used for determining the device label, the target fault data required by the device can be automatically collected by using the data collection interface corresponding to the device label, and the problem of low fault processing efficiency caused by manual collection is avoided. In addition, after the collection of the fault data is finished, the fault data can be directly sent to a processing party corresponding to the equipment label, and the problem of low fault processing efficiency caused by the situations of delay or mistransmission and the like during manual sending of technicians is solved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty. In the drawings:

FIG. 1 schematically illustrates a flow chart of a method of fault data processing in an exemplary embodiment of the disclosure;

FIG. 2 schematically illustrates a flow chart of a method of establishing a communication connection of a data collection interface with a target device in an exemplary embodiment of the disclosure;

FIG. 3 schematically illustrates a flow chart of another method of fault data processing in an exemplary embodiment of the disclosure;

FIG. 4 is a schematic diagram illustrating the components of a fault data processing apparatus in an exemplary embodiment of the present disclosure;

fig. 5 schematically shows a schematic structural diagram of a computer system of an electronic device suitable for implementing an exemplary embodiment of the present disclosure.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

The equipment quantity in large-scale data center is huge, because the brand of various equipment on the market, model are complicated, and the fault data type that the fault data that the different brands of equipment correspond need collect when maintaining equipment is also different, consequently in the correlation technique, can adopt the manual work to collect the fault data usually, and then sends the fault data to the processing side, and then accomplishes the process that equipment trouble reported and repaired. However, the above process completely depends on manual operation of a technician, and the failure repair efficiency is low, thereby affecting the efficiency of failure processing.

In view of one or more of the above problems, in the present exemplary embodiment, a failure data processing method is first provided, which can be applied to a failure repair process of a data center. Referring to fig. 1, the above-mentioned fault data processing method may include the steps of:

s110, reading target alarm data in a fault alarm data pool, and determining a corresponding equipment tag according to the target alarm data;

s120, calling a corresponding data collection interface according to the equipment label to collect data, and storing the collected target fault data in a preset storage space;

s130, generating a storage path corresponding to the target fault data according to the position of the target fault data in the preset storage space;

s140, determining a corresponding processing party according to the equipment tag, and sending the storage path to the processing party so that the processing party reads the target fault data through the storage path.

According to the fault data processing method provided in the exemplary embodiment, on one hand, a plurality of equipment faults occurring at the same time can be processed in parallel by setting the fault alarm data pool, so that the problem that misjudgment faults are caused by serial processing and further fault data are transmitted in error is avoided; on the other hand, the target alarm data is used for determining the device label, the target fault data required by the device can be automatically collected by using the data collection interface corresponding to the device label, and the problem of low fault processing efficiency caused by manual collection is avoided. In addition, after the collection of the fault data is finished, the fault data can be directly sent to a processing party corresponding to the equipment label, and the problem of low fault processing efficiency caused by the situations of delay or mistransmission and the like during manual sending of technicians is solved.

Hereinafter, each step of the fault data processing method in the present exemplary embodiment will be described in more detail with reference to the drawings and the embodiments.

In an example embodiment of the present disclosure, before performing the fault data processing, referring to fig. 2, the method further includes: and receiving fault alarm data sent by equipment, and writing the fault alarm data into the fault alarm data pool.

In an example embodiment of the present disclosure, the pushed fault alert data for a device may include device tag data for determining the identity of the device among a plurality of devices in a data center. The corresponding equipment can be quickly searched in a large-scale data center through the label data. When the equipment of the data center fails, the equipment can report the failure to the data center server, so that the data center server can process the failure. For example, in a machine room inspection process or an equipment use process, relevant workers may find that the equipment has a fault, and at this time, fault alarm data may be pushed to the data center server through the equipment, so as to write the fault alarm data into a fault alarm data pool.

Step S110, reading target alarm data in the fault alarm data pool, and determining a corresponding device tag according to the target alarm data.

In an example embodiment of the present disclosure, a plurality of fault alarm data may be included in the fault alarm data pool. Large-scale data centers may include a very large number of devices, which may cause hundreds of hardware failures each day, and thus there may be cases where multiple devices fail simultaneously. In this case, the fault alarm data pool may include a plurality of fault alarm data.

In an example embodiment of the present disclosure, since the equipment in one data center may be provided by multiple processing parties, when the equipment provided by multiple different processing parties fails, the fault alarm data corresponding to the multiple different processing parties may also exist in the fault alarm data pool at the same time. In this case, since the receipt failure data required by different processing parties is different, the failure alarm data corresponding to the different processing parties can be processed separately. Specifically, the device tag corresponding to the target alarm data may be determined according to the target alarm data to determine the device with the fault, and then data collection is performed according to the requirement of the processing party corresponding to the device on the fault data. It should be noted that the processing party may include the manufacturer itself or a data processing party specified by the manufacturer to process the failure.

In addition, since the failure alarm data corresponding to different processors can be processed separately, it is possible to process in parallel by a plurality of threads, a plurality of processes, or other means. Specifically, a target alarm data in the failure alarm data pool, a corresponding device tag to which the target alarm data belongs, may be read, and the subsequent data collection step may be performed. The purpose of processing a plurality of target alarm data in parallel can be realized by setting the fault alarm data pool, the processing efficiency of the fault data is improved, and meanwhile, the problems of misjudgment faults and mistransmission fault data caused by mutual influence of a plurality of faults when the plurality of fault data are processed in series in the related technology can be avoided.

And step S120, calling a corresponding data collection interface according to the equipment label to collect data, and storing the collected target fault data in a preset storage space.

In an example embodiment of the present disclosure, since data required by a failure data party corresponding to different device processing parties when processing a failure is different, different data collection interfaces may be set for devices of different processing parties, so as to collect target failure data required by the failure data party corresponding to the processing party.

In an example embodiment of the present disclosure, the preset storage space may be in the form of a shared space, so that a data center may perform remote management. For example, the shared space Storage may be selected from a Network File System (Network File System) or an Object Storage Device (Object Storage Device).

Specifically, the invoking a corresponding data collection interface according to the device tag to collect data may include: and reading a processing party label contained in the equipment label, calling a corresponding data collection interface according to the processing party label, and collecting data through the data collection interface.

In an example embodiment of the present disclosure, the device tag may include a handler tag, and the handler tag may be a vendor tag. For example, the vendor tag may be a numeric string or a string composed of numbers and symbols, as shown in table 1. It should be noted that, when the processing party is a data processing party specified by a manufacturer for processing a fault, the data processing party specified by the manufacturer may be searched according to a manufacturer tag, and then a corresponding data collection interface may be called.

Table 1 vendor tag example

Manufacturer(s)

A

B

C

D

E

F

G

Manufacturer label

2、19046

674

2011

11，47196

37945，10876

27500

20301

Several types of data collection interfaces commonly used in this disclosure are described in detail below, using the vendors shown in table 1 as examples:

1. a, a data collection interface of target fault data of a manufacturer server:

logging in a fault device BMC through software and an account password, and generating a collected ffdc log: system > ffdc generator-t 4 and ffdc generator-t 1.

Transferring logs from the failed host BMC to the computing platform temporary space: system > ffdc copy-IP $ share-IP-f $ share-direction-pn 22-u $ user-pw $ password.

The data collection interface of the type needs to log in a fault device to collect target fault data firstly and then transmit the target fault data to a preset storage space, and the whole process is non-interactive automatic processing.

2. B, data collection interface of the target fault data of the manufacturer server:

and (4) collecting sel: racdm-r $ { RACIP } -u $ user-p $ password getsel > $ { log }/$ { FN } _ log

And (2) collecting lc: racdm-r $ { RACIP } -u $ user-p $ password lclog view > $ { log }/$ { FN } _ log

Collecting tsr: racdm-r $ { RACIP } -u $ user-p $ passswswerd technupeport collection-t TTYLog

Generating target fault data: racdm-r $ { RACIP } -u $ user-p $ past copied technupeport export-f $ { log }/$ { FN } _ tsr

This type of data collection interface can be used directly for off-band collection processing, run on a compute node and directly saved in a preset memory space.

3. C, data collection interface of the target fault data of the manufacturer server:

generating the Dump _ info target failure data on the failed device BMC: ssh $ user @ $ ip 'ipmcget-d diaginfo'; for realizing automatic collection, an automatic interface such as sshpass or expect can be used.

And automatically downloading the log just generated by the failed host in a preset storage space. One way of implementation is as follows: sftp $ user @ $ ip @/tmp/dump _ info. tar.gz./$ { SN } _ tar.gz

4. D, a data collection interface of the target fault data of the manufacturer server:

the data collection interface can acquire target fault data through an out-of-band tool, and the specific steps are as follows: curl https:// $ BMCIP/ahsdata/ahs. ahsfrom ═ yyyy-mm-dd1> & to ═ yyyyy-mm-dd 2> "-k-v-u $ user $ password-o $ { SN } _ DATE }. ahs.

The above-described manner requires that time intervals yyyy-mm-dd1 and yyyy-mm-dd2 for collecting target failure data be set in advance. For example, event information for the last three days or a week may be collected. It should be noted that, in order to ensure that the target failure data can be transmitted in the normal network, the time interval may be set to be a shorter time interval.

5. For other vendors (E, F, G) that do not have a separate setup data collection interface, the SEL log of the failed device may be collected remotely as the target failure data. By way of example, this can be achieved by: Ipomitool-I lanplus-H $ IP-U $ USR-P $ PASD sel list > $ IP.

In an example embodiment of the present disclosure, in order to guarantee security of a data center, some or all of devices of the data center may be encrypted. At this time, before calling a corresponding data collection interface to collect data according to the device tag, as shown in fig. 2, the method further includes the following steps S210 to S220:

and step S210, determining target equipment according to the equipment label, and calling an account and a password corresponding to the target equipment in a preset password library through a password calling interface.

In an example embodiment of the present disclosure, in order to ensure the security of the data center, a corresponding account and password are set for the devices of the data center, so that the account and password corresponding to each device may be stored through a dedicated preset password library. After the device tag is determined, the target device with the fault can be determined according to the device tag, and then an account and a password corresponding to the target device are called.

Step S220, establishing a communication connection between the data collection interface and the target device through the account and the password.

In an example embodiment of the present disclosure, after the account and the password of the target device are obtained, in order to enable the invoked data interface to perform data collection, a communication connection between the data collection interface and the target device may be established through the account and the password of the target device, so that the data collection interface performs data collection. It should be noted that, in order to ensure the security of the device, the connection duration between the data collection interface and the target device may be controlled by setting the effective time for establishing the connection or the readable data range after establishing the connection, so as to avoid data leakage caused by long-time connection of the data collection interface. Furthermore, the method is simple. Through the special preset password database and the password calling interface, the problem of information leakage caused by easy leakage of accounts and passwords during manual fault data collection can be solved.

Step S130, generating a storage path corresponding to the target fault data according to the position of the target fault data in the preset storage space.

In an example embodiment of the present disclosure, the storage path may be a network link. Specifically, the preset storage space may be a storage space in a data center server or a storage space shared by a network, and a position of the target fault data in the preset storage space is converted into a network link, so that the processing party can download the target fault data according to the network link.

In an example embodiment of the present disclosure, the storing the collected target fault data in a preset storage space may include: and establishing a folder in the preset storage space by taking the equipment tag and the current time as names, and storing the target fault data in the folder.

In an example embodiment of the present disclosure, in order to facilitate the diagnosis of the data center server, a device tag and a current time of the target device may be used as names, a folder may be established in a preset storage space, and target fault data corresponding to the target device may be stored in the folder. The target fault data are stored by establishing a folder with the equipment label and the current time as names, so that the data center server can conveniently and quickly search the data, and further diagnosis is carried out.

In an example embodiment of the present disclosure, after storing the target failure data in the folder, the method further comprises: and compressing the folder to control the size of the target fault data.

In an example embodiment of the present disclosure, since the target failure data is transmitted to the processing party by transmitting the storage path, in order to facilitate the processing party to download the target failure data according to the storage path, the target failure data may be compressed during storage to control the size of the target failure data. In addition, the target fault data is compressed, so that the problems of target fault data loss and the like can be avoided.

Step S140, determining a corresponding processing party according to the device tag, and sending the storage path to the processing party, so that the processing party reads the target fault data through the storage path.

In an example embodiment of the present disclosure, since manufacturers of different devices are different, and correspondingly, processors of target failure data are different, a corresponding processor may be determined according to a device tag, and a storage path is sent to the processor. The processing party can read the target fault data according to the storage path. For example, when the storage path is a network link, the processing party may directly find the target fault data by clicking the network link, and download the target fault data.

In addition, in order to facilitate data processing by the processing side, the method further comprises: and determining fault component information in the target equipment according to the target alarm data, and sending the fault component information to the processing party.

In an example embodiment of the present disclosure, in order to facilitate the processing of the target failure data by the processing party, failure component information of a failure occurring in the target device may be predetermined according to the target alarm data, and the failure component information may be sent to the processing party, so that the processing party may make a prejudgment on the target failure data.

It should be noted that, since there is a one-to-one correspondence relationship between the faulty component information and the target faulty data, when the storage path and the faulty component information are transmitted to the processing side, the correspondence relationship between the two can be indicated in a specific manner. For example, the transmission may be made through the same named form.

The implementation details of the technical solution of the embodiment of the present disclosure are explained in detail below with reference to fig. 3:

first stage, reporting fault

And step S310, receiving fault alarm data reported by each device, and adding the fault alarm data into a fault alarm data pool.

Second stage, automatically collecting data

Step S320 analyzes the target alarm data read from the failure alarm data pool, and determines the device tag corresponding to the failed target device.

And step S330, calling a corresponding data collection interface according to the equipment label to collect data. For example, including 7 vendors as shown in table 1, there are 7 vendor tags.

Step S340, when the target device is encrypted, an account and a password corresponding to the target device in the preset password library may be called, so that the data collection interface may establish a communication connection with the target device according to the account and the password.

Step S350, creating a folder in the preset storage space with the device tag and the current time as names, storing the collected target fault data in the folder, and compressing the folder.

And step S360, generating a corresponding storage path at the position of the preset storage space according to the target fault data.

Step S370, the generated storage path is sent to the processing side corresponding to the device tag.

The third stage, processing side data processing stage

And step 380, after receiving the storage path, the processing party downloads and analyzes the target fault data according to the storage path so as to process the fault.

It is noted that the above-mentioned figures are merely schematic illustrations of processes involved in methods according to exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.

In addition, in an exemplary embodiment of the present disclosure, a fault data processing apparatus is also provided. Referring to fig. 4, the failure data processing apparatus 400 includes: a tag acquisition module 410, a data collection module 420, a path generation module 430, and a data transmission module 440.

The tag obtaining module 410 may be configured to read target alarm data in a fault alarm data pool, and determine a corresponding device tag according to the target alarm data; the data collection module 420 may be configured to call a corresponding data collection interface according to the device tag to perform data collection, and store the collected target fault data in a preset storage space; the path generating module 430 may be configured to generate a storage path corresponding to the target fault data according to a position of the target fault data in the preset storage space; the data sending module 440 may be configured to determine a corresponding processing party according to the device tag, and send the storage path to the processing party, so that the processing party reads the target fault data through the storage path.

In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the tag obtaining module 410 may be configured to determine a target device according to the device tag, and call, through a password call interface, an account and a password corresponding to the target device in a preset password library; and establishing a communication connection between the data collection interface and the target device through the account and the password.

In an exemplary embodiment of the present disclosure, based on the foregoing solution, the data collection module 420 may be configured to read a handler tag included in the device tag, call a corresponding data collection interface according to the handler tag, and collect data through the data collection interface.

In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the data sending module 440 may be configured to determine the faulty component information in the target device according to the target alarm data, and send the faulty component information to the processing party.

In an exemplary embodiment of the present disclosure, based on the foregoing solution, the data collection module 420 may be configured to establish a folder in the preset storage space by using the device tag and the current time as names, and store the target failure data in the folder.

In an exemplary embodiment of the disclosure, based on the foregoing scheme, the data collection module 420 may be configured to perform compression processing on the folder to control the size of the target failure data.

In an exemplary embodiment of the present disclosure, based on the foregoing scheme, the tag obtaining module 410 may be configured to receive fault alarm data sent by a device, and write the fault alarm data into the fault alarm data pool.

For details which are not disclosed in the embodiments of the apparatus of the present disclosure, please refer to the embodiments of the above-mentioned fault data processing method of the present disclosure for the details which are not disclosed in the embodiments of the apparatus of the present disclosure.

It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.

In addition, in an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above fault data processing method is also provided.

As will be appreciated by one skilled in the art, aspects of the present disclosure may be embodied as a system, method or program product. Accordingly, various aspects of the present disclosure may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.

An electronic device 500 according to such an embodiment of the present disclosure is described below with reference to fig. 5. The electronic device 500 shown in fig. 5 is only an example and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 5, the electronic device 500 is embodied in the form of a general purpose computing device. The components of the electronic device 500 may include, but are not limited to: the at least one processing unit 510, the at least one memory unit 520, a bus 530 connecting various system components (including the memory unit 520 and the processing unit 510), and a display unit 540.

Wherein the storage unit stores program code that is executable by the processing unit 510 to cause the processing unit 510 to perform steps according to various exemplary embodiments of the present disclosure as described in the above section "exemplary methods" of this specification. For example, the processing unit 510 may execute step S110 as shown in fig. 1: reading target alarm data in a fault alarm data pool, and determining a corresponding equipment tag according to the target alarm data; s120: calling a corresponding data collection interface according to the equipment label to collect data, and storing the collected target fault data in a preset storage space; s130: generating a storage path corresponding to the target fault data according to the position of the target fault data in the preset storage space; s140: and determining a corresponding processing party according to the equipment tag, and sending the storage path to the processing party so that the processing party reads the target fault data through the storage path.

As another example, the electronic device may implement the steps shown in FIG. 2.

The storage unit 520 may include readable media in the form of volatile storage units, such as a random access memory unit (RAM)521 and/or a cache memory unit 522, and may further include a read only memory unit (ROM) 523.

The storage unit 520 may also include a program/utility 524 having a set (at least one) of program modules 525, such program modules 525 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

Bus 530 may be one or more of any of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

The electronic device 500 may also communicate with one or more external devices 570 (e.g., keyboard, pointing device, Bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 500, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 500 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interfaces 550. Also, the electronic device 500 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 560. As shown, the network adapter 560 communicates with the other modules of the electronic device 500 over the bus 530. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 500, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the present disclosure may also be implemented in the form of a program product comprising program code for causing a terminal device to perform the steps according to various exemplary embodiments of the present disclosure described in the "exemplary methods" section above of this specification, when the program product is run on the terminal device.

Furthermore, an exemplary embodiment of the present disclosure provides a program product for implementing the above method, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

Furthermore, the above-described figures are merely schematic illustrations of processes included in methods according to exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is to be limited only by the terms of the appended claims.

Claims

1. A method of fault data processing, the method comprising:

2. The method of claim 1, wherein prior to performing data collection, the method further comprises:

3. The method of claim 1, wherein the invoking the corresponding data collection interface for data collection according to the device tag comprises:

4. The method of claim 1, further comprising:

5. The method according to claim 1, wherein storing the collected target fault data in a preset storage space comprises:

6. The method of claim 5, wherein after storing the target failure data in the folder, the method further comprises:

and compressing the folder to control the size of the target fault data.

7. The method of claim 1, wherein prior to reading target alarm data in a pool of fault alarm data, the method further comprises:

8. A fault data processing apparatus, comprising:

9. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the fault data processing method according to any one of claims 1 to 7.

10. An electronic device, comprising:

a processor; and

memory for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the fault data processing method of any of claims 1 to 7.