Associated information generation method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides an associated information generation method and device, electronic equipment and a storage medium. The associated information generation method comprises the following steps: collecting equipment information of equipment managed in a configuration management database; generating an equipment portrait of the equipment based on the equipment information of the equipment; the equipment portrait comprises system information of a system to which the equipment belongs, middleware information running on the equipment and an IP address of the equipment; and based on the device portrait of the device, generating associated information among the system, the middleware and the device managed in the configuration management database. In the embodiment of the invention, the associated information among the system, the middleware and the equipment managed in the configuration management database can be automatically generated, so that the process of generating the associated information can be simplified, and the efficiency of generating the associated information is improved.

Description

Technical Field

[0001] The present application relates to the field of network technology, and in particular to a method, device, electronic device and storage medium for generating association information. Background Art

[0002] With the booming development of cloud computing, the control of cloud resources has become an increasingly prominent issue. The system design based on high-availability architecture brings more devices, and the control of these devices has become a major problem in the operation and maintenance process.

[0003] CMDB (Configuration Management Database) is a database used to manage IT (Information Technology) assets and configuration items. In order to effectively manage CMDB, daily maintenance of CMDB is required. In the current daily maintenance of CMDB, operation and maintenance personnel are required to log in to CMDB, manually associate the systems, middleware and devices managed in CMDB, or manually import table templates to associate systems, middleware and devices, that is, they need to manually configure the association information between systems, middleware and devices managed in CMDB. However, the processing process of the above method is complicated and cumbersome, and the efficiency of generating association information is low. Summary of the invention

[0004] In view of the above problems, the embodiments of the present application propose a method, device, electronic device and storage medium for generating association information, so as to improve the efficiency of generating association information.

[0005] According to one aspect of an embodiment of the present application, a method for generating association information is provided, the method comprising:

[0006] Collect device information of devices managed in the configuration management database;

[0007] Based on the device information of the device, a device portrait of the device is generated; the device portrait includes: system information of the system to which the device belongs, middleware information running on the device, and the IP address of the device;

[0008] Based on the device portrait of the device, association information between the system, middleware, and devices managed in the configuration management database is generated.

[0009] Optionally, the device information includes: the name of the device, the IP address of the device, the user information of the device, the process information of the device, the process port information of the device, and the IP address to which the process port of the device is connected; and generating a device portrait of the device based on the device information includes:

[0010] Based on the name of the device, the IP address of the device, the user information of the device, and the IP address to which the process port of the device is connected, the system information of the system to which the device belongs is obtained;

[0011] Based on the process information of the device and the process port information of the device, obtaining the middleware information running on the device;

[0012] The system information of the system to which the device belongs, the middleware information running on the device and the IP address of the device are used as the device profile of the device.

[0013] Optionally, acquiring system information of a system to which the device belongs based on the name of the device, the IP address of the device, user information of the device, and an IP address to which a process port of the device is connected includes:

[0014] Using the name of the device, the IP address of the device, and the user information of the device as inputs of a pre-trained rule matching model to obtain an output result of the rule matching model;

[0015] When the output result is the system information of a successful match, determining the output result as the system information of the system to which the device belongs;

[0016] When the output result is a match failure, obtaining system information of a system to which an associated device of the device belongs based on an IP address to which a process port of the device is connected;

[0017] After the system information of the system to which the associated device belongs is successfully acquired, the system information of the system to which the associated device belongs is determined as the system information of the system to which the device belongs.

[0018] Optionally, the rule matching model is trained in the following manner:

[0019] Constructing a rule matching model to be trained, wherein the rule matching model to be trained is provided with a system matching condition and a weight of the system matching condition;

[0020] Acquire a sample data set, where the sample data set includes a name of a sample device, an IP address of the sample device, user information of the sample device, and actual system information of a system to which the sample device belongs;

[0021] The rule matching model to be trained is trained using the sample data set, and the rule matching model is obtained after the training is completed; wherein the input of the rule matching model to be trained is the name of the sample device, the IP address of the sample device and the user information of the sample device, and the output is the predicted system information of the system to which the sample device belongs.

[0022] Optionally, the system matching condition includes at least one of a system network segment matching condition, a system name matching condition, and a system user matching condition.

[0023] Optionally, the acquiring system information of a system to which an associated device of the device belongs based on an IP address connected to a process port of the device includes:

[0024] The device corresponding to the IP address connected to the process port of the device is used as the associated device of the device;

[0025] Query whether there is system information of the system to which the associated device belongs;

[0026] When there is system information of the system to which the associated device belongs, acquiring the system information of the system to which the associated device belongs;

[0027] When there is no system information of the system to which the associated device belongs, query whether there is an IP address connected to the process port of the associated device;

[0028] When there is an IP address to which the process port of the associated device is connected, taking the device corresponding to the IP address to which the process port of the associated device is connected as a new associated device of the device, and returning to the step of querying whether there is system information of the system to which the associated device belongs;

[0029] When the IP address to which the process port of the associated device is connected does not exist, it is determined that acquisition of the system information of the system to which the associated device belongs fails.

[0030] Optionally, after acquiring the system information of the system to which the associated device of the device belongs, the method further includes: after failure in acquiring the system information of the system to which the associated device belongs, marking the device as an abnormal device.

[0031] Optionally, obtaining the middleware information running on the device based on the process information of the device and the process port information of the device includes: querying the middleware information corresponding to the process information of the device and the process port information of the device from the preset correspondence between the process, process port and middleware, and determining the queried middleware information as the middleware information running on the device.

[0032] Optionally, the method further includes: for each system, generating an undirected graph corresponding to the system including the middleware and the device based on the association information, and generating a topology graph corresponding to the system including the system, the middleware and the device based on the undirected graph.

