Server alarm information review method and device

Abstract

The application can be used in the technical field of big data technology application in finance, and provides a server alarm information review method and device, the server alarm information review method comprises the following steps: in response to the received alarm information, acquiring the client identity data stored in the local; acquiring the page source code corresponding to the alarm information according to the client identity data; and reviewing the alarm information according to the page source code. The server alarm information review method and device provided by the application can review the server alarm information, thereby greatly reducing the workload of the server device state monitoring personnel, and saving the enterprise cost.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of server state monitoring, and particularly relates to a server alarm information review method and device. BACKGROUND

[0002] The server baseboard management controller (BMC) can perform firmware upgrade, view machine equipment and other operations on the server in the state that the server is not started. Its main functions are as follows:

[0003] (1) Provide IPMI v1.5 LAN messages for remote system management, including system state monitoring; bottom plate control such as restart, power supply, power-off; FRU information, a small amount of SEL information entry; BIOS protection and selection.

[0004] (2) Provide IPMI v1.5 messages for local system manageability.

[0005] (3) Use MD5 signature for LAN messages to ensure the security of remote connection. MD5 signature plus private password can well protect the system from external invasion.

[0006] (4) BIOS or OS can report 'push' warnings as SNMP Traps and report serious events through LAN.

[0007] (5) Independently perform system health monitoring and take corrective action on serious events.

[0008] (6) LAN warning.

[0009] In the prior art, server device alarms are mainly alarmed by the server baseboard management controller. Specifically, the baseboard management controller will first feed back the exception to the out-of-band management system of the server manufacturer after detecting the server exception, then the out-of-band management system will forward the alarm to the centralized monitoring platform, and finally the centralized monitoring platform will display and push the alarm to the server device state supervision personnel. However, due to the characteristics of many and miscellaneous server devices in large data centers, the baseboard management controller alarm is usually not accurate, which brings a lot of useless device warnings to the server device state supervision personnel, thereby bringing a lot of unnecessary work to the personnel. Therefore, an implementation method of a device exception alarm review mechanism is proposed. SUMMARY

[0010] The application can be applied to the technical field of big data technology in the financial field, and can also be applied to any field other than the financial field. The server alarm information review method and device provided by the application can review server alarm information, thereby greatly reducing the workload of server device state monitoring personnel and saving enterprise costs.

[0011] To solve the technical problems in the background art, the application provides the following technical solutions.

[0012] In a first aspect, the application provides a server alarm information review method, which includes the following steps:

[0013] In response to the received alarm information, the client identity data stored locally is obtained.

[0014] According to the client identity data, the page source code corresponding to the alarm information is obtained.

[0015] According to the page source code, the alarm information is reviewed.

[0016] In an embodiment, the obtaining of the client identity data stored locally includes the following steps:

[0017] According to the login information corresponding to the client identity data, the client identity data is obtained.

[0018] In an embodiment, the obtaining of the page source code corresponding to the alarm information according to the client identity data includes the following steps:

[0019] According to the client identity data, the session information of the client is determined.

[0020] According to the session information, the page source code is crawled.

[0021] In an embodiment, the review of the alarm information according to the page source code includes the following steps:

[0022] According to the page source code, the device state label corresponding to the page source code is determined.

[0023] According to the device state label, the alarm information is reviewed.

[0024] In a second aspect, the application provides a server alarm information review device, which includes the following modules:

[0025] An identity data acquisition module is configured to obtain client identity data stored locally in response to received alarm information.

[0026] A page source code acquisition module is configured to obtain page source code corresponding to the alarm information according to the client identity data.

[0027] The alarm information review module is configured to review the alarm information according to the page source code.

[0028] In an embodiment, the identity data acquisition module comprises:

[0029] The identity data acquisition unit is configured to acquire the client identity data according to the login information corresponding to the client identity data.

[0030] In an embodiment, the page source code acquisition module comprises:

[0031] The conversation information acquisition unit is configured to determine the conversation information of the client according to the client identity data.

[0032] The page source code crawling unit is configured to crawl the page source code according to the conversation information.

