A server firmware processing method, device, electronic device and storage medium

Abstract

The present application discloses a method, device, electronic device and storage medium for processing server firmware, the method comprising: obtaining target demand information corresponding to a target server, calling a target log file corresponding to the target server according to the target demand information, and obtaining detection items that meet the target demand information from the target log file; inputting the detection items into a pre-trained analysis model so that the analysis model analyzes the detection items to obtain analysis results; and determining the target firmware that the target server needs to perform preset service operations according to the analysis results. The method provided in the embodiment of the present application can optimize the functions of the server management software, and provides an automated problem location and prediction function in terms of firmware upgrades, which can effectively improve operation and maintenance efficiency. The addition of the automated problem location function not only effectively reduces the tedious work of manually locating problems, but also exposes the deep-seated causes of the problems and the connections between factors.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, device, electronic device, and storage medium for processing server firmware. Background Art

[0002] With the rapid increase in data and information volumes, the demand for servers is increasing, and this in turn places higher demands on server management software. Current management software typically includes monitoring, alarm, and control modules to provide daily server monitoring and maintenance functions. However, this requires a high level of user expertise and suffers from low information utilization between modules. Firmware upgrades allow operators to batch select servers for upgrade, but lack a predictive process. Furthermore, the factors influencing upgrade results are unclear, the relationships between these factors are opaque, and automated problem location is lacking. Summary of the Invention

[0003] In order to solve the above technical problems or at least partially solve the above technical problems, the present application provides a server firmware processing method, device, electronic device and storage medium.

[0004] According to one aspect of an embodiment of the present application, a method for processing server firmware is provided, including:

[0005] Obtaining target requirement information corresponding to a target server, wherein the target requirement information is used to determine a target firmware in the target server that needs to perform a preset service operation;

[0006] Calling a target log file corresponding to the target server according to the target requirement information, and obtaining detection items that meet the target requirement information from the target log file;

[0007] Inputting the detection item into a pre-trained analysis model so that the analysis model analyzes the detection item to obtain an analysis result;

[0008] The target firmware of the target server that needs to perform the preset service operation is determined according to the analysis result.

[0009] Furthermore, calling a target log file corresponding to the target server according to the target requirement information, and obtaining detection items that meet the target requirement information from the target log file, includes:

[0010] When the target requirement information belongs to an abnormal positioning requirement, obtaining a server identifier corresponding to the target server;

[0011] Based on the server identifier, querying the task execution time corresponding to each firmware in the target server from the task record;

[0012] Calling the LOG log file associated with the task execution time, and determining the LOG log file as the target log file;

[0013] At least one error reporting interface is obtained from the target log file based on the abnormality locating requirement, and the error reporting interface is determined as the detection item.

[0014] Furthermore, calling a target log file corresponding to the target server according to the target requirement information, and obtaining detection items that meet the target requirement information from the target log file, includes:

[0015] In a case where the target demand information belongs to a predicted update demand, obtaining a server identifier and a server type corresponding to the target server;

[0016] Obtaining a monitoring log file corresponding to the target server according to the server identifier and the server type;

[0017] Determining the monitoring log file as the target log file;

[0018] Monitoring data is extracted from the target log file based on the update requirement, and the monitoring data is determined as the detection item.

[0019] Furthermore, the inputting of the detection item into a pre-trained analysis model so that the analysis model analyzes the detection item to obtain an analysis result includes:

[0020] Inputting the error reporting interface into the analysis model so that the analysis model obtains a feature set corresponding to the error reporting interface, wherein the feature set includes at least one feature indicator that causes the interface to generate an error;

[0021] The feature set is determined as the analysis result.

[0022] Furthermore, determining the target firmware of the target server that needs to perform the preset service operation according to the analysis result includes:

[0023] Obtaining the server identifier and server type corresponding to the target server;

[0024] Obtaining a monitoring log file corresponding to the target server according to the server identifier and the server type;

[0025] Obtaining a feature value corresponding to each feature indicator in the feature set from the monitoring log file;

[0026] Obtain the target feature set whose feature value reaches the threshold corresponding to the feature index, and report the target error interface corresponding to the target feature set;