[0033] Optionally, collecting device information of devices managed in the configuration management database includes: collecting device information of devices managed in the configuration management database according to a preset collection frequency.

[0034] Optionally, the collecting device information of the devices managed in the configuration management database includes: collecting the device information of the devices managed in the configuration management database, generating a JSON format message from the device information of the devices, encrypting the JSON format message to obtain an encrypted message, and reporting the encrypted message to the configuration management database; generating a device portrait of the device based on the device information of the device includes: decrypting the encrypted message to obtain the JSON format message, extracting the device information of the device from the JSON format message, and generating a device portrait of the device based on the device information of the device.

[0035] According to another aspect of an embodiment of the present application, a device for generating association information is provided, the device comprising:

[0036] A collection module, used to collect device information of devices managed in the configuration management database;

[0037] The analysis module is used to generate a device portrait of the device based on the device information of the device; based on the device portrait of the device, generate association information between the system, middleware, and device managed in the configuration management database; the device portrait includes: system information of the system to which the device belongs, middleware information running on the device, and the IP address of the device.

[0038] Optionally, the device information includes: the name of the device, the IP address of the device, the user information of the device, the process information of the device, the process port information of the device and the IP address to which the process port of the device is connected; the analysis module includes:

[0039] A first acquisition unit, configured to acquire system information of a system to which the device belongs based on a name of the device, an IP address of the device, user information of the device, and an IP address to which a process port of the device is connected;

[0040] A second acquisition unit, configured to acquire middleware information running on the device based on the process information of the device and the process port information of the device;

[0041] The portrait generating unit is used to use the system information of the system to which the device belongs, the middleware information running on the device and the IP address of the device as the device portrait of the device.

[0042] Optionally, the first acquiring unit includes:

[0043] An information matching subunit, used to use the name of the device, the IP address of the device and the user information of the device as inputs of a pre-trained rule matching model to obtain an output result of the rule matching model;

[0044] A first determining subunit, configured to determine the output result as the system information of the system to which the device belongs when the output result is the system information of a successful match;

[0045] An information acquisition subunit is used to acquire system information of a system to which an associated device of the device belongs based on an IP address connected to a process port of the device when the output result is a match failure;

[0046] The second determining subunit is configured to determine the system information of the system to which the associated device belongs as the system information of the system to which the device belongs after the system information of the system to which the associated device belongs is successfully acquired.

[0047] Optionally, the rule matching model is trained in the following manner:

[0048] Constructing a rule matching model to be trained, wherein the rule matching model to be trained is provided with a system matching condition and a weight of the system matching condition;

[0049] Acquire a sample data set, where the sample data set includes a name of a sample device, an IP address of the sample device, user information of the sample device, and actual system information of a system to which the sample device belongs;

[0050] The rule matching model to be trained is trained using the sample data set, and the rule matching model is obtained after the training is completed; wherein the input of the rule matching model to be trained is the name of the sample device, the IP address of the sample device and the user information of the sample device, and the output is the predicted system information of the system to which the sample device belongs.

[0051] Optionally, the system matching condition includes at least one of a system network segment matching condition, a system name matching condition, and a system user matching condition.

[0052] Optionally, the information acquisition subunit is specifically used to:

[0053] The device corresponding to the IP address connected to the process port of the device is used as the associated device of the device;

[0054] Query whether there is system information of the system to which the associated device belongs;

[0055] When there is system information of the system to which the associated device belongs, acquiring the system information of the system to which the associated device belongs;

[0056] When there is no system information of the system to which the associated device belongs, query whether there is an IP address connected to the process port of the associated device;

[0057] When there is an IP address to which the process port of the associated device is connected, taking the device corresponding to the IP address to which the process port of the associated device is connected as a new associated device of the device, and returning to the step of querying whether there is system information of the system to which the associated device belongs;

[0058] When the IP address to which the process port of the associated device is connected does not exist, it is determined that acquisition of the system information of the system to which the associated device belongs fails.

[0059] Optionally, the first acquisition unit further includes: a marking subunit, configured to mark the device as an abnormal device after the acquisition of the system information of the system to which the associated device belongs fails.

[0060] Optionally, the second acquisition unit is specifically used to query the middleware information corresponding to the process information of the device and the process port information of the device from the preset correspondence between the process, process port and middleware, and determine the queried middleware information as the middleware information running on the device.

[0061] Optionally, the device also includes: a generation module, which is used to generate, for each system, an undirected graph corresponding to the system including the middleware and the device based on the association information, and to generate a topology graph corresponding to the system including the system, the middleware and the device based on the undirected graph.

[0062] Optionally, the collection module is specifically used to collect device information of devices managed in the configuration management database according to a preset collection frequency.

[0063] Optionally, the collection module is specifically used to collect device information of devices managed in the configuration management database, generate a JSON format message from the device information of the device, encrypt the JSON format message to obtain an encrypted message, and report the encrypted message to the configuration management database; the analysis module is specifically used to decrypt the encrypted message to obtain the JSON format message, and extract the device information of the device from the JSON format message, and generate a device portrait of the device based on the device information of the device.

[0064] According to another aspect of an embodiment of the present application, an electronic device is provided, comprising a processor and a computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium; when the computer program is executed by the processor, the processor executes the association information generating method as described in any one of the above items.

[0065] According to another aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the processor executes the association information generating method as described in any one of the above items.