[0033] In an embodiment, the alarm information review module comprises:

[0034] The state label determination unit is configured to determine the device state label corresponding to the page source code according to the page source code.

[0035] The alarm information review unit is configured to review the alarm information according to the device state label.

[0036] In a third aspect, the present application provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the server alarm information review method when executing the program.

[0037] In a fourth aspect, the present application provides a computer readable storage medium having a computer program stored thereon, wherein the computer program is executable by a processor to implement the steps of the server alarm information review method.

[0038] From the above description, the embodiment of the application provides a server alarm information review method and device, first, in response to the received alarm information, the client identity data stored on the server is acquired; then, the page source code of the server is acquired according to the client identity data; finally, the server alarm information is reviewed according to the page source code. The application aims at the problem of baseboard management controller BMC alarm false alarm, and increases a secondary review mechanism, that is, after the centralized monitoring platform receives the device out-of-band alarm information, the device state label in the device BMC address interface is reviewed through the device state label in the device BMC address interface after a few seconds of delay, whether the BMC alarm is accurate, and only after the review and verification, the alarm is displayed and forwarded to the server device state monitoring personnel. The server alarm information review method and device provided by the embodiment of the application can review the server alarm information, thereby greatly reducing the workload of the server device state monitoring personnel, and further saving the enterprise cost. BRIEF DESCRIPTION OF DRAWINGS

[0039] In order to more clearly illustrate the technical solutions in the embodiments of the application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or the prior art description. Obviously, the drawings in the following description are some embodiments of the application, and for those skilled in the art, other drawings can also be obtained without creative labor.

[0040] Figure 1 It is a first structure schematic diagram of the server alarm information review system of the embodiment of the application.

[0041] Figure 2 It is a second structure schematic diagram of the server alarm information review system of the embodiment of the application.

[0042] Figure 3 It is a flowchart of the server alarm information review method in the embodiment of the application.

[0043] Figure 4 It is a flowchart of step 101 in the embodiment of the application.

[0044] Figure 5 It is a flowchart of step 200 in the embodiment of the application.

[0045] Figure 6 It is a flowchart of step 300 in the embodiment of the application.

[0046] Figure 7 It is a flowchart of the server alarm information review method in the specific embodiment of the application.

[0047] Figure 8 It is a thinking flowchart of the server alarm information review method in the specific embodiment of the application.

[0048] Figure 9 Block diagram of the server alarm information review device in the embodiment of the present application;

[0049] Figure 10 Block diagram of the identity data acquisition module 10 in the embodiment of the present application;

[0050] Figure 11 Block diagram of the page source code acquisition module 20 in the embodiment of the present application;

[0051] Figure 12 Block diagram of the alarm information review module 30 in the embodiment of the present application;

[0052] Figure 13 Structure schematic diagram of the electronic device in the embodiment of the present application. DETAILED DESCRIPTION

[0053] In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present application.

[0054] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system or a computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0055] It should be noted that the terms "comprising" and "having" and any variations thereof in the specification and claims of the present application and the above drawings are intended to cover not exclusive inclusion, for example, a process, method, system, product or device containing a series of steps or units does not have to be limited to those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0056] The present application also provides a server alarm information review system, referring to Figure 1 The system can be a server A1, which can be in communication connection with a plurality of alarm information receiving devices B1. The server A1 can also be in communication connection with a plurality of databases respectively, or as shown inFigure 2 As shown, these databases can also be set in the server A1. Among them, the alarm information receiving device B1 is used to receive the alarm information of the server in real time. After receiving the alarm information, the server A1 reviews the alarm information. It should be noted that the server alarm information review system should be on the server side, and preferably, it can be built outside the server monitored by the alarm information, or it can be realized as a module or program inside the server, and the present application is not limited thereto.

[0057] It can be understood that the client C1 can include a smart phone, a tablet electronic device, a network set-top box, a portable computer, a desktop computer, a personal digital assistant (PDA), a vehicle-mounted device, a smart wearable device, etc. Among them, the smart wearable device can include smart glasses, a smart watch, a smart bracelet, etc.

