Heterogeneous log management method, electronic equipment and storage medium

Abstract

The invention relates to a heterogeneous log management method, electronic equipment and a storage medium, which are applied to the technical field of computers, and the method comprises the following steps: determining a to-be-processed target log from respective initial logs of at least one type of business system; determining target field data corresponding to a preset audit field from the target log; determining target field translation data corresponding to the target field data; and writing the target field translation data into a position corresponding to the preset auditing field in a pre-configured auditing table so as to audit the initial log through the auditing table.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a heterogeneous log management method, electronic device, and storage medium. Background Technology

[0002] As enterprises advance their digital transformation, heterogeneous business systems (such as dedicated systems for various departments and parallel systems of old and new) are widely used, and the number of log entries is soaring, which brings huge challenges to log analysis and management.

[0003] Log auditing collects logs from heterogeneous business systems in real time (such as login behavior, data modification, permission change logs, etc.) and uses preset rules to audit the logs in order to identify abnormal operations (such as login from different IP addresses, high frequency of failed logins, batch deletion of data, etc.).

[0004] However, in different business systems, the same operation type (such as the end of the review) may have different wording (such as "approval passed / review OK / approval completed"), which leads to inconsistencies in data among customer service, audit, and product, causing confusion and high understanding costs. Summary of the Invention

[0005] This application provides a heterogeneous log management method, electronic device, and storage medium to solve the problem of data inconsistency between different business systems in the prior art.

[0006] According to a first aspect of the embodiments of this application, a heterogeneous log management method is provided, including: Identify the target logs to be processed from the initial logs of at least one type of business system; Determine the target field data corresponding to the preset audit field from the target log; Determine the target field translation data corresponding to the target field data; The translated data of the target field is written into the position corresponding to the preset audit field in the pre-configured audit table, so as to audit the initial log through the audit table.

[0007] Optionally, determining the target field translation data corresponding to the target field data includes: Determine the target scene data in the target field data; Determine the field translation correspondences corresponding to the target scene data, wherein the field translation correspondences are the correspondences between field data and translated data; From the field translation correspondence, determine the target field translation data corresponding to the target field data.

[0008] Optionally, the target logs to be processed are determined from the initial logs of at least one type of business system, including: Obtain initial logs from at least one type of business system; The initial log is transmitted to the message queue; The target log is determined from the message queue.

[0009] Optionally, transmitting the initial log to a message queue includes: Based on the attribute information of the initial logs, the initial logs are classified to obtain classification identifiers; Generate a log identifier for each of the initial logs; The initial log is transmitted to the message queue based on the classification identifier and the log identifier.

[0010] Optionally, determining the target log from the message queue includes: The initial log is rearranged according to the log identifier and the category identifier to obtain the rearranged result; Based on the rearrangement result, messages in the message queue are consumed, and the initial log to be consumed is determined as the target log.

[0011] Optionally, initial logs may be obtained from at least one type of business system, including: Determine the system language of the business system; Call the multilingual conversion interface corresponding to the system language to obtain the initial log from the business system.

[0012] Optional, also includes: Determine the acquisition duration of the initial log; The initial log is stored based on the acquisition duration.

[0013] According to a second aspect of the embodiments of this application, a heterogeneous log management method is provided, including: The system sends its initial logs to a heterogeneous log management system, enabling the system to determine the target logs to be processed from the initial logs of at least one type of business system; it then determines the target field data corresponding to a preset audit field from the target logs; it determines the target field translation data corresponding to the target field data; and it writes the target field translation data into the position corresponding to the preset audit field in a pre-configured audit table. Obtain audit information from the logs; Determine the audit content corresponding to the audit information from the audit table; The audit content is displayed.

[0014] According to a third aspect of the embodiments of this application, an electronic device is provided, including a memory and a processor; The memory is connected to the processor and is used to store programs; The processor is used to implement the heterogeneous log management method as described in the first aspect by running a program in the memory.

[0015] According to a fourth aspect of the embodiments of this application, a storage medium is provided, on which a computer program is stored, and when the computer program is run by a processor, it implements the heterogeneous log management method as described in the first aspect.

[0016] According to a fifth aspect of the embodiments of this application, a computer program product is provided, including computer program instructions that, when executed by a processor, cause the processor to perform the heterogeneous log management method as described in the first aspect.