[0066] In an embodiment of the present application, it is possible to automatically collect device information of devices managed in a configuration management database; based on the device information of the device, automatically generate a device portrait of the device, the device portrait including: system information of the system to which the device belongs, middleware information running on the device, and the IP (Internet Protocol) address of the device; based on the device portrait of the device, automatically generate association information between the system, middleware, and devices managed in the configuration management database, thereby simplifying the process of generating association information and improving the efficiency of generating association information. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] In order to more clearly illustrate the technical solution of the embodiment of the present application, the drawings required for use in the description of the embodiment of the present application will be briefly introduced below. Obviously, the drawings described below are only some drawings of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0068] Figure 1 is a flowchart of the steps of a method for generating association information in an embodiment of the present application;

[0069] Figure 2 is a schematic diagram of an undirected graph including middleware and IP addresses according to an embodiment of the present application;

[0070] Figure 3 is a schematic diagram of a topology diagram including a system, middleware, and devices according to an embodiment of the present application;

[0071] Figure 4 is a flow chart of a process of generating association information according to an embodiment of the present application;

[0072] Figure 5 is a structural block diagram of a device for generating association information according to an embodiment of the present application;

[0073] Figure 6 is a structural block diagram of an electronic device according to an embodiment of the present application;

[0074] Figure 7 It is a structural block diagram of a computer-readable storage medium in an embodiment of the present application. DETAILED DESCRIPTION

[0075] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0076] In CMDB, system, middleware, and equipment are three core concepts, each representing different levels and components in IT infrastructure.

[0077] System: In CMDB, a system usually refers to a group of software and hardware components that work together to perform a specific business function or provide a specific service. These systems can be complex, containing multiple subsystems and components, or relatively simple, consisting of a few key components. A system can be any type of IT system such as an operating system, database, Web server, application server, network equipment, etc. In CMDB, a system is recorded as an independent configuration item and contains its configuration information, status, dependencies, etc.

[0078] Middleware: In CMDB, middleware is a software layer located above the operating system, network and database, which provides a set of services to support communication, transaction processing, resource management and messaging of distributed applications. Middleware plays the role of a bridge in IT architecture, enabling different systems and applications to communicate and collaborate with each other. Middleware can include but is not limited to message queues, service buses, remote procedure call frameworks, object request brokers, etc. In CMDB, middleware will be recorded as a configuration item, and include its version, configuration information, relationship with other systems and hosts, etc.

[0079] Device (also called host): In CMDB, a device refers to a computer hardware platform that runs an operating system and applications. In an IT environment, a device can be a physical server, a virtual machine, or a cloud instance. Devices are the cornerstone of IT infrastructure because they provide the computing resources needed to run systems and middleware. In CMDB, devices are recorded as configuration items and contain information such as their hardware configuration (such as memory, storage, etc.), network configuration (such as IP address, etc.), processes, ports, etc.

[0080] In a CMDB, there are often complex associations and dependencies between systems, middleware, and devices. For example, a system may rely on specific middleware to communicate with other systems, and the middleware may run on a certain device. These associations are critical to understanding how the entire IT architecture works. Therefore, in a CMDB, the association information between systems, middleware, and devices needs to be accurately maintained.

[0081] In an embodiment of the present application, a method is proposed for automatically collecting device information, automatically generating a device portrait based on the device information, including system information of the system to which the device belongs, middleware information running on the device, and the IP address of the device, and automatically generating association information between the system, middleware, and devices in the CMDB based on the device portrait. Manual association is no longer required for operation and maintenance personnel, thereby improving the efficiency of generating association information and improving the accuracy of association information.

[0082] Reference Figure 1 , showing a step flow chart of a method for generating association information in an embodiment of the present application.

[0083] like Figure 1 As shown, the method for generating association information may include the following steps:

[0084] Step 101: Collect device information of devices managed in a configuration management database.

[0085] Exemplarily, the devices managed in the CMDB may include historical devices and newly added devices in the CMDB. The devices may include but are not limited to IAAS (Infrastructure as a Service) devices, etc. IAAS is a type of cloud computing service that provides virtualized resources at the infrastructure level, including computing, storage, network and other resources.

[0086] Exemplarily, the device information of a device may include, but is not limited to: the name of the device, the IP address of the device, the user information of the device, the process information of the device, the process port information of the device, the IP address to which the process port of the device is connected, and so on.

[0087] User information may be information of non-system users at the operating system level, and process information may be information of non-system processes. For example, user information may include user name, user unique identifier, etc., process information may include process name, etc., and process port information may include process port name, etc.

[0088] In an optional implementation, the device information of the devices managed in the configuration management database may be collected at a preset collection frequency, so that the device information can be collected regularly and associated information can be generated based on the device information, so that the associated information can be updated regularly to ensure the validity of the associated information.

[0089] The above collection frequency can be customized in CMDB according to actual needs, and this embodiment does not limit this. For example, since the change of the associated information between the system, middleware, and equipment has little impact on production, in order to ensure that the collection process does not consume too many system resources, a lower collection frequency (such as once an hour, etc.) can be set.

[0090] In an optional implementation, the device information of the devices managed in the CMDB can be collected by the collection module, and the device information of the devices is generated into a JSON (JavaScript Object Notation, a lightweight data exchange format, commonly used for data transmission between Web applications) format message, and the JSON format message is encrypted to obtain an encrypted message, and the encrypted message is reported to the CMDB. The collection module can report the encrypted message to the CMDB by calling the collection interface of the CMDB.

[0091] After receiving the encrypted message, the CMDB decrypts the encrypted message to obtain the JSON format message, extracts the device information of the device from the JSON format message, inputs the device information of the device into the analysis module, and then performs subsequent analysis and processing on the device information of the device through the analysis module.

[0092] For example, a possible JSON format message demo (example) is as follows:

[0093]