[0027] The firmware to which the target error reporting interface belongs is determined as the target firmware.

[0028] Furthermore, the inputting of the detection item into a pre-trained analysis model so that the analysis model analyzes the detection item to obtain an analysis result includes:

[0029] Acquire characteristic values ​​corresponding to each firmware in the target server from the monitoring data;

[0030] The eigenvalue is input into the analysis model so that the analysis model calculates the feature type and the confidence corresponding to the eigenvalue, and determines the feature type and the confidence as the analysis result.

[0031] Furthermore, the method further comprises:

[0032] monitoring at least one candidate server to obtain a log file of the candidate server, and generating a monitoring log sample based on the log file;

[0033] Obtaining a task result of the candidate server executing the firmware upgrade task, and generating a LOG log sample based on the task result;

[0034] Obtain an interface configuration file and a feature configuration file, wherein the interface configuration file carries the interface of each firmware in the candidate server, and the feature configuration file carries the feature indicators that cause the interface to upgrade during the firmware upgrade process, as well as the feature values ​​corresponding to the feature indicators;

[0035] The analysis model is constructed based on the monitoring log samples, LOG log samples, interface configuration files and feature configuration files.

[0036] According to another aspect of an embodiment of the present application, a device for processing the firmware of a server is provided, including:

[0037] An acquisition module, configured to acquire target requirement information corresponding to a target server, wherein the target requirement information is used to determine a target firmware in the target server that needs to perform a preset service operation;

[0038] A calling module is used to call the target log file corresponding to the target server according to the target requirement information, and obtain the detection items that meet the target requirement information from the target log file;

[0039] An analysis module, configured to input the detection item into a pre-trained analysis model, so that the analysis model analyzes the detection item to obtain an analysis result;

[0040] The processing module is used to determine the target firmware of the target server that needs to perform the preset service operation according to the analysis result.

[0041] According to another aspect of an embodiment of the present application, a storage medium is further provided, which includes a stored program, and the above steps are executed when the program is run.

[0042] According to another aspect of an embodiment of the present application, an electronic device is also provided, including a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; wherein: the memory is used to store computer programs; the processor is used to execute the steps in the above method by running the program stored in the memory.

[0043] An embodiment of the present application also provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the steps in the above method.

[0044] The technical solutions provided by the embodiments of the present application have the following advantages over existing technologies: The methods provided by the embodiments of the present application can optimize the functionality of server management software, providing automated problem location and prediction capabilities for firmware upgrades, effectively improving operation and maintenance efficiency. The addition of automated problem location not only effectively reduces the tedious work of manually locating problems, but also reveals the underlying causes and connections between factors. Furthermore, pre-upgrade predictions not only ensure the performance of the controlled server and reduce damage to the server caused by upgrade failures, but also provide prediction reports that help operation and maintenance personnel gain a deeper understanding of the status of the controlled server, facilitating further operation and maintenance work. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] 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 present application.

[0046] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0047] Figure 1 A flowchart of a server firmware processing method provided in an embodiment of the present application;

[0048] Figure 2 A flowchart of a server firmware processing method provided in another embodiment of the present application;

[0049] Figure 3 A block diagram of a server firmware processing device provided in an embodiment of the present application;

[0050] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0051] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. The schematic embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0052] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another similar entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device comprising the element.

[0053] The present invention provides a method, apparatus, electronic device, and storage medium for processing server firmware. The method provided by the present invention can be applied to any desired electronic device, such as a server or terminal. This is not specifically limited here and, for ease of description, is referred to as an electronic device.

[0054] According to one aspect of an embodiment of the present application, a method embodiment of processing server firmware is provided. Figure 1 A flowchart of a server firmware processing method provided in an embodiment of the present application is shown as follows: Figure 1 As shown, the method includes:

[0055] Step S11 : acquiring target requirement information corresponding to the target server, wherein the target requirement information is used to determine the target firmware in the target server that needs to execute a preset service operation.

