BMC (Baseboard Management Controller) log generation method, BMC log processing method and related equipment thereof

Abstract

The invention relates to a BMC log generation method, a BMC log processing method and related equipment thereof. The method comprises the steps that a BMC node obtains target operation information corresponding to a target function module monitored by the BMC node; under the condition that the target function module is determined to be abnormal according to the target operation information, determining a target log information format required by a target BMC log to be generated from a preset log information format set according to the target function module and an event type indicated by the target operation information, the target log information format is used for defining a structured format of target log information included in the target BMC log; filling the target log information format with the target operation information to obtain target log information; and based on a preset log template, packaging the target log information to generate a target BMC log. According to the method and the device, the BMC log generation flexibility is improved, and the subsequent log analysis efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of information processing technology, and in particular to a BMC log generation method, a BMC log processing method, and related equipment. Background Technology

[0002] In a Baseboard Management Controller (BMC) cluster, BMC nodes typically monitor various functional modules within the server during operation. This monitoring generates logs of the monitored modules' operational information, facilitating subsequent log analysis and enabling efficient BMC node operation. Currently, BMC nodes usually generate logs using a fixed log format. However, because different functional modules have varying log analysis requirements, using a fixed format can obscure crucial information, resulting in low log generation flexibility and inefficient subsequent log analysis. Summary of the Invention

[0003] To address the above issues, this application provides a BMC log generation method, a BMC log processing method, and related equipment.

[0004] Firstly, this application provides a BMC log generation method, applied to BMC nodes in a BMC cluster, the method comprising: Obtain the target operation information corresponding to the target functional module monitored by the BMC node; If the target functional module is determined to be abnormal based on the target operation information, the target log information format required for the target BMC log to be generated is determined from the preset log information format set according to the event type indicated by the target functional module and the target operation information. The target running information is filled into the target log information format to obtain the target log information; Based on a preset log template, the target log information is encapsulated to generate the target BMC log.

[0005] Through the above methods, this embodiment pre-sets a preset log information format set. When the target functional module is determined to be abnormal based on the target operation information corresponding to the monitored target functional module obtained by the BMC node, the target log information format required for the target BMC log to be generated is determined from the preset log information format set according to the event type indicated by the target functional module and the target operation information. The target operation information is then filled into the target log information format to obtain the target log information. The target log information is then encapsulated based on a preset template to achieve on-demand customization of the target BMC log, thereby improving the flexibility of log generation and the efficiency of subsequent log analysis.

[0006] In an optional implementation, determining the target log information format required for the target BMC log to be generated from a preset log information format set based on the event type indicated by the target functional module and the target operation information includes: Determine the target module type to which the target functional module belongs; Target rules that match the target module type and the event type indicated by the target operation information are determined from the preset rule set; Based on the target rule, the preset log information format corresponding to the target rule is determined from the first association relationship. The first association relationship stores the correspondence between each preset rule in the preset rule set and each preset log information format in the preset log information format set. The preset log information format corresponding to the target rule is determined as the target log information format required for the target BMC log to be generated.

[0007] In an optional implementation, before performing the step of filling the target runtime information into the target log information format to obtain the target log information, the method further includes: Based on the target operation information, determine the target alarm level corresponding to the target functional module; The step of encapsulating the target log information based on a preset log template to generate the target BMC log includes: Based on a preset log template, the target alarm level and the target log information are encapsulated to generate the target BMC log.

[0008] Secondly, this application provides a BMC log processing method applied to a log processing device, wherein the log processing device is connected to each BMC node in a BMC cluster, and the method includes: For each of the BMC nodes, a target BMC log sent by the BMC node is received, the target BMC log being generated by the BMC log generation method described above; The target classification dimension to which the target BMC log belongs is determined from the preset classification dimension set; Based on the target classification dimension, determine the target storage location corresponding to the target BMC log; Store the target BMC log to the target storage location.

[0009] In this embodiment, for each BMC node connected to the log processing device in the BMC cluster, after receiving the customized target BMC node sent by the BMC node, the corresponding target storage location is determined based on a pre-set preset classification dimension set to store the customized target BMC log in the corresponding target storage location. This achieves the ordered storage of customized target BMC logs, which facilitates the quick location of customized target BMC logs during subsequent log analysis, thus improving the efficiency of log analysis.

[0010] In an optional implementation, before performing the step of receiving the target BMC log sent by the BMC node, the method further includes: Receive node information corresponding to the BMC node sent by the BMC node; Register the node information to the log processing device; After completing the registration of the node information, the step of receiving the target BMC log sent by the BMC node is executed; The step of determining the target classification dimension to which the target BMC log belongs from the preset classification dimension set includes: If the node information corresponding to the BMC node exists in the log processing device, the target classification dimension to which the target BMC log belongs is determined from a preset classification dimension set. After performing the step of storing the target BMC log to the target storage location, the method further includes: Receive a first request sent by the target terminal, the first request being used to query the target BMC log; Based on the target storage location corresponding to the target BMC log, the target BMC log is determined from the target storage location, and the node information corresponding to the BMC node to which the target BMC log belongs is determined; The identified target BMC logs and the node information corresponding to the BMC nodes are sent to the target terminal.

[0011] In an optional implementation, after performing the step of storing the target BMC log to the target storage location, the method further includes: If the BMC node is updated, receive the update information sent by the BMC node; Using the updated information, the node information corresponding to the registered BMC node is updated to obtain the updated node information; Based on the updated node information, return to the step of receiving the target BMC log sent by the BMC node; and... Based on the node information, a heartbeat packet is sent to the BMC node; Upon receiving the response information for the heartbeat packet sent by the BMC node, return to the step of receiving the target BMC log sent by the BMC node.

[0012] In an optional implementation, the target BMC log may also include a target alarm level; The step of determining the target classification dimension to which the target BMC log belongs from the preset classification dimension set includes: Based on the target alarm level and the node information corresponding to the BMC node to which the target BMC log belongs, the target classification dimension to which the target BMC log belongs is determined from a preset classification dimension set; Determining the target storage location corresponding to the target BMC log based on the target classification dimension includes: Based on the target classification dimension, the second association relationship is queried to determine the target storage location corresponding to the target BMC log from the second association relationship. The second association relationship stores the correspondence between each preset classification dimension in the preset classification dimension set and the target storage location. After performing the step of storing the target BMC log to the target storage location, the method further includes: For each target storage location, all target BMC logs stored in the target storage location are aggregated to obtain target statistical results; The obtained log statistics results are displayed on the target interface according to their respective preset display formats.