[0094] Among them, "ip" represents the IP address of the device, "hostname" represents the name of the device, "user" represents the user information of the device (such as the user's unique identifier, etc.), "process" represents the process information of the device (such as the process name, etc.), "port" represents the process port information of the device (such as the process port name, etc.), and "foreignAddress" represents the IP address to which the process port of the device is connected.

[0095] Step 102, based on the device information of the device, generate a device portrait of the device; the device portrait includes: system information of the system to which the device belongs, information of the middleware running on the device, and the IP address of the device.

[0096] In the embodiment of the present application, for each device, a device profile of the device can be generated by analyzing the device information of the device.

[0097] Exemplarily, the device portrait may include, but is not limited to: system information of the system to which the device belongs, information about the middleware running on the device, the IP address of the device, etc. The system information may include the system name, the system unique identifier, etc., and the middleware information may include the middleware name, the middleware type, etc.

[0098] In an optional implementation, the process of generating a device portrait of the device based on the device information of the device may include the following steps A1 to A3:

[0099] Step A1, based on the name of the device, the IP address of the device, the user information of the device and the IP address to which the process port of the device is connected, obtain the system information of the system to which the device belongs.

[0100] Exemplarily, the process of acquiring the system information of the system to which the device belongs based on the name of the device, the IP address of the device, the user information of the device, and the IP address to which the process port of the device is connected may include the following steps A11 to A14:

[0101] Step A11, taking the name of the device, the IP address of the device and the user information of the device as inputs of a pre-trained rule matching model to obtain an output result of the rule matching model.

[0102] In an embodiment of the present application, a method of generating a device portrait based on a rule matching model is proposed, so that the configuration and training of the rule matching model can be completed in advance to ensure the accuracy and effectiveness of the rule matching model.

[0103] Exemplarily, the rule matching model can be trained in the following manner:

[0104] (1) Constructing a rule matching model to be trained, wherein the rule matching model to be trained is provided with system matching conditions and weights of the system matching conditions.

[0105] In the embodiment of the present application, a rule matching model can be set based on professional knowledge, expert experience, etc. to describe the relationship between the device information of the device and the system information of the system to which the device belongs. The rule matching model to be trained is provided with system matching conditions and weights of the system matching conditions.

[0106] Exemplarily, the system matching condition may include but is not limited to at least one of the following: a system network segment matching condition, a system name matching condition, a system user matching condition, etc. Each system matching condition has its own weight.

[0107] The weight of the system matching condition can be set according to actual conditions, and this embodiment does not limit this. For example, it can be set according to the degree of association between the system matching condition and the system. The greater the degree of association between the system matching condition and the system, the higher the weight of the system matching condition.

[0108] (2) Obtain a sample data set, where the sample data set includes a name of a sample device, an IP address of the sample device, user information of the sample device, and actual system information of a system to which the sample device belongs.

[0109] The sample data set can be collected based on the devices whose system information is known in the CMDB.

[0110] (3) Using the sample data set to train the rule matching model to be trained, and obtaining the rule matching model after the training is completed; wherein the input of the rule matching model to be trained is the name of the sample device, the IP address of the sample device, and the user information of the sample device, and the output is the predicted system information of the system to which the successfully matched sample device belongs.

[0111] Exemplarily, the system network segment matching condition may include the network segment corresponding to the system (for example, the production system and the office system correspond to different network segments). In the rule matching model, the network segment corresponding to the sample device can be obtained according to the IP address of the sample device, and the network segment corresponding to the sample device is matched with the system network segment matching condition. If the network segment corresponding to the sample device matches (for example, is the same as) the network segment corresponding to the system in a certain system network segment matching condition, it is considered that the IP address of the sample device successfully matches the system network segment matching condition.

[0112] Exemplarily, the system name matching condition may include the name of the system. In the rule matching model, the name of the sample device may be matched with the system name matching condition. If the name of the sample device matches the name of the system in a certain system name matching condition (for example, the same in words or the same in meaning), it is considered that the name of the sample device successfully matches the system name matching condition. Since the name exists in Chinese, English, commonly used Chinese abbreviations, commonly used English abbreviations, aliases, etc., the name matching includes the same meaning.

[0113] For example, for the name of a device, the standardized naming format is "system category-system name-purpose-customized". Therefore, the system name part of the device name can be matched with the system name matching condition. If the device name is not standardized, it may not be able to successfully match the system name matching condition.

[0114] Exemplarily, the system user matching condition may include common users of the system. In the rule matching model, the user information of the sample device may be matched with the system user matching condition. If the user information of the sample device is the same as the common user of the system in a certain system user matching condition, it is considered that the user information of the sample device successfully matches the system user matching condition.

[0115] Then, in the rule matching model, the predicted system information of the system to which the sample device belongs is comprehensively determined based on the matching results of each system matching condition and the weight of each system matching condition. For example, the system information corresponding to the system matching condition that is successfully matched and has the highest weight can be determined as the predicted system information of the system to which the sample device belongs.

[0116] Whether the training is completed can be determined based on the difference between the actual system information of the system to which the sample device belongs and the predicted system information of the system to which the sample device belongs. For example, when the actual system information of the system to which the sample device belongs that exceeds a preset ratio is the same as the predicted system information of the system to which the sample device belongs, the training can be considered completed, and so on.

[0117] The sample data set is used to train, evaluate and verify the rule matching model to be trained. Based on the evaluation results, the rule matching model to be trained is adjusted and optimized to improve its performance and generalization ability. The adjustment and optimization may include adding new system matching conditions, deleting unnecessary system matching conditions, or adjusting the weights of system matching conditions, etc.

[0118] After the device information of the device is collected, the name of the device, the IP address of the device and the user information of the device are used as inputs of a pre-trained rule matching model to obtain an output result of the rule matching model.

[0119] Step A12: when the output result is the system information of a successful match, determine the output result as the system information of the system to which the device belongs.

[0120] If the rule matching model can successfully predict the system information of the system to which the device belongs, the output result of the rule matching model is the successfully matched system information. In this case, the output result can be determined as the system information of the system to which the device belongs.

[0121] Step A13, when the output result is a match failure, based on the IP address to which the process port of the device is connected, obtain the system information of the system to which the associated device of the device belongs.

[0122] If the rule matching model fails to successfully predict the system information of the system to which the device belongs, the output result of the rule matching model is a matching failure. In this case, the system information of the system to which the associated device of the device belongs can be obtained based on the IP address connected to the process port of the device.

[0123] Exemplarily, the process of obtaining the system information of the system to which the associated device of the device belongs based on the IP address to which the process port of the device is connected may include:

[0124] The device corresponding to the IP address connected to the process port of the device is used as the associated device of the device;

[0125] Query whether there is system information of the system to which the associated device belongs;

[0126] When there is system information of the system to which the associated device belongs, acquiring the system information of the system to which the associated device belongs;

[0127] When there is no system information of the system to which the associated device belongs, query whether there is an IP address connected to the process port of the associated device;

[0128] When there is an IP address to which the process port of the associated device is connected, taking the device corresponding to the IP address to which the process port of the associated device is connected as a new associated device of the device, and returning to the step of querying whether there is system information of the system to which the associated device belongs;

[0129] When the IP address to which the process port of the associated device is connected does not exist, it is determined that the acquisition fails.

[0130] For devices that fail to obtain the system information of the system to which the device belongs according to the rule matching model, the system information of the system to which the remote access device (that is, the device's associated device) belongs can be extracted through the device's port access record (the IP address connected to the process port). If the remote access device has system information of the system to which it belongs, then the device is associated with the remote access device to obtain the system information of the system to which the device belongs. If the remote access device does not have system information of the system to which it belongs, then the system information of the system to which the associated device belongs is further extracted based on the IP address connected to the process port of the remote access device. If all associated devices do not have system information of the system to which they belong, then the device's ownership is marked as abnormal for confirmation by the operation and maintenance personnel.

[0131] For example, for device 1 with an IP address of 192.168.1.2, it fails to obtain the system information of the system to which device 1 belongs. Through the device information of device 1, it is known that non-system port 8921 is running on device 1. Through the port information, it is found that the device connected to port 8921 is device 2 (IP address 192.168.1.3). If device 2 already has system information of the system to which it belongs, the system information of the system to which device 1 belongs is associated with the system information of the system to which device 2 belongs, that is, the system information of the system to which device 2 belongs is used as the system information of the system to which device 1 belongs. If device 2 also does not have system information of the system to which it belongs, then continue to search for devices connected to device 2 through the port of device 2 until a device with system information of the system to which it belongs is found.

[0132] Step A14, after the system information of the system to which the associated device belongs is successfully acquired, the system information of the system to which the associated device belongs is determined as the system information of the system to which the device belongs.

[0133] After the system information of the system to which the associated device belongs fails to be obtained, the device can be marked as an abnormal device. Of course, the operation and maintenance personnel can also be notified that the device is an abnormal device. The operation and maintenance personnel can associate the device with the corresponding system according to the specific abnormal situation of the abnormal device and update the relevant configuration in the rule matching model. The specific process can be handled according to actual experience, and this embodiment will not be discussed in detail here.

[0134] Step A2: Based on the process information of the device and the process port information of the device, obtain the middleware information running on the device.

[0135] Exemplarily, the process of obtaining the middleware information running on the device based on the process information of the device and the process port information of the device may include: querying the middleware information corresponding to the process information of the device and the process port information of the device from the preset correspondence between the process, process port and middleware, and determining the queried middleware information as the middleware information running on the device.

[0136] The corresponding relationship between the above processes, process ports and middleware can be set according to actual conditions, and this embodiment does not impose any limitation on this.

[0137] Step A3, using the system information of the system to which the device belongs, the middleware information running on the device and the IP address of the device as the device portrait of the device.

[0138] After the device portrait of the device is generated, the tag data of the device portrait can be stored in the form of an array. In implementation, any suitable storage medium can be selected to store the device portrait, and this embodiment does not limit this.

[0139] For example, the device portrait may be stored in the form shown in Table 1 below:

[0140] Table 1

[0141]

[0142] In an optional implementation, corresponding to the above-mentioned method of collecting the device information of the device managed in the CMDB through the collection module, generating a JSON format message from the device information of the device, encrypting the JSON format message to obtain an encrypted message, and reporting the encrypted message to the CMDB, the analysis module can generate a device portrait of the device based on the device information of the device. Therefore, after receiving the encrypted message, the analysis module can decrypt the encrypted message to obtain the JSON format message, and extract the device information of the device from the JSON format message, and generate a device portrait of the device based on the device information of the device.

[0143] Step 103, based on the device portrait of the device, generate association information between the system, middleware, and devices managed in the configuration management database.

[0144] Read the stored device portraits, traverse the device portraits of all devices, automatically associate the system information of the system to which the device belongs, the middleware information running on the device, and the IP address of the device, thereby generating the association information between the system, middleware, and devices managed in the CMDB, and storing the association information between the system, middleware, and devices.

[0145] In an embodiment of the present application, it is possible to automatically collect device information of devices managed in a configuration management database; based on the device information of the device, automatically generate a device portrait of the device, the device portrait including: system information of the system to which the device belongs, middleware information running on the device, and the IP (Internet Protocol) address of the device; based on the device portrait of the device, automatically generate association information between the system, middleware, and devices managed in the configuration management database, thereby simplifying the process of generating association information and improving the efficiency of generating association information.

[0146] In an optional implementation, in order to further improve the visibility of the association information, after obtaining the association information, for each system, an undirected graph including the middleware and the device corresponding to the system can be generated based on the association information, and a topology graph including the system, the middleware and the device corresponding to the system can be generated based on the undirected graph. In this way, the topology layout can be optimized to form an easy-to-read topology graph.

[0147] For example, for the association information between systems, middleware, and devices, by aggregating the information about system 1, we can obtain the information shown in Table 2 below:

[0148] Table 2

[0149] id System Information IP address Middleware information 1 System 1 192.168.1.2 Middleware 1 2 System 1 192.168.1.3 Middleware 1 3 System 1 192.168.1.3 Middleware 2 4 System 1 192.168.1.3 Middleware 3 5 System 1 192.168.1.4 Middleware 1 6 System 1 192.168.1.4 Middleware 2

[0150] For the information shown in Table 2 above, the same middleware in the system is aggregated to generate an undirected graph containing middleware and IP addresses. Figure 2 As shown, it is a schematic diagram of an undirected graph including middleware and IP addresses according to an embodiment of the present application. By processing the information shown in Table 2, an undirected graph of middleware 1, middleware 2, middleware 3 and their corresponding IP addresses can be obtained.

[0151] against Figure 2 The undirected graph shown in the figure further optimizes the topological layout and generates a topological graph corresponding to system 1 including the system, middleware and devices. Figure 3 As shown, it is a schematic diagram of a topology diagram including a system, middleware and devices in an embodiment of the present application. Figure 2 By converting the undirected graph shown in FIG. 1 , we can obtain a topological graph of middleware 1, middleware 2, middleware 3 associated with system 1 and their corresponding IP addresses.

[0152] In the embodiment of the present invention, the above process may be executed cyclically to dynamically update the association information among the system, middleware, and devices.

[0153] Reference Figure 4 , showing a flowchart of a process for generating associated information in an embodiment of the present application.

[0154] like Figure 4 As shown, the process of generating associated information involves a collection module and an analysis module.

[0155] The following process is performed in the collection module: collecting device information of the device according to the collection frequency, the device information may include: device name, device IP address, device user information, device process information, device process port information, and IP address of the device process port connection; integrating device information to generate JSON format message; encrypting JSON format message, for example, using AES (Advanced Encryption Standard) and other methods for encryption; calling CMDB interface to upload the encrypted message to CMDB.

[0156] The following process is performed in the analysis module: decrypt the encrypted message; extract device information; obtain the system information of the system to which the device belongs based on the rule matching model; determine whether the system information of the system to which the device belongs is successfully obtained; if not (that is, the system information of the system to which the device belongs is not successfully obtained), extract the port access record, and use the corresponding device of the IP address connected to the process port of the device as the associated device; determine whether the associated device has system information of the system to which it belongs; if so (that is, the associated device has system information of the system to which it belongs), generate portrait data and store it in the database; if not (that is, the associated device does not have system information of the system to which it belongs), use the corresponding device of the IP address connected to the process port of the associated device as a new associated device, and determine whether the associated device has system information of the system to which it belongs; if so (that is, the associated device does not have system information of the system to which it belongs), generate portrait data and store it in the database; if not (that is, the associated device does not have system information of the system to which it belongs), mark the device as an abnormal device; if so (that is, the system information of the system to which the device belongs is successfully obtained), generate portrait data and store it in the database; middleware clustering, generate an undirected graph; generate a topology graph.

[0157] In the embodiment of the present application, based on the rule matching model, the device portrait generation for each device is realized, and the topological relationship between the system, middleware, and device is automatically generated, so as to solve the problem of daily manual configuration and update of CMDB information by operation and maintenance personnel. By automatically generating topological relationships and automatically updating CMDB information, it can not only reduce the workload of operation and maintenance personnel and improve work efficiency, but also reduce the incidence of human errors, ensure the integrity and accuracy of CMDB information, and thus better support IT asset management.

[0158] In the case of multiple systems reusing devices, the device portrait is associated through the application port. In the case that all devices are reused with other systems, a device IP and port are customized through matching rules to build a device portrait for the associated device, thereby realizing the association of different systems. In the case of multiple middleware reuse of devices, the user judgment is used to distinguish between different processes and operating systems. In the case of multiple systems reusing middleware, the corresponding middleware port is found through the process, the remote connection IP address is obtained through the port connection information, and the device portrait is obtained through the remote connection IP address to determine whether there is a shared situation. Continuously monitor and dynamically update the system topology structure to realize automatic management of the system topology and reduce the burden on operation and maintenance personnel.

[0159] Reference Figure 5 , shows a structural block diagram of a correlation information generating device in an embodiment of the present application.

[0160] like Figure 5 As shown, the association information generating device may include the following modules:

[0161] The collection module 501 is used to collect device information of devices managed in the configuration management database;

[0162] The analysis module 502 is used to generate a device portrait of the device based on the device information of the device; based on the device portrait of the device, generate association information between the system, middleware, and device managed in the configuration management database; the device portrait includes: system information of the system to which the device belongs, middleware information running on the device, and the IP address of the device.

[0163] Optionally, the device information includes: the name of the device, the IP address of the device, the user information of the device, the process information of the device, the process port information of the device and the IP address to which the process port of the device is connected; the analysis module 502 includes:

[0164] A first acquisition unit, configured to acquire system information of a system to which the device belongs based on a name of the device, an IP address of the device, user information of the device, and an IP address to which a process port of the device is connected;

[0165] A second acquisition unit, configured to acquire middleware information running on the device based on the process information of the device and the process port information of the device;

[0166] The portrait generating unit is used to use the system information of the system to which the device belongs, the middleware information running on the device and the IP address of the device as the device portrait of the device.

[0167] Optionally, the first acquiring unit includes:

[0168] An information matching subunit, used to use the name of the device, the IP address of the device and the user information of the device as inputs of a pre-trained rule matching model to obtain an output result of the rule matching model;

[0169] A first determining subunit, configured to determine the output result as the system information of the system to which the device belongs when the output result is the system information of a successful match;

[0170] An information acquisition subunit is used to acquire system information of a system to which an associated device of the device belongs based on an IP address connected to a process port of the device when the output result is a match failure;

[0171] The second determining subunit is configured to determine the system information of the system to which the associated device belongs as the system information of the system to which the device belongs after the system information of the system to which the associated device belongs is successfully acquired.

[0172] Optionally, the rule matching model is trained in the following manner:

[0173] Constructing a rule matching model to be trained, wherein the rule matching model to be trained is provided with a system matching condition and a weight of the system matching condition;

[0174] Acquire a sample data set, where the sample data set includes a name of a sample device, an IP address of the sample device, user information of the sample device, and actual system information of a system to which the sample device belongs;

[0175] The rule matching model to be trained is trained using the sample data set, and the rule matching model is obtained after the training is completed; wherein the input of the rule matching model to be trained is the name of the sample device, the IP address of the sample device and the user information of the sample device, and the output is the predicted system information of the system to which the sample device belongs.

[0176] Optionally, the system matching condition includes at least one of a system network segment matching condition, a system name matching condition, and a system user matching condition.

[0177] Optionally, the information acquisition subunit is specifically used to:

[0178] The device corresponding to the IP address connected to the process port of the device is used as the associated device of the device;

[0179] Query whether there is system information of the system to which the associated device belongs;

[0180] When there is system information of the system to which the associated device belongs, acquiring the system information of the system to which the associated device belongs;

[0181] When there is no system information of the system to which the associated device belongs, query whether there is an IP address connected to the process port of the associated device;

[0182] When there is an IP address to which the process port of the associated device is connected, taking the device corresponding to the IP address to which the process port of the associated device is connected as a new associated device of the device, and returning to the step of querying whether there is system information of the system to which the associated device belongs;

[0183] When the IP address to which the process port of the associated device is connected does not exist, it is determined that acquisition of the system information of the system to which the associated device belongs fails.

[0184] Optionally, the first acquisition unit further includes: a marking subunit, configured to mark the device as an abnormal device after the acquisition of the system information of the system to which the associated device belongs fails.

[0185] Optionally, the second acquisition unit is specifically used to query the middleware information corresponding to the process information of the device and the process port information of the device from the preset correspondence between the process, process port and middleware, and determine the queried middleware information as the middleware information running on the device.

[0186] Optionally, the device also includes: a generation module, which is used to generate, for each system, an undirected graph corresponding to the system including the middleware and the device based on the association information, and to generate a topology graph corresponding to the system including the system, the middleware and the device based on the undirected graph.

[0187] Optionally, the collection module 501 is specifically configured to collect device information of devices managed in the configuration management database according to a preset collection frequency.

[0188] Optionally, the collection module 501 is specifically used to collect device information of devices managed in the configuration management database, generate a JSON format message from the device information of the device, encrypt the JSON format message to obtain an encrypted message, and report the encrypted message to the configuration management database; the analysis module 502 is specifically used to decrypt the encrypted message to obtain the JSON format message, and extract the device information of the device from the JSON format message, and generate a device portrait of the device based on the device information of the device.

[0189] In an embodiment of the present application, it is possible to automatically collect device information of devices managed in a configuration management database; based on the device information of the device, automatically generate a device portrait of the device, the device portrait including: system information of the system to which the device belongs, middleware information running on the device, and the IP (Internet Protocol) address of the device; based on the device portrait of the device, automatically generate association information between the system, middleware, and devices managed in the configuration management database, thereby simplifying the process of generating association information and improving the efficiency of generating association information.

[0190] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0191] In an embodiment of the present application, an electronic device is also provided. The electronic device may include a processor and a computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium; when the computer program is executed by the processor, the processor executes the association information generation method of any of the above embodiments.

[0192] Reference Figure 6, shows a structural block diagram of an electronic device according to an embodiment of the present application. Figure 6 As shown, the electronic device 60 includes a processor 601 and a computer-readable storage medium 602 , on which a computer program 6021 is stored.

[0193] The processor 601 is used to execute the computer program 6021 stored on the computer-readable storage medium 602. When executing the computer program 6021, the processor 601 implements the association information generation method of any of the above embodiments and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0194] The processor 601 mentioned above may include but is not limited to: a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0195] The computer-readable storage medium 602 mentioned above may include but is not limited to: Read Only Memory (ROM), Random Access Memory (RAM), Compact Disc Read Only Memory (CD-ROM), Electronic Erasable Programmable Read Only Memory (EEPROM), hard disk, floppy disk, flash memory, and the like.