[0056] In an embodiment of the present application, the target demand information corresponding to the target server may include an abnormality location demand and a predicted firmware update demand. The abnormality location demand is used to identify firmware on the target server that requires abnormality location services. The predicted firmware update demand is used to identify firmware on the target server that requires predicted upgrade / update services. It should be noted that the target demand information may be periodically initiated based on the firmware status on the target server, or may be uploaded by a developer through a client.

[0057] Step S12: calling the target log file corresponding to the target server according to the target requirement information, and obtaining the detection items that meet the target requirement information from the target log file.

[0058] In one embodiment of the present application, calling a target log file corresponding to a target server according to target requirement information, and obtaining detection items that meet the target requirement information from the target log file include the following steps A1-A4:

[0059] Step A1: when the target requirement information is an abnormal positioning requirement, obtain a server identifier corresponding to the target server.

[0060] Step A2: Based on the server identifier, query the task execution time corresponding to each firmware in the target server from the task record.

[0061] Step A3: call the LOG file associated with the task execution time, and determine the LOG file as the target log file.

[0062] Step A4: obtaining at least one error reporting interface from the target log file based on the anomaly location requirement, and determining the error reporting interface as a detection item.

[0063] In an embodiment of the present application, when the target demand information belongs to an abnormal positioning demand, the server identifier of the target server will be called at this time. The server identifier can be the server IP, and the server identifier is used to query the task record of the server. The task record carries the task execution time corresponding to each firmware in the target server. The task execution time includes: the task execution time of the firmware executing the upgrade task, and then the LOG log file corresponding to the task execution time is called. It should be noted that the LOG log file is used to store the task results after each firmware in the server executes the upgrade task. Therefore, after determining the called LOG log file, at least one error interface Inf_fail is obtained from the LOG log file. iThe error reporting interface is the interface where the firmware encounters an error when performing the upgrade task. Finally, the error reporting interface is determined as a detection item.

[0064] In another embodiment of the present application, calling a target log file corresponding to a target server according to target requirement information, and obtaining detection items that meet the target requirement information from the target log file, includes the following steps B1-B4:

[0065] Step B1: When the target demand information is a predicted update demand, obtain the server identifier and server type corresponding to the target server.

[0066] Step B2: Obtain the monitoring log file corresponding to the target server according to the server identifier and server type.

[0067] Step B3: determine the monitoring log file as the target log file.

[0068] Step B4: extracting monitoring data from the target log file based on the update requirement, and determining the monitoring data as a detection item.

[0069] In an embodiment of the present application, when the target requirement information relates to a predicted update requirement, the monitoring log file corresponding to the target server is obtained based on the server identifier and server type corresponding to the target server. It should be noted that the monitoring log file stores relevant data about the monitored server, such as server runtime data, the server's BMC audit log, and system log data. Monitoring data is then extracted from the monitoring log file to determine the detection item based on the update requirement.

[0070] In step S13, the detection items are input into a pre-trained analysis model so that the analysis model analyzes the detection items to obtain analysis results.

[0071] In one embodiment of the present application, step S13, inputting the detection item into a pre-trained analysis model so that the analysis model analyzes the detection item to obtain an analysis result, includes the following steps C1-C2:

[0072] In step C1, the error reporting interface is input into the analysis model so that the analysis model obtains a feature set corresponding to the error reporting interface, wherein the feature set includes at least one feature indicator that causes the interface to generate an error.

[0073] Step C2: determining the feature set as the analysis result.

[0074] In this embodiment of the present application, when the target requirement information is an abnormal location requirement, after the error reporting interface is input into the analysis model, the analysis model directly calls the feature set that causes the interface error condition, which includes at least one feature indicator that causes the interface error condition. The feature indicator is then determined as the analysis result.

[0075] In another embodiment of the present application, step S13, inputting the detection item into a pre-trained analysis model so that the analysis model analyzes the detection item to obtain an analysis result, includes the following steps D1-D2:

[0076] Step D1, obtaining characteristic values ​​corresponding to each firmware in the target server from monitoring data;

[0077] In step D2, the eigenvalue is input into the analysis model so that the analysis model calculates the feature type and confidence level corresponding to the eigenvalue, and determines the feature type and confidence level as the analysis result.