[0013] Thirdly, this application provides a BMC log generation device, applied to a BMC node in a BMC cluster, the device comprising: The acquisition module is used to acquire the target operation information corresponding to the target functional module monitored by the BMC node; The first determining module is used to determine the target log information format required for the target BMC log to be generated from a preset log information format set, based on the target functional module and the event type indicated by the target operational information, when the target functional module is determined to be abnormal according to the target operational information. A filling module is used to fill the target running information into the target log information format to obtain the target log information; The generation module is used to encapsulate the target log information based on a preset log template to generate the target BMC log.

[0014] Fourthly, this application provides a BMC log processing device, applied to a log processing equipment, wherein the log processing equipment is connected to each BMC node in a BMC cluster, and the device includes: The receiving module is configured to receive a target BMC log sent by each of the BMC nodes, wherein the target BMC log is generated by the BMC log generation method described above. The second determining module is used to determine the target classification dimension to which the target BMC log belongs from a preset classification dimension set; The second determining module is further configured to determine the target storage location corresponding to the target BMC log based on the target classification dimension; A storage module is used to store the target BMC logs to the target storage location.

[0015] Fifthly, this application provides a BMC log management system, including a BMC cluster and a log processing device, wherein each BMC node in the BMC cluster is connected to the log processing device; Each BMC node is used to execute the BMC log generation method described above to generate the target BMC log; The log processing device is used to execute the BMC log processing method described above to store the received target BMC log to the target storage location. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0017] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

[0019] Figure 1 A flowchart illustrating a BMC log generation method provided in an embodiment of this application; Figure 2 A flowchart illustrating a BMC log processing method provided in an embodiment of this application; Figure 3 A schematic diagram of the structure of a BMC log management system provided in an embodiment of this application; Figure 4 A schematic diagram of a BMC log generation device provided in an embodiment of this application; Figure 5 A schematic diagram of the structure of a BMC log processing device provided in an embodiment of this application; Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of this application; In the attached diagrams above: 301. BMC Node; 302. Log Processing Equipment; 3021. Log Acquisition Service; 3022. Log Processing Service; 3023. Visualization Service; 401. Acquisition Module; 402. First Determination Module; 403. Filling Module; 404. Generation Module; 501. Receiving module; 502. Second determining module; 503. Storage module; 600. Electronic device; 601. Processor; 602. Memory; 6021. Operating system; 6022. Application program; 603. User interface; 604. Network interface; 605. Bus system. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0021] The following disclosure provides numerous different embodiments or examples for implementing various structures of the invention. To simplify the disclosure, specific examples of components and arrangements are described below. These are merely examples and are not intended to limit the scope of the invention. Furthermore, reference numerals and / or letters may be repeated in different examples. Such repetition is for simplification and clarity and does not in itself indicate a relationship between the various embodiments and / or arrangements discussed.

[0022] refer to Figure 1 , Figure 1 This is a flowchart illustrating a BMC log generation method provided in an embodiment of this application. The BMC log generation method provided in this embodiment includes the following steps: S101: Obtain the target operation information corresponding to the target functional module monitored by the BMC node.

[0023] In this embodiment, the method is applied to the BMC node in a BMC cluster. The BMC node is responsible for monitoring the operational information of various functional modules in the server. These functional modules can be understood as power modules, network interface card (NIC) modules, CPU modules, etc., within the server. Based on the functional modules that the BMC node needs to monitor, corresponding monitoring modules can be set up in the BMC node to monitor the operational information of these modules. For example, when the functional module is a power module, a power monitoring module can be set up in the BMC node to monitor its operational information. Target operational information can be understood as the real-time operational information of the target functional module. For example, when the target functional module is a power module, the target operational information could be the real-time current and real-time voltage of the power module. The target operational information is the original information that triggers the generation of the BMC log and serves as the objective basis for determining whether an anomaly has occurred in the target functional module. Specifically, during the operation of the target functional module, the functional monitoring module corresponding to the target functional module in the BMC node periodically reads the target operational information collected by the sensors in the target functional module, thereby obtaining the target operational information corresponding to the target functional module monitored by the BMC node.

[0024] S102: If the target functional module is found to be abnormal based on the target operation information, the target log information format required for the target BMC log to be generated is determined from the preset log information format set according to the event type indicated by the target functional module and the target operation information.

[0025] In this embodiment, after obtaining the target operation information corresponding to the target functional module monitored by the BMC node, the target operation information can be compared with a preset threshold or normal state range to determine whether the target functional module is abnormal. For example, when the target functional module is a power module, the real-time voltage of the power module is 30V, and the preset threshold is 24V. At this time, the real-time voltage is greater than the preset threshold, indicating that the target functional module is abnormal.

[0026] When a target functional module malfunctions, a corresponding BMC log needs to be generated to facilitate subsequent log analysis and determine the cause of the malfunction. To avoid the low flexibility and inefficient log analysis caused by using a fixed log information format, this embodiment pre-sets a preset log information format set. Based on the event type indicated by the target functional module and the target operating information, the required log information format for the target BMC log to be generated is determined from the preset log information format set. The event type can be understood as the functional module event type categorized based on the target operating information, used to distinguish the state scenarios of different functional modules. For example, if the target functional module is a power module, and the preset threshold is 24V while the real-time voltage of the power module is 30V, the event type could be "voltage exceeding limit." Each preset log information format in the aforementioned preset log information format set can be set based on the functional module and the event type indicated by the corresponding operating information. Therefore, when the target functional module malfunctions, the required target log information format can be determined from the preset log information format set based on the event type indicated by the target functional module and the target operating information.

[0027] In one implementation, step S102 above, based on the event type indicated by the target functional module and the target operating information, determines the target log format required for the target BMC log to be generated from a preset log information format set, specifically including: Determine the target module type to which the target functional module belongs; Target rules that match the target module type and the event type indicated by the target runtime information are determined from the preset rule set; Based on the target rule, the preset log information format corresponding to the target rule is determined from the first association relationship; The preset log information format corresponding to the target rule is determined as the target log information format required for the target BMC log to be generated.