[0196] In an embodiment of the present application, a computer-readable storage medium is further provided, on which a computer program is stored. The computer program can be executed by a processor of an electronic device. When the computer program is executed by the processor, the processor executes the association information generating method described in any of the above embodiments.

[0197] Reference Figure 7 , shows a block diagram of a computer-readable storage medium according to an embodiment of the present application. Figure 7As shown, a computer program 701 is stored on a computer-readable storage medium 70. When the computer program 701 is executed by a processor, the processor executes the method for generating associated information as described in any of the above embodiments and can achieve the same technical effect. To avoid repetition, it will not be described here.

[0198] The various embodiments in this specification are interrelated, and each embodiment is described in a progressive manner. Each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments can be referenced to each other.

[0199] It should be noted that all actions of acquiring signals, information or data in this application are carried out in compliance with the relevant data protection laws and policies of the country where they are located and with the authorization given by the owner of the corresponding device.

[0200] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.

[0201] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application.

[0202] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

[0203] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in the present application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0204] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0205] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0206] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0207] The functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0208] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. In summary, the content of this specification should not be understood as limiting the present application.

Claims

1. A method for generating association information, characterized in that: The method comprises: Collect device information of devices managed in the configuration management database; Based on the device information of the device, a device portrait of the device is generated; the device portrait includes: system information of the system to which the device belongs, middleware information running on the device, and the IP address of the device; Based on the device portrait of the device, association information between the system, middleware, and devices managed in the configuration management database is generated.

