Log file processing method and apparatus, storage medium, and electronic device

Abstract

This application provides a method, apparatus, storage medium, and electronic device for processing log files. The method includes: performing a first parsing operation on log files of a set of specified firmware to obtain parsing results corresponding to the log files of the set of specified firmware; performing a second parsing operation on the parsing results corresponding to the log files of the set of specified firmware to obtain a set of associated parsing results, wherein the second parsing operation is an operation of finding parsing results in the parsing results corresponding to the log files of the set of specified firmware where the attribute information of the first specified attribute is the specified attribute information; integrating the set of associated parsing results according to the attribute information of the second specified attribute in the set of log attributes, and displaying the integrated set of associated parsing results on the same view. This application solves the problem in related technologies where the accuracy and speed of problem solving are affected by the omission or misunderstanding of information in log file processing methods.

Description

Technical Field

[0001] This application relates to the field of computers, and more specifically, to a method and apparatus for processing log files, a storage medium, and an electronic device. Background Technology

[0002] Computer systems can include various types of firmware, such as BMC (Baseboard Management Controller), BIOS (Basic Input / Output System), and CPLD (Complex Programmable Logic Device). Different firmware may generate log files with varying formats and contents. For example, BMC might record information related to system management and monitoring, BIOS might record data during system startup and hardware initialization, while CPLD might focus on recording hardware configuration and state changes. This fragmentation of log data results in large log file sizes and high complexity in data analysis. When system failures or performance issues occur, it typically requires collaborative work from researchers in multiple fields to analyze log files generated by different firmware or modules in order to locate and resolve the problem.

[0003] However, such cross-domain collaboration often leads to reduced efficiency in problem analysis and resolution. In addition, due to the fragmentation of log data, team members often need to spend a lot of time manually integrating and analyzing log data, and the accuracy and speed of problem resolution may be affected by omissions or misunderstandings of information.

[0004] Therefore, it is evident that the log file processing methods in related technologies suffer from problems that affect the accuracy and speed of problem solving due to omissions or misunderstandings of information. Summary of the Invention

[0005] This application provides a method, apparatus, storage medium, and electronic device for processing log files, to at least solve the problem that the accuracy and speed of problem solving are affected by the omission or misunderstanding of information in the log file processing methods of the related art.

[0006] According to one embodiment of this application, a method for processing log files is provided, comprising: performing a first parsing operation on log files of a set of specified firmware to obtain parsing results corresponding to the log files of the set of specified firmware, wherein the first parsing operation is an operation of parsing attribute information of a set of log attributes from the log files of the set of specified firmware, the set of log attributes including a first specified attribute, the first specified attribute being parsed according to attribute information set for specified firmware in the set of specified firmware; performing a second parsing operation on the parsing results corresponding to the log files of the set of specified firmware to obtain a set of associated parsing results, wherein the second parsing operation is an operation of finding parsing results in the parsing results corresponding to the log files of the set of specified firmware where the attribute information of the first specified attribute is specified attribute information, the specified attribute information being used to indicate at least one of the following: an association relationship between different specified firmware, an association relationship between different modules within the same specified firmware; integrating the set of associated parsing results according to the attribute information of the second specified attribute in the set of log attributes, and displaying the integrated set of associated parsing results on the same view.

[0007] According to another embodiment of this application, a log file processing apparatus is provided, comprising: a first parsing unit, configured to perform a first parsing operation on log files of a set of specified firmware to obtain parsing results corresponding to the log files of the set of specified firmware, wherein the first parsing operation is an operation of parsing attribute information of a set of log attributes from the log files of the set of specified firmware, the set of log attributes including a first specified attribute, the first specified attribute being parsed according to attribute information set for specified firmware in the set of specified firmware; a second parsing unit, configured to perform a second parsing operation on the parsing results corresponding to the log files of the set of specified firmware to obtain a set of associated parsing results, wherein the second parsing operation is an operation of finding parsing results in the parsing results corresponding to the log files of the set of specified firmware where the attribute information of the first specified attribute is specified attribute information, the specified attribute information being used to indicate at least one of the following: an association relationship between different specified firmware, an association relationship between different modules within the same specified firmware; and an execution unit, configured to integrate the set of associated parsing results according to the attribute information of the second specified attribute in the set of log attributes, and display the integrated set of associated parsing results on the same view.

[0008] According to yet another embodiment of this application, a computer-readable storage medium is also provided, wherein a computer program is stored therein, and the computer program is configured to perform the steps in any of the above method embodiments when it is run.

[0009] According to yet another embodiment of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0010] According to yet another embodiment of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0011] This application achieves improved efficiency and accuracy in diagnosing system problems, shortens repair time, and enhances system stability and reliability by parsing log entries from different firmware or modules according to their attribute information, and by performing correlation parsing on the log parsing results based on specified attribute information. Furthermore, it addresses the issue in related technologies where log file processing methods suffer from omissions or misunderstandings that affect the accuracy and speed of problem solving, thus improving the accuracy and efficiency of problem resolution. Attached Figure Description

[0012] Figure 1 This is a hardware structure block diagram of a server device for a log file processing method according to an embodiment of this application;

[0013] Figure 2 This is a flowchart illustrating a log file processing method according to an embodiment of this application;

[0014] Figure 3 This is a schematic diagram of a log file processing method according to an embodiment of this application;

[0015] Figure 4 This is a schematic diagram of another log file processing method according to an embodiment of this application;

[0016] Figure 5 This is a flowchart illustrating another method for processing log files according to an embodiment of this application;

[0017] Figure 6 This is a structural block diagram of an optional log file processing device provided in an embodiment of this application. Detailed Implementation

[0018] The embodiments of this application will be described in detail below with reference to the accompanying drawings and examples.

[0019] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0020] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0021] The methods and embodiments provided in this application can be executed on a server device or a similar computing device. Taking running on a server device as an example, Figure 1 This is a hardware structure block diagram of a server device for a log file processing method according to an embodiment of this application. Figure 1 As shown, the server device may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The server device may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the server equipment described above. For example, the server equipment may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0022] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the log file processing method in this embodiment. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thus implementing the above-described method. The memory 104 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to server devices via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0023] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider for the server device. In one example, the transmission device 106 includes a NIC (Network Interface Controller), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be an RF (Radio Frequency) module used for wireless communication with the Internet.