[0017] Compared with the prior art, the technical solution provided in this application has the following advantages: The method provided in this application determines the target log to be processed from the initial logs of at least one type of business system; determines the target field data corresponding to the preset audit field from the target log; determines the target field translation data corresponding to the target field data; and writes the target field translation data into the position corresponding to the preset audit field in a pre-configured audit table, so as to audit the initial log through the audit table. Thus, for the initial logs of different business systems, by translating the target field data according to the unified target field translation data, the consistency of data in each business system is achieved, avoiding confusion and reducing understanding costs. Furthermore, writing the target field translation data uniformly into the audit table enables auditing of the initial logs through the audit table, improving audit efficiency. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0019] Figure 1 A flowchart is provided for an embodiment of the heterogeneous log management method of this application.

[0020] Figure 2 A flowchart is provided for another embodiment of the heterogeneous log management method of this application.

[0021] Figure 3This is a structural diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0022] 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, and 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.

[0023] Exemplary Implementation Environment The heterogeneous log management method according to embodiments of this application can be executed by electronic devices such as terminal devices or servers. Terminal devices can be user equipment (UE), mobile devices, user terminals, terminals, cellular phones, cordless phones, personal digital assistants (PDAs), handheld devices, computing devices, in-vehicle devices, wearable devices, etc. Servers can be independent physical servers, server clusters composed of multiple physical servers, or cloud servers capable of cloud computing. This method can be implemented by a processor calling computer-readable program instructions stored in memory. This application uses the execution of the heterogeneous log management method by a server as an example for explanation, but does not limit it.

[0024] Exemplary methods Please see Figure 1 In one exemplary embodiment, a heterogeneous log management method is provided. This method can be applied to the terminal or server where the heterogeneous log management system resides. The method includes: Step 101: Identify the target logs to be processed from the initial logs of at least one type of business system.

[0025] In some embodiments, each business system generates a large number of initial logs during execution. Each business system sends the generated initial logs to a heterogeneous log management system. Since the data of each business system is inconsistent, the heterogeneous log management system determines the target logs that need to be processed from the acquired initial logs and then performs subsequent processing on them to achieve the goal of data unification among the business systems.

[0026] The aforementioned business systems are heterogeneous, and these heterogeneity can manifest in various ways, such as technological, data, and functional differences. Technological heterogeneity can stem from different underlying frameworks (e.g., Java / Go / Python), deployment environments (cloud / local / edge), or databases (relational / non-relational). Data heterogeneity can arise from inconsistent data formats (structured / semi-structured / unstructured), storage methods, or transmission protocols. Functional heterogeneity can exist within independent business scenarios (e.g., e-commerce transactions / logistics / after-sales service) but require cross-business collaboration to complete the entire process.

[0027] In one optional embodiment, the target log to be processed is determined from the initial logs of at least one type of business system, including: Obtain initial logs from at least one type of business system; The initial log is transmitted to the message queue; The target log is determined from the message queue.

[0028] In some embodiments, the initial logs obtained from each business system are transmitted to a message queue. The message queue receives and temporarily stores the initial logs, which can avoid the initial log writing directly affecting system performance. At the same time, it can support subsequent flexible log processing (such as storage, analysis, alarms, etc.).

[0029] In an optional embodiment, transmitting the initial log to a message queue includes: Based on the attribute information of the initial logs, the initial logs are classified to obtain classification identifiers; Generate a log identifier for each of the initial logs; The initial log is transmitted to the message queue based on the classification identifier and the log identifier.

[0030] In some embodiments, the attribute information of the initial log may be, but is not limited to, the business scenario corresponding to the log, and the environment corresponding to the log (e.g., a test environment or a production environment). The initial log is named based on the attribute information to achieve classification. The classification identifier can be logistics_prod (logistics-related production environment), hr_test (human resources-related test environment), etc.

[0031] When generating the initial log identifier, a unique log identifier (LogUnique Identifier, or logId) and a sequence number (seqNo) can be appended to the message body. Message queues typically partition messages. When the initial log is transmitted to the message queue, a business identifier (businessId) can be used to partition the initial log. In the logistics field, this ensures that the same order number always enters the same partition, reducing out-of-order delivery from the source.