[0028] Specifically, the functional modules that need to be monitored by the BMC node can be pre-classified into module types based on the monitoring dimension. For example, for the power function module that needs to be monitored in the BMC node, its module type can be classified as "Power Class." Functional modules of the same type have similar monitoring objects and event characteristics. By classifying functional modules into module types, it is unnecessary to create preset rules for matching preset log information formats for the same type of functional modules that need to be monitored by the BMC cluster, thus reducing the number of preset rules included in the preset rule set. The preset rule set includes multiple preset rules, each of which is a preset configuration rule that combines module type and event type as conditions.

[0029] Specifically, after obtaining the target runtime information, the target module type is determined. Using the target module type and the event type indicated by the target runtime information as matching conditions, a preset rule set is traversed to identify preset rules that match the target module type and event type. These matched preset rules are then designated as the target rules. It should be noted that if multiple preset rules are matched, the highest priority preset rule is determined based on the pre-set priority of each rule. This highest priority preset rule is then designated as the target rule to ensure the accuracy of the subsequently determined target log information format, thereby improving the efficiency of subsequent log analysis.

[0030] After determining the target rule, a first association relationship can be established. This first association relationship stores the correspondence between each preset rule in the preset rule set and each preset log information format in the preset log information format set. The target rule is then used to query the first association relationship to obtain the preset log information format corresponding to the target rule. This preset log information format is then determined as the target log information format required for the target BMC log to be generated. The determined target log information format is then used to generate the target log information required for the target BMC log. It should be noted that the preset log information format can be JSON, text, string, or binary, etc. Through the above method, this embodiment filters the target rule using dual conditions of target module type and event type, and then maps the target log information format corresponding to the target rule based on the first association relationship. This effectively avoids the confusion of target log information formats caused by single-condition matching. Furthermore, when adding a new functional module, it is only necessary to associate the new functional module with the corresponding module type in the module type mapping table, without the need for separate format mapping configuration, thus reducing maintenance costs.

[0031] In another implementation, after obtaining the target operating information, the target alarm level can be determined based on the target operating information. In step S102 above, the target log format required for the target BMC log to be generated is determined from the preset log information format set according to the target functional module and the event type indicated by the target operating information. Specifically, this includes: Based on the event types indicated by the target functional module and the target operation information, determine whether the target functional module has experienced a related event associated with the event type, and obtain the determination result; Based on the judgment results and the target alarm level, determine the correction value of the initial weight value corresponding to each preset indicator in the preset indicator set; For each preset indicator in each preset indicator set, the initial weight value corresponding to the preset indicator is corrected using the correction value corresponding to the preset indicator in order to obtain the target weight value corresponding to the preset indicator. For each preset log information format in the preset log information format set, the target score corresponding to the preset log information format is determined based on the preset scores and target weight values ​​of all preset indicators in the preset indicator set corresponding to the preset log information format. Based on all the target scores obtained, the target log information format required for the target BMC log to be generated is determined from the preset log information format set.

[0032] To more accurately determine the required log information format for the target BMC log to be generated from the preset log information format set, when an anomaly is determined in the target functional module based on the target operating information, the target alarm level is determined based on the target operating information, and based on the preset time causal relationship, the target functional module is searched in the global event context pool maintained by the BMC node to see if any related events associated with the event type have occurred. For example, when a voltage fluctuation of the power module is detected, the anomaly of the heat dissipation module is checked; the anomaly of the heat dissipation module is a related event associated with the voltage fluctuation of the power module. After obtaining the judgment result and alarm level of the related event, the correction value of each preset indicator in the preset indicator set corresponding to the judgment result and target alarm level can be determined based on the correspondence between the preset judgment result and alarm level and the correction value of each preset indicator in the preset indicator set. This correction value is then used to correct the initial weight value of each preset indicator in the preset indicator set to obtain each target weight value. All target weight values ​​are summed to 1.

[0033] After obtaining the target weight values, for each preset log information format in the preset log information format set, based on the preset scores and target weight values ​​of all preset indicators in the preset indicator set corresponding to the preset log information format, a weighted summation algorithm is used to multiply the preset scores of each preset indicator by the corresponding target weight value and then sum them to obtain the target score of the preset log information format in the current scenario. The highest target score is determined from all target scores, and the preset log information format corresponding to the highest target score is determined as the target log information format. The preset indicators include diagnostic value indicators, storage space usage indicators, and log processing efficiency indicators. The initial weight values ​​and preset scores corresponding to the preset indicators can be set according to actual needs; this embodiment does not impose specific limitations on them. Through the above method, this embodiment, by introducing an intelligent decision-making mechanism that coordinates associated event perception and alarm level, achieves dynamic optimization selection of log information formats, significantly improving resource utilization efficiency and operational analysis effectiveness while ensuring the complete capture of key abnormal information.

[0034] S103: Fill the target running information into the target log information format to obtain the target log information.

[0035] In this embodiment, after determining the target log information format, which is an empty data structure instance, the original target running information is split and mapped and filled into the various fields of the target log information format to obtain the target log information. The target log information is actually a structured data that contains key information about the target functional module's abnormality and is the basis for subsequent encapsulation into a complete BMC log.

[0036] S104: Based on the preset log template, encapsulate the target log information to generate the target BMC log.

[0037] In this embodiment, the preset log template can be understood as a pre-set standard framework for encapsulating target log information generated based on BMC nodes. This preset log template includes fixed fields and variable fields. The fixed fields include log generation time, BMC node ID, log function, etc., while the variable fields are the target log information. After obtaining the target log information, the target log information is embedded into the preset log template, and the field information corresponding to the fixed fields is also embedded into the preset log template, thereby completing the encapsulation of the target log information and generating the target BMC log. Since the target BMC log is generated according to a preset log information format from a pre-set preset log information format set, the generated target BMC log is customized, improving the flexibility of log generation and the efficiency of subsequent log analysis.

[0038] Before performing step S103, the BMC log generation method provided in this embodiment further includes the following steps: Based on the target's operational information, determine the target alarm level corresponding to the target functional module.