[0024] This embodiment provides a method for processing log files. Figure 2 This is a flowchart illustrating a log file processing method according to an embodiment of this application, as shown below. Figure 2 As shown, the process includes the following steps:

[0025] Step S202: Perform a first parsing operation on the log files of a set of specified firmware to obtain the parsing result corresponding to the log files of the set of specified firmware. The first parsing operation is an operation to parse the attribute information of a set of log attributes from the log files of the set of specified firmware. The set of log attributes includes a first specified attribute, which is parsed according to the attribute information set for the specified firmware in the set of specified firmware.

[0026] The log file processing method in this embodiment can be applied to scenarios involving the processing of log files generated by different specified firmware. Different firmware may need to record different types of information during error handling and debugging. For example, some firmware may need to record more error stack information, while other firmware may focus more on recording event timestamps and triggering conditions; firmware may provide different log levels, the definitions and usage of which may vary from firmware to firmware, thus affecting the content of the final generated log file; different firmware may use different technology stacks or development tools, and the logging methods of these tools themselves will also affect the format and content of the log file. Due to these factors, log files generated by different firmware may have significant differences in format and content.

[0027] For example, in modern computer systems (e.g., storage systems), firmware such as the Baseboard Management Controller (BMC), Basic Input / Output System (BIOS), and Complex Programmable Logic Device (CPLD) play a crucial role. This firmware not only manages and monitors the basic operating status of the hardware but also initializes, configures, and provides runtime support for the system. To ensure stable system operation and fault tracing, this firmware logs critical system operations, hardware data, and any abnormal information in its respective firmware log.

[0028] Firmware logs are crucial tools for diagnosing and resolving problems in computer systems. They provide a detailed record of device operation, including timestamped system events, error codes, hardware status information, and more—essential data for analysis and troubleshooting. However, due to the complexity of computer systems, different firmware components may generate log files with varying formats and contents. For example, the BMC might log information related to system administration and monitoring, while the BIOS might log data during system startup and hardware initialization, and the CPLD might focus on recording hardware configuration and status changes.

[0029] This fragmentation of log data not only results in massive log file sizes but also increases the complexity of data analysis. When system failures or performance issues occur, it typically requires collaboration among developers from multiple fields to analyze log files generated by different firmware or modules in order to locate and resolve the problem. This cross-disciplinary collaboration often leads to reduced efficiency in problem analysis and resolution because each team member may only be familiar with a specific type of firmware or log data, while lacking sufficient understanding of other parts.

[0030] Furthermore, due to the lack of a unified log analysis framework or tool, team members often spend a significant amount of time manually integrating and analyzing log data. This is not only time-consuming but can also affect the accuracy and speed of problem-solving due to omissions or misunderstandings of information. Therefore, there is an urgent need to develop a more efficient technical solution that can integrate and analyze log data from different firmware components, improving the efficiency and accuracy of problem diagnosis, thereby optimizing the maintenance and management of computer systems.

[0031] To at least partially address the aforementioned issues, this embodiment parses log entries from different firmware or modules based on log attribute information to obtain log parsing results. These results are then correlated with specified attribute information to obtain correlation parsing results. The correlated log data is then centrally displayed on the same view. In other words, by integrating and analyzing log data between different firmware and different modules within the same firmware, defining log parsing rules for specific firmware, automatically parsing logs to extract key data, defining correlation attributes between firmware and modules, performing log correlation parsing based on timestamps and event types, and centrally displaying the correlation parsing results on a view, the causal relationships of system behavior and performance impacts can be effectively identified, improving the maintenance efficiency and reliability of the computer system.

[0032] In this embodiment, a first parsing operation is performed on the log files of a set of specified firmware. The first parsing operation is the operation of parsing the attribute information of a set of log attributes from the log files of the set of specified firmware. That is, the log files of the specified firmware are parsed to obtain the attribute information of a set of log attributes. The set of log attributes includes a first specified attribute. The first specified attribute is parsed according to the attribute information set for the specified firmware in the set of specified firmware. That is, different firmware can set different attribute information, and the attribute information of the same log attribute of different firmware can be different.

[0033] For example, a set of log attributes may include key attributes. The key attribute information of BMC firmware may include, but is not limited to, IOCARD_PRESENT, and the key attribute information of BIOS firmware may include, but is not limited to, PCIE_LINK.

[0034] Taking the first specified attribute as the key attribute as an example, the first parsing operation is performed on the BMC log, and the attribute information of the first specified attribute is IOCARD_PRESENT.

[0035] In this embodiment, the parsing result corresponding to the log file of the specified firmware can be a correspondence between a set of log attributes and attribute information corresponding to each log entry in the log file of the specified firmware.

[0036] Optionally, in this embodiment, the attribute information of the log attribute can be empty, that is, there is no attribute information corresponding to a certain log attribute in the log entry.

[0037] Step S204: Perform a second parsing operation on the parsing results corresponding to the log files of a set of specified firmware to obtain a set of associated parsing results. The second parsing operation is to find the parsing results in which the attribute information of the first specified attribute is the specified attribute information in the parsing results corresponding to the log files of a set of specified firmware. The specified attribute information is used to indicate at least one of the following: the association relationship between different specified firmware, and the association relationship between different modules within the same specified firmware.

[0038] In this embodiment, a second parsing operation is performed on the parsing results corresponding to the log files of a set of specified firmware. The second parsing operation is to find the parsing results in which the attribute information of the first specified attribute is the specified attribute information in the parsing results corresponding to the log files of a set of specified firmware. That is, the parsing results in which the attribute information of the first specified attribute is the specified attribute information are associated. The number of specified attribute information can be one or more, and this embodiment does not limit this.

[0039] The specified attribute information is used to indicate at least one of the following: the relationship between different specified firmware, and the relationship between different modules within the same specified firmware.

[0040] The associated parsing results can be the result of associating multiple parsing results corresponding to a set of specified firmware log files based on specified attribute information.

[0041] For example, combining Figure 3 Taking the specified attribute information (also known as associated attribute information) as IOCARD_PRESENT and PCIE_LINK as an example, if the first specified attribute is a critical attribute, the attribute information of the critical attribute of the BMC firmware is IOCARD_PRESENT, the attribute information of the critical attribute of the CPLD firmware is IOCARD_PRESENT, and the attribute information of the critical attribute of the BIOS firmware is PCIE_LINK, then the associated parsing result includes the above three parsing results. The above three parsing results may also include the correspondence between the critical attribute and its attribute information, and the correspondence between other log attributes and their attribute information in a set of log attributes.

