Operation and maintenance data processing method and device and electronic equipment

Abstract

The application discloses an operation and maintenance data processing method and device and electronic equipment. The method comprises the following steps: obtaining operation and maintenance data of a target data source, wherein the operation and maintenance data comprises object information, relationship information and running data of an operation and maintenance object; constructing an operation and maintenance object relationship network based on the object information and the relationship information of the operation and maintenance object, wherein the operation and maintenance object relationship network is used for displaying multiple operation and maintenance relationships of the operation and maintenance object; creating a visual view based on the operation and maintenance object relationship network to display the object information, the relationship information and the running data of the operation and maintenance object under different performance dimensions, wherein the visual view is used for displaying a physical deployment diagram and a key link diagram of the operation and maintenance object. The application solves the technical problem that the operation and maintenance object, the operation and maintenance relationship and the running data of the operation and maintenance object cannot be uniformly integrated, so that the running state of the operation and maintenance object cannot be clearly and conveniently displayed.

Description

Technical Field

[0001] This application relates to the field of data management technology, and more specifically, to a method, apparatus, and electronic device for processing operation and maintenance data. Background Technology

[0002] Currently, data center management involves a wide variety of operational objects, including infrastructure such as server rooms, systems, and networks, as well as various software, application systems, batch tasks, and other services running on these infrastructures. These operational objects also exhibit highly complex relationships. Since some of these operational objects and relationships are scattered across various operational tools (system operations, network operations, application operations, etc.) and others are present in the manual ledgers of administrators in different departments, administrators can manually draw physical deployment diagrams of these operational objects and relationships using drawing tools.

[0003] However, since the physical deployment map cannot be associated with IT resource supply, batch dependencies, and service access call chains, it is impossible to explore the IT resource supply used by the application system, batch execution efficiency, and business request response performance. Consequently, in daily production and maintenance, it is not possible to meet the demand for quickly, intuitively, and comprehensively displaying the operation status of maintenance objects associated with fault nodes in data center fault handling scenarios.

[0004] There is currently no effective solution to the above problems. Summary of the Invention

[0005] This application provides a method, apparatus, and electronic device for processing operation and maintenance data, which at least solves the technical problem that the operation status of operation and maintenance objects cannot be clearly and conveniently displayed because related technologies do not uniformly integrate operation and maintenance objects, operation and maintenance relationships, and operation data of operation and maintenance objects.

[0006] According to one aspect of the embodiments of this application, a method for processing operation and maintenance data is provided, comprising: acquiring operation and maintenance data from a target data source, wherein the operation and maintenance data includes: object information, relationship information, and runtime data of operation and maintenance objects; constructing an operation and maintenance object relationship network based on the object information and relationship information of the operation and maintenance objects, wherein the operation and maintenance object relationship network is used to display multiple types of operation and maintenance relationships of the operation and maintenance objects; and creating a visualization view based on the operation and maintenance object relationship network to display the object information, relationship information, and runtime data of the operation and maintenance objects under different performance dimensions, wherein the visualization view is used to display the physical deployment diagram and various key link diagrams of the operation and maintenance objects, and the key link diagrams include at least one of the following: batch dependency link, resource supply link, and service access call link.

[0007] Specifically, an operation and maintenance object relationship network is constructed by using the object information and relationship information of the operation and maintenance objects. A visual view for displaying operational data is created through the operation and maintenance object relationship network. This integrates the dependency relationships of batch jobs, the relationship between batches and IT assets, the calling relationships of application services, and the relationship between application services and IT assets on the basis of the original IT asset objects. This achieves unified integration of the object information and operational data of operation and maintenance objects, which solves the technical problem that related technologies only integrate and manage IT asset-type operation and maintenance objects, but do not unify the integration of the object information and operational data of operation and maintenance objects, thus failing to efficiently and clearly display the operational status of operation and maintenance objects.

[0008] Optionally, the target data source includes a first target data source and a second target data source. Acquiring the operation and maintenance data of the target data source includes: acquiring object information and relationship information of the operation and maintenance object from the first target data source, wherein the first target data source is used to record various computer resources; and acquiring the operation data of the operation and maintenance object from the second target data source, wherein the second target data source is used to record the operation data of the operation and maintenance object in different performance dimensions.

[0009] Optionally, constructing an operation and maintenance object relationship network based on the object information and relationship information of the operation and maintenance objects includes: storing the object information of each type of operation and maintenance object into a corresponding dataset according to the object type of the operation and maintenance object, to obtain at least one first dataset; storing the relationship information of each type of operation and maintenance object into a corresponding dataset according to the relationship type of the operation and maintenance object, to obtain at least one second dataset; and constructing an operation and maintenance object relationship network based on at least one first dataset and at least one second dataset.

[0010] Optionally, a visualization view is created based on the relationship network of operation and maintenance objects to display the object information, relationship information, and operational data of the operation and maintenance objects under different performance dimensions. This includes: determining the target operation and maintenance object in response to the selection operation and maintenance object in the visualization view; and displaying the target physical deployment diagram and each target key link of the target operation and maintenance object through the visualization view. The target object information, target relationship information, and target operational data of the target operation and maintenance object under different performance dimensions are displayed through the target physical deployment diagram and each target key link.

[0011] The system displays the deployment status of selected target operation and maintenance objects in a visual view, making it easy to intuitively view the target object information, target relationship information, and target operation data. At the same time, the target physical deployment map can be drilled down to display various key links of the target operation and maintenance objects, enabling the association of the physical deployment map and the object information and relationship information of the operation and maintenance objects displayed in the physical deployment map with IT resource supply links, batch dependency links, and service access call links. This allows for the exploration of the relationship between the IT resources used by the operation and maintenance objects and batch execution efficiency, business request response performance, and other factors.

[0012] Optionally, after creating a visual view based on the operation and maintenance object relationship network, the method further includes: in response to the editing operation of the visual view, recording the editing information during the editing process, and storing the editing information as an operation and maintenance data in the target database, wherein the target database is used to store the first dataset and the second dataset.

[0013] By editing the visualization view, users can display the node information that they are most concerned about, while hiding the less important node information, thus highlighting the maintenance objects that users care about.

[0014] Optionally, after obtaining the operation and maintenance data of the target data source, the method further includes: encoding and converting the object information and relationship information of the operation and maintenance object to obtain the target code of the operation and maintenance object, wherein the target code includes: operation and maintenance object code and operation and maintenance relationship code.

[0015] Specifically, by encoding the object information and relationship information of the operation and maintenance objects, it is possible to quickly retrieve the operation and maintenance objects when there are a large number of operation and maintenance objects and a variety of operation and maintenance scenarios. At the same time, the object information and relationship information of the operation and maintenance objects can be quickly displayed in the visualization view corresponding to various operation and maintenance scenarios through target encoding.