[0039] The above step S104 specifically includes: Based on a preset log template, the target alarm level and target log information are encapsulated to generate the target BMC log.

[0040] In this embodiment, existing technologies typically do not add alarm level identifiers when generating BMC logs. This results in BMC logs of different alarm levels being mixed together. During subsequent log analysis, maintenance personnel need to analyze each BMC log individually, hindering timely responses to urgent anomalies. Therefore, to address this issue, this embodiment pre-sets multiple preset threshold intervals, each corresponding to a specific alarm level. After obtaining the target operational information, it is compared with these preset threshold intervals to determine the corresponding interval. The alarm level corresponding to the determined threshold interval is then identified as the target alarm level for the target functional module. The preset log template also includes an alarm level in its fixed fields. After determining the target alarm level, it is embedded into the target alarm level field, and the target log information is embedded into the variable fields, thus encapsulating the target log information and the target alarm level, thereby generating the target BMC log. The alarm levels mentioned above include Debug, Info, Warning, Error, and Fatal. Of course, alarm levels can be set according to actual needs; this embodiment does not impose any limitations on them. It should be noted that during encapsulation, other fields besides the alarm level in the fixed fields also need to be embedded. These other fields can be referred to the above description and will not be elaborated upon here. Through the above method, this embodiment determines the target alarm level corresponding to the target functional module and generates target BMC logs using the target alarm level and target log information. This enables subsequent operations and maintenance personnel to quickly locate anomalies requiring urgent handling based on the target alarm level during log analysis, improving anomaly response efficiency.

[0041] This embodiment provides a BMC log generation method. By pre-setting a preset log information format set, when a target functional module is determined to be abnormal based on the target operation information obtained by the BMC node, the target log information format required for the target BMC log to be generated is determined from the preset log information format set according to the event type indicated by the target functional module and the target operation information. The target operation information is then filled into the target log information format to obtain the target log information. The target log information is then encapsulated based on a preset template to achieve on-demand customization of the target BMC log, improving the flexibility of log generation and the efficiency of subsequent log analysis.

[0042] refer to Figure 2 , Figure 2 This is a flowchart illustrating a BMC log processing method provided in an embodiment of this application. The BMC log processing method provided in this embodiment includes the following steps: S201: For each BMC node in the BMC cluster, receive the target BMC log sent by the BMC node.

[0043] S202: Determine the target category dimension to which the target BMC log belongs from the preset category dimension set.

[0044] S203: Determine the target storage location corresponding to the target BMC log based on the target classification dimension.

[0045] S204: Store the target BMC log to the target storage location.

[0046] Regarding steps S201 to S204 above, this method is applied to a log processing device. The log processing device is connected to each BMC node in the BMC cluster; that is, the log processing device establishes a long-lived connection with all BMC nodes in the BMC cluster via the network. The target BMC log mentioned above is generated using the BMC log generation method described above. The log processing device can be understood as the centralized log management center of the BMC cluster; it is essentially a server. When a BMC node generates the target BMC log, it uploads the target BMC log to the log processing device via the DBus channel, ensuring that only one BMC node uploads the target BMC log to the log processing device at a time. This isolation between the BMC nodes avoids concurrent conflicts. To facilitate accurate location of target BMC logs by maintenance personnel, the log processing device, upon receiving a target BMC log from any BMC node in the BMC cluster, determines the target classification dimension of the target BMC log from a preset classification dimension set. Based on the target classification dimension, it determines the target storage location of the target BMC log and stores the received target BMC log in the target storage location. This avoids disordered storage of target BMC logs, enabling relevant personnel to accurately locate the target BMC log based on the target storage location, thus improving the efficiency of BMC log analysis.

[0047] The aforementioned set of preset classification dimensions includes multiple preset classification dimensions. These preset classification dimensions can be understood as the log category to which the target BMC log belongs. For example, preset classification dimensions may include alarm level, same module type, and same BMC node. The preset classification dimensions can be set according to actual needs; this embodiment does not specifically limit the preset classification dimensions. The target storage location can be understood as a specific path pre-divided based on the preset classification dimensions for storing the target BMC logs sent by the BMC node. It should be noted that, referring to... Figure 3 As shown, the log processing device 302 adopts a microservice architecture, including a log collection service 3021 and a log processing service 3022. Data is transmitted between the log collection service 3021 and the log processing service 3022 via sockets. The log collection service 3021 receives target BMC logs sent by any BMC node 301 in the BMC cluster and transmits the target BMC logs to the log processing service 3022 via sockets. After receiving the target BMC logs, the log processing service 3022 determines the target category dimension to which the target BMC logs belong from a preset category dimension set. Based on the target category dimension, it determines the target storage location corresponding to the target BMC logs and stores the target BMC logs in the target storage location. In this embodiment, the log processing device, by adopting a microservice architecture, achieves functional decoupling, reduces the complexity of the log processing device, and improves the reliability of its operation.

[0048] In this embodiment, before performing step S201 above, the BMC log processing method provided in this embodiment further includes the following steps: Receive node information corresponding to the BMC node sent by the BMC node; Register node information to the log processing device; After completing the node information registration, execute the step of receiving the target BMC logs sent by the BMC node.

[0049] The above-mentioned step S202 specifically includes: If the log processing device stores the node information corresponding to the BMC node, the target classification dimension to which the target BMC log belongs is determined from the preset classification dimension set.

[0050] After performing step S204 above, the BMC log processing method provided in this embodiment further includes the following steps: Receive the first request sent by the target terminal; Based on the target storage location corresponding to the target BMC log, the target BMC log is determined from the target storage location, and the node information corresponding to the BMC node to which the target BMC log belongs is determined. The identified target BMC log and the node information corresponding to the BMC node to which the target BMC log belongs are sent to the target terminal.