[0058] In actual application, the part of reviewing the alarm information of the server can be executed on the server A1 side as described above, i.e., the architecture as shown in Figure 1 or Figure 2 The architecture can also complete all operations in the client C1 device. Specifically, it can be selected according to the processing capacity of the client device and the limitation of the user's use scene, etc. The present application is not limited thereto. If all operations are completed in the client device, the client device can also include a processor for reviewing the alarm information of the server and the like.

[0059] The above-mentioned client C1 device can have a communication module (i.e., a communication unit) and can be communicatively connected with a remote server to realize data transmission with the server. The server can include a server for reviewing the alarm information of the server, and in other implementation scenarios, it can also include a server of an intermediate platform, for example, a server of a third-party server platform communicatively connected with the server for reviewing the alarm information of the server. The server can include a single computer device, or a server cluster composed of multiple servers, or a server structure of a distributed device.

[0060] The server and the client device can use any suitable network protocol for communication, including a network protocol not yet developed at the filing date of the present application. The network protocol can include, for example, a TCP / IP protocol, a UDP / IP protocol, an HTTP protocol, an HTTPS protocol, etc. Of course, the network protocol can also include a RPC protocol (Remote Procedure Call Protocol) used on the above-mentioned protocol, a REST protocol (Representational State Transfer), etc.

[0061] It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other without conflict. The present application will be described in detail below with reference to the drawings and in combination with the embodiments.

[0062] The embodiment of the present application provides a specific implementation of a server alarm information review method, referring to Figure 3 The method specifically includes the following contents:

[0063] Step 100: In response to the received alarm information, the client identity data stored locally is obtained.

[0064] There are many false alarms of common server alarm information, for example, power state abnormal alarm, hard disk plug-in alarm, and the main reason for the false alarm of these two kinds of alarm information is the temporary communication abnormality, which has no actual effect on the normal work of the server. However, in the prior art, it is still pushed to the server device state monitoring personnel, which brings a lot of unnecessary attention to the relevant staff.

[0065] In the implementation of step 100, when receiving the alarm information of the server, the login information of the user is sent to the server, so as to obtain the identity data of the user stored on the server.

[0066] It should be noted that the actions performed by steps 100, 200 and 300 can be initiated by the server side, that is, a module can be set in the server monitored by the alarm information, and the module stores the program corresponding to the method contained in steps 100 to 300.

[0067] Step 200: Obtain the page source code corresponding to the alarm information according to the client identity data.

[0068] Specifically, a piece of code can be obtained through the html syntax rule and according to the client identity data, and the piece of code can display text, pictures and the like. The target code can be generated through the page source code, that is, the code that can be recognized by the computer. The page source code is also responsible for explaining the software, that is, explaining the writing of the software. It should be noted that the modification of the source code cannot change the generated target code. If the target code needs to be modified accordingly, it must be recompiled.

[0069] On the other hand, the page source code can be divided into dynamic source code, including: ASP, PHP, JSP,.NET, CGI and the like, and static source code, including: html page, Flash, JavaScript, VBScript and the like.

[0070] Step 300: Review the alarm information according to the page source code.

[0071] Specifically, information that can indicate whether the server has a real exception is found in the page source code, so that the server alarm information is screened, and false alarm information is filtered out.

[0072] From the above description, it can be known that the embodiment of the present application provides a server alarm information review method, which first acquires client identity data stored on a server in response to received alarm information, then acquires page source code of the server according to the client identity data, and finally reviews server alarm information according to the page source code. The present application aims at the problem of false alarm of a baseboard management controller (BMC), and adds a secondary review mechanism, that is, after a centralized monitoring platform receives out-of-band alarm information of a device, the device state tag in the feedback device BMC address interface is crawled after a delay of several seconds to review whether the BMC alarm is accurate, and only after the review and verification, the alarm is displayed and forwarded to a server device state monitoring personnel. The server alarm information review method provided by the embodiment of the present application can review server alarm information, thereby greatly reducing the workload of a server device state monitoring personnel, and further saving enterprise cost.

