Storage methods, devices, equipment, and media for AIOPS operations and maintenance metadata.
By generating a collection and association of metadata for operation and maintenance objects, AI algorithms, and operation and maintenance operations based on the platform and application architecture in automated operation and maintenance scenarios, the flexibility and applicability issues of metadata management in existing technologies are solved, and efficient storage management of complex systems is achieved.
Patent Information
- Application Number
- CN202311287222.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-09-28
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2043-09-28
AI Technical Summary
Existing data processing methods are not suitable for operation and maintenance metadata scenarios with complex architectures and diverse metadata associations, resulting in poor flexibility and limited applicability.
Based on the platform and application architecture of automated operation and maintenance scenarios, a collection and relationship of metadata of operation and maintenance objects, basic metadata of AI algorithms, and metadata of operation and maintenance operations are generated and stored. The metadata of operation and maintenance objects of IaaS, PaaS, and SaaS are obtained through the system networking architecture, and the metadata of SaaS operation and maintenance objects is obtained through abstraction, decomposition and reorganization. The relationship of tool metadata is constructed.
It enables efficient storage and management of operation and maintenance metadata for complex systems, improving flexibility and applicability, and is suitable for objects with mixed architectural features.
Smart Images

Figure CN117539859B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of intelligent operation and maintenance, and in particular to a method, apparatus, device and medium for storing AIOPS operation and maintenance metadata. Background Technology
[0002] Metadata is data that describes data and serves as a unit of data asset management. As systems grow in scale, the cost of manually maintaining metadata increases, making automated and intelligent operations and maintenance (O&M) the mainstream approach. AIOPS (Artificial Intelligence for IT Operations) is a high-level implementation of automated O&M, reducing manual input and freeing up human productivity. Its key to implementation is asset management of O&M metadata across the entire domain, including sets of O&M objects, sets of O&M object operations, and sets of O&M object characteristics and their relationships, ultimately achieving automated / intelligent O&M operations.
[0003] Currently, data processing methods based on fixed spatial models are suitable for metadata management of data conforming to the characteristics of fixed spatial models. However, for heterogeneous metadata with clear classifications and distinct characteristics for each category, significant manpower is required for model selection. Metadata management methods based on SaaS architecture are suitable for scenarios where metadata can be transformed using custom rules and where the relationships between hierarchical data are clearly defined. However, for different metadata with varying characteristics, it is difficult to define rule transformations and relationship associations. Data management methods based on fixed architectures are suitable for scenarios where the data processing process conforms to architectural characteristics, but are not applicable to objects whose datasets have mixed architectural characteristics.
[0004] In summary, existing data processing methods are not suitable for operation and maintenance metadata processing scenarios with complex architectures and diverse metadata associations, resulting in poor flexibility and limited applicability. Summary of the Invention
[0005] The main objective of this invention is to provide a method, apparatus, device, and storage medium for storing AIOPS operation and maintenance metadata, aiming to solve the technical problem of inefficient storage and management of intelligent operation and maintenance metadata.
[0006] To achieve the above objectives, this invention provides a method for storing AIOPS operation and maintenance metadata, wherein the operation and maintenance metadata includes operation and maintenance object metadata, AI algorithm basic metadata, and operation and maintenance class metadata, and the method includes:
[0007] Based on the platform architecture and application architecture of the automated operation and maintenance scenario, a collection of metadata and related relationships of the operation and maintenance objects are generated and stored.
[0008] Based on the data architecture of the operation and maintenance objects, a collection of basic metadata and their relationships for the AI algorithm are generated and stored;
[0009] Based on the platform architecture and application architecture of the automated operation and maintenance scenario, a collection of metadata and related relationships of the operation and maintenance operation classes are generated and stored.
[0010] For example, the platform architecture is a tool integration approach, the application architecture is a set of tools used in the business process, and the operation and maintenance object metadata includes IaaS operation and maintenance object metadata, PaaS operation and maintenance object metadata, PaaS tool set metadata, and SaaS operation and maintenance object metadata.
[0011] The steps of generating and storing the collection and association relationships of the metadata of the operation and maintenance objects in the platform architecture and application architecture based on the automated operation and maintenance scenario include:
[0012] Based on the configuration management database corresponding to the system network architecture, obtain the IaaS operation and maintenance object metadata, PaaS operation and maintenance object metadata, and PaaS tool set metadata corresponding to the tool integration method.
[0013] Based on the abstract decomposition and reorganization of the metadata of the operation and maintenance application, the metadata of the SaaS operation and maintenance objects corresponding to the set of tools used in the business process is obtained.
[0014] For example, the step of obtaining the SaaS operation and maintenance object metadata corresponding to the set of tools used in the business process based on the abstract decomposition and reorganization of operation and maintenance application metadata includes:
[0015] The functional characteristics of each processing unit in the processing unit link of the business process and the matrix characteristics of each data unit in the data unit link of the business process are combined to obtain a general application link.
[0016] Based on the application metadata decomposition and reorganization method abstracted in the process of data unit dimension transformation, the operation and maintenance application metadata corresponding to the general application link is decomposed and reorganized to obtain the SaaS operation and maintenance object metadata corresponding to the tool set used in the business process.
[0017] For example, the data architecture is a method for associating and managing data during business processes. The step of generating and storing the set of basic metadata and their relationships for the AI algorithm based on the data architecture of the operation and maintenance object includes:
[0018] The full set of operation and maintenance feature units corresponding to the data architecture is deduplicated to generate a collection of operation and maintenance object feature units; wherein, the operation and maintenance feature units are feature units corresponding to the operation and maintenance object feature data that are associated and related in the business process;
[0019] Associate the relationships between operation and maintenance objects and object units to generate a set of object units for operation and maintenance objects;
[0020] The data architecture based on operation and maintenance objects adds object unit associations to the object unit set, and generates and stores the set of basic metadata of the AI algorithm and its associations.
[0021] For example, the platform architecture is a tool integration approach, and the application architecture is a collection of tools used in the business process;
[0022] The steps of generating and storing the set of metadata and their relationships for the operation and maintenance classes in the platform architecture and application architecture based on the automated operation and maintenance scenario include:
[0023] By abstracting, decomposing, and reorganizing the metadata of the operation and maintenance applications corresponding to the set of tools used in the business process, tool metadata is obtained.
[0024] Based on the tool integration method, the association relationship between the tool metadata is constructed, and the operation and maintenance class metadata is obtained.
[0025] For example, after the step of constructing the association relationship between the tool metadata based on the tool integration method and obtaining the operation and maintenance class metadata, the following steps are included:
[0026] Determine the smallest repeating unit for constructing the interrelationships between the tool metadata based on the tool integration method;
[0027] Using the smallest repeating unit as the basic unit metadata object, traverse the basic unit metadata object to generate a complete set of relationships for the operation and maintenance class metadata.
[0028] For example, the step of traversing the basic unit metadata object to generate a complete set of relationships for the operation and maintenance class metadata includes:
[0029] By describing the cognitive attributes of the operation and maintenance application metadata, classifying the concrete types of metadata units, exhaustively arranging the metadata entities at the application execution cognitive level, and describing the entities at the entity execution level, a complete set of relationships for the operation and maintenance operation class metadata is obtained.
[0030] Furthermore, to achieve the above objectives, the present invention also provides a storage device for AIOPS operation and maintenance metadata, wherein the operation and maintenance metadata includes operation and maintenance object metadata, AI algorithm basic metadata, and operation and maintenance class metadata. The storage device for AIOPS operation and maintenance metadata includes:
[0031] The first storage module is used to generate and store the collection and association relationships of the metadata of the operation and maintenance objects based on the platform architecture and application architecture of the automated operation and maintenance scenario.
[0032] The second storage module is used to generate and store a set of basic metadata and related relationships of the AI algorithm based on the data architecture of the operation and maintenance object;
[0033] The third storage module is used to generate and store the collection and association relationships of the metadata of the operation and maintenance classes based on the platform architecture and application architecture of the automated operation and maintenance scenario.
[0034] In addition, to achieve the above objectives, the present invention also provides a storage device for AIOPS operation and maintenance metadata, the device comprising: a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program being configured to implement the steps of the above-described method for storing AIOPS operation and maintenance metadata.
[0035] In addition, to achieve the above objectives, the present invention also provides a storage medium on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the above-described method for storing AIOPS operation and maintenance metadata.
[0036] In the AIOPS operation and maintenance metadata storage method of the present invention, the operation and maintenance metadata includes operation and maintenance object metadata, AI algorithm basic metadata, and operation and maintenance operation class metadata. The operation and maintenance metadata is stored in modules based on the metadata characteristics of the objects corresponding to the AIOPS architecture, object characteristics, and the domain in which the operations reside. Specifically: based on the platform architecture and application architecture of the automated operation and maintenance scenario, a set of operation and maintenance object metadata and its associated relationships are generated and stored; based on the data architecture of the operation and maintenance objects, a set of AI algorithm basic metadata and its associated relationships are generated and stored; based on the platform architecture and application architecture of the automated operation and maintenance scenario, a set of operation and maintenance operation class metadata and its associated relationships are generated and stored.
[0037] This application proposes an AIOPS operation and maintenance metadata modular storage implementation method based on system architecture demonstration. It constructs metadata sets and the relationships between sets and between set elements through the architectural characteristics of the operation and maintenance objects themselves, and efficiently stores and manages them. Since the method of classifying and traversing metadata objects and automatically constructing relationships based on the basic object platform, business and data architecture and application metadata characteristics is universal and easy to use, it is suitable for the metadata storage model design of general systems, and is especially suitable for complex systems implemented through architecture updates. Attached Figure Description
[0038] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0039] Figure 1 This is a schematic diagram of the hardware operating environment involved in the embodiments of the present invention;
[0040] Figure 2 This is a flowchart illustrating an embodiment of the AIOPS operation and maintenance metadata storage method of the present invention;
[0041] Figure 3 This is a schematic diagram of the platform architecture of an embodiment of the AIOPS operation and maintenance metadata storage method of the present invention;
[0042] Figure 4 This is a schematic diagram of the application architecture of an embodiment of the AIOPS operation and maintenance metadata storage method of the present invention.
[0043] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation
[0044] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
[0045] like Figure 1 As shown, Figure 1 This is a schematic diagram of the device structure of the hardware operating environment involved in the embodiments of the present invention. The device of the hardware operating environment of the embodiments of the present invention may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, and a communication bus 1002. The communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen and an input unit such as a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be a high-speed RAM memory or a stable memory (non-volatile memory), such as a disk storage device. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.
[0046] Optionally, the hardware operating environment may also include a camera, RF (Radio Frequency) circuitry, sensors, audio circuitry, a WiFi module, and so on. Sensors include, for example, light sensors, motion sensors, and others. An ambient light sensor can adjust the display brightness based on ambient light levels, while a proximity sensor can turn off the display and / or backlight when the hardware device is moved close to the ear. As a type of motion sensor, a gravity accelerometer can detect the magnitude of acceleration in various directions (typically three axes). When stationary, it can detect the magnitude and direction of gravity, and can be used for applications that identify the hardware device's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition functions (such as pedometers, tapping), etc. Of course, the hardware device can also be equipped with other sensors such as gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, which will not be elaborated upon here.
[0047] Those skilled in the art will understand that Figure 1 The device structure shown does not constitute a limitation on the device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0048] like Figure 1 As shown, the memory 1005, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and computer programs.
[0049] exist Figure 1 In the device shown, network interface 1004 is mainly used to connect to the backend server and communicate with it; user interface 1003 is mainly used to connect to the client (user terminal) and communicate with it; while processor 1001 can be used to call computer programs stored in memory 1005 and perform the following operations:
[0050] The operation and maintenance metadata includes operation and maintenance object metadata, AI algorithm basic metadata, and operation and maintenance operation class metadata.
[0051] Based on the platform architecture and application architecture of the automated operation and maintenance scenario, a collection of metadata and related relationships of the operation and maintenance objects are generated and stored.
[0052] Based on the data architecture of the operation and maintenance objects, a collection of basic metadata and their relationships for the AI algorithm are generated and stored;
[0053] Based on the platform architecture and application architecture of the automated operation and maintenance scenario, a collection of metadata and related relationships of the operation and maintenance operation classes are generated and stored.
[0054] Furthermore, the processor 1001 can call a computer program stored in the memory 1005 and also perform the following operations:
[0055] The platform architecture is a tool integration approach, the application architecture is a collection of tools used in the business process, and the operation and maintenance object metadata includes IaaS operation and maintenance object metadata, PaaS operation and maintenance object metadata, PaaS tool set metadata, and SaaS operation and maintenance object metadata.
[0056] The steps of generating and storing the collection and association relationships of the metadata of the operation and maintenance objects in the platform architecture and application architecture based on the automated operation and maintenance scenario include:
[0057] Based on the configuration management database corresponding to the system network architecture, obtain the IaaS operation and maintenance object metadata, PaaS operation and maintenance object metadata, and PaaS tool set metadata corresponding to the tool integration method.
[0058] Based on the abstract decomposition and reorganization of the metadata of the operation and maintenance application, the metadata of the SaaS operation and maintenance objects corresponding to the set of tools used in the business process is obtained.
[0059] Furthermore, the processor 1001 can call a computer program stored in the memory 1005 and also perform the following operations:
[0060] The steps for obtaining SaaS operation and maintenance object metadata corresponding to the set of tools used in the business process by abstracting, decomposing, and reorganizing the metadata of operation and maintenance applications include:
[0061] The functional characteristics of each processing unit in the processing unit link of the business process and the matrix characteristics of each data unit in the data unit link of the business process are combined to obtain a general application link.
[0062] Based on the application metadata decomposition and reorganization method abstracted in the process of data unit dimension transformation, the operation and maintenance application metadata corresponding to the general application link is decomposed and reorganized to obtain the SaaS operation and maintenance object metadata corresponding to the tool set used in the business process.
[0063] Furthermore, the processor 1001 can call a computer program stored in the memory 1005 and also perform the following operations:
[0064] The data architecture refers to the method of data association and management during business processes. The steps of generating and storing the set of basic metadata and related relationships of the AI algorithm based on the data architecture of the operation and maintenance object include:
[0065] The full set of operation and maintenance feature units corresponding to the data architecture is deduplicated to generate a collection of operation and maintenance object feature units; wherein, the operation and maintenance feature units are feature units corresponding to the operation and maintenance object feature data that are associated and related in the business process;
[0066] Associate the relationships between operation and maintenance objects and object units to generate a set of object units for operation and maintenance objects;
[0067] The data architecture based on operation and maintenance objects adds object unit associations to the object unit set, and generates and stores the set of basic metadata of the AI algorithm and its associations.
[0068] Furthermore, the processor 1001 can call a computer program stored in the memory 1005 and also perform the following operations:
[0069] The platform architecture is a tool integration approach, and the application architecture is a collection of tools used in the business process;
[0070] The steps of generating and storing the set of metadata and their relationships for the operation and maintenance classes in the platform architecture and application architecture based on the automated operation and maintenance scenario include:
[0071] By abstracting, decomposing, and reorganizing the metadata of the operation and maintenance applications corresponding to the set of tools used in the business process, tool metadata is obtained.
[0072] Based on the tool integration method, the association relationship between the tool metadata is constructed, and the operation and maintenance class metadata is obtained.
[0073] Furthermore, the processor 1001 can call a computer program stored in the memory 1005 and also perform the following operations:
[0074] After the step of constructing the association relationship between the tool metadata based on the tool integration method and obtaining the operation and maintenance class metadata, the following steps are included:
[0075] Determine the smallest repeating unit for constructing the interrelationships between the tool metadata based on the tool integration method;
[0076] Using the smallest repeating unit as the basic unit metadata object, traverse the basic unit metadata object to generate a complete set of relationships for the operation and maintenance class metadata.
[0077] Furthermore, the processor 1001 can call a computer program stored in the memory 1005 and also perform the following operations:
[0078] The step of traversing the basic unit metadata object to generate a complete set of relationships for the operation and maintenance class metadata includes:
[0079] By describing the cognitive attributes of the operation and maintenance application metadata, classifying the concrete types of metadata units, exhaustively arranging the metadata entities at the application execution cognitive level, and describing the entities at the entity execution level, a complete set of relationships for the operation and maintenance operation class metadata is obtained.
[0080] In one embodiment of the AIOPS operation and maintenance metadata storage method of the present invention, the operation and maintenance metadata includes operation and maintenance object metadata, AI algorithm basic metadata, and operation and maintenance class metadata, as shown in the figure. Figure 2 The method includes:
[0081] Step S10: Based on the platform architecture and application architecture of the automated operation and maintenance scenario, generate and store the collection of metadata and association relationships of the operation and maintenance objects;
[0082] Step S20: Based on the data architecture of the operation and maintenance object, generate and store the set of basic metadata of the AI algorithm and its association relationships;
[0083] Step S30: Based on the platform architecture and application architecture of the automated operation and maintenance scenario, generate and store the collection and association relationships of the operation and maintenance operation class metadata.
[0084] The operation and maintenance metadata is stored in modules based on the metadata characteristics of objects, object characteristics, and the domain in which operations are performed, corresponding to the AIOPS architecture.
[0085] This application proposes a modular storage implementation method for AIOPS operation and maintenance metadata based on system architecture argumentation. The system architecture described in this application includes platform architecture, application architecture, and data architecture, aiming to form a transparent operation and maintenance metadata management system. The platform architecture refers to the integration method of various tools; the application architecture refers to the set of tools used in the business process from data source, logical processing, result output, and result display, and their integration method; the data architecture refers to the data association and management method in the business implementation process. The basic viewpoint of this application is that AIOPS is essentially a process of implementing automated OPS based on statistical analysis of basic operation and maintenance data combined with AI algorithm control, representing a high-level implementation of automated operation and maintenance. For ease of description, AIOPS will be decomposed into a process of data statistics + AI algorithms + automated OPS. This application's description is based on architecture and provides a general method for decomposing AIOPS operation and maintenance metadata modules.
[0086] For example, the step of storing the operation and maintenance metadata in modules based on the metadata characteristics of objects, object characteristics, and the domain in which the operation is located, corresponding to the AIOPS architecture, includes:
[0087] Based on the platform architecture and application architecture of the automated operation and maintenance scenario, a collection of metadata and related relationships of the operation and maintenance objects are generated and stored.
[0088] Based on the data architecture of the operation and maintenance objects, a collection of basic metadata and their relationships for the AI algorithm are generated and stored;
[0089] Based on the platform architecture and application architecture of the automated operation and maintenance scenario, a collection of metadata and related relationships of the operation and maintenance operation classes are generated and stored.
[0090] Specifically, for a complete system, the operation and maintenance objects include: network devices, computing servers, software on the servers, business logic units on the software, data on the business logic units, and the network architecture relationships between these five objects. The operation and maintenance management process involves the automated and intelligent application of these objects. The operation and maintenance management process objects include automated processing logic units, operation and maintenance object characteristics, intelligent algorithm units, and their integration relationships. Therefore, the operation and maintenance management process objects have various forms and unstructured characteristics; they are a collection of metadata abstractions, and this collection is labeled as SE.
[0091] Taking the storage of operation and maintenance metadata involved in the intelligent operation and maintenance of SaaS (Software as a Service) applications using cloud-based PaaS (Platform as a Service) tools as an example, according to the above analysis, operation and maintenance metadata includes the following sets:
[0092] I represents the metadata of IaaS (Infrastructure as a Service) operation and maintenance objects;
[0093] P represents the metadata of the PaaS operation and maintenance object;
[0094] T represents the set of PAAS tools, and Tt represents each tool.
[0095] S represents the metadata of SaaS operation and maintenance objects and the metadata involved in their continuous data flow;
[0096] A represents the automated operation and maintenance metadata storage object;
[0097] G represents the intelligent operation and maintenance metadata storage object;
[0098] L represents the above set and the relationships between its elements.
[0099] Among them, I, P, T, and S can obtain the object set through exhaustive enumeration of operation and maintenance assets. The operation and maintenance application metadata of A and G have a unified format (M). G is a special case of A, which is a process of refining A and integrating AI algorithms. The processed objects include two types of data. One type is the metadata that describes the application itself as a storage object. The other type is the input and output feature data matrix of the operation and maintenance application. The latter needs to be constructed and stored according to the characteristics of the specific operation and maintenance application itself. The acquisition of L is more complicated and needs to be explained through classification.
[0100] (1) Relationship 1: Relationships between elements of I, P, T, and S
[0101] (2) Relationship 2: Interrelationships between I, P, T, S and M
[0102] (3) Relationship 3: Relationship between M elements
[0103] A modular storage implementation method for AIOPS operation and maintenance metadata based on system architecture demonstration is essentially a method for implementing modular storage of metadata based on the metadata characteristics of three domains reflected by the architecture: objects, object characteristics, and operations. It consists of three steps: First, forming a set of operation and maintenance object metadata and its relationships based on the platform architecture and application architecture, processing relationship 1; Second, forming a set of AI algorithm basic data and its relationships based on the operation and maintenance object data architecture, processing relationship 2; Third, generating a set of automated operation and maintenance class metadata and its relationships, processing relationship 3.
[0104] For example, the platform architecture is a tool integration approach, the application architecture is a set of tools used in the business process, and the operation and maintenance object metadata includes IaaS operation and maintenance object metadata, PaaS operation and maintenance object metadata, PaaS tool set metadata, and SaaS operation and maintenance object metadata.
[0105] Based on the configuration management database corresponding to the system network architecture, obtain the IaaS operation and maintenance object metadata, PaaS operation and maintenance object metadata, and PaaS tool set metadata corresponding to the tool integration method.
[0106] Based on the abstract decomposition and reorganization of the metadata of the operation and maintenance application, the metadata of the SaaS operation and maintenance objects corresponding to the set of tools used in the business process is obtained.
[0107] Step 1: Based on the platform architecture and application architecture, form a collection of metadata for operation and maintenance objects and their relationships;
[0108] The platform architecture determines the application architecture, and the platform architecture and application architecture together constitute the overall set of operation and maintenance objects. Based on the platform architecture and application architecture of the business system, a set of operation and maintenance object metadata is formed. This set covers the operation and maintenance object entities and the relationships between them.
[0109] The platform offers multiple ways to implement business operations, and its architecture enables network hardware to operate at peak efficiency. The application architecture, on the other hand, is the integrated logic by which platform tools efficiently implement business operations; it is the largest collection of operational metadata and their relationships after business functionality has been established. For example, if the platform is a PaaS cloud, PaaS offers many tool components. Different tool components can be used to achieve the same function for the same business, resulting in different application architectures depending on the use of these components.
[0110] For the aforementioned three types of object data, I, P, and T (I represents IaaS operation and maintenance object metadata, P represents PaaS operation and maintenance object metadata, and T represents PaaS tool set, with Tt representing each tool), the elements and relationships of these three sets are determined by the actual system's network architecture, and its storage system is generally an asset configuration table (CMDB).
[0111] S represents the metadata of SaaS operation and maintenance objects and the metadata involved in the continuous flow of data. It is a type of data formed based on the characteristics of the tool itself. It can only be obtained by abstracting, decomposing and reorganizing the metadata of operation and maintenance applications. The basic idea of the method is to decompose the application metadata units and form an application architecture chain according to the tools running in different unit entities.
[0112] For example, the step of obtaining the SaaS operation and maintenance object metadata corresponding to the set of tools used in the business process based on the abstract decomposition and reorganization of operation and maintenance application metadata includes:
[0113] The functional characteristics of each processing unit in the processing unit link of the business process and the matrix characteristics of each data unit in the data unit link of the business process are combined to obtain a general application link.
[0114] Based on the application metadata decomposition and reorganization method abstracted in the process of data unit dimension transformation, the operation and maintenance application metadata corresponding to the general application link is decomposed and reorganized to obtain the SaaS operation and maintenance object metadata corresponding to the tool set used in the business process.
[0115] 1.1 Obtaining Application Metadata and Application Links
[0116] The basic idea of the method is to combine the functional characteristics of each processing link in the processing unit link and the matrix characteristics of each data unit in the data unit link to form a general application link. Then, based on the application metadata abstracted from the data unit dimension transformation process, it is decomposed and recombined to obtain the SaaS operation and maintenance object metadata.
[0117] Taking the implementation process of AIOPS log anomaly prediction application as an example, and using log line selection bag-of-words statistics as the basic method for text conversion into a matrix, the principle of this step is explained. CH{preprocessing, time window selection, keyword statistics, data annotation, feature matrix generation, matrix input pre-transformation} = {E1, E2, E3, E4, E5, E6}, after being decomposed and reorganized by the application metadata, forms the following chain 1 and chain 2.
[0118] Link 1:
[0119] Application link: CZ1{J1az, E1, J2az, Pk, J5b(c+1), E5, J6de, E6, J7fg}, its processing unit link can be denoted as CH1{E1, Pk, E5, E6}, and its data unit link can be denoted as DH1{J1az, J2az, J5b(c+1), J6de, J7fg}.
[0120] Link 2:
[0121] Application link: Pk{J2az, E2, J3bz, E3, J4bc, E4, J5b(c+1)}, its processing unit link can be denoted as {E2, E3, E4}, and its data unit link can be denoted as {J2az, J3bz, J4bc, J5b(c+1)}.
[0122] In this process, CH{preprocessing, time window selection, keyword statistics, data labeling, feature matrix generation, matrix input pre-transformation, AI algorithm calculation, calculation result business conversion, triggering OPS operation, operation execution} is labeled CH{E1, E2, E3, ..., E10}. The data units for input and output of each processing step are labeled DH{J1, J2, J3, ..., J9}. The execution process can be represented as CZ{J1, E1, J2, E2, J3, E3, ..., J9, E9, E10}, where CH is the processing unit link, DH is the data unit link, and CZ is the application link.
[0123] Assuming J1 has dimensions (a, z), and J1az represents J1 as a matrix with a rows and z columns, then E1 is preprocessed (J2az), E2 is time window selection (J3bz, where b is a value less than a), E3 is keyword statistics (J4bc, where c is the number of keywords), E4 is data annotation (J5b(c+1)), E5 is feature matrix generation (J6de), E6 is matrix input pre-transformation (J7fg), E7 is AI algorithm calculation (J8hi), and E8 is business transformation of calculation results (J9jk).
[0124] The final data unit link DH is {J1az, J2az, J3bz, J4bc, J5b(c+1), J6de, J7fg, J8hi, J9jk}.
[0125] The application link CZ is CZ{J1az,E1,J2az,E2,J3bz,E3,J4bc,E4,J5b(c+1),E5,J6de,E6,J7fg,E7,J8hi,E8,J9jk,E9,E10}.
[0126] 1.2 Forming an application call chain
[0127] The basic method involves forming a call chain of application metadata unit execution entities, and designing a tool set based on the tool function module design method of data unit transformation characteristics. This design method determines the smallest repeating unit based on the decomposed application link, and then performs experience-level feature recombination according to the smallest repeating unit to form a tool-level feature set. Taking the application link decomposed in the AIOPS data processing scenario of log anomaly prediction as an example, the smallest repeating unit is {J1, E0, J2}, which is a set consisting of an input set, a minimum processing abstraction, and an output. The result of description, transformation, and concatenation processing according to the experience data feature set TO = {data source, computational load, implementation method, transformation timeliness} is as follows:
[0128] (1) Tool 1, application link: {J1az, E1, J2az, Pk, J5b(c+1), E5, J6de, E6, J7fg}, the processing involved includes {preprocessing, time window selection + keyword statistics + data annotation, feature matrix generation, matrix input pre-conversion}; also includes application link: {J8hi, E8, J9jk}, the processing involved includes {calculation result business conversion}.
[0129] The corresponding functional module feature set T1 elements include {cross-database scheduling}, {big data distributed computing, multi-engine execution}, {custom development, module reuse, program decomposability, parameter adjustment}, {stream processing}, {user multi-tenancy management}, {access control}, and {operation log}.
[0130] (2) Tool 2, application link: {J7fg, E7, J8hi}, the corresponding processing process includes {AI algorithm calculation}, actual experience feature value {intermediate value / database, large, reusable conversion, real time}, the corresponding functional module feature set T2 elements include: {custom data source}, {dedicated calculation engine}, {reusable sharing}, {real-time processing}, {user management}, {permission management}, {operation log}.
[0131] (3) Tool 3, application link: {E9, E10}, the corresponding processing procedure is {trigger OPS operation, operation execution}, the actual experience feature value is {none, none, single point control, parallel / high concurrency processing}, the corresponding functional module feature set T3 elements include: {single point control}, {parallel / high concurrency processing}, {user management}, {permission management}, {operation log}.
[0132] Assuming that tools 1, 2, and 3 are containerization tools for PaaS, and there is a process of transferring data from tool 1 to tool 2 to the physically deployed database D, then the tool access call chain is extended to tool 1 - database D - tool 2 - tool 1 - tool 3 to form a SaaS application, where tool 1, tool 2, tool 3, and database D are T1, T2, T3, and T4, respectively.
[0133] In basic platform architecture Figure 3 For details on the application architecture formed by adding the calling relationships of the tool set, please refer to [link / reference]. Figure 4 , Figure 4 Solid lines indicate the direction of business data flow, while dashed lines indicate the set to which the data belongs.
[0134] For example, the data architecture is a method for associating and managing data during business processes. The step of generating and storing the set of basic metadata and their relationships for the AI algorithm based on the data architecture of the operation and maintenance object includes:
[0135] The full set of operation and maintenance feature units corresponding to the data architecture is deduplicated to generate a collection of operation and maintenance object feature units; wherein, the operation and maintenance feature units are feature units corresponding to the operation and maintenance object feature data that are associated and related in the business process;
[0136] Associate the relationships between operation and maintenance objects and object units to generate a set of object units for operation and maintenance objects;
[0137] The data architecture based on operation and maintenance objects adds object unit associations to the object unit set, and generates and stores the set of basic metadata of the AI algorithm and its associations.
[0138] Step 2: Based on the data architecture of the operation and maintenance objects, form the basic data set of AI algorithms and their relationships.
[0139] The operation and maintenance object data architecture refers to the characteristic data architecture of operation and maintenance objects formed based on the operation and maintenance object architecture.
[0140] The metadata of operation and maintenance (O&M) objects originates from the O&M objects themselves and is concrete data describing the O&M objects. It can be understood as data describing the characteristic data of the O&M objects. The characteristic data of O&M objects is the foundational data for AI algorithms, including metrics, logs, and alarms. The relationships between these foundational data are determined by the relationships between the objects in the first step of forming the set and the log characteristics of the O&M object itself, and this set is labeled D. The steps for constructing the O&M object characteristic data architecture are as follows:
[0141] 2.1 Constructing the Feature Object Unit of Operation and Maintenance Object
[0142] The entire set of operation and maintenance feature units is deduplicated to form a set of operation and maintenance object feature units. For example, if Tool 1 has an indicator set A = {T1, T2, T3} and Tool 2 has an indicator set B = {Y1, T2}, this operation is to take the intersection of A and B.
[0143] 2.2 Relationships between associated operation and maintenance objects and object units
[0144] Based on the operational experience of the operation and maintenance objects, a set of object units for tools is formed. For tool T, its indicators include {P1, P2, P3}, which are mapped one by one to the object units to form the set of object units for the operation and maintenance objects.
[0145] 2.3 Constructing object unit relationships based on the operation and maintenance object architecture
[0146] This step can be summarized as replacing the node with a set of object units in the original operation and maintenance object architecture to form the final set of object units.
[0147] 2.4 Adding object unit relationships based on business call chains
[0148] Based on step one, the architecture relationship of operation and maintenance objects is realized, forming the object unit relationship construction.
[0149] For example, the platform architecture is a tool integration approach, and the application architecture is a collection of tools used in the business process;
[0150] The steps of generating and storing the set of metadata and their relationships for the operation and maintenance classes in the platform architecture and application architecture based on the automated operation and maintenance scenario include:
[0151] By abstracting, decomposing, and reorganizing the metadata of the operation and maintenance applications corresponding to the set of tools used in the business process, tool metadata is obtained.
[0152] Based on the tool integration method, the association relationship between the tool metadata is constructed, and the operation and maintenance class metadata is obtained.
[0153] Step 3: Generate a collection of metadata for automated operation and maintenance classes and their associated relationships;
[0154] Application architecture and data architecture based on automated operation and maintenance scenarios aggregate object operation metadata sets.
[0155] 3.1 Classification and Collection of Tool Metadata
[0156] Based on the decomposition and reorganization of application metadata, tool metadata is categorized. Here, metadata refers to the metadata of the tools themselves. The basic idea is to combine the functional characteristics of each processing unit in the processing unit chain and the matrix characteristics of each data unit in the data unit chain to form a general application chain. Referring to the example in the first step, in the implementation of the AIOPS log anomaly prediction application, bag-of-words statistics are used as the basic method for converting log lines into matrices. The application processing chain is: CH{preprocessing, time window selection, keyword statistics, data annotation, feature matrix generation, matrix input pre-transformation, AI algorithm calculation, business conversion of calculation results, triggering OPS operation, operation execution}.
[0157] Link 1:
[0158] Application link: CZ1{J1az, E1, Pki, Pk, Pko, E5, J6de, E6, J7fg, E7, J8hi, E8, J9jk, E9, E10}, its processing unit link can be denoted as CH1{E1, Pk, E5, E6, E7, E8, E9, E10}, and its data unit link can be denoted as DH1{J1az, Pki, Pko, J6de, J7fg, J8hi, J9jk}.
[0159] Link 2:
[0160] Application link: Pk{J2az, E2, J3bz, E3, J4bc, E4, J5b(c+1)}, its processing unit link can be denoted as {E2, E3, E4}, and its data unit link can be denoted as {J2az, J3bz, J4bc, J5b(c+1)}.
[0161] For example, after the step of constructing the association relationship between the tool metadata based on the tool integration method and obtaining the operation and maintenance class metadata, the following steps are included:
[0162] Determine the smallest repeating unit for constructing the interrelationships between the tool metadata based on the tool integration method;
[0163] Using the smallest repeating unit as the basic unit metadata object, traverse the basic unit metadata object to generate a complete set of relationships for the operation and maintenance class metadata.
[0164] 3.2 Relationships between tool metadata
[0165] The tool-based integration approach constructs relationships between tool metadata. Its design method involves determining the smallest repeating unit based on the decomposed application chain, and then reorganizing features at an empirical level according to this smallest repeating unit to form a tool-level feature set. Taking the application chain decomposed in the AIOPS data processing scenario of log anomaly prediction as an example, the smallest repeating unit is {J1, E0, J2}, which is a set consisting of an input set, a minimum processing abstraction, and an output, outputting the relationships between different tool metadata.
[0166] (1) Tool 1: {E1, Pk, E5, E6, E8}, i.e. {E1, E2, E3, E4, E5, E6, E8}
[0167] (2) Tool 2: E7
[0168] (3) Tools 3: E9, E10
[0169] The relationship is as follows, according to the application architecture call flow, the application chain {tool 1, tool 2, tool 3}.
[0170] 3.3 Traversing the basic unit metadata object forms a complete set of relations.
[0171] Based on the set of operation and maintenance object entities, a hierarchical storage model design method for operation and maintenance metadata based on application metadata classification and traversal is adopted, forming a multi-layer storage model according to four levels: human cognition, concrete classification, software cognition, and software execution.
[0172] For example, the step of traversing the basic unit metadata object to generate a complete set of relationships for the operation and maintenance class metadata includes:
[0173] By describing the cognitive attributes of the operation and maintenance application metadata, classifying the concrete types of metadata units, exhaustively arranging the metadata entities at the application execution cognitive level, and describing the entities at the entity execution level, a complete set of relationships for the operation and maintenance operation class metadata is obtained.
[0174] First: Describe the cognitive attributes of application metadata. This refers to summarizing the application according to its major categories. For example, signals and systems are divided into three main parts: input, processing, and output. Taking the operation and maintenance automation scenario as an example, its application metadata cognitive attribute description can be summarized as {signal, automation OPS, operation and maintenance object}. Second: Describe the concrete type classification of metadata units. This refers to the concrete description based on the generalized results. It is a description summary at the implementation level. Its goal is to combine the attribute objects with the implementation process of human brain calculation, transformation, and execution, guiding the next layer of human brain execution layer traversal process. Its decomposition process is related to the application's own attributes. The data object processed in the automation OPS application scenario is the operation and maintenance object. OPS operations include performing detection and modification on the operation and maintenance object. Therefore, {signal, automation OPS, execution object}. The signal is a relatively fixed trigger signal. Automation OPS includes two categories: {detection, modification}. The execution object refers to the operation and maintenance object, which includes {network hardware, software carrier running on the hardware, business logic entity, and data flow}. Third: Perform metadata entity traversal and arrangement; based on the second step, implement exhaustive arrangement of metadata entities at the application execution cognitive level. Machine-level execution metadata refers to the traversal and arrangement of metadata at a level that the software carrier can directly recognize. Fourth: Perform entity description at the entity execution level, designing storage entry points for the transfer process to obtain and access each arrangement relationship.
[0175] Taking the automated and intelligent operation and maintenance metadata layered storage model as an example, the specific layering process is as follows:
[0176] First layer: {signals, automated OPS, maintenance objects};
[0177] The second layer consists of: {signals, {detection and change}, {network hardware, software running on the hardware, business logic entities, and data flow}.
[0178] The third layer consists of 40 elements: A is the total set of automated OPS {configuration changes, status changes, operation changes, inspections, special tests} and the operation and maintenance objects E {switches, servers, load balancers, data acquisition tools, ETL, TD, BI, job flows on ETL tools and their relationships}.
[0179] Fourth layer: 40 execution control units combined with third layer units
[0180] Based on the independent and repeating data units in the processing results of 3.2, the complete set of relations is formed by iterative traversal according to the processing method in 3.3. The traversal method is described below:
[0181] First layer: {Signal, Tool 1, Tool 2, Tool 3, SE}
[0182] Second layer: {signal, {E1, Pk, E5, E6, E8}, {E7}, {E9, E10}, SE}
[0183] Third layer: Basic unit {signals, {E1, E2, E3, E4, E5, E6, E8}, {E7}, {E9, E10}, SE}
[0184] Each unit is expanded using Tools 1, 2, and 3 as follows:
[0185] Tool 1: {Signals, {E1, E2, E3, E4, E5, E6, E8}, D}
[0186] Tool 2: {D, E7, Signal}
[0187] Tool 3: {Signals, {E9, E10}, SE}
[0188] Each tool's third-layer parameter set is formed by combining the component parameter objects of various instances. The number of combinations for each tool is recorded as X, Y, and Z. Therefore, the total number of control unit values in this layer is N = X * Y * Z.
[0189] The fourth layer consists of N combined control execution units, i.e., storage entry points.
[0190] Thus, by using the above method, the metadata of all operation and maintenance objects of the platform and application, as well as the metadata of their characteristic data and the relationships between these objects, are stored, thereby realizing the storage model of full data metadata of AIOPS for the first time.
[0191] In this application: 1. A three-step implementation method for modular storage of AIOPS operation and maintenance metadata based on system architecture demonstration: Step 1: Forming a set of operation and maintenance object metadata and its relationships based on platform architecture and application architecture; Step 2: Forming a set of AI algorithm basic data and its relationships based on the operation and maintenance object data architecture; Step 3: Generating a set of automated operation and maintenance class metadata and its relationships. 2. A method for designing a hierarchical storage model for operation and maintenance metadata based on application metadata decomposition and reorganization, constructing relationships between tool metadata based on tool integration methods, and classifying and traversing application metadata based on the set of operation and maintenance object entities. This model forms a multi-layered storage model according to four levels: human cognition, concrete classification, software cognition, and software execution, and implements modular storage of operation and maintenance object metadata according to the formed multi-layered storage model.
[0192] This application proposes a modular storage implementation method for AIOPS operation and maintenance metadata based on system architecture demonstration. It constructs a metadata set of operation and maintenance objects and the relationships between their elements through platform architecture and application architecture. Combining this with the application metadata characteristics of AIOPS itself, a four-layer storage model is formed through classification and traversal. Furthermore, it constructs a basic data set for AI algorithms and its relationships based on the data architecture of the operation and maintenance objects, aiming to efficiently achieve automated and intelligent storage management of operation and maintenance metadata. This application provides a method for classifying and traversing metadata objects and constructing relationships based on the basic object platform, business and data architecture, and application metadata characteristics, making it more universal. Furthermore, the method provided in this application not only exhaustively enumerates the relationships between stored objects and their elements but also provides a general method for automatically constructing these relationships, resulting in better efficiency and broader coverage. It is particularly suitable for the metadata storage model design of general systems, especially for complex systems implemented through architecture updates, where the system has a complex architecture, often using multiple platform architectures in combination, and the application and data architectures are also relatively complex.
[0193] Furthermore, this embodiment of the invention also provides a storage device for AIOPS operation and maintenance metadata, wherein the operation and maintenance metadata includes operation and maintenance object metadata, AI algorithm basic metadata, and operation and maintenance class metadata. The storage device for AIOPS operation and maintenance metadata includes:
[0194] The first storage module is used to generate and store the collection and association relationships of the metadata of the operation and maintenance objects based on the platform architecture and application architecture of the automated operation and maintenance scenario.
[0195] The second storage module is used to generate and store a set of basic metadata and related relationships of the AI algorithm based on the data architecture of the operation and maintenance object;
[0196] The third storage module is used to generate and store the collection and association relationships of the metadata of the operation and maintenance classes based on the platform architecture and application architecture of the automated operation and maintenance scenario.
[0197] For example, the platform architecture is a tool integration approach, the application architecture is a collection of tools used in the business process, and the operation and maintenance object metadata includes IaaS operation and maintenance object metadata, PaaS operation and maintenance object metadata, PaaS tool collection metadata, and SaaS operation and maintenance object metadata; the first storage module is further used for:
[0198] Based on the configuration management database corresponding to the system network architecture, obtain the IaaS operation and maintenance object metadata, PaaS operation and maintenance object metadata, and PaaS tool set metadata corresponding to the tool integration method.
[0199] Based on the abstract decomposition and reorganization of the metadata of the operation and maintenance application, the metadata of the SaaS operation and maintenance objects corresponding to the set of tools used in the business process is obtained.
[0200] For example, the first storage module is further configured to:
[0201] The functional characteristics of each processing unit in the processing unit link of the business process and the matrix characteristics of each data unit in the data unit link of the business process are combined to obtain a general application link.
[0202] Based on the application metadata decomposition and reorganization method abstracted in the process of data unit dimension transformation, the operation and maintenance application metadata corresponding to the general application link is decomposed and reorganized to obtain the SaaS operation and maintenance object metadata corresponding to the tool set used in the business process.
[0203] For example, the data architecture is a method for associating and managing data during business processes, and the second storage module is further used for:
[0204] The full set of operation and maintenance feature units corresponding to the data architecture is deduplicated to generate a collection of operation and maintenance object feature units; wherein, the operation and maintenance feature units are feature units corresponding to the operation and maintenance object feature data that are associated and related in the business process;
[0205] Associate the relationships between operation and maintenance objects and object units to generate a set of object units for operation and maintenance objects;
[0206] The data architecture based on operation and maintenance objects adds object unit associations to the object unit set, and generates and stores the set of basic metadata of the AI algorithm and its associations.
[0207] For example, the platform architecture is a tool integration approach, and the application architecture is a collection of tools used in the business process; the third storage module is also used for:
[0208] By abstracting, decomposing, and reorganizing the metadata of the operation and maintenance applications corresponding to the set of tools used in the business process, tool metadata is obtained.
[0209] Based on the tool integration method, the association relationship between the tool metadata is constructed, and the operation and maintenance class metadata is obtained.
[0210] For example, the third storage module is further configured to:
[0211] After the step of constructing the interrelationships between the tool metadata based on the tool integration method and obtaining the operation and maintenance class metadata,
[0212] Determine the smallest repeating unit for constructing the interrelationships between the tool metadata based on the tool integration method;
[0213] Using the smallest repeating unit as the basic unit metadata object, traverse the basic unit metadata object to generate a complete set of relationships for the operation and maintenance class metadata.
[0214] For example, the third storage module is further configured to:
[0215] By describing the cognitive attributes of the operation and maintenance application metadata, classifying the concrete types of metadata units, exhaustively arranging the metadata entities at the application execution cognitive level, and describing the entities at the entity execution level, a complete set of relationships for the operation and maintenance operation class metadata is obtained.
[0216] The AIOPS operation and maintenance metadata storage device provided by this invention adopts the AIOPS operation and maintenance metadata storage method in the above embodiments, solving the technical problem of difficulty in efficiently storing and managing intelligent operation and maintenance metadata. Compared with the prior art, the beneficial effects of the AIOPS operation and maintenance metadata storage device provided by this invention are the same as the beneficial effects of the AIOPS operation and maintenance metadata storage method provided in the above embodiments, and other technical features in this AIOPS operation and maintenance metadata storage device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.
[0217] Furthermore, this invention also proposes a storage device for AIOPS operation and maintenance metadata. The storage device for AIOPS operation and maintenance metadata includes: a memory, a processor, and a computer program stored on the memory and executable on the processor. When the computer program is executed by the processor, it implements the steps of the above-described embodiments of the operation response method for the storage device of AIOPS operation and maintenance metadata.
[0218] Furthermore, this embodiment of the invention also proposes a readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the above-described embodiments of the storage device operation response method for AIOPS operation and maintenance metadata.
[0219] The extended content of the specific implementation of the storage device and readable storage medium for AIOPS operation and maintenance metadata of the present invention is basically the same as the various embodiments of the above-mentioned AIOPS operation and maintenance metadata storage device operation response method, and will not be repeated here.
[0220] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system 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 system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.
[0221] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0222] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.
[0223] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.
Claims
1. A method for storing AIOPS operation and maintenance metadata, characterized in that, The operation and maintenance metadata includes operation and maintenance object metadata, AI algorithm basic metadata, and operation and maintenance operation class metadata. The method includes: Based on the platform architecture and application architecture of the automated operation and maintenance scenario, a collection of metadata and related relationships of the operation and maintenance objects are generated and stored. Based on the data architecture of the operation and maintenance objects, a collection of basic metadata and their relationships for the AI algorithm are generated and stored; Based on the platform architecture and application architecture of the automated operation and maintenance scenario, a collection of metadata and related relationships of the operation and maintenance operation classes are generated and stored. The platform architecture is a tool integration approach, the application architecture is a collection of tools used in the business process, and the operation and maintenance object metadata includes IaaS operation and maintenance object metadata, PaaS operation and maintenance object metadata, PaaS tool set metadata, and SaaS operation and maintenance object metadata. The steps of generating and storing the collection and association relationships of metadata for the operation and maintenance objects in the platform architecture and application architecture based on the automated operation and maintenance scenario include: Based on the configuration management database corresponding to the system network architecture, obtain the IaaS operation and maintenance object metadata, PaaS operation and maintenance object metadata, and PaaS tool set metadata corresponding to the tool integration method. Based on the abstract decomposition and reorganization of the metadata of the operation and maintenance application, obtain the SaaS operation and maintenance object metadata corresponding to the set of tools used in the business process; The data architecture refers to the method of data association and management during business processes. The steps of generating and storing the set of basic metadata and related relationships of the AI algorithm based on the data architecture of the operation and maintenance object include: The full set of operation and maintenance feature units corresponding to the data architecture is deduplicated to generate a collection of operation and maintenance object feature units; wherein, the operation and maintenance feature units are feature units corresponding to the operation and maintenance object feature data that are associated and related in the business process; Associate the relationships between operation and maintenance objects and object units to generate a set of object units for operation and maintenance objects; The data architecture based on operation and maintenance objects adds object unit associations to the object unit set, and generates and stores the set and associations of the basic metadata of the AI algorithm. The platform architecture is a tool integration approach, and the application architecture is a collection of tools used in the business process; The steps of generating and storing the set of metadata and their relationships for the operation and maintenance classes in the platform architecture and application architecture based on the automated operation and maintenance scenario include: By abstracting, decomposing, and reorganizing the metadata of the operation and maintenance applications corresponding to the set of tools used in the business process, tool metadata is obtained. Based on the tool integration method, the association relationship between the tool metadata is constructed, and the operation and maintenance class metadata is obtained.
2. The method for storing AIOPS operation and maintenance metadata as described in claim 1, characterized in that, The steps for obtaining SaaS operation and maintenance object metadata corresponding to the set of tools used in the business process by abstracting, decomposing, and reorganizing the metadata of operation and maintenance applications include: The functional characteristics of each processing unit in the processing unit link of the business process and the matrix characteristics of each data unit in the data unit link of the business process are combined to obtain a general application link. Based on the application metadata decomposition and reorganization method abstracted in the process of data unit dimension transformation, the operation and maintenance application metadata corresponding to the general application link is decomposed and reorganized to obtain the SaaS operation and maintenance object metadata corresponding to the tool set used in the business process.
3. The method for storing AIOPS operation and maintenance metadata as described in claim 1, characterized in that, After the step of constructing the association relationship between the tool metadata based on the tool integration method and obtaining the operation and maintenance class metadata, the following steps are included: Determine the smallest repeating unit for constructing the interrelationships between the tool metadata based on the tool integration method; Using the smallest repeating unit as the basic unit metadata object, traverse the basic unit metadata object to generate a complete set of relationships for the operation and maintenance class metadata.
4. The method for storing AIOPS operation and maintenance metadata as described in claim 3, characterized in that, The step of traversing the basic unit metadata object to generate a complete set of relationships for the operation and maintenance class metadata includes: By describing the cognitive attributes of the operation and maintenance application metadata, classifying the concrete types of metadata units, exhaustively arranging the metadata entities at the application execution cognitive level, and describing the entities at the entity execution level, a complete set of relationships for the operation and maintenance operation class metadata is obtained.
5. A storage device for AIOPS operation and maintenance metadata, characterized in that, The operation and maintenance metadata includes operation and maintenance object metadata, AI algorithm basic metadata, and operation and maintenance operation class metadata. The storage device for the AIOPS operation and maintenance metadata implements the steps of the storage method for AIOPS operation and maintenance metadata as described in any one of claims 1 to 4, including: The first storage module is used to generate and store the collection and association relationships of the metadata of the operation and maintenance objects based on the platform architecture and application architecture of the automated operation and maintenance scenario. The second storage module is used to generate and store a set of basic metadata and related relationships of the AI algorithm based on the data architecture of the operation and maintenance object; The third storage module is used to generate and store the collection and association relationships of the metadata of the operation and maintenance classes based on the platform architecture and application architecture of the automated operation and maintenance scenario.
6. A storage device for AIOPS operation and maintenance metadata, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the method for storing AIOPS operation and maintenance metadata as described in any one of claims 1 to 4.
7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method for storing AIOPS operation and maintenance metadata as described in any one of claims 1 to 4.
Citation Information
Patent Citations
Operation and maintenance data management method and device, electronic equipment and storage medium
CN111651508A
Centralized service development method and equipment based on structured object
CN112925771A