[0051] To prevent unauthorized BMC nodes from sending BMC logs and interfering with the management of normal BMC logs, and to improve the efficiency of anomaly location, in this embodiment, before receiving the target BMC logs sent by the BMC nodes, each BMC node in the BMC cluster needs to send node information to the log processing device through a preset registration interface. This node information includes the BMC node's MAC address, IP address, and information about the functional modules monitored by the BMC node. The monitored functional module information includes the model of the functional module and the number of functional modules of the same type. After receiving the node information sent by the BMC nodes, the log processing device verifies the node information. If the verification is successful, the node information is registered in the log processing device. Registering node information in the log processing device can be understood as storing the mapping relationship between BMC nodes and node information in the database of the log processing device. The mapping relationship is actually the mapping relationship between the MAC address of the BMC node and the node information. After completing node registration, a BMC node can send a target BMC log to the log processing device. Upon receiving the target BMC log, the log processing device determines whether corresponding node information exists within the device based on the MAC address carried in the log. If a node is found to exist, the target BMC log is processed (i.e., the step of determining the target category dimension to which the target BMC log belongs from a preset category dimension set is performed, thus storing the target BMC log in the target storage location). This facilitates subsequent log analysis. In this way, the log processing device only receives target BMC logs sent by BMC nodes successfully registered with the device, preventing logs sent by unauthorized BMC nodes from interfering with the normal management of BMC logs. It should be noted that, according to the reference... Figure 3 As shown, when registering the node information corresponding to the BMC node, the log collection service 3021 needs to receive the node information corresponding to the BMC node 301 and send the node information to the log processing service 3022 so that the log processing service 3022 can verify and register the node information.

[0052] After the log processing device completes the processing of the target BMC log (i.e., stores the target BMC log to the target storage location), to improve the efficiency of anomaly localization, when maintenance personnel query the target BMC log based on the target terminal, the target terminal generates a first request for querying the target BMC log. Upon receiving the first request, the log processing device can, based on the identifier of the target BMC log carried in the first request, query the target storage location where the target BMC log is stored. Based on the target storage location, it can then retrieve the target BMC log and the node information corresponding to the BMC node to which the target BMC log belongs. Finally, it returns the target BMC log and node information to the target terminal, enabling the maintenance personnel at the target terminal to locate the abnormal functional module within the BMC node based on the node information, thus improving log analysis efficiency. It should be noted that the target terminal can be a mobile phone, tablet, etc., and the specific form of the target terminal can be selected according to actual needs. (Reference) Figure 3 As shown, when the target terminal generates the first request, the first request is sent to the log processing service 3022, so that the log processing service 3022 responds to the first request and returns the target BMC log and the node information corresponding to the BMC node to which the target BMC log belongs.

[0053] In this embodiment, after executing step S204, the BMC log processing method provided in this embodiment further includes the following steps: When an update occurs at the BMC node, receive the update information sent by the BMC node; The updated information is used to update the node information corresponding to the registered BMC node to obtain the updated node information. Based on the updated node information, return to the step of receiving the target BMC log sent by the BMC node; and... Based on node information, send heartbeat packets to the BMC node; Upon receiving a response message for the heartbeat packet from the BMC node, return to the step of receiving the target BMC log sent by the BMC node.

[0054] Regarding the above steps, after the BMC node completes its registration in the log processing device, to avoid errors in subsequent query results and the inability to receive target BMC logs sent by the updated BMC node due to the BMC node being updated but the node information in the log processing device not being updated, thus preventing such errors, this embodiment, in the event of a BMC node update, has the BMC node actively send update information to the log processing device. Upon receiving the update information, the log processing device updates the node information corresponding to the BMC node using the update information, and then returns to execute step S201 based on the updated node information. This ensures the accuracy of subsequent query results even when the BMC node is updated, and also ensures that the target BMC logs sent by the authorized BMC node can still be received, facilitating BMC log management. The aforementioned BMC node update can be understood as an update to the BMC node's IP address or an update to the functional modules monitored by the BMC node, etc., and the update information can be understood as the updated information within the BMC node. It should be noted that, referring to... Figure 3 As shown, after BMC node 301 generates update information, it sends the update information to log collection service 3021, which then sends the update information to log processing service 3022, so that log processing service 3022 can update the node information based on the update information.

[0055] In addition, to prevent the log processing device from being unable to receive the target BMC logs sent by the BMC node due to BMC node downtime, thus affecting the timeliness of exception handling, this embodiment, after storing the target BMC logs to the target storage location, also sends a heartbeat packet to the BMC node based on the IP address of the BMC node included in the node information to detect whether the BMC node is online. If the BMC node is online, it will send a response message to the log processing device, causing the log processing device to return to the step of receiving the target BMC logs sent by the BMC node (i.e., step S201). If the BMC node is offline, the log processing device will not receive the response message sent by the BMC node within a preset time. At this time, an alarm needs to be triggered, and the device needs to return to the step of receiving the target BMC logs sent by the BMC node to receive the target BMC logs sent by other BMC nodes in the BMC cluster. It should be noted that, referring to Figure 3As shown, the log processing service 3022 sends heartbeat packets to the BMC nodes via the log collection service 3021 based on node information. Upon receiving a response from the BMC node to the heartbeat packet, the log collection service 3021 sends the response information to the log processing service 3022, enabling the log processing service 3022 to receive the target BMC logs sent by the BMC node based on the response information. This embodiment improves the operational reliability and maintainability of the BMC cluster, as well as the timeliness of anomaly handling, by monitoring whether each BMC node in the BMC cluster is online.

[0056] In this embodiment, the target BMC log also includes a target alarm level. Step S202 specifically includes: Based on the target alarm level and the node information corresponding to the BMC node to which the target BMC log belongs, the target classification dimension to which the target BMC log belongs is determined from the preset classification dimension set.

[0057] The above-mentioned step S203 specifically includes: Based on the target classification dimension, the second association is queried to determine the target storage location corresponding to the target BMC log. The second association stores the correspondence between each preset classification dimension and each target storage location in the preset classification dimension set.

[0058] In this embodiment, after executing step S204, the BMC log processing method provided in this embodiment further includes the following steps: For each target storage location, all target BMC logs stored in that location are aggregated to obtain target statistics. The statistical results of each target log are displayed on the target interface according to their respective preset display formats.

[0059] To avoid the problem of limited flexibility in BMC log querying due to the single storage dimension in existing technologies, this embodiment pre-sets multiple preset classification dimensions based on alarm level and node information. Each preset classification dimension corresponds to a target storage location (i.e., a second association). After obtaining the target BMC log, it is parsed to obtain the target alarm level and the node information corresponding to the target BMC node to which the target BMC log belongs. Based on the target alarm level and node information, a target classification dimension matching the target alarm level and node information is determined from the multiple preset classification dimensions. The second association is then queried using the target classification dimension to find the target storage location corresponding to the target classification dimension. The target storage location corresponding to each target classification dimension is then determined as the target storage location for the target BMC log. This allows for rapid location of BMC logs based on different query scenarios, improving the flexibility of BMC log querying and increasing log analysis efficiency.