[0016] Optionally, the object information and relationship information of the operation and maintenance object are encoded and converted to obtain the target code, including: determining the technical attributes and operation and maintenance scenarios of the operation and maintenance object, and determining the operation and maintenance object code based on the technical attributes and operation and maintenance scenarios, wherein the operation and maintenance object code includes: a main code for reflecting the technical attributes of the operation and maintenance object, and an auxiliary code for determining the operation and maintenance scenarios referenced by the operation and maintenance object; determining the business attributes and relationship number of the operation and maintenance relationship, and determining the operation and maintenance relationship code based on the business attributes and relationship number; and obtaining the target code based on the operation and maintenance object code and the operation and maintenance relationship code.

[0017] Optionally, the technical attributes include: object type and business characteristics. The process of determining the operation and maintenance object code based on the technical attributes and the operation and maintenance scenario includes: encoding the object type data according to a preset first encoding rule to obtain the object type code, and encoding the business characteristics according to a preset second encoding rule to obtain the business characteristic code; determining the main code based on the object type code and the business characteristic code; determining the auxiliary code based on the operation and maintenance scenario; and obtaining the operation and maintenance object code based on the main code and the auxiliary code.

[0018] Optionally, the auxiliary coding includes: operation and maintenance scenario coding, operation and maintenance scenario layer coding, and operation and maintenance scenario sequence number. Determining the auxiliary coding based on the operation and maintenance scenario includes: determining the operation and maintenance scenario referenced by the operation and maintenance object, and coding the operation and maintenance scenario according to a preset third coding rule to obtain the operation and maintenance scenario coding; determining the operation and maintenance scenario layer referenced by the operation and maintenance object, and coding the operation and maintenance scenario layer according to a preset fourth coding rule to obtain the operation and maintenance scenario layer coding; determining the operation and maintenance scenario sequence number referenced by the operation and maintenance object; and obtaining the auxiliary coding based on the operation and maintenance scenario coding, operation and maintenance scenario layer coding, and operation and maintenance scenario sequence number.

[0019] Optionally, the business attributes include: relationship type and relationship constraints. The determination of the operation and maintenance relationship code based on the business attributes and relationship sequence number includes: encoding the relationship type according to a preset fifth encoding rule to obtain a relationship type code, wherein the relationship type includes at least one of the following: cluster relationship, composition relationship, connection relationship, call relationship, installation relationship, and dependency relationship; determining the relationship constraint code based on the object type code of the operation and maintenance objects connected in the operation and maintenance relationship; and determining the operation and maintenance relationship code based on the relationship type code, the relationship constraint code, and the relationship sequence number.

[0020] According to another aspect of the embodiments of this application, an operation and maintenance data processing apparatus is also provided, comprising: an acquisition module, configured to acquire operation and maintenance data from a target data source, wherein the operation and maintenance data includes: object information, relationship information, and runtime data of operation and maintenance objects; a construction module, configured to construct an operation and maintenance object relationship network based on the object information and relationship information of the operation and maintenance objects, wherein the operation and maintenance object relationship network is used to display multiple types of operation and maintenance relationships of the operation and maintenance objects; and a display module, configured to create a visualization view based on the operation and maintenance object relationship network to display the object information, relationship information, and runtime data of the operation and maintenance objects under different performance dimensions, wherein the visualization view is used to display the physical deployment diagram and various key link diagrams of the operation and maintenance objects, and the key link diagrams include at least one of the following: batch dependency link, resource supply link, and service access call link.

[0021] According to another aspect of the embodiments of this application, an electronic device is also provided, the electronic device including: a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the above-described method for processing operation and maintenance data through the computer program.

[0022] In this embodiment, operational data from the target data source is acquired. This operational data includes object information, relationship information, and runtime data of the operational objects. An operational object relationship network is constructed based on the object and relationship information of the operational objects. This network displays various operational relationships of the operational objects. A visualization view is created based on the operational object relationship network to display the object information, relationship information, and runtime data of the operational objects under different performance dimensions. This visualization view displays the physical deployment diagram and key link diagrams of the operational objects. The key link diagrams include at least one of the following: batch dependency link, resource supply link, and service access call link. This provides a one-stop operational data service for scenarios such as fault emergency response in a visual and efficient manner, truly serving as a "battle map." It allows relevant parties involved in operational fault emergency response to have concrete information during discussions and communication, clearly defining the objects and scope of the emergency response. This makes communication in operational emergency response more efficient, thus solving the technical problem that related technologies do not uniformly integrate operational objects, operational relationships, and the runtime data of operational objects, making it impossible to clearly and conveniently display the operational status of operational objects. Attached Figure Description

[0023] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0024] Figure 1 This is a flowchart of an optional method for processing operation and maintenance data according to an embodiment of this application;

[0025] Figure 2 This is a schematic diagram of an optional application system wall according to an embodiment of this application;

[0026] Figure 3 This is a schematic diagram of another optional application system wall according to an embodiment of this application.

[0027] Figure 4 This is a schematic diagram of another optional application system wall according to an embodiment of this application;

[0028] Figure 5 This is a schematic diagram of an optional operation and maintenance object relationship network according to an embodiment of this application;

[0029] Figure 6This is a flowchart of an optional method for determining the target code according to an embodiment of this application;

[0030] Figure 7 This is a schematic diagram of link navigation in an optional application system according to an embodiment of this application;

[0031] Figure 8 This is a schematic diagram of an optional target physical deployment diagram according to an embodiment of this application;

[0032] Figure 9 This is a schematic diagram of an optional IT resource supply chain according to an embodiment of this application;

[0033] Figure 10a This is a schematic diagram of an optional batch dependency link diagram according to an embodiment of this application;

[0034] Figure 10b This is a schematic diagram of another optional batch dependency link diagram in an embodiment of this application;

[0035] Figure 11 This is a schematic diagram of another optional physical deployment diagram according to an embodiment of this application;

[0036] Figure 12 This is a schematic diagram of an optional operation and maintenance data processing device according to an embodiment of this application. Detailed Implementation

[0037] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0038] It should be noted that the terms "first," "second," etc., used in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0039] To better understand the embodiments of this application, the following is a translation and explanation of some nouns or terms that appear in the description of the embodiments of this application:

[0040] Operation and maintenance objects refer to various IT resources that are operated and managed by the data center to support business operations. These include computer rooms, hardware facilities, network lines, basic software, virtual machines, containers, application systems, batch tasks, and application services. Operation and maintenance objects are the objects of the data center's work.