[0042] Step S206: Integrate a set of association resolution results according to the attribute information of the second specified attribute in a set of log attributes, and display the integrated set of association resolution results on the same view.

[0043] Here, the second specified attribute may be the same as or different from the aforementioned first specified attribute, and this embodiment does not impose any restrictions on this.

[0044] Integrating a set of association resolution results according to the attribute information of the second specified attribute in a set of log attributes can be done by integrating the arrangement order of a set of association resolution results according to the attribute information of the second specified attribute, so that the integrated set of association resolution results can be displayed on the same view according to the logical relationship between the attribute information of multiple second specified attributes.

[0045] This embodiment displays related log data centrally on a single view. This not only allows for intuitive comparison and analysis of events and behaviors across firmware or modules, but also significantly improves the efficiency and accuracy of diagnosing system problems. Through this centralized display method, developers can identify the root cause of problems more quickly, thereby shortening repair time and improving system stability and reliability.

[0046] Through the above steps, a first parsing operation is performed on the log files of a set of specified firmware to obtain parsing results corresponding to the log files of the set of specified firmware. The first parsing operation involves parsing attribute information of a set of log attributes from the log files of the set of specified firmware. The set of log attributes includes a first specified attribute, which is parsed according to the attribute information set for each specified firmware within the set of specified firmware. A second parsing operation is performed on the parsing results corresponding to the log files of the set of specified firmware to obtain a set of associated parsing results. The second parsing operation involves finding the parsing results in the set of specified firmware where the attribute information of the first specified attribute is specified attribute information. The specified attribute information indicates at least one of the following: the association between different specified firmware, or the association between different modules within the same specified firmware. The set of associated parsing results is integrated according to the attribute information of the second specified attribute in the set of log attributes, and the integrated set of associated parsing results is displayed on the same view. This solves the problem in related technologies where log file processing methods are affected by omissions or misunderstandings of information, thus affecting the accuracy and speed of problem solving, and improves the accuracy and efficiency of problem solving.

[0047] In one exemplary embodiment, a first parsing operation is performed on the log files of a specified set of firmware to obtain parsing results corresponding to the log files of the specified set of firmware, including:

[0048] S11, perform the first parsing operation in parallel on the log files of each specified firmware in a set of specified firmware to obtain the parsing result corresponding to the log file of each specified firmware. The log file of each specified firmware is obtained from the log file storage location corresponding to each specified firmware. The set of log attributes also includes at least one of the following: log number, timestamp, error code, module identifier, log level, event type, and log content.

[0049] To improve log parsing efficiency, the first parsing operation can be performed in parallel on the log files of each specified firmware in a set of specified firmware, so as to obtain the parsing result corresponding to the log file of each specified firmware.

[0050] Typically, log files are stored in a specific location on the device or system where the firmware resides, such as in a specific folder or directory. To obtain the log file for each specific firmware, you can access the log file storage location corresponding to that firmware.

[0051] Similar to the foregoing embodiments, the key attributes may differ across different firmware versions, and may be defined for each firmware version. In addition to the key attributes mentioned in the foregoing embodiments, a set of log attributes includes at least one of the following: log number, timestamp, error code, module identifier, log level, event type, and log content.

[0052] 1. Log ID: A unique identifier assigned to each log entry, making it easy to find a specific log record when needed.

[0053] For example: LogID:0012345.

[0054] 2. Timestamp: Records the specific time when the log was created, usually including the date and time.

[0055] For example: 2023-03-15 14:22:10.

[0056] 3. Error Code: This indicates the code of the error or warning recorded in the log, making it easier to identify the type of problem.

[0057] For example: ErrorCode:0x0001.

[0058] 4. Module ID: Indicates the firmware module that generated the log, which helps to locate the problem.

[0059] For example: ModuleID:NetworkController (network controller module).

[0060] 5. Log Level: Indicates the severity of the log, such as INFO (Information), WARN (Warning), ERROR, etc., used to quickly determine the severity of the problem. Among them, the INFO level is usually used to record general information, the WARN level is used to indicate possible problems, and the ERROR level is used to record errors or abnormal situations.

[0061] For example: LogLevel:ERROR.

[0062] 6. Event Type: Indicates the type of event recorded in the log, such as system startup, device failure, etc.

[0063] For example: EventType: DeviceFailure.

[0064] 7. Log Message: Provides a detailed description of the specific content and related information of the log entry.

[0065] For example: LogMessage: "Network connection lost. Please check the network cable." The log message indicates that the network connection has been lost and the network cable needs to be checked.

[0066] In this embodiment, by performing the first parsing in parallel on the log files of multiple specified firmware, the efficiency of log parsing can be improved.

[0067] In an exemplary embodiment, before performing a first parsing operation on a set of specified firmware log files to obtain parsing results corresponding to the set of specified firmware log files, the above method further includes:

[0068] S21, extract firmware information of a set of specified firmware and attribute information set for a specified firmware in a set of specified firmware from the preset configuration information, wherein the preset configuration information is used to configure the firmware to be parsed for log files and the attribute information set for the firmware to be parsed for log files.

[0069] S22, according to the firmware information of a set of specified firmware, extract the log files of a set of specified firmware from the log file storage location corresponding to each specified firmware in the set of specified firmware.

[0070] The preset configuration information is used to configure the firmware to be parsed for log files and the attribute information set for the firmware to be parsed for log files. That is, the preset configuration information includes firmware information of the specified firmware and indication information of attribute information.

[0071] For example, in this embodiment, the preset configuration information may include, but is not limited to: BMC checking that the sensor temperature exceeds a threshold, BMC controlling the fan to increase its speed, CPLDPWM control signal changes, and BMC recording changes in fan speed.

[0072] To improve resource utilization, in this embodiment, it is not necessary to perform full parsing of all log files of all firmware in the computer system. That is, the firmware information of a set of specified firmware and the attribute information set for a specified firmware in a set of specified firmware are extracted from the preset configuration information. According to the firmware information of a set of specified firmware, the log files of a set of specified firmware are extracted from the log file storage location corresponding to each specified firmware in a set of specified firmware.

[0073] Optionally, in order to further reduce the log data parsed, in this embodiment, the first parsing operation may be performed only on log entries that contain attribute information of a specified firmware setting from a set of specified firmware extracted from preset configuration information.