[0060] To facilitate intuitive viewing of anomalies in the BMC cluster by operations and maintenance personnel, pre-defined classification dimensions and aggregation analysis dimensions are pre-associated. After storing target BMC logs according to the pre-defined classification dimensions to their corresponding target storage locations, all target BMC logs stored in the target storage locations corresponding to each pre-defined classification dimension are aggregated and analyzed according to the aggregation analysis dimension. This yields log statistics for each target storage location, which are then displayed on the target interface according to their respective pre-defined display formats. This makes anomalies readily apparent and lowers the barrier to entry for operations and maintenance. The pre-defined display formats can be set according to actual needs; for example, they can be bar charts, line charts, pie charts, etc. It should be noted that the reference... Figure 3 As shown, after obtaining the target statistical results, the log processing service 3022 in the log processing device 302 sends the target statistical results to the visualization service 3023 in the log processing device 302, so that the visualization service 3023 can display the obtained log statistical results on the target interface according to their respective preset display formats, thereby decoupling log processing and log display and improving the reliability of the log processing device operation.

[0061] This embodiment provides a BMC log processing method. For each BMC node connected to the log processing device in the BMC cluster, after receiving the customized target BMC node sent by the BMC node, the method determines the corresponding target storage location for the customized target BMC log based on a pre-set preset classification dimension set, so as to store the customized target BMC log in the corresponding target storage location. This achieves the ordered storage of customized target BMC logs, which facilitates the quick location of customized target BMC logs during subsequent log analysis, thereby improving the efficiency of log analysis.

[0062] refer to Figure 3 , Figure 3 A BMC log management system is provided for embodiments of this application. The BMC log management system includes a BMC cluster and a log processing device 302. Each BMC node 301 in the BMC cluster is connected to the log processing device 302. Each BMC node 301 is used to execute the BMC log generation method described above to generate target BMC logs; the log processing device 302 is used to execute the BMC log processing method described above to store the received target BMC logs to a target storage location.

[0063] based on Figure 3 The following is an example to illustrate the entire BMC log management process: For each BMC node 301 in the BMC cluster, the BMC node 301 sends its own node information to the log processing service 3022 in the log processing device 302 through the log collection service 3021 in the log processing device 302, so that the log processing service 3022 registers the node information in the log processing device 302. BMC node 301 acquires the operational information corresponding to each functional module it monitors; BMC node 301 determines whether there are any abnormalities in the corresponding functional modes based on the acquired operational information. If there are abnormalities, it determines the alarm level of the abnormal functional module and the event type indicated by the abnormal functional module and the operational information corresponding to the abnormal functional module, and determines the log information format required to generate the BMC log corresponding to the abnormal functional module. The runtime information corresponding to the abnormal functional module is filled into the log information format to obtain the log information. Then, based on the preset log template, the log information is encapsulated to generate the target BMC log. After BMC node 301 generates a BMC log, it sends the BMC log to log processing service 3022 through log collection service 3021. Upon receiving the BMC log, log processing service 3022 determines whether there is node information in log processing device 302 corresponding to BMC node 301 to which the BMC log belongs. If not, the BMC log is not processed. If it exists, based on BMC node 301 and the node information corresponding to BMC node 301, the service determines the classification dimension to which the received BMC log belongs and stores the BMC log in the storage location corresponding to the classification dimension. After storage is completed, all BMC logs in the storage location are aggregated to obtain statistical results, which are then sent to the visualization service 3023 in the log processing device 302. The visualization service 3023 displays the results in the corresponding interface according to its own display format so that maintenance personnel can view them. In addition, if the node information corresponding to BMC node 301 has been registered in log processing device 302, and if the functional module monitored by BMC node 301 is updated, BMC node 301 will send the corresponding update information to log processing service 3022 through log collection service 3021, so that log processing service 3022 can update the node information corresponding to BMC node 301 based on the update information to obtain the updated node information; After receiving the updated node information, if BMC logs are received from BMC node 301, the updated node information can be used to determine BMC node 301. After determining that the node information corresponding to BMC node 301 has been registered in log processing device 302, the subsequent BMC log processing flow can be executed. Furthermore, if the node information corresponding to BMC node 301 has been registered in the log processing device 302, the log processing service 3022 can send a heartbeat packet to BMC node 301 through the log collection service 3021 to determine whether BMC node 301 is online. If BMC node 301 returns a response to the heartbeat packet, it indicates that BMC node 301 is online and the subsequent BMC log processing flow is executed. If BMC node 301 does not return a response to the heartbeat packet, it indicates that BMC node 301 is offline and an alarm can be triggered.

[0064] refer to Figure 4 , Figure 4This is a schematic diagram of a BMC log generation device provided in an embodiment of this application. The BMC log generation device provided in this embodiment includes an acquisition module 401, a first determination module 402, a filling module 403, and a generation module 404. The acquisition module 401 is used to acquire target operation information corresponding to the target functional module monitored by the BMC node. The first determination module 402 is used to determine, when the target functional module is determined to be abnormal based on the target operation information, the target log information format required for the target BMC log to be generated from a preset log information format set, based on the target functional module and the event type indicated by the target operation information. The filling module 403 is used to fill the target operation information into the target log information format to obtain the target log information. The generation module 404 is used to encapsulate the target log information based on a preset log template to generate the target BMC log.

[0065] In this embodiment, the first determining module 402 is further configured to: Determine the target module type to which the target functional module belongs; Target rules that match the target module type and the event type indicated by the target operation information are determined from the preset rule set; Based on the target rule, the preset log information format corresponding to the target rule is determined from the first association relationship. The first association relationship stores the correspondence between each preset rule in the preset rule set and each preset log information format in the preset log information format set. The preset log information format corresponding to the target rule is determined as the target log information format required for the target BMC log to be generated.

