CN111581002A

CN111581002A - Automatic fault reporting method, device and equipment for server fault

Info

Publication number: CN111581002A
Application number: CN202010355761.4A
Authority: CN
Inventors: 朱晶熙; 童星
Original assignee: Shanghai Zhongtongji Network Technology Co Ltd
Current assignee: Shanghai Zhongtongji Network Technology Co Ltd
Priority date: 2020-04-29
Filing date: 2020-04-29
Publication date: 2020-08-25

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 fault reporting method, device and equipment for server fault

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, and a device for automatically reporting a server fault.

Background

The server provides computing or application services for other clients (such as terminals like a PC, a smart phone, an ATM and the like, and even large equipment like a train system and the like) in a network, and generally, the server has the capability of bearing response service requests, bearing services and guaranteeing services. However, in the operation process of the server, hardware faults occur inevitably, and at this time, a manager needs to report faults to relevant maintenance personnel in real time so as to perform fault diagnosis and maintenance.

At present, when a server fails, manual fault reporting is usually performed by manually dialing a server fault reporting hot line, relevant information of the server needs to be manually provided and a server log needs to be uploaded in the fault reporting process, and then relevant personnel diagnose and feed back a diagnosis result according to the provided information and log, and get-on maintenance is provided when necessary. However, the manual fault reporting mode is time-consuming and labor-consuming, and particularly in medium and large-sized internet enterprises with a large number of servers, the manual fault reporting mode requires high labor cost and low efficiency.

Disclosure of Invention

The application provides an automatic fault reporting method, device and equipment for server faults, and aims to solve the problems of high labor cost and low efficiency in the existing fault reporting mode.

The above object of the present application is achieved by 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 the server is determined to be out of order, creating an event record; the event record is used for recording relevant information of a server fault event;

collecting a target log based on the event record; the target log is a server log in the running process of the fault server;

and reporting faults based on the event records and the target log.

Optionally, the information related to the server failure event includes one or more of the following: serial number, server make and model, failure type, number of failed components, failure date, and problem description.

Optionally, the creating an event record includes:

reading pre-stored configuration information of a fault server based on a Configuration Management Database (CMDB);

and creating an event record by combining the actual situation of the fault event.

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

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

sending the event record and the log url link to a maintenance worker so as to report an obstacle; and after viewing the event record, the maintenance personnel can download the target log based on the log url link.

Optionally, the sending the event record and the log url link to a service person for reporting an obstacle includes:

and sending the event record and the log url link to a preset technical support mailbox in a mail attachment mode so as to report faults.

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

the event creating module is used for creating an event record when the server is determined to have a fault; the event record is used for recording relevant information of a server fault event;

a log collection module for collecting a target log based on the event record; the target log is a server log in the running process of the fault server;

and the fault reporting module is used for reporting faults based on the event records and the target log.

Optionally, the event creating module includes:

the reading unit is used for reading the configuration information of the fault server stored in advance based on a configuration management database CMDB;

and the creating unit is used for creating an event record by combining the actual situation of the fault event.

Optionally, the fault reporting module includes:

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

the sending unit is used for sending the event record and the log url link to a maintenance worker so as to report faults; and after viewing the event record, the maintenance personnel can download the target log based on the log url link.

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

a memory and a processor coupled to the memory;

the memory is used for storing a program, and the program is at least used for executing the automatic fault reporting method for the server fault;

the processor is used for calling and executing the program stored in the memory.

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