[0032] The logId can be generated, but is not limited to, by the snowflake algorithm. The logId can guarantee the global uniqueness of the log. The logId generated by different services, different machines, and different times will never be repeated. In addition, it contains an implicit timestamp, which can be used to deduce the approximate time of log generation, making it easy to sort and track.

[0033] seqNo can be obtained by auto-incrementing, thus ensuring local ordering. For the same logId, logs will be assigned sequence numbers 1, 2, 3... according to the order of generation, thus solving the problem of log out-of-order within the same request. Even in high-concurrency scenarios, logs of the same request can be correctly sorted by seqNo at the consumer end.

[0034] The businessId is a globally unique identifier bound to the initial log, serving as a business aggregation key. This allows initial logs scattered across different services and stages to be quickly associated with the same business object (such as the same order or the same logistics order).

[0035] In an optional embodiment, determining the target log from the message queue includes: The initial log is rearranged according to the log identifier and the category identifier to obtain the rearranged result; Based on the rearrangement result, messages in the message queue are consumed, and the initial log to be consumed is determined as the target log.

[0036] In some embodiments, by rearranging the initial logs, initial logs belonging to the same partition can be consumed uniformly, avoiding the omission of logs with the same serial number. This rearrangement can be done, but is not limited to, by using the FlinkKeyedProcessFunction function according to seqNo. KeyedProcessFunction provides the ability to perform fine-grained event processing and state management on the keyed partition stream, and also supports a timer mechanism to handle the temporal characteristics of events.

[0037] When consuming the initial logs in the message queue, a consumption window can be configured. For late messages, they can be output to the side stream first to avoid congesting the main link.

[0038] In one optional embodiment, initial logs are obtained from at least one type of business system, including: Determine the system language of the business system; Call the multilingual conversion interface corresponding to the system language to obtain the initial log from the business system.

[0039] In some embodiments, different system languages ​​may be used for different business systems. For example, business system 1 uses Java and business system 2 uses PHP. In order to enable the heterogeneous log management system to accurately process the logs of each business system, a multi-language conversion interface (SDK) can be made for Java, PHP and other languages ​​in the heterogeneous log management system. By calling the corresponding SDK, the initial logs from different business systems can be transmitted to the message queue, and the subsequent processing of the logs is handled by the system.

[0040] Step 102: Determine the target field data corresponding to the preset audit field from the target log.

[0041] In some embodiments, when auditing data in the target log, a portion of it may be audited. The fields to be audited are configured as preset audit fields. After the target log is determined, the corresponding target field data is determined from the target log based on the preset audit fields.

[0042] The preset audit fields may include, but are not limited to, the business scenario corresponding to the log, the primary key (businessId), the content of the log object before the change, the content of the log object after the change, the operator, and the timestamp (occurTime).

[0043] For example, multiple preset audit fields can be configured in advance. When defining them, they can be represented by "keys," and different key values ​​can be configured for each key to distinguish different fields in the log. When determining the target field data, the field in the target log can be compared with the preset audit fields, and the field that is the same as the preset audit field is identified as the target field data.

[0044] Step 103: Determine the target field translation data corresponding to the target field data.

[0045] In an optional embodiment, determining the target field translation data corresponding to the target field data includes: Determine the target scene data in the target field data; Determine the field translation correspondences corresponding to the target scene data, wherein the field translation correspondences are the correspondences between field data and translated data; From the field translation correspondence, determine the target field translation data corresponding to the target field data.

[0046] In some embodiments, depending on the business system, there may be multiple scenarios. For different scenarios, the corresponding field translation correspondence can be set for each scenario.

[0047] By pre-configuring the correspondence between field data and translation data, after obtaining the target field data, for target field data in the same scenario, the same field translation correspondence is used to determine its corresponding target field translation data. This ensures that the same target field data can be translated into the same target field translation data, thereby achieving the goal of data unification and reducing the cost of understanding.

[0048] The aforementioned scenario data may include, but is not limited to, scenarios such as the courier's rest route and the tracking of orders after a call.