[0066] In this embodiment, the first determining module 402 is further configured to: Based on the target operation information, determine the target alarm level corresponding to the target functional module.

[0067] In this embodiment, the generation module 404 is further configured to: Based on a preset log template, the target alarm level and the target log information are encapsulated to generate the target BMC log.

[0068] This embodiment provides a BMC log generation device that, by pre-setting a preset log information format set, determines the target log information format required for the target BMC log to be generated based on the target operation information corresponding to the monitored target functional module obtained by the BMC node, according to the event type indicated by the target functional module and the target operation information. The target operation information is then filled into the target log information format to obtain the target log information. Furthermore, the target log information is encapsulated based on a preset template to achieve on-demand customization of the target BMC log, improving the flexibility of log generation and the efficiency of subsequent log analysis.

[0069] refer to Figure 5 , Figure 5 This is a schematic diagram of a BMC log processing device provided in an embodiment of this application. The BMC log generation device provided in this embodiment includes a receiving module 501, a second determining module 502, and a storage module 503. The receiving module 501 is used to receive a target BMC log sent by each BMC node, the target BMC log being generated using the BMC log generation method described above. The second determining module 502 is used to determine the target classification dimension to which the target BMC log belongs from a preset classification dimension set; and based on the target classification dimension, determine the target storage location corresponding to the target BMC log. The storage module 503 is used to store the target BMC log to the target storage location.

[0070] In this embodiment, the receiving module 501 is further configured to: Receive node information corresponding to the BMC node sent by the BMC node; Register the node information to the log processing device; After completing the registration of the node information, the target BMC log sent by the BMC node is received.

[0071] In this embodiment, the second determining module 502 is further configured to: If the node information corresponding to the BMC node exists in the log processing device, the target classification dimension to which the target BMC log belongs is determined from the preset classification dimension set.

[0072] The BMC log processing device provided in this embodiment further includes a sending module, which is used for: After storing the target BMC log to the target storage location, a first request is received from the target terminal, the first request being used to query the target BMC log; Based on the target storage location corresponding to the target BMC log, the target BMC log is determined from the target storage location, and the node information corresponding to the BMC node to which the target BMC log belongs is determined; The identified target BMC logs and the node information corresponding to the BMC nodes are sent to the target terminal.

[0073] In this embodiment, the receiving module 501 is further configured to: After storing the target BMC log in the target storage location, if the BMC node is updated, receive the update information sent by the BMC node; Using the updated information, the node information corresponding to the registered BMC node is updated to obtain the updated node information; Receive the target BMC log sent by the BMC node based on the updated node information.

[0074] In this embodiment, the receiving module 501 is further configured to: After storing the target BMC logs to the target storage location, a heartbeat packet is sent to the BMC node based on the node information; Upon receiving the response information for the heartbeat packet sent by the BMC node, the target BMC log sent by the BMC node is received.

[0075] In this embodiment, the target BMC log also includes a target alarm level; the second determination module 502 is further configured to: Based on the target alarm level and the node information corresponding to the BMC node to which the target BMC log belongs, the target classification dimension to which the target BMC log belongs is determined from a preset classification dimension set; Based on the target classification dimension, the second association relationship is queried to determine the target storage location corresponding to the target BMC log from the second association relationship. The second association relationship stores the correspondence between each preset classification dimension in the preset classification dimension set and each target storage location. This embodiment provides a BMC log processing device, which further includes a display module. The display module is used for: For each target storage location, all target BMC logs stored in the target storage location are aggregated to obtain target statistical results; The obtained log statistics results are displayed on the target interface according to their respective preset display formats.

[0076] This embodiment provides a BMC log processing device. For each BMC node connected to the log processing device in the BMC cluster, after receiving the customized target BMC node sent by the BMC node, it determines the corresponding target storage location for the customized target BMC log based on a pre-set preset classification dimension set, so as to store the customized target BMC log in the corresponding target storage location. This realizes the ordered storage of customized target BMC logs, which facilitates the quick location of customized target BMC logs during subsequent log analysis, thereby improving the efficiency of log analysis.

[0077] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 6 The illustrated electronic device 600 can be any BMC node or log processing device in the aforementioned BMC cluster. Electronic device 600 includes: at least one processor 601, memory 602, at least one network interface 604, and other user interfaces 603. The various components in electronic device 600 are coupled together via a bus system 605. It is understood that the bus system 605 is used to implement communication between these components. In addition to a data bus, the bus system 605 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 6 The general designated all buses as Bus System 605.

[0078] The user interface 603 may include a display, keyboard, or clicking device (e.g., mouse, trackball, touchpad, or touchscreen).

[0079] It is understood that the memory 602 in this embodiment of the invention can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 602 described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0080] In some implementations, memory 602 stores elements, executable units or data structures, or subsets thereof, or extended sets thereof: operating system 6021 and application program 6022.

[0081] The operating system 6021 includes various system programs, such as the framework layer, core library layer, and driver layer, used to implement various basic business functions and handle hardware-based tasks. The application program 6022 includes various applications, such as a media player and a browser, used to implement various application functions. The program implementing the method of this embodiment can be included in the application program 6022.

[0082] In this embodiment of the invention, the processor 601 executes the method steps provided in each method embodiment by calling the program or instructions stored in the memory 602, specifically the program or instructions stored in the application program 6022.

[0083] The methods disclosed in the above embodiments of the present invention can be applied to processor 601, or implemented by processor 601. Processor 601 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in processor 601 or by instructions in the form of software. The processor 601 may be a general-purpose processor, 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, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present invention can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software units in the decoding processor. The software units may be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory 602. Processor 601 reads the information in memory 602 and, in conjunction with its hardware, completes the steps of the above method.

[0084] It is understood that the embodiments described herein can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described herein, or combinations thereof.

[0085] For software implementation, the techniques described herein can be implemented by units that perform the functions described herein. The software code can be stored in memory and executed by a processor. The memory can be implemented in the processor or external to the processor.

[0086] The electronic device provided in this embodiment may be as follows: Figure 6 The electronic device shown can perform the following: Figure 1 and Figure 2 All steps of the method, thus achieving Figure 1 and Figure 2 For details on the technical effects of the method shown, please refer to [link / reference]. Figure 1 and Figure 2 The relevant descriptions are presented concisely and will not be elaborated upon here.