[0041] Deployment Diagram: Used to display the physical architecture of software and hardware in a system. From the deployment diagram, one can understand the physical relationships between software and hardware components, as well as the component distribution of processing nodes. Using a deployment diagram, one can show the structure of the runtime system, while also conveying the configuration and deployment of the application's hardware and software elements.

[0042] Example 1

[0043] According to an embodiment of this application, a method for processing operation and maintenance data is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0044] Figure 1 This is a flowchart of an optional method for processing operation and maintenance data according to an embodiment of this application, such as... Figure 1 As shown, the method includes at least steps S102-S106, wherein:

[0045] Step S102: Obtain the operation and maintenance data of the target data source, wherein the operation and maintenance data includes: object information, relationship information and running data of the operation and maintenance object.

[0046] In the technical solution provided by step S102 of the present invention, the target data source can be understood as a data source for obtaining operation and maintenance data. The operation and maintenance objects and relationships can be directly obtained from the data center. The object information of the operation and maintenance objects includes, but is not limited to, the object type of the operation and maintenance object and the applied operation and maintenance scenario; while the relationship information of the operation and maintenance objects includes, but is not limited to, business attributes such as relationship type and relationship constraints, and relationship sequence number.

[0047] The operational data of the maintenance objects can be divided into the following aspects: First, the management process information required for managing the maintenance objects, such as change management processes and event management processes; second, the operational status of the maintenance objects, such as performance data collected by various monitoring tool platforms; and third, data such as alarms, operational risks, and high-risk user operations for each monitored object. Since these data are distributed across different data tool systems, the data source for the operational data of the maintenance objects is these tool systems. Furthermore, the operational data of the maintenance objects can be categorized according to different performance dimensions, such as change data, performance data, event data, alarm data, high-risk operation data, and operational risk data.

[0048] Step S104: Construct an operation and maintenance object relationship network based on the object information and relationship information of the operation and maintenance object. The operation and maintenance object relationship network is used to display the various operation and maintenance relationships of the operation and maintenance object.

[0049] In the technical solution provided by step S104 of the present invention, the object information and relationship information of the operation and maintenance object are integrated to form a three-dimensional, multi-level, complex operation and maintenance object relationship network, and the network contains multiple types of operation and maintenance relationships related to the operation and maintenance object.

[0050] Step S106: Create a visualization view based on the operation and maintenance object relationship network to display the object information, relationship information, and runtime data of the operation and maintenance objects under different performance dimensions. The visualization view displays the physical deployment diagram and various key link diagrams of the operation and maintenance objects. The key link diagrams include at least one of the following: batch dependency link, resource provisioning link, and service access call link.

[0051] In the technical solution provided in step S106 of the present invention, since the operation and maintenance object relationship network contains the object information and relationship information of the operation and maintenance object, the visualization view created based on the operation and maintenance object relationship network can intuitively display the object information, relationship information and operation data of the operation and maintenance object under different performance dimensions by displaying the physical deployment diagram of the operation and maintenance object and each key link. Thus, through an innovative visualization method, the operation and maintenance object and its relationship with the IT resource supply link, batch dependency link and service access call link are intuitively displayed, thereby realizing a 1:1 mapping between the physical existence and digital twin of the operation and maintenance object, which makes it easier for technicians to explore the relationship between the IT resources used by the operation and maintenance object and the batch execution efficiency, business request response performance and so on.

[0052] As an optional implementation, the scenario category of the operation and maintenance scenario referenced by the operation and maintenance object can also be determined; the visualization view can be segmented according to the scenario category to obtain at least one visualization subview, wherein the visualization subview is used to display the operation data of the operation and maintenance object under each type of operation and maintenance scenario.

[0053] In this embodiment, in order to facilitate the management of a large number of operation and maintenance objects, the visualization view can be segmented according to the scenario category of the operation and maintenance scenario of the operation and maintenance object to obtain the operation data under the operation and maintenance scenario corresponding to each scenario category, thereby realizing efficient management of operation and maintenance data.

[0054] Since application systems are critical operational objects, a clear and intuitive display of these systems and the relationships between them is essential for the maintenance and management of bank data centers. In this embodiment, the operational data of the target data source is preferably displayed using an application system wall. The following section will use an application system wall as an example to explain the visualization method in detail.

[0055] Specifically, Figure 2 This is a schematic diagram of an optional application system wall according to an embodiment of this application, such as... Figure 2 As shown, each application wall in this application system wall includes one type of application (i.e., applications of the same object type are in one wall). Therefore, when a user logs into the homepage of the application system wall, they can click on a specific application wall to display all applications of that same type.

[0056] Furthermore, Figure 3 This is a schematic diagram of another optional application system wall according to an embodiment of this application, such as... Figure 3 As shown, the alarm information of the application system (i.e., relevant information of the running data) can be displayed intuitively through the application wall. Different levels of alarm information can be identified by different colors.

[0057] For example, Figure 3 In the CXX category, the application systems in the fourth row, second column, and the application systems in the sixth row, ninth column are dark gray and marked with an equilateral triangle symbol, indicating that they contain the highest level of alarm information.

[0058] In addition, Figure 3 The leftmost side displays six categories: AXX, BXX, CXX, DXX, and EXX. Users can switch between different application display options by clicking on the leftmost tags.

[0059] For example, if the app wall currently displays apps categorized as CXX, clicking on a tag for category AXX will switch the display to the app wall for category AXX. Similarly, when a user clicks on an app on a specific app wall within the app system, other related apps will be displayed, thus visually demonstrating the relationships between apps.

[0060] Figure 4 This is a schematic diagram of another optional application system wall according to an embodiment of this application, such as... Figure 4 As shown, clicking on application system A in category CXX displays other application systems in category AXX that have service call relationships with application system A, and application systems in category BXX that have batch dependencies on application system A. Simultaneously, the application system wall interface displays detailed records such as application system change logs, fault events, and historical alarms, allowing users to easily view them. Change logs can record the following: work order number, change window, change category, change content, change status, and change start and end times; fault events can record the following: event type, event content, event location, fault handling result, and fault handling start and end times; historical alarms can record the following: work order number, alarm type, alarm event, alarm content, alarm handling result, and alarm handling start and end times.