2. The method according to claim 1, characterized in that The device information includes: the name of the device, the IP address of the device, the user information of the device, the process information of the device, the process port information of the device, and the IP address connected to the process port of the device; generating a device portrait of the device based on the device information includes: Based on the name of the device, the IP address of the device, the user information of the device, and the IP address to which the process port of the device is connected, the system information of the system to which the device belongs is obtained; Based on the process information of the device and the process port information of the device, obtaining the middleware information running on the device; The system information of the system to which the device belongs, the middleware information running on the device and the IP address of the device are used as the device profile of the device.

3. The method according to claim 2, characterized in that The acquiring system information of the system to which the device belongs based on the name of the device, the IP address of the device, the user information of the device, and the IP address to which the process port of the device is connected includes: Using the name of the device, the IP address of the device, and the user information of the device as inputs of a pre-trained rule matching model to obtain an output result of the rule matching model; When the output result is the system information of a successful match, determining the output result as the system information of the system to which the device belongs; When the output result is a match failure, obtaining system information of a system to which an associated device of the device belongs based on an IP address to which a process port of the device is connected; After the system information of the system to which the associated device belongs is successfully acquired, the system information of the system to which the associated device belongs is determined as the system information of the system to which the device belongs.

4. The method according to claim 3, characterized in that The rule matching model is trained in the following way: Constructing a rule matching model to be trained, wherein the rule matching model to be trained is provided with a system matching condition and a weight of the system matching condition; Acquire a sample data set, where the sample data set includes a name of a sample device, an IP address of the sample device, user information of the sample device, and actual system information of a system to which the sample device belongs; The rule matching model to be trained is trained using the sample data set, and the rule matching model is obtained after the training is completed; wherein the input of the rule matching model to be trained is the name of the sample device, the IP address of the sample device and the user information of the sample device, and the output is the predicted system information of the system to which the sample device belongs.