[0049] For example, if the target scenario data is personnel scheduling, the target field data is 1001, and its corresponding target field translation data is "refresh of desired rest", the target field data is 1002, and its corresponding target field translation data is "manually created scheduling task", and the target field data is 1003, and its corresponding target field translation data is "routine scheduling for next week on Thursday".

[0050] Step 104: Write the target field translation data into the position corresponding to the preset audit field in the pre-configured audit table, so as to audit the initial log through the audit table.

[0051] In some embodiments, by writing the target field translation data into an audit table, the log data in the acquired initial logs can be stored in a structured manner, which facilitates the auditing of the initial logs of various business systems using the audit table.

[0052] When auditing the initial logs is required, the audit information to be audited can be entered into the audit system. The heterogeneous log management system searches the audit table based on the audit information to determine the audit content corresponding to the audit information. Through the reusable front-end component configured on the heterogeneous log management system, the audit content is displayed to the business system requesting the audit.

[0053] The front-end components can be, but are not limited to, React components. React is a JavaScript library for building user interfaces. It is widely used to build single-page applications (SPAs) and complex front-end interfaces, with componentization, declarative programming, and the virtual DOM (Document Object Model) as its core features.

[0054] Audit information may include, but is not limited to, business scenarios, primary keys, log object content before changes, log object content after changes, operators, timestamps, etc.

[0055] For example, in the scenario where the target data is the courier's on-and-off schedule, the audit information can be the businessId (date and employee number). A query using the businessId returns all on-and-off schedule changes for the day within 2 seconds. In the scenario where the target data is call tracking, the audit information can be the waybill number, which returns an ordered log chain. This reduces the average time to locate anomalies from 2 hours to seconds, meeting the requirements for year-end audits.

[0056] In an optional embodiment, the heterogeneous log management method further includes: Determine the acquisition duration of the initial log; The initial log is stored based on the acquisition duration.

[0057] In some embodiments, the acquisition duration of the initial log can be determined based on the acquisition time of the initial log and the current time. If the acquisition duration is less than a preset duration, the initial log is stored in a first type of storage space. If the acquisition duration is greater than the preset duration, the initial log is stored in a second type of storage space. The first type of storage space may be, but is not limited to, HBase, and the second type of storage space may be, but is not limited to, external storage.

[0058] Alternatively, if the acquisition time exceeds the preset time, the initial logs can be compressed into Parquet format for storage, thereby enabling low-cost storage of massive amounts of data. Furthermore, storing data in Parquet format offers advantages such as saving storage space, fast query speed, and easy scalability.

[0059] HBase is a distributed column-oriented database based on Hadoop, primarily used for real-time reading and writing of massive amounts of structured / semi-structured data. It boasts high scalability, supporting horizontal scaling of the cluster and handling petabyte (PB) level data storage. Data is organized by column families, allowing access to only the required column families, improving query efficiency. Fault tolerance: It relies on the Hadoop Distributed File System (HDFS) to achieve redundant data storage, ensuring data availability even in the event of node failures.

[0060] The heterogeneous log management method provided in this application breaks down the entire log chain into five segments: "access, transmission, computation, storage, and display." Each segment performs only one task, and the segments are decoupled from each other using queues or interfaces. Business systems submit logs to the access layer, and the entire process is handled by the heterogeneous log management system, achieving platformization. Any business system can handle the access, storage, querying, and display of new scenarios. The platform standardizes the processes of "writing logs, transmitting logs, computing logs, storing logs, and viewing logs" into a streamlined pipeline. Business users only need to focus on their own business logic, while the platform handles everything else, truly achieving "write once, access across the entire network, and query anytime."

[0061] By using a pre-configured audit table, elements such as business scenarios, primary keys, before and after changes, and operators from the initial logs of each business system are abstracted all at once. All initial log access is filled out according to the format of this audit table, page components are directly reused, and text is automatically translated, achieving uniformity across business systems. Furthermore, an SDK is created for different languages ​​(e.g., Java, PHP) on the access side. A few lines of calls in the business code can drop logs into the message queue, and subsequent processing is handled by the platform without requiring any platform modifications. Hot data is stored in HBase, and cold data is compressed and stored in objects, significantly reducing storage costs and extending log retention time. Real-time aggregation and order preservation are achieved using Flink. Each message is assigned a sequence number, and Flink reorders them by sequence number, solving the persistent problem of out-of-order processing in multi-partition scenarios. A complete timeline is returned within one second of entering a tracking number. For the same requirement, scheduling is shortened, storage costs are lower, and retention time is longer. Development, customer service, and auditing all use the same explanation, eliminating the need for back-and-forth explanations. By using React components, the system displays data in both table and timeline formats, and can be embedded into any page in a short time, enabling visual tracking.