[0061] In the embodiments of steps S102-S106 of this application, operation and maintenance data of the target data source is obtained. This operation and maintenance data includes: object information, relationship information, and operational data of the operation and maintenance objects. An operation and maintenance object relationship network is constructed based on the object information and relationship information of the operation and maintenance objects. This network is used to display various types of operation and maintenance relationships of the operation and maintenance objects. A visualization view is created based on the operation and maintenance object relationship network to display the object information, relationship information, and operational data of the operation and maintenance objects under different performance dimensions. This visualization view is used to display the physical deployment diagram and various key link diagrams of the operation and maintenance objects. The key link diagrams include at least one of the following: batch dependency link, resource supply link, and service access call link. This provides a one-stop operation and maintenance data service for scenarios such as fault emergency response in an intuitive and efficient manner through visualization, truly serving as a "battle map" and enabling relevant parties participating in operation and maintenance fault emergency response to have meaningful discussions and communications, clearly defining the objects and scope of the fault emergency response. This makes communication for operations and maintenance emergencies more efficient, thereby solving the technical problem that the operational status of operations and maintenance objects cannot be clearly and conveniently displayed because the relevant technologies have not unified and integrated the operations and maintenance objects, operations and maintenance relationships, and the operational data of the operations and maintenance objects.

[0062] The method described in this embodiment will be further described below.

[0063] As an optional implementation, in the technical solution provided in step S102 of the present invention, the target data source includes a first target data source and a second target data source. The method may include: obtaining object information and relationship information of the operation and maintenance object from the first target data source, wherein the first target data source is used to record various computer resources; and obtaining the operation data of the operation and maintenance object from the second target data source, wherein the second target data source is used to record the operation data of the operation and maintenance object in different performance dimensions.

[0064] Specifically, the operation and maintenance objects include IT resources from data centers, and therefore, the operation and maintenance objects include, but are not limited to: data center infrastructure, IT equipment, logical devices, operating systems, software programs, program services, and batches. Among them, data center infrastructure includes, but is not limited to: data centers, server racks, power supply, and fire protection; IT equipment includes, but is not limited to: network devices such as network firewalls and switches, system devices such as servers and storage, or network security devices such as encryption machines and security gateways; logical devices include, but are not limited to: logical devices based on various virtualization platforms and cloud platforms, such as logical server partitions based on virtualization platforms and containers based on cloud platforms; software programs include, but are not limited to: basic software such as middleware and databases, or commercially purchased or self-developed application software; program services and batches include, but are not limited to: interface services and batch jobs provided by commercially purchased or self-developed application software. Operation and maintenance relationships are used to represent the associations between various operation and maintenance objects, and these associations include, but are not limited to: cluster relationships, composition relationships, connection relationships, calling relationships, installation relationships, and dependency relationships.

[0065] In addition, the operational data of the maintenance objects includes, but is not limited to: change data, time data, operational risk data, high-risk operation data, performance data, and alarm data. Furthermore, the sources of operational data for different performance dimensions are not the same. Therefore, various types of operational data can be obtained from different source platforms. For example, change data can be obtained from ITSM (IT Service Management) platforms and change automation platform tools; event data can be obtained from the ITSM platform; operational risk data can be obtained from the operational risk management platform; high-risk operation data can be obtained from bastion host operation records and personalized change tool operation records; performance data can be obtained from monitoring tool platforms across various departments; and alarm data can be obtained from centralized alarm management platforms, etc.

[0066] As an optional implementation, in the technical solution provided in step S104 of the present invention, the method may include: storing the object information of various types of operation and maintenance objects into corresponding datasets according to the object type of the operation and maintenance objects, to obtain at least one first dataset; storing the relationship information of various types of operation and maintenance objects into corresponding datasets according to the relationship type of the operation and maintenance objects, to obtain at least one second dataset; and constructing an operation and maintenance object relationship network based on at least one first dataset and at least one second dataset.

[0067] In this embodiment, since the operation and maintenance objects include various types, to avoid confusion of object information for different types of operation and maintenance objects, the acquired object information can be classified according to the object type of the operation and maintenance object, and the object information for each type of operation and maintenance object can be stored in a corresponding first dataset. Alternatively, it can be understood that the object information for each object type can be stored in a corresponding operation and maintenance object data model. Similarly, the acquired relationship information of the operation and maintenance objects is also classified according to the relationship type of the operation and maintenance objects, and the relationship information for each type of operation and maintenance object can be stored in a corresponding second dataset. Alternatively, it can be understood that the relationship information for each relationship type can be stored in a corresponding operation and maintenance relationship data model. Thus, an operation and maintenance object relationship network can be constructed based on the first dataset storing the object information of each type of operation and maintenance object and the second dataset storing the relationship information of each type of operation and maintenance object.

[0068] Specifically, Figure 5 This is a schematic diagram of an optional operation and maintenance object relationship network according to an embodiment of this application, such as... Figure 5 As shown, the operation and maintenance object relationship network includes a storage layer, a network device layer, an OS layer, and a service layer. Each layer contains multiple operation and maintenance objects (represented by small circles), and each operation and maintenance object contains multiple types of operation and maintenance relationships. The inter-layer relationships of operation and maintenance objects are identified by dashed lines, and the relationships between different layers of operation and maintenance objects are identified by solid lines.

[0069] In addition, considering the large amount of data and complex relationships of the object information and relationship information of the operation and maintenance objects, the relationship network of the operation and maintenance objects can be stored. At the same time, the relationship network of the operation and maintenance objects can also be stored in a relational database to facilitate subsequent application services such as data query.

[0070] Furthermore, since there are many types of operation and maintenance objects in practical applications, and the application scenarios of operation and maintenance objects are very rich, in order to facilitate and quickly retrieve operation and maintenance objects and operation and maintenance relationships during application, the operation and maintenance objects can be globally encoded according to the following rules.

[0071] As an optional implementation method, the object information and relationship information of the operation and maintenance object are encoded and converted to obtain the target code of the operation and maintenance object, wherein the target code includes: operation and maintenance object code and operation and maintenance relationship code.

[0072] The above-mentioned operation and maintenance object encoding can be understood as encoding the object information of the operation and maintenance object, and the operation and maintenance relationship encoding is encoding the relationship information of the operation and maintenance object.

[0073] Specifically, Figure 6 This is a flowchart of an optional method for determining the target encoding according to an embodiment of this application, such as... Figure 6As shown, the target code can be determined through steps S1-S3:

[0074] S1. Determine the technical attributes and operation and maintenance scenarios of the operation and maintenance object, and determine the operation and maintenance object code based on the technical attributes and operation and maintenance scenarios.

[0075] The operation and maintenance object coding includes: a main coding that reflects the technical attributes of the operation and maintenance object, and an auxiliary coding that determines the operation and maintenance scenario in which the operation and maintenance object is referenced.

[0076] S2, determine the business attributes and relationship sequence number of the operation and maintenance relationship, and determine the operation and maintenance relationship code based on the business attributes and relationship sequence number.

[0077] S3, the target code is obtained based on the operation and maintenance object code and the operation and maintenance relationship code.