5. The method according to claim 4, characterized in that The system matching condition includes at least one of a system network segment matching condition, a system name matching condition, and a system user matching condition.

6. The method according to claim 3, characterized in that The acquiring, based on the IP address of the process port connection of the device, system information of the system to which the associated device of the device belongs includes: The device corresponding to the IP address connected to the process port of the device is used as the associated device of the device; Query whether there is system information of the system to which the associated device belongs; When there is system information of the system to which the associated device belongs, acquiring the system information of the system to which the associated device belongs; When there is no system information of the system to which the associated device belongs, query whether there is an IP address connected to the process port of the associated device; When there is an IP address to which the process port of the associated device is connected, taking the device corresponding to the IP address to which the process port of the associated device is connected as a new associated device of the device, and returning to the step of querying whether there is system information of the system to which the associated device belongs; When the IP address to which the process port of the associated device is connected does not exist, it is determined that acquisition of the system information of the system to which the associated device belongs fails.

7. The method according to claim 3, characterized in that After obtaining the system information of the system to which the associated device of the device belongs, the method further includes: After the system information of the system to which the associated device belongs fails to be acquired, the device is marked as an abnormal device.

8. The method according to claim 2, characterized in that: The acquiring the middleware information running on the device based on the process information of the device and the process port information of the device includes: From the preset correspondence between the process, the process port and the middleware, the middleware information corresponding to the process information of the device and the process port information of the device is queried, and the queried middleware information is determined as the middleware information running on the device.