[0062] Exemplary methods Accordingly, this application also provides a heterogeneous log management method, which can be applied to the terminal or server where the business system resides. See [link to relevant documentation]. Figure 2 The method includes: Step 201: Send your initial logs to the heterogeneous log management system.

[0063] In some embodiments, for each business system, a large number of initial logs are generated during system execution. After the initial logs are generated, the business system sends its own initial logs to the heterogeneous log management system. The heterogeneous log management system determines the target log to be processed from the initial logs of at least one type of business system; determines the target field data corresponding to the preset audit field from the target log; determines the target field translation data corresponding to the target field data; and writes the target field translation data into the position corresponding to the preset audit field in a pre-configured audit table.

[0064] Step 202: Obtain audit information for the logs.

[0065] In some embodiments, the audit information can be information that needs to be audited, entered by the user on the relevant audit page of the business system. Audit information may include, but is not limited to, business scenarios, primary keys, log object content before and after changes, operator information, timestamps, etc.

[0066] Step 203: Determine the audit content corresponding to the audit information from the audit table.

[0067] Step 204: Display the audit content.

[0068] In some embodiments, when auditing the initial logs is required, the audit information to be audited can be entered into the audit system. The heterogeneous log management system searches the audit table based on the audit information to determine the audit content corresponding to the audit information. The audit content is then displayed to the business system requesting the audit through a reusable front-end component configured on the heterogeneous log management system.

[0069] Furthermore, intercept fields can be added to the initial logs, and an interceptor can be added to the ORM (Object-Relational Mapping) layer. This interceptor automatically captures fields, thereby capturing logs and writing them to the database. In this way, when a new business system is added, the interceptor can directly capture the intercept fields of the new business system and write its logs to the database. This allows for non-intrusive log collection without modifying the business code.

[0070] Exemplary device Accordingly, embodiments of this application also provide a heterogeneous log management device, including: The first determining unit is used to determine the target log to be processed from the initial logs of at least one type of business system. The second determining unit is used to determine the target field data corresponding to the preset audit field from the target log; The third determining unit is used to determine the target field translation data corresponding to the target field data; The writing unit is used to write the target field translation data into the position corresponding to the preset audit field in the pre-configured audit table, so as to audit the initial log through the audit table.

[0071] Accordingly, embodiments of this application also provide a heterogeneous log management device, including: The sending unit is configured to send its own initial logs to the heterogeneous log management system, so that the heterogeneous log management system can determine the target log to be processed from the initial logs of at least one type of business system; determine the target field data corresponding to the preset audit field from the target log; determine the target field translation data corresponding to the target field data; and write the target field translation data into the position corresponding to the preset audit field in the pre-configured audit table. The acquisition unit is used to acquire audit information from the logs; The fourth determining unit is used to determine the audit content corresponding to the audit information from the audit table; The display unit is used to display the audit content.

[0072] The heterogeneous log management device provided in this embodiment belongs to the same application concept as the heterogeneous log management method provided in the above embodiments of this application. It can execute the method provided in any of the above embodiments of this application and has the corresponding functional modules and beneficial effects of the method. Technical details not described in detail in this embodiment can be found in the specific processing content of the heterogeneous log management method provided in the above embodiments of this application, and will not be repeated here.

[0073] The functions implemented by each unit in the above heterogeneous log management device can be implemented by the same or different processors, and this application embodiment does not limit this.

[0074] It should be understood that each unit in the above device can be implemented by a processor calling software. For example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of each unit in the device. The processor can be a general-purpose processor, such as a CPU or microprocessor, and the memory can be internal or external to the device. Alternatively, the units in the device can be implemented as hardware circuits. By designing the hardware circuits, some or all of the unit functions can be implemented. The hardware circuits can be understood as one or more processors. For example, in one implementation, the hardware circuit is an ASIC, and the functions of some or all of the above units are implemented by designing the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a PLD, such as an FPGA, which can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files to implement the functions of some or all of the above units. All units in the above device can be implemented entirely by a processor calling software, entirely by hardware circuits, or partially by a processor calling software with the remaining parts implemented by hardware circuits.