[0074] In this embodiment, based on preset configuration information, a portion of log files are selectively selected from the full log files for the first parsing operation, which reduces the amount of log data that the system needs to parse, improves system resource utilization, and increases log parsing efficiency.

[0075] In one exemplary embodiment, a first parsing operation is performed on the log files of a specified set of firmware to obtain parsing results corresponding to the log files of the specified set of firmware, including:

[0076] S31, based on the log parsing rules corresponding to a set of specified firmware, the log files of a set of specified firmware are parsed line by line according to a set of log attributes to obtain the parsing results corresponding to the log files of a set of specified firmware. The log parsing rules corresponding to a set of specified firmware are used to indicate the method of parsing the attribute information of a set of log attributes from the log files of different specified firmware in a set of specified firmware.

[0077] Considering that log files of different firmware may correspond to different log formats, in this embodiment, log files of a set of specified firmware can be parsed one by one according to a set of log attributes based on log parsing rules corresponding to a set of specified firmware.

[0078] The log parsing rules corresponding to a set of specified firmware are used to indicate how to parse attribute information of a set of log attributes from the log files of different specified firmware within the set of specified firmware.

[0079] For example, in this embodiment, a detailed set of log parsing rules can be defined. These rules are customized for the specific log recording formats of different firmware (such as BMC, BIOS, CPLD, etc.), and corresponding parsing rules are formulated according to their structural characteristics. These parsing rules include, but are not limited to, identifying and parsing operation timestamps, event types, error codes, and related module identifiers.

[0080] For BMC / BIOS logs, the log recording format is defined as: [timestamp][log level][module][log content]. The [log content] typically includes: key value records, key value changes, error descriptions, etc., and the parsing rules are defined as follows:

[0081] Key numerical records: parsed according to the "keyword:value" format;

[0082] Key value changes: Parsed according to the format "value descriptor: value old → value new";

[0083] Error description: Error descriptions are mainly identified by defining specific error identifiers, such as error, fail, fault, etc.

[0084] For CPLDs, due to limited storage space, only critical hardware signals are typically recorded. One recording method uses one bit to represent one signal value, and a hexadecimal number can record eight signals. When a hardware signal changes, all signal values ​​and the current time are saved as a log in hexadecimal. The CPLD log parsing rules define the bit position, module, and timestamp corresponding to each signal.

[0085] In this embodiment, after defining the log parsing rules, the next step is to implement these rules to automatically parse the log files in the computer system. This process mainly involves programmatically scanning the log files line by line to accurately extract key data. This data includes, but is not limited to, the log timestamps, key variables involved, the specific module to which the log belongs, and any recorded error reports.

[0086] Parsing methods include using regular expressions and fuzzy matching techniques to match specific formats in the log text. For example, regular expressions can be used to identify and extract standard timestamp formats, error codes, or specific keywords; and predefined error identifiers can be used to identify error log entries in the log.

[0087] In this embodiment, by using log parsing rules corresponding to different firmware to parse the generated log files, parsing results corresponding to different firmware can be obtained, thereby improving the readability of log data.

[0088] In an exemplary embodiment, after performing a first parsing operation on a set of specified firmware log files to obtain parsing results corresponding to the set of specified firmware log files, the above method further includes:

[0089] S41, convert the parsing results corresponding to the log files of a set of specified firmware into log data in a specified data format to obtain the log data corresponding to the log files of a set of specified firmware.

[0090] S42, save the log data corresponding to a set of specified firmware log files to the target database, wherein the second parsing operation is performed on the log data corresponding to a set of specified firmware log files in the target database.

[0091] To facilitate the second parsing operation, the parsing results corresponding to the log files of a specified set of firmware can be converted into log data in a specified data format, resulting in log data corresponding to the log files of the specified set of firmware. This log data is then saved to the target database. Using a unified log format allows for convenient management and storage of log files from various firmware, and facilitates easy searching and analysis of log data.

[0092] For example, in this embodiment, the logs are centrally processed, converted into a unified data format, and saved to the database, so that relevant information can be quickly retrieved in subsequent correlation analysis and result display.

[0093] Optionally, in this embodiment, performing a first parsing operation on a set of specified firmware log files to obtain parsing results corresponding to the set of specified firmware log files, converting the parsing results corresponding to the set of specified firmware log files into log data in a specified data format to obtain log data corresponding to the set of specified firmware log files; saving the log data corresponding to the set of specified firmware log files to the target database may include the following steps:

[0094] Step 1, Identify Log Format: Identify the format of the log files generated by each firmware. This may include timestamps, log levels (such as errors, warnings, messages, etc.), log content, etc.

[0095] Step 2, Parse the log content: Based on the format of the logs generated by each firmware, write or use existing parsing tools to extract key information from the logs.

[0096] Step 3, Define a unified format: Determine a common data format, which may include the aforementioned log attributes, such as fields like timestamp, log level, module identifier, and log content. This format can accommodate the main information from logs across all different firmware versions.

[0097] Step 4, Transform Log Data: Convert the raw log data of each firmware into a defined uniform format. This can be done through methods such as data mapping, field renaming, or data type conversion.

[0098] Step 5, Data Standardization: Ensure that the transformed data is consistent in format, such as date and time formats, log level naming, etc.

[0099] Step 6, Storage and Use: Store the converted, uniformly formatted logs in a location that is easily accessible and processed, such as a database or log management system. This allows for further analysis, monitoring, or report generation.

[0100] Optionally, in this embodiment, the second parsing operation is performed on the log data in the target database corresponding to the log files of a set of specified firmware.

[0101] This embodiment simplifies the complexity of data analysis and processing, improves efficiency, and enables unified management of log data from different devices or firmware by converting log files generated by different firmware into a unified format for centralized storage.

[0102] In one exemplary embodiment, integrating a set of association resolution results according to the attribute information of a second specified attribute in a set of log attributes includes:

[0103] S51, according to the association relationship indicated by the specified attribute information and the time order indicated by the timestamp attribute information, a set of association resolution results are integrated, wherein the second specified attribute includes the first specified attribute and the timestamp, and the integrated set of association resolution results is consistent with the association relationship indicated by the specified attribute information.

[0104] The specified attribute information is used to indicate at least one of the following:

[0105] The association between the status signal of the first specified firmware in a set of specified firmware and the firmware operation of the second specified firmware in a set of specified firmware, wherein the specified attribute information includes first attribute information and second attribute information, the first attribute information is used to record the status signal of the first specified firmware, and the second attribute information is used to record the firmware operation of the second specified firmware.

[0106] A chain of state changes for a specified firmware in a set of specified firmware triggered by a specified event, wherein the specified attribute information includes third attribute information corresponding to each specified firmware in the set of specified firmware, and the third attribute information corresponding to each specified firmware is used to record the state changes of each specified firmware.

[0107] The association between a specified operation performed by a target component controlled by a fourth specified firmware in a set of specified firmware and the execution result of the specified operation obtained by the fourth specified firmware, wherein the specified attribute information includes fourth attribute information and fifth attribute information. The fourth attribute information is used to record the specified operation performed by the target component controlled by the fourth specified firmware, and the fifth attribute information is used to record the execution result of the specified operation obtained by the fourth specified firmware.

[0108] The association between status signals of the same type for each specified firmware in a set of specified firmware, wherein the specified attribute information includes a sixth attribute information corresponding to each specified firmware in the set of specified firmware, the sixth attribute information being used to record the status signals of the same type for each specified firmware.

[0109] In this embodiment, to improve the readability of a set of association resolution results displayed on the same view, the set of association resolution results can be integrated according to the association relationships indicated by the specified attribute information and / or the time order indicated by the timestamp attribute information. That is, a set of association resolution results can be displayed sequentially according to the chronological order, or sequentially according to the association relationships.

[0110] For example, in this embodiment, the definition of specified attribute information (also known as associated attribute information) includes, but is not limited to, the following aspects:

[0111] 1. Data association: (1) The association relationship between the same type of status signals of each specified firmware in a set of specified firmware, wherein the specified attribute information includes the sixth attribute information corresponding to each specified firmware in a set of specified firmware, the sixth attribute information is used to record the same type of status signals of each specified firmware, that is, to associate the same type of attribute information between different firmware or different modules.

[0112] (2) The association between the status signal of a first specified firmware in a set of specified firmware and the firmware operation of a second specified firmware in a set of specified firmware, wherein the specified attribute information includes first attribute information and second attribute information. The first attribute information is used to record the status signal of the first specified firmware, and the second attribute information is used to record the firmware operation of the second specified firmware. That is, the data association between different components refers to the association between the status signal recorded by one component and the data recorded by another component. For example, the temperature signal recorded by a sensor component may be associated with the operation data of another control component.

[0113] 2. Event-triggered state change chain: A state change chain of specified firmware within a set of specified firmware triggered by a specified event. The specified attribute information includes third attribute information corresponding to each specified firmware in the set, which is used to record the state changes of each specified firmware. This means that a state change in one component can trigger state changes in other components, forming an event-triggered state change chain. For example, when a sensor detects that the ambient temperature exceeds a preset range, its state change will trigger the control component to activate the cooling system, thereby causing other related components to adjust their states.

[0114] 3. Control and Feedback Mechanism: This mechanism establishes the correlation between a specified operation performed by a target component controlled by a fourth specified firmware within a set of specified firmware, and the execution result of that specified operation obtained by the fourth specified firmware. The specified attribute information includes fourth attribute information and fifth attribute information. The fourth attribute information records the specified operation performed by the target component controlled by the fourth specified firmware, and the fifth attribute information records the execution result of the specified operation obtained by the fourth specified firmware. In this control and feedback mechanism, a component performs a control operation based on sensor data and records the corresponding changes. For example, a control component can adjust the fan speed based on temperature sensor data and simultaneously record the changes in fan speed.

[0115] Examples of related attribute information definitions are as follows:

[0116] The association between status signals of the same type in each specified firmware in a set of specified firmware: the external card presence status signal recorded by the CPLD is associated with the external card presence status data recorded by the BMC, and is also associated with data such as PCIe link status in the BIOS log.

[0117] A chain of state changes for a specified firmware within a set of specified firmware triggered by a specified event: abnormal output voltage / current data of PSU (Power supply unit) → change in CPLD power status signal → change in CPLD backup power signal → change in CPLD power-on / off signal.

[0118] The correlation between the specified operation performed by the target component controlled by the fourth specified firmware in a set of specified firmware and the execution result of the specified operation obtained by the fourth specified firmware: BMC checks that the sensor temperature exceeds the threshold → BMC controls the fan to increase the speed → CPLD PWM control signal changes → BMC records the fan speed change.

[0119] Based on predefined event types and associated attributes, the system further matches and associates log entries. Specifically, the system automatically identifies and matches relevant information within log entries according to the defined event types and associated attributes, categorizing related log entries. The categorized association results are then saved to the database for future querying and analysis.

[0120] Based on the results of the correlation analysis, the system integrates the related log data into a unified view for display. This view shows in detail the occurrence time, duration, and relationship of each event to other events.

[0121] The view is presented through a graphical user interface, allowing users to intuitively understand the chronological order and logical relationships of events. Users can use this interface to view detailed log data for a specific event or observe how multiple events interact.

[0122] Optionally, in this embodiment, combined with Figure 4 A set of association resolution results can be stored using log numbers as identifiers.

[0123] This embodiment allows for the centralized display of a set of association resolution results on the same page view based on the logical order of the association relationship or the time order indicated by the timestamp, which can improve the readability of the displayed log data.

[0124] In one exemplary embodiment, a set of designated firmware refers to firmware on the same server, and the set of designated firmware includes at least one of the following: a baseboard management controller, a basic input / output system, and a programmable logic device.

[0125] A Baseboard Management Controller (BMC) is firmware used for monitoring and managing server and data center hardware. It is responsible for monitoring hardware status, system health, and enabling remote management. The BMC typically communicates with other system components via the Intelligent Platform Management Interface (IPMI) protocol.

[0126] BIOS (Basic Input / Output System) is a type of firmware used to initialize and configure hardware devices when a computer starts up so that the operating system can load and run. The BIOS is responsible for performing the self-test (POST) process, setting the system clock, and other basic system settings.

[0127] A programmable logic device (PLD) is a semiconductor device that can be programmed to perform specific digital logic functions. They are commonly used to implement complex digital circuit designs, such as FPGAs (Field-Programmable Gate Arrays) and CPLDs (Complex Programmable Logic Devices).