[0073] In an embodiment, referring to Figure 4 , the step 100 specifically includes:

[0074] Step 101: acquiring the client identity data according to login information corresponding to the client identity data.

[0075] Preferably, the client identity data can be Cookie data. Cookie data is a small text file, and is data stored on a local terminal of a user (usually encrypted) for identifying a user identity and performing Session tracking, and is information temporarily or permanently saved by a user client computer.

[0076] Further, a Web site can generate a unique ID for each visitor, and then save the ID in the form of a Cookie file on each user's machine. If a Web is accessed by using a browser, all the Cookie saved on the hard disk can be seen. Each file in this folder is a text file composed of "name / value" pairs, and another file saves information of all corresponding Web sites. Each Cookie file here is a simple and ordinary text file. Through the file name, it can be seen which Web site places the Cookie on the machine (of course, the site information is also saved in the file).

[0077] In step 101, Cookie is a small piece of text data no more than 4KB, which consists of a name (Name), a value (Value) and several optional attributes for controlling the validity period, security and usage range of Cookie. Among them:

[0078] (1) Name / Value: Set the name and corresponding value of Cookie. For authentication Cookie, the Value value includes the access token provided by the Web server.

[0079] (2) Expires attribute: Set the survival period of Cookie. There are two storage types of Cookie: session and persistence. When the Expires attribute is default, it is a session Cookie, which is only saved in the client memory and invalid when the user closes the browser; a persistent Cookie is saved in the user's hard disk until the survival period expires or the user directly clicks the "logout" button on the webpage to end the session.

[0080] (3) Path attribute: Defines the directory on the Web site that can access the Cookie.

[0081] (4) Domain attribute: Specifies the Web site or domain that can access the Cookie. The Cookie mechanism does not follow the strict same-origin policy, allowing a subdomain to set or get the Cookie of its parent domain. When implementing a single sign-on solution, the above characteristics of Cookie are very useful, but also increase the risk of Cookie attacks, such as attackers can launch session fixation attacks. Therefore, the browser prohibits setting.org,.com and other generic top-level domains, as well as second-level domain names registered under the country and regional top-level domains in the Domain attribute, to reduce the scope of attack.

[0082] (5) Secure attribute: Specifies whether to use HTTPS secure protocol to send Cookie. Using HTTPS secure protocol can protect the transmission of Cookie between the browser and the Web server from being stolen and tampered with. This method can also be used for Web site identity authentication, that is, during the HTTPS connection establishment phase, the browser will check the validity of the Web site's SSL certificate. However, due to compatibility reasons (such as some websites use self-signed certificates), when the SSL certificate is detected to be invalid, the browser does not immediately terminate the user's connection request, but displays a security risk message, and the user can still choose to continue accessing the site. Because many users lack security awareness, they may still connect to the website forged by the Pharming attack.

[0083] (6) HTTPOnly attribute: used to prevent client-side scripts from accessing cookies through the document.cookie attribute, helps to protect cookies from being stolen or tampered with by cross-site scripting attacks. However, the application of HTTPOnly still has limitations, some browsers can prevent client-side scripts from reading cookies, but allow write operations; in addition, most browsers still allow the XMLHTTP object to read the Set-Cookie header in the HTTP response.

[0084] Step 101, in implementation, sends user login information to the network address of the server through post or get method to obtain the cookie data of the user.

[0085] In an embodiment, referring to Figure 5 , step 200 further comprises:

[0086] Step 201: determining the session information of the client according to the client identity data;

[0087] Preferably, the session information comprises SessionID data, and step 200, in implementation, obtains the SessionID data according to the cookie data, and the SessionID data is stored in the server memory and the cookie of the client. When the user makes a request, the server compares the SessionID recorded in the cookie of the user with the SessionID in the server memory, so as to find the corresponding Session of the user for operation. In addition, the SessionID data has the following characteristics:

[0088] 1. Used to track the session of each user, identified by the SessionID generated by the server, used to distinguish users. The Session is stored in the memory of the server, and the SessionID is stored in the server memory and the cookie of the client.