[0078] In an embodiment of the present application, when the target demand information belongs to a predicted update demand, the characteristic values ​​corresponding to each firmware in the target server are obtained from the monitoring data, and the characteristic values ​​are input into the analysis model so that the analysis model performs calculations based on the characteristic values ​​to obtain the characteristic type and confidence corresponding to the characteristic values, and uses them as the analysis results.

[0079] Step S14: determining the target firmware for the target server to execute the preset service operation according to the analysis result.

[0080] In the embodiment of the present application, step S14, determining the target firmware that the target server needs to perform the preset service operation according to the analysis result, includes the following steps E1-E5:

[0081] Step E1, obtaining the server identifier and server type corresponding to the target server;

[0082] Step E2: Obtain the monitoring log file corresponding to the target server according to the server identifier and server type;

[0083] Step E3, obtaining the feature value corresponding to each feature indicator in the feature set from the monitoring log file;

[0084] Step E4, obtaining a target feature set whose feature value reaches the threshold corresponding to the feature index, and reporting the target error interface corresponding to the target feature set;

[0085] Step E5: Determine the firmware to which the target error reporting interface belongs as the target firmware.

[0086] In an embodiment of the present application, when the target demand information belongs to an abnormality location demand, the monitoring log file corresponding to the target server is obtained according to the server identifier and server type, the characteristic values ​​corresponding to each characteristic indicator in the feature set are obtained from the monitoring log file, and then the characteristic values ​​are analyzed to determine the target error reporting interface whose characteristic values ​​reach the threshold corresponding to the characteristic indicators, and the firmware corresponding to the target error reporting interface is determined as the target firmware, and the target firmware is the firmware after abnormality location.

[0087] In an embodiment of the present application, step S14, determining the target firmware on which the target server needs to perform the preset service operation based on the analysis results, also includes: when the target requirement information belongs to a predicted update requirement, determining the target feature type based on the feature type with the highest confidence in the analysis results, where the feature types include: upgrade type and non-upgrade type.

[0088] The method provided in the embodiments of the present application can optimize the functionality of server management software, providing automated problem location and prediction capabilities for firmware upgrades, effectively improving operation and maintenance efficiency. The addition of automated problem location not only effectively reduces the tedious work of manually locating problems, but also reveals the underlying causes and connections between factors. Furthermore, pre-upgrade predictions not only ensure the performance of the controlled server and reduce damage to the server caused by upgrade failures, but also provide prediction reports that help operation and maintenance personnel gain a deeper understanding of the controlled server's status, facilitating further operation and maintenance work.

[0089] Figure 2 A flowchart of a server firmware processing method provided in another embodiment of the present application, the method further comprising:

[0090] Step S21: monitor at least one candidate server to obtain a log file of the candidate server, and generate a monitoring log sample based on the log file.

[0091] Step S22: Obtain the task result of the candidate server executing the firmware upgrade task, and generate a LOG log sample based on the task result.

[0092] Step S23, obtaining an interface configuration file and a feature configuration file, wherein the interface configuration file carries interfaces of each firmware in the candidate server, and the feature configuration file carries feature indicators that cause the interface in the firmware upgrade process, and feature values ​​corresponding to the feature indicators.

[0093] Step S24: construct an analysis model based on the monitoring log samples, the LOG log samples, the interface configuration file, and the feature configuration file.

[0094] In this embodiment, the operating status of the managed server, as well as the server's out-of-band BMC audit log and system log, are monitored in real time and saved to a file server. Information related to added upgrade tasks is stored in a database, and the results of each upgrade task are recorded in a log file. Furthermore, the underlying management software contains interface configuration files based on machine model, firmware type, and interface level, as well as feature configuration files that affect upgrades. These are all sources of data processing. When model building is triggered, the program constructs the model based on historical data.

[0095] The out-of-band firmware upgrade is implemented by calling several restful interfaces one by one. The monitoring log and program LOG log file are obtained according to the specified log file path. The IP set that executes the firmware upgrade is obtained according to the task record. The result record information of each IP in the IP set is retrieved in the LOG log file. According to the interface configuration file and the fail and success descriptions following the interface, the result of the firmware upgrade executed by each IP is obtained, such as upgrade success or interface failure, to generate data set D.