according to the technical scheme provided by the embodiment of the application, when the server is determined to have a fault, an event record is firstly created and used for recording relevant information of the fault event of the server, then a server log relevant to the fault in the running process of the server is collected based on the event record, and finally automatic fault reporting can be carried out based on the event record and the server log. By the arrangement, the problems of the traditional fault reporting method (fault reporting by a manual 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, and the labor cost is reduced.

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 application.

Drawings

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

Fig. 1 is a schematic flowchart illustrating an automatic fault reporting method for a server fault according to an embodiment of the present disclosure;

fig. 2 is a schematic structural diagram of an automatic fault reporting apparatus for a server fault according to an embodiment of the present disclosure;

fig. 3 is a schematic structural diagram of an automatic fault reporting apparatus for a server fault according to an embodiment of the present disclosure.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

At present, when a server has a hardware fault, manual fault reporting is usually performed by manually dialing a server fault reporting hot line, and in the fault reporting process, relevant information (including a machine model, a fault description, a serial number, an actual position where a machine is located, and the like) of the server needs to be manually provided and server logs are uploaded, and then relevant personnel perform diagnosis according to the provided information and logs and feed back a diagnosis result in the form of a telephone and an email, and provide home service maintenance if necessary.

The disadvantages of the above method include:

the manual fault reporting is time-consuming and labor-consuming, and the efficiency is low. Taking the manual fault reporting process performed when 1 server device fails as an example, the time spent includes: dialing a customer service call (about 1 minute), switching on manual service, providing fault information (about 2-4 minutes), collecting and uploading logs (about 4 minutes), feeding back a diagnosis result (about 1-10 minutes), wherein the whole process takes about 8-19 minutes;

furthermore, with the scale of tens of thousands or even hundreds of thousands of servers of medium and large-sized internet companies, if a manual fault reporting mode is relied on, in order to ensure timely processing, a large amount of labor cost needs to be increased, and the efficiency is very low.

Secondly, the size limit of fault log uploaded by the servers of different brands is different, and extra repair time is increased when the log is too large. For example, the log uploading requirement of the HP (hewlett packard) server cannot exceed 20M, that is, when the log size exceeds 20M, the log cannot be uploaded directly through a mail, and an FTP (File Transfer Protocol) link needs to be additionally provided by a customer service for manual uploading, so that the process complexity is improved, and the repair time is increased.

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

Examples

Referring to fig. 1, fig. 1 is a schematic flowchart illustrating an automatic fault reporting method for a server fault according to an embodiment of the present disclosure. As shown in fig. 1, the method comprises the steps of:

s101: when the server is determined to be out of order, creating an event record; the event record is used for recording relevant information of a server fault event;

it should be noted that, as to the method and the process for determining whether the server fails and what kind of failure occurs, a selection may be made from common methods in the prior art, and what kind of method is specifically adopted may be determined according to actual needs, which is not limited in the present application. The method and the device have the advantages that the method and the device are focused on how to automatically report faults after the server is determined to be in fault.

Specifically, when it is determined that the server fails, an event record is automatically created, where the event record may be a log file or a file in another format, so as to record relevant information in the event of the server failure, including: serial number, server brand and model, fault type, fault component number, failure report date, problem description and the like.

In some embodiments, creating the event record may include:

Wherein, the Configuration Management Database (CMDB) contains all relevant information of Configuration Items (CIs) used by IT services of an organization and relationships among the Configuration items, and the main tasks of the CMBD include: a certification of the configuration items contained in the CMDB; controlling the data to ensure that the data can only be modified by appointed personnel; state maintenance, including ensuring that the current state of any configuration item is always recorded and kept updated. For the present embodiment, the CMDB contains configuration information of all relevant servers in the entire system, so that the configuration information of a failed server can be read based on the CMDB. Afterwards, in order to facilitate the relevant maintenance personnel to diagnose and maintain the fault of the server, the actual condition of the fault event, such as the fault type, the number of fault components, the fault reporting date, the location of the fault server, and the like, can also be recorded.

S102: collecting a target log based on the event record; the target log is a server log in the running process of the fault server;

in particular, a server log (server log) is one or more log files that are automatically created and maintained by the server, including a list of activities that it performs. Taking the log of the most typical web server as an example, the log contains the history of the page requests, including, for example, the client IP address, the request date/time, the requested web page, the HTTP code, the number of bytes provided, the user agent, the reference address, etc. By looking at the server log, a technician can learn the historical operating status of the server, and can determine whether the server has failed and the type of failure.

Further, in some embodiments, based on the failure detection method adopted, all logs of the failed server can be queried, but only the logs related to the event records are collected, so that the amount of log data needing to be processed subsequently is reduced.

S103: and reporting faults based on the event records and the target log.

And when an event record is created and a related log of a fault server is collected, automatic fault reporting can be carried out.

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

sending the event record and the log url link to a maintenance worker so as to report an obstacle; for example, the event record and the log url link may be sent to a preset technical support mailbox in the form of a mail attachment so as to report an error; and after viewing the event record, the maintenance personnel can download the target log based on the log url link.

In particular, distributed file storage is a data storage technology, and as opposed to centralized file storage, refers to physical storage resources that are not necessarily directly connected to local nodes, but are connected to nodes via a computer network. For example, data is stored in a distributed manner in each corner of an enterprise by using disk space on each machine in the enterprise via a network and configuring these distributed storage resources as a virtual storage device. And url (uniform resource locator) is a representation method for specifying the location of information on a web service on the internet. In this embodiment, the location of the target log file of the distributed storage is indicated by the url link.

That is to say, by adopting the mode of linking distributed file storage and url, failure reporting only needs to be linked by the mail upload log url without uploading the log file, so that the problem of size limitation of the log uploaded by different brands of servers can be solved. After receiving the mail, the related maintenance personnel can automatically download the server log through the url link so as to analyze and diagnose the server fault.

In order to more fully explain the technical solution of the present application, in correspondence to the automatic fault reporting method for a server fault provided in the foregoing embodiment of the present application, an embodiment of the present application further provides an automatic fault reporting device for a server fault.

Referring to fig. 2, fig. 2 is a schematic structural diagram of an automatic fault reporting device for a server fault according to an embodiment of the present disclosure. As shown in fig. 2, the apparatus includes the following structure:

an event creating module 21 for creating an event record when it is determined that the server has failed; the event record is used for recording relevant information of a server fault event;

a log collection module 22 for collecting a target log based on the event record; the target log is a server log in the running process of the fault server;

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

Optionally, the event creating module 21 includes:

Optionally, the fault reporting module 23 includes:

Specifically, the specific implementation manner of the function of each functional module may be implemented by referring to corresponding contents in the automatic fault reporting method for server failure, which is not described in detail herein.

Referring to fig. 3, fig. 3 is a schematic structural diagram of an automatic fault reporting apparatus for a server fault according to an embodiment of the present disclosure. As shown in fig. 3, the apparatus includes the following structure:

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

the memory 31 is used for storing a program for executing at least the above-described automatic failure reporting method for a 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 the like, wherein the function of the program may be implemented by referring to the corresponding content in the above-mentioned automatic fault reporting method for the server fault, which is not described in detail herein.

It is understood that the same or similar parts in the above embodiments may be mutually referred to, and the same or similar parts in other embodiments may be referred to for the content which is not described in detail in some embodiments.

It should be noted that, in the description of the present application, the terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Further, in the description of the present application, the meaning of "a plurality" means at least two unless otherwise specified.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.

It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the 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, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.

It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.

In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.

The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.

In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above 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 embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.

Claims

1. An automatic fault reporting method for server faults is characterized by comprising the following steps:

and reporting faults based on the event records and the target log.

2. The method of claim 1, wherein the information related to the server failure event comprises one or more of: serial number, server make and model, failure type, number of failed components, failure date, and problem description.

3. The method of claim 1, wherein creating the event record comprises:

4. The method of claim 1, wherein the troubleshooting based on the event record and the target log comprises:

5. The method of claim 5, wherein sending the event record and the log url link to a service person for troubleshooting comprises:

6. An automatic fault reporting device for server faults is characterized by comprising:

7. The apparatus of claim 6, wherein the information related to the server failure event comprises one or more of: serial number, server make and model, failure type, number of failed components, failure date, and problem description.

8. The apparatus of claim 6, wherein the event creation module comprises:

9. The apparatus of claim 6, wherein the fault reporting module comprises:

10. An automatic fault reporting device for server failure, comprising:

a memory and a processor coupled to the memory;

the memory for storing a program for at least performing the method of automatic fault reporting of a server failure according to any one of claims 1 to 5;