[0078] In this embodiment, a primary code for uniquely identifying an O&M object is determined by its technical attributes, and an auxiliary code for quickly retrieving O&M objects involved in the application scenario is determined by matching the O&M object with the application scenario. Additionally, an O&M relationship code for uniquely locating various relationships within the relationship network is determined by the business attributes and relationship sequence number of the O&M relationship. The relationship sequence number can be represented as a 10-bit or 16-bit random code corresponding to the O&M relationship. The target code, composed of the O&M object code and the O&M relationship code, can be represented as a coordinate system for the O&M object.

[0079] As an optional implementation, in the technical solution provided in step S1 of the present invention, the technical attributes include: object type and business characteristics. The method may include: encoding object type data according to a preset first encoding rule to obtain an object type code; encoding business characteristics according to a preset second encoding rule to obtain a business characteristic code; determining a primary code based on the object type code and the business characteristic code; determining an auxiliary code based on the operation and maintenance scenario; and obtaining an operation and maintenance object code based on the primary code and the auxiliary code.

[0080] In this embodiment, the object types mentioned above include at least one of the following: data center, device, virtual machine, container, software, batch task, and interface service. The first encoding rule mentioned above may, but is not limited to, assigning a two-letter code to different object types of operation and maintenance objects to obtain an object type code for quick identification of the object type. For example, a data center may be encoded as JF, a device as SB, a virtual machine as XN, a container as RQ, software as RJ, a batch task as PC, and an interface service as JK, etc.

[0081] Business characteristic coding can be based on the business attributes of different object types. The second coding rule can be based on a uniformly recognized coding structure within the organization, allowing for customization in practical applications. For example, Guangzhou has two data centers, which can be coded as JF_GZ_001 and JF_GZ_002 respectively. Another example is a DB2 software installation instance of an application system (which can be coded as ABC), which can be coded as RJ_DB2_ABC_001.

[0082] Therefore, the object type code and business characteristic code obtained above together form the master code. When various operation and maintenance tools interact with data, the master code is used to quickly achieve the association and matching of operation and maintenance objects.

[0083] As another optional implementation, in the technical solution provided in step S1 of the present invention, the auxiliary encoding includes: operation and maintenance scenario encoding, operation and maintenance scenario layer encoding, and operation and maintenance scenario sequence number. The method may include: determining the operation and maintenance scenario referenced by the operation and maintenance object, and encoding the operation and maintenance scenario according to a preset third encoding rule to obtain the operation and maintenance scenario encoding; determining the operation and maintenance scenario layer referenced by the operation and maintenance object, and encoding the operation and maintenance scenario layer according to a preset fourth encoding rule to obtain the operation and maintenance scenario layer encoding; determining the operation and maintenance scenario sequence number referenced by the operation and maintenance object; and obtaining the auxiliary encoding based on the operation and maintenance scenario encoding, operation and maintenance scenario layer encoding, and operation and maintenance scenario sequence number.

[0084] In this embodiment, the auxiliary encoding is a multi-valued attribute used to represent the encoding for determining the matching operation and maintenance scenario of the operation and maintenance object. It is mainly used to quickly retrieve the operation and maintenance objects and relationships involved in the operation and maintenance scenario when providing services in a specific operation and maintenance scenario. Therefore, the auxiliary encoding includes: application scenario type encoding, operation and maintenance scenario sequence number, operation and maintenance scenario layer encoding, etc.

[0085] Specifically, application scenario type encoding is used to quickly identify in which scenarios an operational object is referenced. Therefore, different types of application scenarios can be encoded using a third encoding rule to obtain the type of operational scenario in which the operational object is applied. This third encoding rule can, but is not limited to, assigning a three-letter code to each application scenario type to obtain the application scenario type encoding for quick identification. For example, an application physical deployment graph scenario can be encoded as BST, a resource supply graph as GJT, a batch dependency graph as YLT, and a transaction access chain as FWL, etc.

[0086] When subsequently displaying operation and maintenance objects and relationships through a visual view, since different object types belong to different layers in different operation and maintenance scenarios, a fourth encoding rule is used to encode the operation and maintenance scenario layers. This allows for quick retrieval of the layer where the operation and maintenance object belongs within the application scenario using the operation and maintenance scenario layer code. This fourth encoding rule can, but is not limited to, assigning a three-letter code to the application scenario of different scenario layers to obtain an application scenario layer code for rapid identification. For example, the network device layer can be encoded as WLC, the system resource layer as XTC, the basic software layer as RJC, and the application layer as YYC, etc.

[0087] Additionally, the operation and maintenance scenario number is used to quickly retrieve all operation and maintenance objects under a specific scenario when access to an operation and maintenance object is required. For example, if an operation and maintenance object belongs to the deployment diagram of the ABC application system, its operation and maintenance scenario number might be ABC001.

[0088] Therefore, auxiliary coding is constructed by combining the operation and maintenance scenario code, the operation and maintenance scenario layer code, and the operation and maintenance scenario sequence number. For example, taking a network firewall in the network layer of the ABC deployment diagram as an example, its auxiliary coding can be written as BST_ABC001_WLC_001.

[0089] As an optional implementation, in the technical solution provided in step S2 of the present invention, the business attributes include: relationship type and relationship constraints. The method may include: encoding the relationship type according to a preset fifth encoding rule to obtain a relationship type encoding, wherein the relationship type includes at least one of the following: cluster relationship, composition relationship, connection relationship, call relationship, installation relationship, and dependency relationship; determining the relationship constraint encoding based on the object type encoding of the operation and maintenance objects connected in the operation and maintenance relationship; and determining the operation and maintenance relationship encoding based on the relationship type encoding, the relationship constraint encoding, and the relationship sequence number.

[0090] In the above embodiments, the relationship type is used to reflect the association between various operation and maintenance objects. Therefore, the relationship type can be encoded using the fifth encoding rule to obtain a relationship type code, thereby quickly identifying the association between operation and maintenance objects. The fifth encoding rule can, but is not limited to, assigning a three-letter code to different relationship types to obtain a relationship type code for rapid identification. For example, a call relationship can be encoded as DY, a dependency relationship as YL, and an installation relationship as AZ, etc.

[0091] Relationship constraints describe the object types of the operations and maintenance objects within the operation and maintenance relationship connection. Therefore, relationship constraints can be composed of the object type codes of each operation and maintenance object in the connection. For example, in a batch dependency relationship, the batch constraint code can be represented as PC-PC, while the constraint code in an OS installation relationship can be represented as OS-XN.

[0092] Therefore, the operation and maintenance relation code can be composed of relation type encoding, relation sequence number, and relation constraint encoding. For example, the relation code for DB2 software installed on a certain XN (virtual machine) can be AZ_DB2XN_001.