[0096] Then, according to each characteristic indicator in the characteristic configuration file, the monitoring log and the LOG log file are matched to obtain the characteristic indicator θ of each server that has performed the firmware upgrade. i and the eigenvalue v i Map i {IP i {(θ1,v1),(θ2,v2),...,(θ i ,v i ),...,(θ n ,v n )}}, each IP corresponds to a Map, and the feature set C can be obtained, C = {Map1,Map2,...Map i}

[0097] The obtained data set D and the obtained feature set C are the same IP as a sample, and the sample set S is generated and input into the random forest model; when building the model, the random forest program randomly extracts M samples and Q features to form multiple decision trees for training. When each decision tree is built, the C4.5 algorithm is used as the basis for node selection, and the information gain rate IG is calculated when selecting nodes at each layer. ratio =Gain(θ i ) / H(θ i ), the feature with the highest information gain rate is used as the node of this layer, and the feature to be selected for the next node is determined recursively, where Gain(θ i ) is the characteristic index θ i The information gain, H(θ i ) is the characteristic index θi The classification information measure of .

[0098] The feature set {θ1,θ2,θ3,...,θ i The information entropy of each feature and data result set {Inf_fail1,Inf_fail1,...,Inf_fail1,...,Inf_success} in} is recorded as EN(θ i ), EN(Inf), then Gain(θ i )=EN(Inf)-EN(θ i ), and the calculation formula of information entropy is: The random forest model is trained through historical data, and the influencing factors of each interface can be clarified based on the final model.

[0099] The embodiment of the present application is based on a server firmware upgrade automated problem location and prediction component model based on C4.5 and RF, which can realize automated problem location and firmware upgrade prediction. The model is constructed based on historical monitoring logs and software logs, matching and filtering each data according to the timestamp, and mining the firmware upgrade records performed by users. This valuable information is combined with the specific configuration files in the software and trained based on the random forest algorithm. When the automated problem location is triggered, the log file is retrieved according to the IP address of the server to be located to obtain the error interface, and the corresponding feature value is obtained based on the analysis of the impact characteristics of the error interface in the model and combined with the monitoring log. After processing, the influencing factors are output. When the upgrade prediction is triggered, the status indicators of the server to be upgraded and the upgrade parameters are detected. After data preprocessing, a feature set is obtained and input into the model, and after processing, a prediction report is output. This invention not only automates problem location, but also can mine the intrinsic connection between factors, making the problem more concrete.

[0100] Figure 3 This is a block diagram of a server firmware processing device provided in an embodiment of the present application. The device can be implemented as part or all of an electronic device through software, hardware, or a combination of both. Figure 3 As shown, the device includes:

[0101] An acquisition module 31 is configured to acquire target requirement information corresponding to a target server, wherein the target requirement information is used to determine a target firmware in the target server that needs to perform a preset service operation;

[0102] A calling module 32 is configured to call a target log file corresponding to a target server according to target requirement information, and obtain detection items that meet the target requirement information from the target log file;

[0103] An analysis module 33 is used to input the detection items into a pre-trained analysis model so that the analysis model analyzes the detection items and obtains analysis results;

[0104] The processing module 34 is configured to determine the target firmware for the target server to execute the preset service operation according to the analysis result.

[0105] In an embodiment of the present application, a calling module is used to obtain the server identifier corresponding to the target server when the target requirement information belongs to the abnormal location requirement; based on the server identifier, the task execution time corresponding to each firmware in the target server is queried from the task record; the LOG log file associated with the task execution time is called, and the LOG log file is determined as the target log file; based on the abnormal location requirement, at least one error reporting interface is obtained from the target log file, and the error reporting interface is determined as a detection item.

[0106] In an embodiment of the present application, a calling module is used to obtain the server identifier and server type corresponding to the target server when the target demand information belongs to a predicted update demand; obtain the monitoring log file corresponding to the target server based on the server identifier and server type; determine the monitoring log file as the target log file; extract monitoring data from the target log file based on the update demand, and determine the monitoring data as a detection item.