[0128] In advanced server and data center environments, firmware BMC, BIOS, and PLD may be used for efficient monitoring and management. BMC is used to monitor and manage system systems, BIOS is used to initialize and manage hardware devices, and PLD can be used to implement specific logical functions or hardware interfaces.

[0129] In some custom hardware designs, these three firmware types may be needed to implement specific functions. For example, a custom embedded system may require a BMC for remote management and monitoring, a BIOS for initializing and configuring hardware devices, and a PLD for implementing specific hardware interfaces or logic functions.

[0130] In some complex industrial control systems, these three firmware types may be needed to achieve highly integrated monitoring, control, and management functions. The BMC can be used for remote monitoring and management, the BIOS is used to configure and initialize hardware devices, and the PLD can be used to implement specific control logic or interfaces.

[0131] In this embodiment, we take the example of BMC, BIOS and PLD running on the same server.

[0132] Optionally, in this embodiment, a set of specified firmware may also include, but is not limited to:

[0133] Hard drive firmware, whose firmware log is used to record events that affect the operation of the hard drive, such as errors, failures, and performance problems.

[0134] RAID card firmware, whose firmware log is used to record events that affect the operation of the RAID array, including array configuration and status changes.

[0135] Network interface card (NIC) firmware, its firmware log is used to record events that affect NIC operation, such as connection and disconnection, packet loss and error rate.

[0136] The server management controller firmware has a firmware log used to record hardware status and events, such as temperature, fan speed, and other sensor readings.

[0137] TPM (Trusted Platform Module) firmware has a firmware log used to record security events, such as firmware or software signature verification or secure boot processes.

[0138] The storage controller firmware, whose firmware log is used to record events that affect the operation of the storage controller, including cached battery status or SSD firmware updates.

[0139] The firmware of network switches and routers includes firmware logs used to record events that affect the operation of network devices, such as configuration changes, interface status, and routing table updates.

[0140] As an optional exemplary embodiment of this application, the log file processing method of the embodiments of this application will be explained and described using the integration and analysis of log data between different firmware and different modules of the same firmware in a computer system as an example.

[0141] Combination Figure 5 The log file processing method in this application embodiment may include the following steps:

[0142] Log parsing rule definition: First, this embodiment defines log parsing rules, which are customized for specific log recording formats, keywords, and modules of different firmware (such as BMC, BIOS, CPLD, etc.). These rules ensure that key information, such as operation timestamps, event types, error codes, and related module identifiers, is accurately extracted from various log formats.

[0143] Log parsing execution: According to the log parsing rules defined above, the method in this embodiment automatically parses the log files (i.e., source logs) in the computer system one by one to extract key data, including but not limited to timestamps, key variables, the module to which the log belongs, and any error reports.

[0144] Association Attribute Definitions: This embodiment further defines the association attributes between different firmware components and between different modules within the same firmware. These association definitions indicate how different components interact with each other and how specific events affect the behavior and performance of the entire system.

[0145] Log Correlation Analysis: After completing basic log parsing, this embodiment further performs log correlation analysis. This step involves matching and associating log entries from different firmware or modules based on timestamps, event types, or defined association attributes. Through this correlation analysis, potential causal relationships or patterns can be identified.

[0146] Log Association Display: Based on the association analysis results from the previous steps, this embodiment displays related log data centrally on the same view. This not only allows for intuitive comparison and analysis of events and behaviors across firmware or modules, but also significantly improves the efficiency and accuracy of diagnosing system problems. Through this centralized display method, developers can identify the root cause of problems more quickly, thereby shortening repair time and improving system stability and reliability.

[0147] Overall, this embodiment significantly improves the efficiency of firmware problem diagnosis and resolution in computer systems by integrating and optimizing the log analysis process, which is extremely valuable for maintaining complex computer system environments.

[0148] This application proposes a computer system hardware log correlation analysis system and method, aiming to improve the integration and analysis of log data between different firmware and modules in a computer system. The method includes defining log parsing rules, correlation attributes, performing log parsing, conducting log correlation parsing, and centrally displaying related log data. Through precise log parsing and correlation analysis, this solution can improve the accuracy of problem diagnosis and ensure the correct identification of the root cause of the problem. Centralized display of related log data makes problem identification and resolution faster, reducing the time required to locate the problem. A unified analysis framework promotes effective collaboration among personnel from different professional fields, improving the overall work efficiency of the team. Timely and accurate problem handling helps maintain the stability and reliability of the system, which is especially important for computer systems that rely on high availability.

[0149] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods of the various embodiments of this application.

[0150] According to another aspect of the embodiments of this application, a log file processing apparatus is also provided. This apparatus is used to implement the log file processing method provided in the above embodiments, and details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0151] Figure 6 This is a structural block diagram of an optional log file processing device provided in an embodiment of this application, such as... Figure 6 As shown, the device includes:

[0152] The first parsing unit 602 is used to perform a first parsing operation on a set of specified firmware log files to obtain a parsing result corresponding to the set of specified firmware log files. The first parsing operation is an operation to parse attribute information of a set of log attributes from the set of specified firmware log files. The set of log attributes includes a first specified attribute, which is parsed according to the attribute information set for the specified firmware in the set of specified firmware.

[0153] The second parsing unit 604 is used to perform a second parsing operation on the parsing results corresponding to the log files of a set of specified firmware to obtain a set of associated parsing results. The second parsing operation is to find the parsing results in which the attribute information of the first specified attribute is the specified attribute information in the parsing results corresponding to the log files of a set of specified firmware. The specified attribute information is used to indicate at least one of the following: the association relationship between different specified firmware, and the association relationship between different modules within the same specified firmware.

[0154] Execution unit 606 is used to integrate a set of association parsing results according to the attribute information of the second specified attribute in a set of log attributes, and display the integrated set of association parsing results on the same view.

[0155] It should be noted that the first parsing unit 602 in this embodiment can be used to execute the above step S202, the second parsing unit 604 in this embodiment can be used to execute the above step S204, and the execution unit 606 in this embodiment can be used to execute the above step S206.