[0093] Optionally, after obtaining the target code of the operation and maintenance object, a first mapping relationship between the operation and maintenance object and the operation and maintenance object code can be established based on the technical attributes of the operation and maintenance object, and a second mapping relationship between the operation and maintenance relationship and the operation and maintenance relationship code can be established based on the business attributes of the operation and maintenance relationship.

[0094] The first mapping rule can be understood as an attribute of the operation and maintenance object in the operation and maintenance object data model. This allows the corresponding operation and maintenance object code to be obtained after each acquisition of the operation and maintenance object information, thus achieving the purpose of fast coding. Similarly, the second mapping rule can be understood as an attribute of the operation and maintenance relationship in the operation and maintenance relationship data model.

[0095] In addition, in order to quickly integrate the operational data of the operation and maintenance objects into the operation and maintenance object relationship network, mapping and transformation rules corresponding to the operational data of the operation and maintenance objects can be formulated based on the main code of the operation and maintenance objects, thereby realizing the unified integration of the operational data and object information of the operation and maintenance objects.

[0096] The above mapping and conversion rules can be understood as follows: if the operation information of the operation and maintenance object is encoded as A in the collected operation data of the operation and maintenance object, while the operation and maintenance objects in the operation and maintenance object relationship network are encoded as B, then the encoding A of the operation information of the operation and maintenance object can be mapped and converted into the encoding B of the operation and maintenance object through the established mapping and conversion rules, thereby realizing the integration of the operation data of the operation and maintenance object with the operation and maintenance object relationship network.

[0097] As an optional implementation, in the technical solution provided by step S106 of the present invention, the method may include: in response to the selection operation of the operation and maintenance object in the visualization view, determining the target operation and maintenance object; displaying the target physical deployment diagram and each target key link of the target operation and maintenance object through the visualization view, wherein the target physical deployment diagram and each target key link display the target object information, target relationship information and target operation data under different performance dimensions of the target operation and maintenance object.

[0098] In the embodiments of this application, it can be combined with Figure 4 For example, when a user is Figure 4 When an application chart in the CXX category is selected in the application system wall (i.e., the visualization view), navigation to the key link diagrams of that application system will be displayed on the interface, connecting to the application architecture, physical deployment diagram, batch link diagram, transaction link diagram, etc. of that application system. Figure 7 As shown.

[0099] Compared to existing technologies that can only manage IT asset-type operation and maintenance objects, the solution of this application embodiment can use an innovative visualization view to associate operation and maintenance objects and relationships in the physical deployment diagram with resource supply links, batch dependency links, and service access call links, thereby enabling the exploration of the relationship between the IT resources used by the application system and batch execution efficiency, business request response performance, etc.

[0100] Specifically, Figure 8 This is a schematic diagram of an optional target physical deployment diagram according to an embodiment of this application, such as... Figure 8 As shown, the target physical deployment diagram of the application system is used to visually demonstrate the deployment of the application system in the data center. It includes various IT resources directly used by the application system, their operational data, and the operational data of the application system's deployment program. When displaying the application system's system information, the overall display interface can be arranged according to... Figure 8 The left-center-right layout shown here (this is just an example and is not limited to this layout) displays basic information about the application system on the left, such as basic information about the application system, change information of the system application dimension, event information, high-risk operation information, and operational risk information; the middle is the display area of ​​the physical deployment diagram; and the right is the running information of a specific operation and maintenance object selected in the physical deployment diagram, such as the OS hostname, OS type, last restart time, allocated CPU and memory, and other performance or alarm information.

[0101] Based on the above target physical deployment diagram, you can drill down to display the IT resource supply chain of a selected entity, such as... Figure 9 As shown in the diagram, this link diagram displays the link relationships between server racks, physical servers, storage devices, ESXi, and Linux.

[0102] As another optional implementation, in the technical solution provided by step S106 of the present invention, the method may include: in response to the editing operation of the visual view, recording the editing information during the editing process, and storing the editing information as a maintenance data in the target database, wherein the target database is used to store the first dataset and the second dataset.

[0103] In this embodiment, in order to more intuitively display the information of the nodes of interest to the user on the link diagram, the link diagram can optionally be edited to hide some unimportant nodes.

[0104] For example, Figure 10a This is a schematic diagram of an optional batch dependency chain diagram according to an embodiment of this application. The batch dependency chain diagram involves 3 application systems and a total of 5 batch tasks. If a user only focuses on the start and end batches, the user can select the batch tasks to be hidden in the batch dependency chain, thus displaying only two key batch tasks, A and E, thereby obtaining... Figure 10b The batch dependency chain diagram is shown below. Additionally, users can also click... Figure 10b The circular icon in the image allows you to quickly expand hidden batch tasks, thus enabling you to view the dependency chain diagram of completed batches.

[0105] Additionally, relevant performance information can be integrated into the link graph. For example, it can be... Figure 10a The batch dependency chain diagram shown integrates the performance information of batch execution to obtain... Figure 11 The diagram shown illustrates the physical deployment, which allows for a visual exploration of batch dependency information for a specific application system.

[0106] In the above implementation, by encoding based on the technical attributes and application scenarios of the maintenance objects, and by encoding based on the business attributes and relationship numbers of the maintenance relationships, the resulting global encoding is made more readable. This enables efficient and rapid retrieval of maintenance objects when faced with a large number of maintenance objects and relationships. At the same time, through a visual display method that associates physical deployment diagrams and link diagrams, the relationship between batches and IT resources, the calling relationship of application services, and the relationship between application services and IT assets are intuitively displayed. This clearly and efficiently displays the operating status of maintenance objects, facilitating efficient and intuitive data access and query services in scenarios such as fault emergency response. It ensures that relevant parties involved in maintenance fault emergency response can communicate efficiently and quickly resolve emergency fault issues based on accurate and comprehensive maintenance data.

[0107] Example 2

[0108] According to an embodiment of this application, an apparatus for processing operation and maintenance data to implement the above-described method for processing operation and maintenance data is also provided. Figure 12 This is a schematic diagram of the structure of an optional operation and maintenance data processing device according to an embodiment of this application, as shown below. Figure 12 As shown, the data processing device for operation and maintenance includes at least an acquisition module 122, a construction module 124, and a display module 126, wherein:

[0109] The acquisition module 122 is used to acquire the operation and maintenance data of the target data source. The operation and maintenance data includes: object information, relationship information and running data of the operation and maintenance object.