[0089] 2. The SessionID object stores the attributes and configuration information required for a specific user session.

[0090] 3. When the user requests a Web page from the application, if the user does not have a session, the Web server will automatically create a SessionID object. When the session expires or is abandoned, the server will terminate the session. The most common use of the Session object is to store user preferences.

[0091] 4. If the user indicates that he does not like to view graphics, the information can be stored in the SessionID object. For details of using the SessionID object, the session state is only retained in the cookie-enabled browser.

[0092] Step 202: According to the dialogue information, the page source code is crawled.

[0093] Specifically, the page source code of the server can be crawled according to the SessionID data in the following four ways. Before crawling the content, the structure of the web page needs to be analyzed to find out where the required data is stored, so as to select the appropriate crawling method:

[0094] 1. Find the Ajax interface, find the parameters, request method, and then simulate it with the HTTP library; use the proxy package Fiddler / Charles to view the interface.

[0095] 2. Simulate browser execution, suitable for complex interface cases. For example, use Selenium, Splinter, Spynner, pyppeteer, PhantomJS, Splash, requests-html, etc. to achieve, and the most commonly used is Selenium.

[0096] 3. Directly extract JavaScript data, suitable for data contained in the results of HTML, which can be obtained using regular expressions.

[0097] 4. Simulate the execution of JavaScript. Suitable for having mastered some execution and encryption logic of JavaScript, such as using Selenium, PyExecJS, PyV8, js2py, etc.

[0098] In an embodiment, referring to Figure 6 , step 300 specifically includes:

[0099] Step 301: Determine the device state label corresponding to the page source code according to the page source code;

[0100] It can be understood that the device state label contains flag information indicating whether a real exception occurs in the server at the current time.

[0101] Step 302: Review the alarm information according to the device state label.

[0102] On the basis of step 301, the "real state" of the server at the current time can be known from the device state label, so that false alarm information can be filtered out, reducing the workload of the staff.

[0103] In a specific embodiment, the present application also provides a specific embodiment of a server alarm information review method, see Figure 7 and Figure 8 , specifically including the following.

[0104] The present method mainly helps to reduce the false alarm of bmc alarm, and reduce the workload of server device state monitoring personnel checking.

[0105] S1: send login information to the target address by post or get method to obtain the sessionid item of its cookie.

[0106] S2: obtain the page source code that needs to be crawled by bypassing the login interface by carrying the sessionid obtained in step S1.

[0107] S3: obtain the information that needs to be crawled by matching the label.

[0108] S4: review the server alarm information according to the crawled information.

[0109] In steps S1 to S2, first, an httpclient object is created, a login information form is submitted using the post method to complete login, the information after login is obtained using the get method, and then jsoup is called to parse the obtained page source code, and the information that needs to be crawled is obtained by matching the class using the getElementById method,

[0110] From the above description, the present application embodiment provides a server alarm information review method, first, in response to the received alarm information, the client identity data stored on the server is obtained; then, the page source code of the server is obtained according to the client identity data; finally, the server alarm information is reviewed according to the page source code. The present application aims at the problem of bmc alarm false alarm, and increases the secondary review mechanism, that is, after the centralized monitoring platform receives the device out-of-band alarm information, the device state label in the device bmc address interface is reviewed through the feedback device state label after a few seconds of delay, whether the bmc alarm is accurate, only after the review and verification, the alarm is displayed and forwarded to the server device state monitoring personnel. The server alarm information review method provided by the present application embodiment can review the server alarm information, thereby greatly reducing the workload of the server device state monitoring personnel, and further saving the enterprise cost.

[0111] Based on the same inventive concept, the embodiment of the present application further provides a server alarm information review device, which can be used to implement the method described in the above embodiment, as follows. Since the principle of solving problems of the server alarm information review device is similar to that of the server alarm information review method, the implementation of the server alarm information review device can be referred to the implementation of the server alarm information review method, and the repeated parts will not be described herein. The term "unit" or "module" used below can be a combination of software and / or hardware that can implement a predetermined function. Although the system described in the following embodiment is preferably implemented in software, the implementation of hardware or a combination of software and hardware is also possible and conceived.