[0075] In this application embodiment, a processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a CPU, microprocessor, GPU, or DSP. In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. These logical relationships are fixed or reconfigurable. For example, the processor may be a hardware circuit implemented as an ASIC or PLD, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the processor loading instructions to implement the functions of some or all of the above units. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as an NPU, TPU, or DPU.

[0076] As can be seen, each unit in the above device can be one or more processors (or processing circuits) configured to implement the above methods, such as: CPU, GPU, NPU, TPU, DPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor forms.

[0077] Furthermore, the units in the above devices can be integrated in whole or in part, or they can be implemented independently. In one implementation, these units are integrated together and implemented in the form of a System-on-Chip (SoC). The SoC may include at least one processor for implementing any of the above methods or implementing the functions of the units in the device. The at least one processor may be of different types, such as CPU and FPGA, CPU and artificial intelligence processor, CPU and GPU, etc.

[0078] Exemplary electronic devices Another embodiment of this application also provides an electronic device, see [link to relevant documentation] Figure 3 As shown, the device includes: Memory 300 and processor 310; The memory 300 is connected to the processor 310 and is used to store programs; The processor 310 is configured to implement the heterogeneous log management method disclosed in any of the above embodiments by running the program stored in the memory 300.

[0079] Specifically, the aforementioned heterogeneous log management device may also include: a bus, a communication interface 320, an input device 330, and an output device 340.

[0080] The processor 310, memory 300, communication interface 320, input device 330, and output device 340 are interconnected via a bus. Among them: A bus can include a pathway for transmitting information between various components of a computer system.

[0081] The processor 310 can be a general-purpose processor, such as a general-purpose central processing unit (CPU), a microprocessor, etc., or an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present invention. It can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0082] Processor 310 may include a main processor, as well as a baseband chip, modem, etc.

[0083] The memory 300 stores a program that executes the technical solution of this invention, and may also store an operating system and other key business functions. Specifically, the program may include program code, which includes computer operation instructions. More specifically, the memory 300 may include read-only memory (ROM), other types of static storage devices capable of storing static information and instructions, random access memory (RAM), other types of dynamic storage devices capable of storing information and instructions, disk storage, flash memory, etc.

[0084] Input device 330 may include a device for receiving user input data and information, such as a keyboard, mouse, camera, scanner, light pen, voice input device, touch screen, pedometer, or gravity sensor.

[0085] Output device 340 may include devices that allow information to be output to a user, such as a display screen, printer, speaker, etc.

[0086] The communication interface 320 may include a device that uses any transceiver to communicate with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), etc.

[0087] The processor 310 executes the program stored in the memory 300 and calls other devices, which can be used to implement the various steps of any heterogeneous log management method provided in the above embodiments of this application.

[0088] Exemplary computer program products and storage media In addition to the methods and devices described above, embodiments of this application may also be computer program products, which include computer program instructions that, when executed by a processor, cause the processor to perform the steps in the heterogeneous log management method according to various embodiments of this application as described in any of the above embodiments of this specification.

[0089] The computer program product can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of this application. The programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0090] Furthermore, embodiments of this application may also be storage media storing a computer program, which is executed by a processor using the steps of the heterogeneous log management method according to various embodiments of this application described above. Specifically, the following steps can be implemented: Identify the target logs to be processed from the initial logs of at least one type of business system; Determine the target field data corresponding to the preset audit field from the target log; Determine the target field translation data corresponding to the target field data; The translated data of the target field is written to the position corresponding to the preset audit field in a pre-configured audit table, so as to audit the initial log through the audit table. Alternatively, The system sends its initial logs to a heterogeneous log management system, enabling the system to determine the target logs to be processed from the initial logs of at least one type of business system; it then determines the target field data corresponding to a preset audit field from the target logs; it determines the target field translation data corresponding to the target field data; and it writes the target field translation data into the position corresponding to the preset audit field in a pre-configured audit table. Obtain audit information from the logs; Determine the audit content corresponding to the audit information from the audit table; The audit content is displayed.