[0087] This invention also provides a storage medium (computer-readable storage medium). This storage medium stores one or more programs. The storage medium may include volatile memory, such as random access memory; it may also include non-volatile memory, such as read-only memory, flash memory, hard disk, or solid-state drive; and it may also include combinations of the above types of memory.

[0088] When one or more programs in the storage medium can be executed by one or more processors to achieve the above-described method of execution on the device side.

[0089] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0090] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented in hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0091] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for generating BMC logs, characterized in that, The method, applied to BMC nodes in a BMC cluster, includes: Obtain the target operation information corresponding to the target functional module monitored by the BMC node; If the target functional module is determined to be abnormal based on the target operation information, the target log information format required for the target BMC log to be generated is determined from the preset log information format set according to the event type indicated by the target functional module and the target operation information. The target running information is filled into the target log information format to obtain the target log information; Based on a preset log template, the target log information is encapsulated to generate the target BMC log.

2. The method according to claim 1, characterized in that, The step of determining the target log information format required for the target BMC log to be generated from a preset log information format set based on the event type indicated by the target functional module and the target operation information includes: Determine the target module type to which the target functional module belongs; Target rules that match the target module type and the event type indicated by the target operation information are determined from the preset rule set; Based on the target rule, the preset log information format corresponding to the target rule is determined from the first association relationship. The first association relationship stores the correspondence between each preset rule in the preset rule set and each preset log information format in the preset log information format set. The preset log information format corresponding to the target rule is determined as the target log information format required for the target BMC log to be generated.

3. The method according to claim 1, characterized in that, Before performing the step of filling the target running information into the target log information format to obtain the target log information, the method further includes: Based on the target operation information, determine the target alarm level corresponding to the target functional module; The step of encapsulating the target log information based on a preset log template to generate the target BMC log includes: Based on a preset log template, the target alarm level and the target log information are encapsulated to generate the target BMC log.

4. A BMC log processing method, characterized in that, The method, applied to a log processing device connected to various BMC nodes in a BMC cluster, includes: For each of the BMC nodes, a target BMC log sent by the BMC node is received, the target BMC log being generated by the BMC log generation method according to any one of claims 1 to 3; The target classification dimension to which the target BMC log belongs is determined from the preset classification dimension set; Based on the target classification dimension, determine the target storage location corresponding to the target BMC log; Store the target BMC log to the target storage location.

5. The method according to claim 4, characterized in that, Before performing the step of receiving the target BMC log sent by the BMC node, the method further includes: Receive node information corresponding to the BMC node sent by the BMC node; Register the node information to the log processing device; After completing the registration of the node information, the step of receiving the target BMC log sent by the BMC node is executed; The step of determining the target classification dimension to which the target BMC log belongs from the preset classification dimension set includes: If the node information corresponding to the BMC node exists in the log processing device, the target classification dimension to which the target BMC log belongs is determined from a preset classification dimension set. After performing the step of storing the target BMC log to the target storage location, the method further includes: Receive a first request sent by the target terminal, the first request being used to query the target BMC log; Based on the target storage location corresponding to the target BMC log, the target BMC log is determined from the target storage location, and the node information corresponding to the BMC node to which the target BMC log belongs is determined; The identified target BMC logs and the node information corresponding to the BMC nodes are sent to the target terminal.

6. The method according to claim 5, characterized in that, After performing the step of storing the target BMC log to the target storage location, the method further includes: If the BMC node is updated, receive the update information sent by the BMC node; Using the updated information, the node information corresponding to the registered BMC node is updated to obtain the updated node information; Based on the updated node information, return to the step of receiving the target BMC log sent by the BMC node; and... Based on the node information, a heartbeat packet is sent to the BMC node; Upon receiving the response information for the heartbeat packet sent by the BMC node, return to the step of receiving the target BMC log sent by the BMC node.

7. The method according to claim 5, characterized in that, The target BMC log also includes the target alarm level; The step of determining the target classification dimension to which the target BMC log belongs from the preset classification dimension set includes: Based on the target alarm level and the node information corresponding to the BMC node to which the target BMC log belongs, the target classification dimension to which the target BMC log belongs is determined from a preset classification dimension set; Determining the target storage location corresponding to the target BMC log based on the target classification dimension includes: Based on the target classification dimension, the second association relationship is queried to determine the target storage location corresponding to the target BMC log from the second association relationship. The second association relationship stores the correspondence between each preset classification dimension in the preset classification dimension set and each target storage location. After performing the step of storing the target BMC log to the target storage location, the method further includes: For each target storage location, all target BMC logs stored in the target storage location are aggregated to obtain target statistical results; The obtained log statistics results are displayed on the target interface according to their respective preset display formats.

8. A BMC log generation device, characterized in that, The device, applied to BMC nodes in a BMC cluster, includes: The acquisition module is used to acquire the target operation information corresponding to the target functional module monitored by the BMC node; The first determining module is used to determine the target log information format required for the target BMC log to be generated from a preset log information format set, based on the target functional module and the event type indicated by the target operational information, when the target functional module is determined to be abnormal according to the target operational information. A filling module is used to fill the target running information into the target log information format to obtain the target log information; The generation module is used to encapsulate the target log information based on a preset log template to generate the target BMC log.

9. A BMC log processing device, characterized in that, An apparatus for use in log processing devices, wherein the log processing devices are connected to various BMC nodes in a BMC cluster, the apparatus comprising: A receiving module is configured to receive a target BMC log sent by each of the BMC nodes, wherein the target BMC log is generated by the BMC log generation method according to any one of claims 1 to 3; The second determining module is used to determine the target classification dimension to which the target BMC log belongs from a preset classification dimension set; The second determining module is further configured to determine the target storage location corresponding to the target BMC log based on the target classification dimension; A storage module is used to store the target BMC logs to the target storage location.

10. A BMC log management system, characterized in that, It includes a BMC cluster and a log processing device, wherein each BMC node in the BMC cluster is connected to the log processing device; Each BMC node is used to execute the BMC log generation method as described in any one of claims 1 to 3 to generate a target BMC log; The log processing device is used to execute the BMC log processing method as described in any one of claims 4 to 7 to store the received target BMC log to a target storage location.

Images