[0107] In an embodiment of the present application, the analysis module is used to input the error reporting interface into the analysis model so that the analysis model obtains a feature set corresponding to the error reporting interface, wherein the feature set includes at least one feature indicator that causes the interface to generate an error; and the feature set is determined as the analysis result.

[0108] In an embodiment of the present application, a processing module is used to obtain a server identifier and a server type corresponding to a target server; obtain a monitoring log file corresponding to the target server based on the server identifier and the server type; obtain feature values ​​corresponding to each feature indicator in a feature set from the monitoring log file; obtain a target feature set whose feature values ​​reach thresholds corresponding to feature indicators, and a target error reporting interface corresponding to the target feature set; and determine the firmware to which the target error reporting interface belongs as the target firmware.

[0109] In an embodiment of the present application, the analysis module is used to obtain the characteristic values ​​corresponding to each firmware in the target server from the monitoring data; input the characteristic values ​​into the analysis model so that the analysis model calculates the characteristic type and confidence corresponding to the characteristic values, and determines the characteristic type and confidence as the analysis results.

[0110] In an embodiment of the present application, the device also includes: a construction module, which is used to monitor at least one candidate server to obtain the log file of the candidate server, and generate a monitoring log sample based on the log file; obtain the task result of the candidate server performing the firmware upgrade task, and generate a LOG log sample based on the task result; obtain an interface configuration file and a feature configuration file, wherein the interface configuration file carries the interface of each firmware in the candidate server, and the feature configuration file carries the feature indicators that cause the interface in the firmware upgrade process, as well as the feature values ​​corresponding to the feature indicators; and construct an analysis model based on the monitoring log sample, the LOG log sample, the interface configuration file, and the feature configuration file.

[0111] The present application also provides an electronic device, such as Figure 4 As shown, the electronic device may include: a processor 1501 , a communication interface 1502 , a memory 1503 and a communication bus 1504 , wherein the processor 1501 , the communication interface 1502 , and the memory 1503 communicate with each other via the communication bus 1504 .

[0112] Memory 1503, used for storing computer programs;

[0113] The processor 1501 is configured to implement the steps of the above embodiment when executing the computer program stored in the memory 1503 .

[0114] The communication bus mentioned in the terminal can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. This communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is used in the figure, but this does not mean that there is only one bus or only one type of bus.

[0115] The communication interface is used for communication between the above terminal and other devices.

[0116] The memory may include random access memory (RAM) or non-volatile memory, such as at least one disk storage. Alternatively, the memory may be at least one storage device located away from the processor.

[0117] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.

[0118] In another embodiment provided by the present application, a computer-readable storage medium is further provided, in which instructions are stored. When the computer-readable storage medium is run on a computer, the computer executes a server firmware processing method described in any one of the above embodiments.

[0119] In another embodiment provided by the present application, a computer program product including instructions is further provided, which, when executed on a computer, enables the computer to execute a server firmware processing method described in any one of the above embodiments.

[0120] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive SolidState Disk).

[0121] The above description is only a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application are included in the scope of protection of the present application.

[0122] The foregoing is merely a list of specific embodiments of the present application, intended to enable those skilled in the art to understand or implement the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application is not limited to the embodiments shown herein, but is intended to conform to the broadest scope consistent with the principles and novel features of the present application.

Claims

1. A method for processing server firmware, characterized in that: include: Obtaining target requirement information corresponding to a target server, wherein the target requirement information is used to determine a target firmware in the target server that needs to perform a preset service operation; Calling a target log file corresponding to the target server according to the target requirement information, and obtaining detection items that meet the target requirement information from the target log file; Inputting the detection item into a pre-trained analysis model so that the analysis model analyzes the detection item to obtain an analysis result; Determining the target firmware of the target server that needs to perform the preset service operation according to the analysis result; The calling of a target log file corresponding to the target server according to the target requirement information, and obtaining detection items that meet the target requirement information from the target log file, includes: When the target requirement information belongs to an abnormal positioning requirement, obtaining a server identifier corresponding to the target server; Based on the server identifier, querying the task execution time corresponding to each firmware in the target server from the task record; Calling the LOG log file associated with the task execution time, and determining the LOG log file as the target log file; Acquire at least one error reporting interface from the target log file based on the anomaly locating requirement, and determine the error reporting interface as the detection item; Alternatively, calling a target log file corresponding to the target server according to the target requirement information, and obtaining detection items that meet the target requirement information from the target log file, includes: In a case where the target demand information belongs to a predicted update demand, obtaining a server identifier and a server type corresponding to the target server; Obtaining a monitoring log file corresponding to the target server according to the server identifier and the server type; Determining the monitoring log file as the target log file; Monitoring data is extracted from the target log file based on the update requirement, and the monitoring data is determined as the detection item.