[0091] For the foregoing method embodiments, in order to simplify the description, they are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, because according to this application, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0092] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For apparatus embodiments, since they are basically similar to method embodiments, the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0093] The steps in the methods of the various embodiments of this application can be adjusted, merged, or deleted in order according to actual needs, and the technical features described in each embodiment can be replaced or combined.

[0094] The modules and sub-modules in the apparatus and terminal in the various embodiments of this application can be merged, divided, and deleted according to actual needs.

[0095] It should be understood that the disclosed terminals, devices, and methods can be implemented in other ways, given the several embodiments provided in this application. For example, the terminal embodiments described above are merely illustrative. For instance, the division of modules or sub-modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple sub-modules or modules may be combined or integrated into another module, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or modules, and may be electrical, mechanical, or other forms.

[0096] The modules or submodules described as separate components may or may not be physically separate. The components that constitute a module or submodule may or may not be physical modules or submodules; that is, they may be located in one place or distributed across multiple network modules or submodules. Some or all of the modules or submodules can be selected to achieve the purpose of this embodiment's solution, depending on actual needs.

[0097] Furthermore, the functional modules or sub-modules in the various embodiments of this application can be integrated into one processing module, or each module or sub-module can exist physically separately, or two or more modules or sub-modules can be integrated into one module. The integrated modules or sub-modules described above can be implemented in hardware or in the form of software functional modules or sub-modules.

[0098] 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 implementation should not be considered beyond the scope of this application.

[0099] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software unit executed by a processor, or a combination of both. The software unit 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.

[0100] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0101] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A heterogeneous log management method, characterized in that, include: Identify the target logs to be processed from the initial logs of at least one type of business system; Determine the target field data corresponding to the preset audit field from the target log; Determine the target field translation data corresponding to the target field data; The translated data of the target field is written into the position corresponding to the preset audit field in the pre-configured audit table, so as to audit the initial log through the audit table.

2. The method according to claim 1, characterized in that, The step of determining the target field translation data corresponding to the target field data includes: Determine the target scene data in the target field data; Determine the field translation correspondences corresponding to the target scene data, wherein the field translation correspondences are the correspondences between field data and translated data; From the field translation correspondence, determine the target field translation data corresponding to the target field data.

3. The method according to claim 1, characterized in that, Identify the target logs to be processed from the initial logs of at least one type of business system, including: Obtain initial logs from at least one type of business system; The initial log is transmitted to the message queue; The target log is determined from the message queue.

4. The method according to claim 3, characterized in that, Transmitting the initial log to the message queue includes: Based on the attribute information of the initial logs, the initial logs are classified to obtain classification identifiers; Generate a log identifier for each of the initial logs; The initial log is transmitted to the message queue based on the classification identifier and the log identifier.

5. The method according to claim 3, characterized in that, Determining the target log from the message queue includes: The initial log is rearranged according to the log identifier and the category identifier to obtain the rearranged result; Based on the rearrangement result, messages in the message queue are consumed, and the initial log to be consumed is determined as the target log.

6. The method according to claim 3, characterized in that, Obtain initial logs from at least one type of business system, including: Determine the system language of the business system; Call the multilingual conversion interface corresponding to the system language to obtain the initial log from the business system.

7. The method according to claim 1, characterized in that, Also includes: Determine the acquisition duration of the initial log; The initial log is stored based on the acquisition duration.

8. A heterogeneous log management method, characterized in that, include: Send its own initial logs to the heterogeneous log management system so that the heterogeneous log management system can determine the target logs to be processed from the initial logs of at least one type of business system. Determine the target field data corresponding to the preset audit field from the target log; Determine the target field translation data corresponding to the target field data; Write the translated data of the target field into the position corresponding to the preset audit field in the pre-configured audit table; Obtain audit information from the logs; Determine the audit content corresponding to the audit information from the audit table; The audit content is displayed.

9. An electronic device, characterized in that, Including memory and processor; The memory is connected to the processor and is used to store programs; The processor is used to implement the heterogeneous log management method as described in any one of claims 1 to 8 by running a program in the memory.

10. A storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, implements the heterogeneous log management method as described in any one of claims 1 to 8.

Images