CN111581002A - Automatic failure reporting method, device and equipment for server failure - Google Patents

Abstract

The application relates to a method, a device and equipment for automatically reporting fault of a server fault. Wherein the method comprises: when the server is determined to have a fault, creating an event record for recording relevant information of the fault event of the server; collecting server logs in the running process of a fault server based on the event records; and reporting faults based on the event records and the target log. According to the arrangement, the problem of the traditional fault reporting method (fault reporting by an artificial customer service hot line) can be solved based on the thought and the method for automatically collecting the logs remotely, so that the fault reporting efficiency is greatly improved, the labor cost is reduced, in addition, the fault reporting method can be based on the mode that the distributed file storage is linked with the url, the log url is uploaded only through the mail during fault reporting, the log file is not required to be uploaded, the problem of log size limitation uploading of servers of different brands is solved, and therefore the technical scheme has high practicability.

Description

Automatic failure reporting method, device and equipment for server failure

technical field

The present application relates to the field of computer technology, and in particular, to an automatic fault reporting method, device and device for server faults.

Background technique

The server provides computing or application services for other clients (such as PCs, smartphones, ATMs and other terminals, and even large equipment such as train systems) in the network. Generally speaking, servers have the ability to respond to service requests, undertake services, and guarantee services. ability. However, during the operation of the server, it is inevitable that hardware failures will occur. At this time, the administrator needs to report the failure to the relevant maintenance personnel immediately, so as to carry out fault diagnosis and maintenance.

At present, when the server fails, the fault is usually reported manually by dialing the server repair hotline. During the fault reporting process, it is necessary to manually provide server-related information and upload server logs, and then the relevant personnel will diagnose based on the provided information and logs. Feedback the diagnosis results and provide on-site maintenance if necessary. However, the method of manually reporting faults is time-consuming and labor-intensive, especially in medium and large Internet companies with a large number of servers, the manual reporting method requires high labor costs and is inefficient.

SUMMARY OF THE INVENTION

The present application provides an automatic fault reporting method, device and device for server faults, so as to solve the problems of high labor cost and low efficiency in the existing fault reporting methods.

The above-mentioned purpose of the present application is achieved through the following technical solutions:

In a first aspect, an embodiment of the present application provides an automatic fault reporting method for a server fault, including:

When it is determined that the server fails, an event record is created; the event record is used to record the relevant information of the server failure event;

Collect the target log based on the event record; the target log is the server log in the running process of the faulty server;

A fault is reported based on the event record and the target log.

Optionally, the relevant information of the server failure event includes one or more of the following contents: serial number, server brand and model, failure type, number of failed parts, failure reporting date, and problem description.

Optionally, the creating an event record includes:

Based on the configuration management database CMDB, read the pre-stored configuration information of the faulty server;

Create an event record based on the actual situation of the fault event.

Optionally, the fault reporting based on the event record and the target log includes:

Perform distributed file storage on the target log, and generate a corresponding log url link;

The event record and the log url link are sent to maintenance personnel to report faults; the maintenance personnel can download the target log based on the log url link after viewing the event record.

Optionally, sending the event record and the log url link to maintenance personnel to report faults, including:

Send the event record and the log url link to the preset technical support mailbox in the form of an email attachment to report the fault.

In a second aspect, an embodiment of the present application also provides an automatic fault reporting device for a server fault, including:

an event creation module for creating an event record when it is determined that a server failure occurs; the event record is used to record the relevant information of the server failure event;

A log collection module, configured to collect target logs based on the event records; the target logs are server logs in the running process of the faulty server;

A fault reporting module, configured to report faults based on the event record and the target log.

Optionally, the relevant information of the server failure event includes one or more of the following contents: serial number, server brand and model, failure type, number of failed parts, failure reporting date, and problem description.

Optionally, the event creation module includes:

The reading unit is used to read the pre-stored configuration information of the faulty server based on the configuration management database CMDB;

Create a unit, which is used to create an event record based on the actual situation of the fault event.

Optionally, the fault reporting module includes:

a storage unit for performing distributed file storage on the target log, and generating a corresponding log url link;

The sending unit is configured to send the event record and the log url link to maintenance personnel to report faults; the maintenance personnel can download the target log based on the log url link after viewing the event record.

In a third aspect, an embodiment of the present application also provides an automatic fault reporting device for server faults, including:

a memory and a processor connected to the memory;

The memory is used to store a program, and the program is at least used to execute the above-mentioned automatic fault reporting method for server failure;

The processor is configured to call and execute the program stored in the memory.