9. The method according to claim 1, characterized in that: The method further comprises: For each system, an undirected graph corresponding to the system and including the middleware and the device is generated based on the association information, and a topology graph corresponding to the system and including the system, the middleware and the device is generated based on the undirected graph.

10. The method according to claim 1, characterized in that The device information of the devices managed in the acquisition configuration management database includes: The device information of the devices managed in the configuration management database is collected according to the preset collection frequency.

11. The method according to claim 1, characterized in that: The collecting device information of the devices managed in the configuration management database includes: collecting the device information of the devices managed in the configuration management database, generating a JSON format message from the device information of the devices, encrypting the JSON format message to obtain an encrypted message, and reporting the encrypted message to the configuration management database; The generating of the device portrait of the device based on the device information of the device includes: decrypting the encrypted message to obtain the JSON format message, extracting the device information of the device from the JSON format message, and generating the device portrait of the device based on the device information of the device.

12. A device for generating related information, characterized in that: The device comprises: A collection module, used to collect device information of devices managed in the configuration management database; The analysis module is used to generate a device portrait of the device based on the device information of the device; based on the device portrait of the device, generate association information between the system, middleware, and device managed in the configuration management database; the device portrait includes: system information of the system to which the device belongs, middleware information running on the device, and the IP address of the device.

13. An electronic device, characterized in that: The electronic device comprises a processor and a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program; When the computer program is executed by the processor, the processor is caused to execute the method for generating association information according to any one of claims 1 to 11.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processor executes the method for generating association information according to any one of claims 1 to 11.

Images