[0156] Through the embodiments of this application, a first parsing operation is performed on the log files of a set of specified firmware to obtain parsing results corresponding to the log files of the set of specified firmware. The first parsing operation is an operation to parse attribute information of a set of log attributes from the log files of the set of specified firmware. The set of log attributes includes a first specified attribute, which is parsed according to the attribute information set for the specified firmware in the set of specified firmware. A second parsing operation is performed on the parsing results corresponding to the log files of the set of specified firmware to obtain a set of associated parsing results. The second parsing operation is an operation to find the parsing results of the first specified attribute in the parsing results corresponding to the log files of the set of specified firmware where the attribute information is the specified attribute information. The specified attribute information is used to indicate at least one of the following: the association relationship between different specified firmware, and the association relationship between different modules within the same specified firmware. The set of associated parsing results is integrated according to the attribute information of the second specified attribute in the set of log attributes, and the integrated set of associated parsing results is displayed on the same view. This solves the problem in the related art where the accuracy and speed of problem solving are affected by the omission or misunderstanding of information in the log file processing method.

[0157] In one exemplary embodiment, the first parsing unit includes:

[0158] The first parsing module is used to perform a first parsing operation in parallel on the log files of each specified firmware in a set of specified firmware, and obtain the parsing result corresponding to the log file of each specified firmware. The log file of each specified firmware is obtained from the log file storage location corresponding to each specified firmware. The set of log attributes also includes at least one of the following: log number, timestamp, error code, module identifier, log level, event type, and log content.

[0159] In one exemplary embodiment, the above-described apparatus further includes:

[0160] The first extraction unit is used to extract firmware information of a set of specified firmware and attribute information set for a specified firmware in a set of specified firmware from preset configuration information before performing a first parsing operation on the log files of a set of specified firmware and obtaining the parsing results corresponding to the log files of a set of specified firmware. The preset configuration information is used to configure the firmware to be parsed and the attribute information set for the firmware to be parsed.

[0161] The second extraction unit is used to extract the log files of a set of specified firmware from the log file storage location corresponding to each specified firmware in the set of specified firmware, according to the firmware information of the set of specified firmware.

[0162] In one exemplary embodiment, the first parsing unit includes:

[0163] The second parsing module is used to parse the log files of a set of specified firmware one by one according to a set of log attributes based on the log parsing rules corresponding to a set of specified firmware, and to obtain the parsing results corresponding to the log files of a set of specified firmware. The log parsing rules corresponding to a set of specified firmware are used to indicate the method of parsing the attribute information of a set of log attributes from the log files of different specified firmware in a set of specified firmware.

[0164] In one exemplary embodiment, the above-described apparatus further includes:

[0165] The conversion unit is used to perform a first parsing operation on a set of specified firmware log files, and after obtaining the parsing result corresponding to the set of specified firmware log files, convert the parsing result corresponding to the set of specified firmware log files into log data in a specified data format, so as to obtain the log data corresponding to the set of specified firmware log files.

[0166] The storage unit is used to save log data corresponding to a set of specified firmware log files into the target database, wherein the second parsing operation is performed on the log data corresponding to the set of specified firmware log files in the target database.

[0167] In one exemplary embodiment, the execution unit includes:

[0168] The integration module is used to integrate a set of association resolution results according to the association relationship indicated by the specified attribute information and the time order indicated by the timestamp attribute information. The second specified attribute includes the first specified attribute and the timestamp. The integrated set of association resolution results is consistent with the association relationship indicated by the specified attribute information.

[0169] The specified attribute information is used to indicate at least one of the following:

[0170] The association between the status signal of the first specified firmware in a set of specified firmware and the firmware operation of the second specified firmware in a set of specified firmware, wherein the specified attribute information includes first attribute information and second attribute information, the first attribute information is used to record the status signal of the first specified firmware, and the second attribute information is used to record the firmware operation of the second specified firmware.

[0171] A chain of state changes for a specified firmware in a set of specified firmware triggered by a specified event, wherein the specified attribute information includes third attribute information corresponding to each specified firmware in the set of specified firmware, and the third attribute information corresponding to each specified firmware is used to record the state changes of each specified firmware.

[0172] The association between a specified operation performed by a target component controlled by a fourth specified firmware in a set of specified firmware and the execution result of the specified operation obtained by the fourth specified firmware, wherein the specified attribute information includes fourth attribute information and fifth attribute information. The fourth attribute information is used to record the specified operation performed by the target component controlled by the fourth specified firmware, and the fifth attribute information is used to record the execution result of the specified operation obtained by the fourth specified firmware.

[0173] The association between status signals of the same type for each specified firmware in a set of specified firmware, wherein the specified attribute information includes a sixth attribute information corresponding to each specified firmware in the set of specified firmware, the sixth attribute information being used to record the status signals of the same type for each specified firmware.

[0174] In one exemplary embodiment, a set of designated firmware refers to firmware on the same server, and the set of designated firmware includes at least one of the following: a baseboard management controller, a basic input / output system, and a programmable logic device.

[0175] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0176] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when run.

[0177] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as USB flash drives, ROM (Read-Only Memory), RAM (Random Access Memory), portable hard drives, magnetic disks, or optical disks.

[0178] Embodiments of this application also provide an electronic device, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0179] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0180] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0181] Embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0182] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0183] The embodiments described herein also provide a computer program that includes computer instructions stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the steps in any of the above method embodiments.

[0184] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0185] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A method for processing log files, characterized in that, include: A first parsing operation is performed on the log files of a set of specified firmware to obtain the parsing result corresponding to the log files of the set of specified firmware. The first parsing operation is an operation to parse the attribute information of a set of log attributes from the log files of the set of specified firmware. The set of log attributes includes a first specified attribute, which is parsed according to the attribute information set for the specified firmware in the set of specified firmware. A second parsing operation is performed on the parsing results corresponding to the log files of the specified set of firmware to obtain a set of associated parsing results. The second parsing operation is to find the parsing results in which the attribute information of the first specified attribute is the specified attribute information in the parsing results corresponding to the log files of the specified set of firmware. The specified attribute information is used to indicate at least one of the following: the association relationship between different specified firmware, and the association relationship between different modules within the same specified firmware. The set of association resolution results are integrated according to the attribute information of the second specified attribute in the set of log attributes, and the integrated set of association resolution results are displayed on the same view; The integration of the set of association parsing results according to the attribute information of the second specified attribute in the set of log attributes includes: integrating the set of association parsing results according to the association relationship indicated by the specified attribute information and the time order indicated by the timestamp attribute information, wherein the second specified attribute includes the first specified attribute and the timestamp, and the integrated set of association parsing results is consistent with the association relationship indicated by the specified attribute information; wherein the specified attribute information is used to indicate at least one of the following: the association relationship between the status signal of the first specified firmware in the set of specified firmware and the firmware operation of the second specified firmware in the set of specified firmware, wherein the specified attribute information includes first attribute information and second attribute information, the first attribute information is used to record the status signal of the first specified firmware, and the second attribute information is used to record the firmware operation of the second specified firmware; a state change chain of the specified firmware in the set of specified firmware triggered by a specified event, wherein... The specified attribute information includes third attribute information corresponding to each specified firmware in the set of specified firmware, and the third attribute information corresponding to each specified firmware is used to record the state changes of each specified firmware; the association between the specified operation executed by the target component controlled by the fourth specified firmware in the set of specified firmware and the execution result of the specified operation obtained by the fourth specified firmware, wherein the specified attribute information includes fourth attribute information and fifth attribute information, the fourth attribute information is used to record the specified operation executed by the target component controlled by the fourth specified firmware, and the fifth attribute information is used to record the execution result of the specified operation obtained by the fourth specified firmware; the association between the same type of state signals of each specified firmware in the set of specified firmware, wherein the specified attribute information includes sixth attribute information corresponding to each specified firmware in the set of specified firmware, and the sixth attribute information is used to record the same type of state signals of each specified firmware.