The technical solutions provided by the embodiments of the present application may include the following beneficial effects:

In the technical solutions provided by the embodiments of the present application, when it is determined that a server failure occurs, an event record is first created to record the relevant information of the server failure event, and then based on the event record, the server operation process related to this failure is collected. Server logs, and finally automatic fault reporting based on event records and server logs. In this way, based on the idea and method of remote automatic log collection, the problems existing in the traditional method of reporting faults (manual customer service hotline reporting) can be overcome, thereby greatly improving the efficiency of reporting faults and reducing labor costs.

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

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description serve to explain the principles of the application.

1 is a schematic flowchart of an automatic fault reporting method for a server fault provided by an embodiment of the present application;

2 is a schematic structural diagram of an automatic fault reporting device for a server fault provided by an embodiment of the present application;

FIG. 3 is a schematic structural diagram of an automatic fault reporting device for a server fault provided by an embodiment of the present application.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. Where the following description refers to the drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the illustrative examples below are not intended to represent all implementations consistent with this application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as recited in the appended claims.

At present, when a hardware failure occurs on a server, the failure is usually reported manually by calling the server repair hotline. During the failure reporting process, it is necessary to manually provide server-related information (including machine model, failure description, serial number, and the actual location of the machine, etc. ) and upload the server log, and then the relevant personnel will diagnose based on the information and logs provided and feedback the diagnosis results by phone and email, and provide on-site maintenance if necessary.

Disadvantages of the above approach include:

① Manual reporting of obstacles is time-consuming and labor-intensive, and the efficiency is low. Taking the manual fault reporting process when a server device fails as an example, the time spent includes: calling customer service (about 1 minute) - connecting to manual service and providing fault reporting information (about 2-4 minutes) - collecting Log and upload the log (about 4 minutes) - feedback the diagnosis results (about 1-10 minutes), the whole process takes about 8-19 minutes;

Further, with the scale of tens of thousands or even hundreds of thousands of servers of medium and large Internet companies, if relying on the method of manual fault reporting, in order to ensure timely processing, a large amount of labor costs will need to be added, and the efficiency is also very low.

②The size limit of the fault report log uploaded by different brands of servers is different. If the log is too large, additional repair time will be added. For example, the HP (Hewlett-Packard) server upload log requirement cannot exceed 20M, that is to say, when the log size exceeds 20M, it will not be able to be uploaded directly through email, and the customer service needs to provide an additional FTP (File Transfer Protocol, File Transfer Protocol) link to upload manually, thus Improve the complexity of the process and increase the repair time.

Based on this, in order to solve the above problems, the embodiments of the present application provide an automatic fault reporting method for a server fault and a corresponding device and device. The following embodiments will describe in detail the specific implementations of the automatic fault reporting method, device and device of the present application.

Example

Please refer to FIG. 1. FIG. 1 is a schematic flowchart of an automatic fault reporting method for a server fault provided by an embodiment of the present application. As shown in Figure 1, the method includes the following steps:

S101: when it is determined that a server failure occurs, create an event record; the event record is used to record relevant information of a server failure event;

It should be noted that, for the method and process of judging whether the server has failed and what kind of failure has occurred, it can be selected from common methods in the prior art, and the specific method to be adopted can be determined according to actual needs. There is no restriction on this. The focus of this application is how to automatically report the failure after it is determined that the server has failed.

Specifically, when it is determined that a server failure occurs, an event record is automatically created, and the event record can be a log file or a file in other formats, so as to record relevant information in the server failure event, for example, including: serial number, server brand and model, failure Information such as type, number of faulty parts, fault report date and problem description.

In some embodiments, the process of creating an event record may include:

Based on the configuration management database CMDB, read the pre-stored configuration information of the faulty server;

Create an event record based on the actual situation of the fault event.

Among them, the Configuration Management Database (CMDB) contains all the relevant information of the configuration items (configuration items, CI) used by an organization's IT services and the relationship between these configuration items. The main tasks of the CMBD include: Proof of configuration items in the CMDB; data control to ensure that data can only be modified by designated personnel; state maintenance, including ensuring that the current state of any configuration item is always documented and kept up-to-date. For this embodiment, the CMDB contains the configuration information of all relevant servers in the entire system, so that the configuration information of the faulty server can be read based on the CMDB. After that, in order to facilitate the relevant maintenance personnel to diagnose and repair the fault of the server, the actual situation of the fault event can also be recorded, such as the type of fault, the number of faulty parts, the date of reporting the fault, and the location of the faulty server.