[0112] The embodiment of the present application provides a specific implementation of a server alarm information review device capable of implementing a server alarm information review method, as follows Figure 9 , the server alarm information review device specifically includes the following contents:

[0113] An identity data acquisition module 10 is configured to acquire client identity data stored locally in response to received alarm information.

[0114] A page source code acquisition module 20 is configured to acquire page source code corresponding to the alarm information according to the client identity data.

[0115] An alarm information review module 30 is configured to review the alarm information according to the page source code.

[0116] In an embodiment, as shown in Figure 10 , the identity data acquisition module 10 includes:

[0117] An identity data acquisition unit 101 is configured to acquire the client identity data according to login information corresponding to the client identity data.

[0118] In an embodiment, as shown in Figure 11 , the page source code acquisition module 20 includes:

[0119] A conversation information acquisition unit 201 is configured to determine conversation information of the client according to the client identity data.

[0120] A page source code crawling unit 202 is configured to crawl the page source code according to the conversation information.

[0121] In an embodiment, as shown in Figure 12 , the alarm information review module 30 includes:

[0122] A state label determination unit 301 is configured to determine a device state label corresponding to the page source code according to the page source code.

[0123] The alarm information review unit 302 is configured to review the alarm information according to the device status tag.

[0124] From the above description, it can be known that the embodiment of the present application provides a server alarm information review device, which first acquires client identity data stored on a server in response to received alarm information, then acquires page source code of the server according to the client identity data, and finally reviews server alarm information according to the page source code. The present application aims at the problem of false alarm of a baseboard management controller (BMC), and increases a secondary review mechanism, that is, after a centralized monitoring platform receives device out-of-band alarm information, the device status tag in the device BMC address interface fed back through crawling is reviewed to determine whether the BMC alarm is accurate after a delay of several seconds. Only after the review and verification, the alarm is displayed and forwarded to a server device status monitoring personnel. The server alarm information review device provided by the embodiment of the present application can review server alarm information, thereby greatly reducing the workload of the server device status monitoring personnel, and further saving enterprise cost.

[0125] The embodiment of the present application further provides a specific implementation of an electronic device capable of implementing all steps of the server alarm information review method in the above embodiment, which is described with reference to Figure 13 , and the electronic device specifically includes the following contents:

[0126] a processor 1201, a memory 1202, a communications interface 1203 and a bus 1204;

[0127] The processor 1201, the memory 1202 and the communications interface 1203 complete mutual communication through the bus 1204; the communications interface 1203 is configured to realize information transmission between a server device, a client device and other related devices;

[0128] The processor 1201 is configured to call a computer program in the memory 1202, and the processor implements all steps of the server alarm information review method in the above embodiment when executing the computer program, for example, the processor implements the following steps when executing the computer program:

[0129] Step 100: acquiring client identity data stored locally in response to received alarm information;

[0130] Step 200: acquiring page source code corresponding to the alarm information according to the client identity data;

[0131] Step 300: reviewing the alarm information according to the page source code.

[0132] The embodiments of the present application further provide a computer readable storage medium capable of implementing all steps of the server alarm information review method in the above-mentioned embodiments. The computer readable storage medium stores a computer program. When the computer program is executed by a processor, all steps of the server alarm information review method in the above-mentioned embodiments are implemented. For example, when the processor executes the computer program, the following steps are implemented:

[0133] Step 100: In response to the received alarm information, obtaining the locally stored client identity data;

[0134] Step 200: Obtaining the page source code corresponding to the alarm information according to the client identity data;

[0135] Step 300: Reviewing the alarm information according to the page source code.

[0136] Each of the embodiments in the specification is described in a progressive manner, and the same or similar parts of each embodiment can be referred to each other. Each embodiment focuses on the difference from other embodiments. In particular, for the hardware + program type embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the part of the method embodiment.