2. The method according to claim 1, characterized in that Inputting the detection item into a pre-trained analysis model so that the analysis model analyzes the detection item to obtain an analysis result includes: Inputting the error reporting interface into the analysis model so that the analysis model obtains a feature set corresponding to the error reporting interface, wherein the feature set includes at least one feature indicator that causes the interface to generate an error; The feature set is determined as the analysis result.

3. The method according to claim 2, characterized in that The determining, according to the analysis result, the target firmware of the target server that needs to perform the preset service operation includes: Obtaining the server identifier and server type corresponding to the target server; Obtaining a monitoring log file corresponding to the target server according to the server identifier and the server type; Obtaining a feature value corresponding to each feature indicator in the feature set from the monitoring log file; Obtain the target feature set whose feature value reaches the threshold corresponding to the feature index, and report the target error interface corresponding to the target feature set; The firmware to which the target error reporting interface belongs is determined as the target firmware.

4. The method according to claim 1, wherein Inputting the detection item into a pre-trained analysis model so that the analysis model analyzes the detection item to obtain an analysis result includes: Acquire characteristic values ​​corresponding to each firmware in the target server from the monitoring data; The eigenvalue is input into the analysis model so that the analysis model calculates the feature type and the confidence corresponding to the eigenvalue, and determines the feature type and the confidence as the analysis result.

5. The method according to claim 1, wherein The method further comprises: monitoring at least one candidate server to obtain a log file of the candidate server, and generating a monitoring log sample based on the log file; Obtaining a task result of the candidate server executing the firmware upgrade task, and generating a LOG log sample based on the task result; Obtain an interface configuration file and a feature configuration file, wherein the interface configuration file carries the interface of each firmware in the candidate server, and the feature configuration file carries the feature indicators that cause the interface to upgrade during the firmware upgrade process, as well as the feature values ​​corresponding to the feature indicators; The analysis model is constructed based on the monitoring log samples, LOG log samples, interface configuration files and feature configuration files.

6. A server firmware processing device, characterized in that: include: An acquisition module, configured to acquire target requirement information corresponding to a target server, wherein the target requirement information is used to determine a target firmware in the target server that needs to perform a preset service operation; A calling module is used to call the target log file corresponding to the target server according to the target requirement information, and obtain the detection items that meet the target requirement information from the target log file; An analysis module, configured to input the detection item into a pre-trained analysis model, so that the analysis model analyzes the detection item to obtain an analysis result; A processing module, configured to determine the target firmware of the target server that needs to perform the preset service operation according to the analysis result; The calling module is used to obtain the server identifier corresponding to the target server when the target requirement information belongs to the abnormality positioning requirement; based on the server identifier, query the task execution time corresponding to each firmware in the target server from the task record; call the LOG log file associated with the task execution time, and determine the LOG log file as the target log file; obtain at least one error reporting interface from the target log file based on the abnormality positioning requirement, and determine the error reporting interface as a detection item; Alternatively, a calling module is used to obtain the server identifier and server type corresponding to the target server when the target demand information belongs to a predicted update demand; obtain the monitoring log file corresponding to the target server based on the server identifier and server type; determine the monitoring log file as the target log file; extract monitoring data from the target log file based on the update demand, and determine the monitoring data as a detection item.

7. A storage medium, characterized in that: The storage medium includes a stored program, wherein the program executes the method steps of any one of claims 1 to 5 when running.

8. An electronic device, characterized in that: The system comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; wherein: Memory for storing computer programs; A processor, configured to execute the method steps according to any one of claims 1 to 5 by running a program stored in a memory.

Images