2. The method according to claim 1, characterized in that, The first parsing operation performed on a set of specified firmware log files to obtain parsing results corresponding to the set of specified firmware log files includes: The first parsing operation is performed in parallel on the log files of each specified firmware in the set of specified firmware to obtain the parsing result corresponding to the log file of each specified firmware. The log file of each specified firmware is obtained from the log file storage location corresponding to each specified firmware. The set of log attributes also includes at least one of the following: log number, timestamp, error code, module identifier, log level, event type, and log content.

3. The method according to claim 1, characterized in that, Before performing the first parsing operation on a set of specified firmware log files to obtain the parsing result corresponding to the set of specified firmware log files, the method further includes: The firmware information of the specified set of firmware and the attribute information set for the specified firmware in the specified set of firmware are extracted from the preset configuration information. The preset configuration information is used to configure the firmware to be parsed for log files and the attribute information set for the firmware to be parsed for log files. Based on the firmware information of the specified set of firmware, the log files of the specified set of firmware are extracted from the log file storage location corresponding to each specified firmware in the specified set of firmware.

4. The method according to claim 1, characterized in that, The first parsing operation performed on a set of specified firmware log files to obtain parsing results corresponding to the set of specified firmware log files includes: Based on the log parsing rules corresponding to the set of specified firmware, the log files of the set of specified firmware are parsed line by line according to the set of log attributes to obtain the parsing results corresponding to the log files of the set of specified firmware. The log parsing rules corresponding to the set of specified firmware are used to indicate the method of parsing the attribute information of the set of log attributes from the log files of different specified firmware in the set of specified firmware.

5. The method according to claim 1, characterized in that, After performing a first parsing operation on a set of specified firmware log files to obtain parsing results corresponding to the set of specified firmware log files, the method further includes: The parsing results corresponding to the log files of the specified set of firmware are converted into log data in a specified data format to obtain the log data corresponding to the log files of the specified set of firmware. The log data corresponding to the log files of the specified set of firmware is saved to the target database, wherein the second parsing operation is performed on the log data corresponding to the log files of the specified set of firmware in the target database.

6. The method according to any one of claims 1 to 5, characterized in that, The specified set of firmware refers to firmware on the same server, and the specified set of firmware includes at least one of the following: a baseboard management controller, a basic input / output system, and a programmable logic device.

7. A log file processing apparatus, characterized in that, include: The first parsing unit is used to perform a first parsing operation on the log files of a set of specified firmware to obtain a parsing result corresponding to the log files of the set of specified firmware. The first parsing operation is an operation to parse attribute information of a set of log attributes from the log files of the set of specified firmware. The set of log attributes includes a first specified attribute, which is parsed according to the attribute information set for the specified firmware in the set of specified firmware. The second parsing unit is used to perform a second parsing operation on the parsing results corresponding to the log files of the set of specified firmware to obtain a set of associated parsing results. The second parsing operation is to find the parsing results in which the attribute information of the first specified attribute is the specified attribute information in the parsing results corresponding to the log files of the set of specified firmware. The specified attribute information is used to indicate at least one of the following: the association relationship between different specified firmware, and the association relationship between different modules within the same specified firmware. An execution unit is used to integrate the set of association parsing results according to the attribute information of the second specified attribute in the set of log attributes, and to display the integrated set of association parsing results on the same view; The execution unit includes: an integration module, configured to integrate the set of association parsing results according to the association relationship indicated by the specified attribute information and the time sequence indicated by the timestamp attribute information, wherein the second specified attribute includes the first specified attribute and the timestamp, and the integrated set of association parsing results is consistent with the association relationship indicated by the specified attribute information; wherein the specified attribute information is used to indicate at least one of the following: the association relationship between the status signal of the first specified firmware in the set of specified firmware and the firmware operation of the second specified firmware in the set of specified firmware, wherein the specified attribute information includes first attribute information and second attribute information, the first attribute information is used to record the status signal of the first specified firmware, and the second attribute information is used to record the firmware operation of the second specified firmware; a state change chain of the specified firmware in the set of specified firmware triggered by a specified event, wherein the specified attribute information includes the association relationship between the first specified firmware and the second specified firmware, and the second specified firmware, and the third specified firmware, and the fourth specified firmware, and the fifth specified firmware, and the sixth specified firmware, and the seventh specified firmware, and the eighth specified firmware, and the ninth specified firmware, and the tenor relationship ... The third attribute information corresponding to each specified firmware in the group of specified firmware is used to record the state changes of each specified firmware; the association between the specified operation executed by the target component controlled by the fourth specified firmware in the group of specified firmware and the execution result of the specified operation obtained by the fourth specified firmware, wherein the specified attribute information includes fourth attribute information and fifth attribute information, the fourth attribute information is used to record the specified operation executed by the target component controlled by the fourth specified firmware, and the fifth attribute information is used to record the execution result of the specified operation obtained by the fourth specified firmware; the association between the same type of state signals of each specified firmware in the group of specified firmware, wherein the specified attribute information includes a sixth attribute information corresponding to each specified firmware in the group of specified firmware, and the sixth attribute information is used to record the same type of state signals of each specified firmware.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the method of any one of claims 1 to 6.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method of any one of claims 1 to 6.

Images