S102: Collect target logs based on the event records; the target logs are server logs during the operation of the faulty server;

Specifically, a server log is one or more log files automatically created and maintained by a server, which contain a list of activities performed by it. Take the log of the most typical web server as an example, which contains the history of page requests, such as client IP address, request date/time, requested web page, HTTP code, number of bytes provided, user agent, referring address, etc. . By viewing the server logs, technicians can understand the historical operating status of the server, so that they can determine whether the server has failed and the type of failure.

Further, in some embodiments, based on the adopted fault detection method, all logs of the faulty server may be queried, but only logs related to the above-mentioned event records are collected therefrom, thereby reducing the amount of log data to be processed subsequently.

S103: Report a fault based on the event record and the target log.

After the event record is created and the relevant logs of the faulty server are collected, the fault can be automatically reported.

The technical solutions provided by the embodiments of the present application may include the following beneficial effects:

In the technical solutions provided by the embodiments of the present application, when it is determined that a server failure occurs, an event record is first created to record the relevant information of the server failure event, and then based on the event record, the server operation process related to this failure is collected. Server logs, and finally automatic fault reporting based on event records and server logs. In this way, based on the idea and method of remote automatic log collection, the problems existing in the traditional method of reporting faults (manual customer service hotline reporting) can be overcome, thereby greatly improving the efficiency of reporting faults and reducing labor costs.

Further, in some embodiments, the process of reporting the failure may include:

Perform distributed file storage on the target log, and generate a corresponding log url link;

Send the event record and the log url link to the maintenance personnel to report faults; for example, the event record and the log url link can be sent to the preset technical support mailbox in the form of an email attachment to report the problem. The maintenance personnel can download the target log based on the log url link after viewing the event record.

Specifically, distributed file storage is a data storage technology. Compared with centralized file storage, it means that physical storage resources are not necessarily directly connected to local nodes, but are connected to nodes through computer networks. For example, the disk space on each machine in the enterprise is used through the network, and these scattered storage resources are formed into a virtual storage device, and the data is scattered and stored in all corners of the enterprise. And url (uniform resource locator, Uniform Resource Locator) is a representation method for specifying the location of information on the World Wide Web service program of the Internet. In this embodiment, the location of the distributed storage target log file is indicated through the url link.

That is to say, by adopting the method of distributed file storage and url linking, it is only necessary to upload the log url link by email when reporting a fault, without uploading the log file itself, so the problem of the limit of the upload log size of different brand servers can be solved. After receiving the email, the relevant maintenance personnel can download the server log by themselves through the url link to analyze and diagnose the server failure.

In order to provide a more comprehensive description of the technical solutions of the present application, corresponding to the automatic fault reporting methods for server faults provided by the above embodiments of the present application, the embodiments of the present application further provide an automatic fault reporting device for server faults.

Please refer to FIG. 2 , which is a schematic structural diagram of an automatic fault reporting device for a server fault according to an embodiment of the present application. As shown in Figure 2, the device includes the following structures:

The event creation module 21 is used to create an event record when it is determined that a server failure occurs; the event record is used to record the relevant information of the server failure event;

A log collection module 22, configured to collect target logs based on the event records; the target logs are the server logs during the operation of the faulty server;

The fault reporting module 23 is configured to report faults based on the event record and the target log.

Optionally, the relevant information of the server failure event includes one or more of the following contents: serial number, server brand and model, failure type, number of failed parts, failure reporting date, and problem description.

Optionally, the event creation module 21 includes:

The reading unit is used to read the pre-stored configuration information of the faulty server based on the configuration management database CMDB;

Create a unit, which is used to create an event record based on the actual situation of the fault event.

Optionally, the fault reporting module 23 includes:

a storage unit for performing distributed file storage on the target log, and generating a corresponding log url link;

The sending unit is configured to send the event record and the log url link to maintenance personnel to report faults; the maintenance personnel can download the target log based on the log url link after viewing the event record.

Specifically, the specific implementation manner of the function of each of the above functional modules can be implemented with reference to the corresponding content in the above-mentioned automatic fault reporting method for server faults, which will not be described in detail.

For a more comprehensive description of the technical solutions of the present application, corresponding to the automatic fault reporting method for server faults provided by the above embodiments of the present application, the embodiments of the present application further provide an automatic fault reporting device for server faults.

Please refer to FIG. 3 , which is a schematic structural diagram of an automatic fault reporting device for a server fault provided by an embodiment of the present application. As shown in Figure 3, the device includes the following structures:

a memory 31 and a processor 32 connected to the memory 31;

The memory 31 is used for storing a program, and the program is at least used to execute the above-mentioned automatic failure reporting method for server failure;

The processor 32 is used to call and execute the program stored in the memory 31 .

Specifically, the device may be a computer or a similar device, and the specific implementation of the functions of the program can be implemented by referring to the corresponding content in the above-mentioned automatic fault reporting method for server faults, which will not be described in detail.

It can be understood that, the same or similar parts in the above embodiments may refer to each other, and the content not described in detail in some embodiments may refer to the same or similar content in other embodiments.

It should be noted that, in the description of the present application, the terms "first", "second" and the like are only used for the purpose of description, and should not be construed as indicating or implying relative importance. Also, in the description of this application, unless otherwise specified, the meaning of "plurality" means at least two.

Any description of a process or method in the flowcharts or otherwise described herein may be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing a specified logical function or step of the process , and the scope of the preferred embodiments of the present application includes alternative implementations in which the functions may be performed out of the order shown or discussed, including performing the functions substantially concurrently or in the reverse order depending upon the functions involved, which should It is understood by those skilled in the art to which the embodiments of the present application belong.

It should be understood that various parts of this application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented by any one or a combination of the following techniques known in the art: Discrete logic circuits, application specific integrated circuits with suitable combinational logic gates, Programmable Gate Arrays (PGA), Field Programmable Gate Arrays (FPGA), etc.

Those skilled in the art can understand that all or part of the steps carried by the methods of the above embodiments can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, and the program can be stored in a computer-readable storage medium. When executed, one or a combination of the steps of the method embodiment is included.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing module, or each unit may exist physically alone, or two or more units may be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. If the integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may also be stored in a computer-readable storage medium.

The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, and the like.

In the description of this specification, description with reference to the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples", etc., mean specific features described in connection with the embodiment or example , structure, material or feature is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

Although the embodiments of the present application have been shown and described above, it should be understood that the above embodiments are exemplary and should not be construed as limitations to the present application. Embodiments are subject to variations, modifications, substitutions and variations.

Claims (10)

1. the automatic fault reporting method of a server failure, is characterized in that, comprises: When it is determined that the server fails, an event record is created; the event record is used to record the relevant information of the server failure event; Collect the target log based on the event record; the target log is the server log in the running process of the faulty server; A fault is reported based on the event record and the target log. 2. The method according to claim 1, wherein the relevant information of the server failure event comprises one or more of the following: serial number, server brand and model, failure type, number of failed parts, failure reporting date and Problem Description. 3. The method of claim 1, wherein the creating an event record comprises: Based on the configuration management database CMDB, read the pre-stored configuration information of the faulty server; Create an event record based on the actual situation of the fault event. 4. The method according to claim 1, wherein the reporting an error based on the event record and the target log comprises: Perform distributed file storage on the target log, and generate a corresponding log url link; The event record and the log url link are sent to maintenance personnel to report faults; the maintenance personnel can download the target log based on the log url link after viewing the event record. 5. The method according to claim 5, wherein the sending the event record and the log url link to maintenance personnel to report faults, comprising: Send the event record and the log url link to the preset technical support mailbox in the form of an email attachment to report the fault. 6. An automatic fault reporting device for server failure, characterized in that, comprising: an event creation module for creating an event record when it is determined that a server failure occurs; the event record is used to record the relevant information of the server failure event; A log collection module, configured to collect target logs based on the event records; the target logs are server logs in the running process of the faulty server; A fault reporting module, configured to report faults based on the event record and the target log. 7. The device according to claim 6, wherein the relevant information of the server failure event includes one or more of the following: serial number, server brand and model, failure type, number of failed parts, failure reporting date and Problem Description. 8. The apparatus according to claim 6, wherein the event creation module comprises: The reading unit is used to read the pre-stored configuration information of the faulty server based on the configuration management database CMDB; Create a unit, which is used to create an event record based on the actual situation of the fault event. 9. The device according to claim 6, wherein the fault reporting module comprises: a storage unit for performing distributed file storage on the target log, and generating a corresponding log url link; The sending unit is configured to send the event record and the log url link to maintenance personnel to report faults; the maintenance personnel can download the target log based on the log url link after viewing the event record. 10. An automatic fault reporting device for server failure, characterized in that, comprising: a memory and a processor connected to the memory; The memory is used for storing a program, and the program is at least used to execute the automatic failure reporting method for a server failure according to any one of claims 1-5; The processor is configured to call and execute the program stored in the memory.

Images