[0110] Optionally, the target data source includes a first target data source and a second target data source. The acquisition module 122 is also used to acquire object information and relationship information of the operation and maintenance object from the first target data source, wherein the first target data source is used to record various computer resources; and to acquire the operation data of the operation and maintenance object from the second target data source, wherein the second target data source records the operation data of the operation and maintenance object in different performance dimensions.

[0111] Module 124 is used to construct an operation and maintenance object relationship network based on the object information and relationship information of the operation and maintenance object. The operation and maintenance object relationship network is used to display the various operation and maintenance relationships of the operation and maintenance object.

[0112] Optionally, the construction module 124 is further configured to store the object information of various operation and maintenance objects into corresponding datasets according to the object type of the operation and maintenance objects, to obtain at least one first dataset; store the relationship information of various operation and maintenance objects into corresponding datasets according to the relationship type of the operation and maintenance objects, to obtain at least one second dataset; and construct an operation and maintenance object relationship network based on at least one first dataset and at least one second dataset.

[0113] The display module 126 is used to create a visual view based on the relationship network of operation and maintenance objects to display the object information, relationship information and running data of operation and maintenance objects under different performance dimensions. The visual view is used to display the physical deployment diagram and various key link diagrams of the operation and maintenance objects. The key link diagrams include at least one of the following: batch dependency link, resource supply link, and service access call link.

[0114] Optionally, the display module 126 also responds to the selection operation of the operation and maintenance object in the visualization view to determine the target operation and maintenance object; and displays the target physical deployment diagram and each target key link of the target operation and maintenance object through the visualization view, wherein the target physical deployment diagram and each target key link display the target object information, target relationship information and target operation data under different performance dimensions of the target operation and maintenance object.

[0115] Optionally, after creating a visual view based on the operation and maintenance object relationship network, the display module 126 can also respond to the editing operation of the visual view, record the editing information during the editing process, and store the editing information as an operation and maintenance data in the target database, wherein the target database is used to store the first dataset and the second dataset.

[0116] As an optional implementation, the system also includes an encoding module for encoding and converting the object information and relationship information of the operation and maintenance object to obtain the target encoding of the operation and maintenance object, wherein the target encoding includes: operation and maintenance object encoding and operation and maintenance relationship encoding.

[0117] Optionally, the technical attributes and operation and maintenance scenarios of the operation and maintenance object are determined, and the operation and maintenance object code is determined based on the technical attributes and operation and maintenance scenarios. The operation and maintenance object code includes: a main code reflecting the technical attributes of the operation and maintenance object, and an auxiliary code for determining the operation and maintenance scenarios referenced by the operation and maintenance object; the business attributes and relationship number of the operation and maintenance relationship are determined, and the operation and maintenance relationship code is determined based on the business attributes and relationship number; and the target code is obtained based on the operation and maintenance object code and the operation and maintenance relationship code.

[0118] Optionally, the technical attributes include: object type and business characteristics. The encoding module is further used to encode the object type data according to a preset first encoding rule to obtain the object type code, and to encode the business characteristics according to a preset second encoding rule to obtain the business characteristic code; determine the main code based on the object type code and the business characteristic code; determine the auxiliary code according to the operation and maintenance scenario; and obtain the operation and maintenance object code based on the main code and the auxiliary code.

[0119] Optionally, the auxiliary coding includes: operation and maintenance scenario coding, operation and maintenance scenario layer coding, and operation and maintenance scenario sequence number. The coding module is further used to determine the operation and maintenance scenario referenced by the operation and maintenance object, and to code the operation and maintenance scenario according to a preset third coding rule to obtain the operation and maintenance scenario coding; to determine the operation and maintenance scenario layer referenced by the operation and maintenance object, and to code the operation and maintenance scenario layer according to a preset fourth coding rule to obtain the operation and maintenance scenario layer coding; to determine the operation and maintenance scenario sequence number referenced by the operation and maintenance object; and to obtain the auxiliary coding based on the operation and maintenance scenario coding, operation and maintenance scenario layer coding, and operation and maintenance scenario sequence number.

[0120] Optionally, the business attributes include: relationship type and relationship constraints. The encoding module is further used to encode the relationship type according to the preset fifth encoding rule to obtain the relationship type encoding. The relationship type includes at least one of the following: cluster relationship, composition relationship, connection relationship, call relationship, installation relationship, and dependency relationship. The relationship constraint encoding is determined based on the object type encoding of the operation and maintenance objects connected in the operation and maintenance relationship. The operation and maintenance relationship encoding is determined based on the relationship type encoding, the relationship constraint encoding, and the relationship sequence number.

[0121] It should be noted that each module in the operation and maintenance data processing device in this application embodiment corresponds one-to-one with each implementation step of the operation and maintenance data processing method in embodiment 1. Since embodiment 1 has been described in detail, some details not shown in this embodiment can be referred to embodiment 1, and will not be elaborated further here.

[0122] Example 3

[0123] According to an embodiment of this application, an electronic device is also provided, comprising: a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the operation and maintenance data processing method of Embodiment 1 through the computer program.

[0124] Optionally, the processor is configured to execute the following steps via a computer program:

[0125] Step S102: Obtain the operation and maintenance data of the target data source, wherein the operation and maintenance data includes: object information, relationship information and running data of the operation and maintenance object.

[0126] Step S104: Construct an operation and maintenance object relationship network based on the object information and relationship information of the operation and maintenance object. The operation and maintenance object relationship network is used to display the various operation and maintenance relationships of the operation and maintenance object.

[0127] Step S106: Create a visualization view based on the operation and maintenance object relationship network to display the object information, relationship information, and running data of the operation and maintenance objects under different performance dimensions. The visualization view is used to display the physical deployment diagram and various key link diagrams of the operation and maintenance objects. The key link diagrams include at least one of the following: batch dependency link, resource supply link, and service access call link.

[0128] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0129] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0130] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0131] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0132] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0133] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0134] The above are merely preferred embodiments of this application. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for processing operation and maintenance data, characterized in that, include: The process involves acquiring operation and maintenance data from a target data source, encoding and converting the object information and relationship information of the operation and maintenance object to obtain a target code for the operation and maintenance object. The target code includes an operation and maintenance object code and an operation and maintenance relationship code. This target code is used to retrieve the operation and maintenance object and its relationships. The operation and maintenance data includes the object information, relationship information, and runtime data of the operation and maintenance object. The process also involves determining the technical attributes and operation and maintenance scenarios of the operation and maintenance object, and then determining the operation and maintenance object code based on these attributes and scenarios. The operation and maintenance object code includes a primary code reflecting the technical attributes of the operation and maintenance object, and an auxiliary code for determining the operation and maintenance scenario in which the operation and maintenance object is referenced. An operation and maintenance object relationship network is constructed based on the object information and relationship information of the operation and maintenance object, wherein the operation and maintenance object relationship network is used to display the various operation and maintenance relationships of the operation and maintenance object; A visualization view is created based on the relationship network of the operation and maintenance objects to display the object information, relationship information, and runtime data of the operation and maintenance objects under different performance dimensions. Specifically, the scenario category of the operation and maintenance scenarios referenced by the operation and maintenance objects is determined. The visualization view is then segmented according to the scenario category to obtain at least one visualization sub-view. The visualization sub-view is used to display the runtime data of the operation and maintenance objects under each type of operation and maintenance scenario. The visualization view is used to display the physical deployment diagram and various key link diagrams of the operation and maintenance objects. The key link diagrams include at least one of the following: batch dependency link, resource provisioning link, and service access call link.