[0137] The above describes specific embodiments of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be executed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multi-task processing and parallel processing are possible or can be advantageous.

[0138] Although the present application provides method operation steps such as embodiments or flowcharts, more or fewer operation steps can be included based on conventional or non-creative labor. The order of steps listed in the embodiments is only one of the many step execution orders, and does not represent the only execution order. When the device or client product is executed in practice, it can be executed in the order of the method shown in the embodiments or in parallel (for example, in the environment of parallel processor or multi-thread processing).

[0139] For ease of description, the above apparatus is described in various modules with functions respectively. Of course, functions of each module can be implemented in one or more software and / or hardware in implementing the embodiments of the present specification, and modules implementing the same function can be implemented by combination of a plurality of sub-modules or sub-units, etc. The apparatus embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed each other can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0140] Those skilled in the art also know that, in addition to implementing the controller in the form of pure computer readable program code, the controller can also be implemented in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers and embedded microcontrollers, etc. by logically programming the method steps to achieve the same function. Therefore, such a controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the devices for implementing various functions can even be considered as both software modules implementing the method and structures within the hardware component.

[0141] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0142] The memory can include non-persistent memory in computer readable media, random access memory (RAM), and / or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). The memory is an example of computer readable media. The memory is an example of computer readable media.

[0143] The embodiments of the present specification can be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. The embodiments of the present specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communication network. In a distributed computing environment, program modules can be located in both local and remote computer storage media including the storage devices.

[0144] Each of the embodiments in the specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other. Each of the embodiments focuses on the difference from other embodiments. In particular, the system embodiments are described simply because they are basically similar to the method embodiments, and the relevant parts can be referred to the description of the method embodiments. In the description of the specification, the description of the terms "one embodiment", "some embodiments", "an example", "a specific example", or "some examples" means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the embodiments of the specification. The illustrative description of the above terms in the specification does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any suitable manner in any one or more embodiments or examples. In addition, the person skilled in the art can combine and combine the different embodiments or examples described in the specification and the features of the different embodiments or examples without contradiction.

[0145] The above only describes the embodiments of the embodiments of the specification and does not limit the embodiments of the specification. The embodiments of the specification can have various changes and variations for those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiments of the specification shall be included in the scope of claims of the embodiments of the specification.

Claims

1. A method for reviewing server alarm information, characterized by, Comprising: In response to the received alarm information, obtain the stored local client identity data; wherein the client identity data is used to identify the user identity; According to the client identity data to determine the conversation information of the client; wherein the conversation information includes SessionID data; According to the page source code crawling; According to the device state label corresponding to the page source code; wherein the device state label contains the flag information of whether the server has a real exception at the current time; According to the device state label to review the alarm information.

2. The server alarm information review method of claim 1, wherein, The acquisition of the stored local client identity data includes: According to the login information corresponding to the client identity data, the client identity data is obtained.

3. A server alarm information review apparatus characterized by comprising: Comprising: Identity data acquisition module, for responding to the received alarm information, obtain the stored local client identity data; wherein the client identity data is used to identify the user identity; Page source code acquisition module, for according to the client identity data to obtain the page source code corresponding to the alarm information; Alarm information review module, for according to the page source code to review the alarm information; Wherein, the alarm information review module includes: State label determination unit, for according to the page source code to determine the device state label corresponding to it; wherein the device state label contains the flag information of whether the server has a real exception at the current time; Alarm information review unit, for according to the device state label to review the alarm information; Wherein, the page source code acquisition module includes: Conversation information acquisition unit, for according to the client identity data to determine the conversation information of the client; wherein the conversation information includes SessionID data; Page source code crawling unit, for according to the conversation information to crawl the page source code.

4. The server alarm information review apparatus according to claim 3, wherein The identity data acquisition module includes: Identity data acquisition unit, for according to the login information corresponding to the client identity data, the client identity data is obtained.

5. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, The processor executes the program to realize the steps of the server alarm information review method of any one of claims 1 to 2.

6. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to realize the steps of the server alarm information review method of any one of claims 1 to 2.

Images