2. The method according to claim 1, characterized in that, The target data source includes: a first target data source and a second target data source. The operation and maintenance data of the target data source is obtained, including: Obtain the object information and the relationship information of the operation and maintenance object from the first target data source, wherein the first target data source is used to record various types of computer resources; Obtain the operational data of the operation and maintenance object from the second target data source, wherein the second target data source is used to record the operational data of the operation and maintenance object in different performance dimensions.

3. The method according to claim 1, characterized in that, Based on the object information and relationship information of the operation and maintenance objects, an operation and maintenance object relationship network is constructed, including: According to the object type of the operation and maintenance object, the object information of each type of operation and maintenance object is stored in the corresponding dataset to obtain at least one first dataset; According to the relationship type of the operation and maintenance objects, the relationship information of each type of operation and maintenance object is stored in the corresponding dataset to obtain at least one second dataset; The operation and maintenance object relationship network is constructed based on at least one of the first datasets and at least one of the second datasets.

4. The method according to claim 1, characterized in that, A visualization view is created based on the operation and maintenance object relationship network to display the object information, relationship information, and operational data of the operation and maintenance objects under different performance dimensions, including: In response to the selection operation of the operation and maintenance object in the visualization view, the target operation and maintenance object is determined; The visualization view displays the target physical deployment diagram and each target key link of the target operation and maintenance object. The target physical deployment diagram and each target key link display the target object information, target relationship information, and target operation data under different performance dimensions of the target operation and maintenance object.

5. The method according to claim 3, characterized in that, After creating a visual view based on the operation and maintenance object relationship network, the method further includes: In response to the editing operation of the visualization view, the editing information during the editing process is recorded, and the editing information is stored as an operation and maintenance data in the target database, wherein the target database is used to store the first dataset and the second dataset.

6. The method according to claim 1, characterized in that, The object information and relationship information of the operation and maintenance object are encoded and converted to obtain the target code, including: Determine the business attributes and relationship sequence number of the operation and maintenance relationship, and determine the operation and maintenance relationship code based on the business attributes and the relationship sequence number; The target code is obtained based on the operation and maintenance object code and the operation and maintenance relationship code.

7. The method according to claim 6, characterized in that, The technical attributes include: object type and business characteristics. Determining the operation and maintenance object code based on the technical attributes and the operation and maintenance scenario includes: The object type is encoded according to a preset first encoding rule to obtain an object type encoding, and the business characteristics are encoded according to a preset second encoding rule to obtain a business characteristic encoding. The main code is determined based on the object type code and the business characteristic code; The auxiliary code is determined based on the aforementioned operation and maintenance scenario; The operation and maintenance object code is obtained based on the main code and the auxiliary code.

8. The method according to claim 7, characterized in that, The auxiliary coding includes: an operation and maintenance scenario code, an operation and maintenance scenario layer code, and an operation and maintenance scenario sequence number. Determining the auxiliary coding based on the operation and maintenance scenario includes: The operation and maintenance scenario referenced by the operation and maintenance object is determined, and the operation and maintenance scenario is encoded according to the preset third encoding rule to obtain the operation and maintenance scenario code; Determine the operation and maintenance scene layer referenced by the operation and maintenance object, and encode the operation and maintenance scene layer according to the preset fourth encoding rule to obtain the operation and maintenance scene layer code; Determine the sequence number of the operation and maintenance scenario referenced by the operation and maintenance object; The auxiliary code is obtained based on the operation and maintenance scenario code, the operation and maintenance scenario layer code, and the operation and maintenance scenario sequence number.

9. The method according to claim 7, characterized in that, The business attributes include: relationship type and relationship constraints, wherein determining the operation and maintenance relationship code based on the business attributes and the relationship sequence number includes: The relationship type is encoded according to the preset fifth encoding rule to obtain the relationship type encoding, wherein the relationship type includes at least one of the following: cluster relationship, composition relationship, connection relationship, call relationship, installation relationship and dependency relationship; The relationship constraint code is determined based on the object type code of the operation and maintenance object connected in the operation and maintenance relationship; The operation and maintenance relationship code is determined based on the relationship type code, the relationship constraint code, and the relationship sequence number.

10. A device for processing operation and maintenance data, characterized in that, include: The acquisition module is used to acquire operation and maintenance data from a target data source, encode and convert the object information and relationship information of the operation and maintenance object to obtain the target code of the operation and maintenance object. The target code includes an operation and maintenance object code and an operation and maintenance relationship code. The target code is used to retrieve the operation and maintenance object and its relationships. The operation and maintenance data includes the object information, relationship information, and runtime data of the operation and maintenance object. The module also determines the technical attributes and operation and maintenance scenarios of the operation and maintenance object, and determines the operation and maintenance object code based on these attributes and scenarios. The operation and maintenance object code includes a primary code reflecting the technical attributes of the operation and maintenance object and an auxiliary code for determining the operation and maintenance scenario referenced by the operation and maintenance object. A construction module is used to construct an operation and maintenance object relationship network based on the object information and relationship information of the operation and maintenance object, wherein the operation and maintenance object relationship network is used to display the multiple operation and maintenance relationships of the operation and maintenance object; The display module is used to create a visual view based on the relationship network of the operation and maintenance objects to display the object information, relationship information, and runtime data of the operation and maintenance objects under different performance dimensions. Specifically, it determines the scenario category of the operation and maintenance scenarios referenced by the operation and maintenance objects; it segments the visual view according to the scenario category to obtain at least one visual sub-view, wherein the visual sub-view is used to display the runtime data of the operation and maintenance objects under each type of operation and maintenance scenario; the visual view is used to display the physical deployment diagram and various key link diagrams of the operation and maintenance objects, wherein the key link diagrams include at least one of the following: batch dependency link, resource provisioning link, and service access call link.

11. An electronic device, characterized in that, include: A memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute, through the computer program, the method for processing maintenance data according to any one of claims 1 to 9.

Images