Service and middleware association relationship acquisition method and device, equipment, medium and product

Abstract

The invention discloses a service and middleware association relationship acquisition method, device and equipment, a medium and a product, and relates to the technical field of distributed systems. The method comprises the steps of firstly collecting service matching information of all services and middleware matching information of all middleware, storing a collection result in a database, then receiving and analyzing service metadata reported by any service through an agent packet when the service is started, so as to obtain information of any service and middleware metadata, and sending the information of any service and middleware metadata to the server. The information is matched with information for service matching in a database, the middleware metadata is matched with information for middleware matching in the database, and if it is found that the information is matched with the information for service matching of a certain service and the middleware metadata is matched with the information for middleware matching of a certain middleware, the middleware is matched with the information for middleware matching of the certain middleware. And if yes, determining that the certain service has an association relationship with the certain middleware, so that the aim of automatically collecting the association relationship between the service and the middleware can be fulfilled.

Description

Technical Field

[0001] The present invention belongs to the technical field of distributed systems, and specifically relates to a method, device, equipment, medium and product for collecting association relationships between services and middleware. Background Art

[0002] At present, the distributed system applications on the market are becoming more and more extensive. In the distributed system, with the increase in the number of services, the middleware (i.e., an independent software system or service program) used by the services is also increasing, and the types of middleware are also becoming more and more extensive; for example, there are database middleware, message middleware, and cache middleware, among which there are many types of database middleware, such as mysql, oracle, postgresql, and sqlserver. When the number of services and the number and types of middleware reach a certain scale, the association between the middleware and the service becomes more and more complicated, and when the middleware changes (such as migration, version upgrade, or upgrade configuration, etc.), if the services associated with the middleware are not known, the middleware configuration information in these services cannot be changed accordingly, which will cause the service to be unavailable at the least, and even cause production accidents at the worst, causing certain losses to the company. When the service or middleware is deactivated, if the associated information is not known, the associated service or middleware cannot be deactivated, and then these idle resources cannot be released, resulting in waste of resources and increase in costs, causing certain economic losses to the company.

[0003] In summary, it is extremely important to maintain the relationship between services and middleware. The existing way to achieve the relationship between services and middleware is mainly manual maintenance, which inevitably requires a lot of manpower to sort out the relationship between services and middleware, and there are certain loopholes. If any changes occur, manual maintenance is required, which lacks timeliness and flexibility. Summary of the invention

[0004] The purpose of the present invention is to provide a method, device, computer equipment, computer-readable storage medium and computer program product for collecting service and middleware association relationships, so as to solve the problems of large manpower requirements and easy manual omissions in existing solutions for manually maintaining service and middleware association relationships.

[0005] In order to achieve the above object, the present invention adopts the following technical solutions:

[0006] In a first aspect, a method for collecting association relationships between services and middleware is provided, comprising:

[0007] Collect service matching information of all services and middleware matching information of all middleware, and store the collection results in a database;

[0008] receiving service metadata reported by any service through an agent package when the service is started, wherein the service metadata includes information of the service and middleware metadata included in the configuration content of the service, and the docking information of the agent package is pre-added to the startup parameters of the service, so as to complete the docking with the agent package when the service is started, and reporting the service metadata of the service through the agent package;

[0009] Parsing the service metadata to obtain information of any service and the middleware metadata, and matching the information of any service with the service matching information in the database, and matching the middleware metadata with the middleware matching information in the database;

[0010] If it is found that the information of any one of the services matches the service matching information of a certain service and the middleware metadata matches the middleware matching information of a certain middleware, it is determined that the certain service and the certain middleware have an association relationship.

[0011] Based on the above invention content, a new solution for automatically collecting the association between services and middleware based on Java bytecode enhancement technology is provided, that is, first collecting the service matching information of all services and the middleware matching information of all middleware, and storing the collection results in a database, and then receiving and parsing the service metadata reported by any service through the agent package when starting, so as to obtain the information and middleware metadata of any service, and match the information with the service matching information in the database, and match the middleware metadata with the middleware matching information in the database. If it is found that the information matches the service matching information of a certain service and the middleware metadata matches the middleware matching information of a certain middleware, it is determined that the certain service has an association with the certain middleware. In this way, the purpose of automatically collecting the association between services and middleware can be achieved, that is, no manual maintenance is required, which can greatly reduce the manpower demand and avoid manual omissions, and is convenient for practical application and promotion.

[0012] In a possible design, after determining that the certain service has an association relationship with the certain middleware, the method further includes:

[0013] After receiving the association query request for the certain service, information of all middlewares that have an association relationship with the certain service is returned.

[0014] In a possible design, after determining that the certain service has an association relationship with the certain middleware, the method further includes:

[0015] After receiving the association query request for the certain middleware, information of all services associated with the certain middleware is returned.

[0016] In a possible design, after determining that the certain service has an association relationship with the certain middleware, the method further includes:

[0017] When it is found that a certain middleware has been changed, a notification is issued to restart all services associated with the certain middleware or to modify configuration contents of all services associated with the certain middleware.

[0018] In one possible design, the service matching information includes a service name and / or a service unique identifier.

[0019] In a possible design, the middleware matching information includes the middleware type, the middleware IP address, the middleware name, the middleware unique identifier, the parameters of the CPU used by the middleware and / or the parameters of the memory used by the middleware.

[0020] In a second aspect, a device for collecting association relationships between services and middleware is provided, comprising an information collection unit, a data receiving unit, a parsing and matching unit, and a relationship determination unit;

[0021] The information collection unit is used to collect service matching information of all services and middleware matching information of all middleware, and store the collection results in a database;

[0022] The data receiving unit is used to receive service metadata reported by any service through an agent package when the service is started, wherein the service metadata includes information of the service and middleware metadata included in the configuration content of the service, and the docking information of the agent package is pre-added to the startup parameters of the service, so as to complete the docking with the agent package when the service is started, and report the service metadata of the service through the agent package;

[0023] The parsing and matching unit is communicatively connected to the information collecting unit and the data receiving unit, respectively, and is used to parse the service metadata to obtain the information of any service and the middleware metadata, and to match the information of any service with the service matching information in the database, and to match the middleware metadata with the middleware matching information in the database;

[0024] The relationship determination unit is communicatively connected to the parsing and matching unit, and is used to determine that the certain service has an association relationship with the certain middleware if it is found that the information of any service matches the service matching information of a certain service and the middleware metadata matches the middleware matching information of a certain middleware.

[0025] In a third aspect, the present invention provides a computer device comprising a memory, a processor and a transceiver which are communicatively connected in sequence, wherein the memory is used to store a computer program, the transceiver is used to send and receive messages, and the processor is used to read the computer program to execute the service and middleware association relationship collection method as described in the first aspect or any possible design of the first aspect.

[0026] In a fourth aspect, the present invention provides a computer-readable storage medium having instructions stored thereon, which, when executed on a computer, executes the method for collecting the association relationship between services and middleware as described in the first aspect or any possible design of the first aspect.

[0027] In a fifth aspect, the present invention provides a computer program product, including a computer program or instructions, which, when executed by a computer, implements the method for collecting service and middleware association relationships as described in the first aspect or any possible design of the first aspect.

[0028] Beneficial effects of the above scheme:

[0029] (1) The present invention provides a new solution for automatically collecting the relationship between services and middleware based on Java bytecode enhancement technology, that is, first collecting the service matching information of all services and the middleware matching information of all middleware, and storing the collection results in a database, and then receiving and parsing the service metadata reported by any service through the agent package when starting, so as to obtain the information and middleware metadata of any service, and match the information with the service matching information in the database, and match the middleware metadata with the middleware matching information in the database. If it is found that the information matches the service matching information of a certain service and the middleware metadata matches the middleware matching information of a certain middleware, it is determined that the certain service has an association relationship with the certain middleware. In this way, the purpose of automatically collecting the relationship between services and middleware can be achieved, that is, no manual maintenance is required, which can greatly reduce the manpower demand and avoid manual omissions.

[0030] (2) It can also achieve timeliness and flexibility in responding to middleware changes and avoid waste of resources;

[0031] (3) By adopting Java bytecode enhancement technology, the complexity of docking and the difficulty of going online can be greatly reduced, which is convenient for practical application and promotion. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0033] Figure 1 A flowchart of a method for collecting service and middleware association relationships provided in an embodiment of the present application.

[0034] Figure 2 An example diagram of different metadata reported by different services provided in an embodiment of the present application.

[0035] Figure 3 An example diagram of returning all middleware associated with different services provided in an embodiment of the present application.

[0036] Figure 4 An example diagram of returning all services associated with different middlewares provided in an embodiment of the present application.

[0037] Figure 5 A schematic diagram of the structure of a device for collecting service and middleware association relationships provided in an embodiment of the present application.

[0038] Figure 6 A schematic diagram of the structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the present invention will be briefly introduced below in combination with the drawings and the description of the embodiments or the prior art. Obviously, the following description of the structures of the drawings is only some embodiments of the present invention. For ordinary technicians in this field, other embodiments can be obtained based on these embodiments without creative work. It should be noted that the description of these embodiments is used to help understand the present invention, but does not constitute a limitation of the present invention.

[0040] It should be understood that although the terms first and second, etc. may be used herein to describe various objects, these objects should not be limited by these terms. These terms are only used to distinguish one object from another object. For example, a first object can be referred to as a second object, and similarly, a second object can be referred to as a first object without departing from the scope of the exemplary embodiments of the present invention.

[0041] It should be understood that the term "and / or" that may appear in this document is merely a description of the association relationship between associated objects, indicating that there may be three relationships. For example, A and / or B can indicate three situations: A exists alone, B exists alone, or A and B exist at the same time. For another example, A, B and / or C can indicate the existence of any one of A, B and C or any combination of them. The term " / and" that may appear in this document describes another type of association object relationship, indicating that there may be two relationships. For example, A / and B can indicate two situations: A exists alone or A and B exist at the same time. In addition, the character " / " that may appear in this document generally indicates that the previous and next associated objects are in an "or" relationship.

[0042] Example

[0043] like Figure 1 As shown, the service and middleware association relationship collection method provided in the first aspect of this embodiment can be, but is not limited to, executed by a computer device with certain computing resources, such as a cloud server, a personal computer (PC, a multi-purpose computer with a size, price and performance suitable for personal use; desktops, laptops, small laptops, tablets and ultrabooks are all personal computers), smart phones, personal digital assistants (PDA) or wearable devices. Figure 1 As shown, the service and middleware association relationship collection method may include but is not limited to the following steps S1 to S4.

[0044] S1. Collect service matching information of all services and middleware matching information of all middleware, and store the collection results in a database.

[0045] In step S1, the service matching information is used to participate in service matching, and specifically includes but is not limited to the service name and / or service unique identifier, etc. The middleware matching information is used to participate in middleware matching, and specifically includes but is not limited to the middleware type, middleware IP address, middleware name, middleware unique identifier, CPU parameters used by the middleware, and / or memory parameters used by the middleware, etc. Specifically, the service matching information of all services and the middleware matching information of all middleware can be automatically collected from suppliers (such as Huawei Cloud suppliers or Alibaba Cloud suppliers, etc.) through conventional collection procedures.

[0046] S2. Receive service metadata reported by any service through an agent package when the service is started, wherein the service metadata includes but is not limited to information of the any service and middleware metadata contained in the configuration content of the any service, etc., and the docking information of the agent package is pre-added to the startup parameters of the any service, so as to complete the docking with the agent package when the any service is started, and report the service metadata of the any service through the agent package.

[0047] In step S2, the agent package is a special jar (Java Archive) package / software component that implements Java bytecode enhancement, which is designed to interact with a specific system or service to implement specific functions or services (for example, it can perform various tasks such as system monitoring, performance analysis and security scanning, depending on the purpose of its design and implementation), so it can be applied in this embodiment to report the service metadata of the service when the service is started. The docking information is used to achieve the docking of the service and the agent package, specifically but not limited to the package name of the agent package, and can be manually added to the startup parameters of each service in advance by the maintenance personnel; for example, if the package name of the agent package is "cmdb-agent.jar", the following startup parameter can be added: "-javaagent: / opt / jmx-agent / cmdb-agent.jar". In addition, the information of any of the services will also be used to participate in service matching, and specifically but not limited to including the service name and / or the service unique identifier, etc.; the middleware metadata will also be used to participate in middleware matching, and specifically but not limited to including the middleware type, middleware IP address, middleware name, middleware unique identifier, CPU parameters used by the middleware and / or memory parameters used by the middleware, etc.; different metadata reported by different services, for example Figure 2 shown.

[0048] S3. Parse the service metadata to obtain information of any service and the middleware metadata, and match the information of any service with the service matching information in the database, and match the middleware metadata with the middleware matching information in the database.

[0049] In step S3, the specific means of data analysis and the specific means of information matching are both existing technical means and will not be described in detail here.

[0050] S4. If it is found that the information of any service matches the service matching information of a certain service and the middleware metadata matches the middleware matching information of a certain middleware, it is determined that the certain service has an association relationship with the certain middleware.

[0051] In step S4, since any one of the services belongs to all the services, when all the services are started, it can be automatically determined whether each service in all the services has an association relationship with each middleware in all the middleware, thereby achieving the purpose of automatically collecting the association relationship between services and middleware, that is, there is no need to manually maintain the association relationship between services and middleware, thus avoiding manual omissions. In order to achieve the purpose of querying the association relationship, preferably, after determining that a certain service has an association relationship with a certain middleware, the method also includes: after receiving an association query request for the certain service, returning information on all middleware that has an association relationship with the certain service; Figure 3 As shown, all middlewares associated with different services can be returned; or, after receiving an association query request for a certain middleware, information of all services associated with the certain middleware is returned; as shown Figure 4 As shown, all services associated with different middlewares can be returned.

[0052] In step S4, in order to achieve timeliness and flexibility in responding to middleware changes, preferably, after determining that a certain service is associated with a certain middleware, the method also includes but is not limited to: when it is found that a certain middleware has changed (such as migration, version upgrade, or upgrade configuration, etc.), a notification is issued to restart all services associated with the certain middleware or modify the configuration content of all services associated with the certain middleware. The object of the aforementioned notification can be specifically the business system to which the service belongs. In this way, through the aforementioned notification means, it is possible to avoid production accidents caused by failure to restart the service or modify the corresponding configuration in time due to changes in the middleware.

[0053] After step S3, in order to achieve the purpose of updating the association between the service and the middleware, if the certain service and the certain middleware are predetermined to have an association relationship, and it is currently found that the information of any one of the services matches the service matching information of the certain service and the middleware metadata does not match the middleware matching information of the certain middleware, or the information of any one of the services does not match the service matching information of the certain service and the middleware metadata matches the middleware matching information of the certain middleware, then it is determined that the certain service and the certain middleware no longer have an association relationship.

[0054] Based on the service and middleware association relationship collection method described in the above steps S1 to S4, a new solution for automatically collecting the service and middleware association relationship based on Java bytecode enhancement technology is provided, that is, first collect the service matching information of all services and the middleware matching information of all middleware, and store the collection results in the database, then receive and parse the service metadata reported by any service through the agent package when starting, so as to obtain the information and middleware metadata of any service, and match the information with the service matching information in the database, and match the middleware metadata with the middleware matching information in the database, if it is found that the information matches the service matching information of a certain service and the middleware metadata matches the middleware matching information of a certain middleware, then it is determined that the certain service has an association relationship with the certain middleware, so that the purpose of automatically collecting the service and middleware association relationship can be achieved, that is, no manual maintenance is required, which can greatly reduce the manpower demand and avoid manual omissions. In addition, the timeliness and flexibility of the response to middleware changes can be achieved, and the waste of resources can be avoided. By adopting Java bytecode enhancement technology, the complexity of docking and the difficulty of going online can be greatly reduced, which is convenient for practical application and promotion.

[0055] like Figure 5 As shown, the second aspect of this embodiment provides a virtual device for implementing the service and middleware association relationship collection method described in the first aspect, including an information collection unit, a data receiving unit, a parsing and matching unit, and a relationship determination unit;

[0056] The information collection unit is used to collect service matching information of all services and middleware matching information of all middleware, and store the collection results in a database;

[0057] The data receiving unit is used to receive service metadata reported by any service through an agent package when the service is started, wherein the service metadata includes information of the service and middleware metadata included in the configuration content of the service, and the docking information of the agent package is pre-added to the startup parameters of the service, so as to complete the docking with the agent package when the service is started, and report the service metadata of the service through the agent package;

[0058] The parsing and matching unit is communicatively connected to the information collecting unit and the data receiving unit, respectively, and is used to parse the service metadata to obtain the information of any service and the middleware metadata, and to match the information of any service with the service matching information in the database, and to match the middleware metadata with the middleware matching information in the database;

[0059] The relationship determination unit is communicatively connected to the parsing and matching unit, and is used to determine that the certain service has an association relationship with the certain middleware if it is found that the information of any service matches the service matching information of a certain service and the middleware metadata matches the middleware matching information of a certain middleware.

[0060] The working process, working details and technical effects of the aforementioned device provided in the second aspect of this embodiment can be referred to the service and middleware association relationship collection method described in the first aspect, and will not be repeated here.

[0061] like Figure 6 As shown, the third aspect of this embodiment provides a computer device for executing the service and middleware association relationship collection method as described in the first aspect, including a memory, a processor and a transceiver that are sequentially connected in communication, wherein the memory is used to store a computer program, the transceiver is used to send and receive messages, and the processor is used to read the computer program to execute the service and middleware association relationship collection method as described in the first aspect. For example, the memory may include, but is not limited to, a random access memory (Random-Access Memory, RAM), a read-only memory (Read-Only Memory, ROM), a flash memory (Flash Memory), a first-in-first-out memory (First Input First Output, FIFO) and / or a first-in-last-out memory (First Input Last Output, FILO), etc.; the processor may include, but is not limited to, a microprocessor of the STM32F105 series. In addition, the computer device may also include, but is not limited to, a power module, a display screen and other necessary components.

[0062] The working process, working details and technical effects of the aforementioned computer device provided in the third aspect of this embodiment can be found in the service and middleware association relationship collection method described in the first aspect, and will not be repeated here.

[0063] In a fourth aspect of this embodiment, there is provided a computer-readable storage medium storing instructions including the service and middleware association relationship collection method as described in the first aspect, that is, the computer-readable storage medium stores instructions, and when the instructions are executed on a computer, the service and middleware association relationship collection method as described in the first aspect is executed. The computer-readable storage medium refers to a carrier for storing data, which may include but is not limited to computer-readable storage media such as floppy disks, optical disks, hard disks, flash memory, USB flash drives and / or memory sticks, and the computer may be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices.

[0064] The working process, working details and technical effects of the aforementioned computer-readable storage medium provided in the fourth aspect of this embodiment can be referred to the service and middleware association relationship collection method described in the first aspect, and will not be repeated here.

[0065] In a fifth aspect, this embodiment provides a computer program product, including a computer program or an instruction, which, when executed by a computer, implements the service and middleware association relationship collection method as described in the first aspect. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.

[0066] Finally, it should be noted that the above description is only a preferred embodiment of the present invention and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for collecting association relationships between services and middleware, characterized in that: include: Collect service matching information of all services and middleware matching information of all middleware, and store the collection results in a database; receiving service metadata reported by any service through an agent package when the service is started, wherein the service metadata includes information of the service and middleware metadata included in the configuration content of the service, and the docking information of the agent package is pre-added to the startup parameters of the service, so as to complete the docking with the agent package when the service is started, and reporting the service metadata of the service through the agent package; Parsing the service metadata to obtain information of any service and the middleware metadata, and matching the information of any service with the service matching information in the database, and matching the middleware metadata with the middleware matching information in the database; If it is found that the information of any one of the services matches the service matching information of a certain service and the middleware metadata matches the middleware matching information of a certain middleware, it is determined that the certain service and the certain middleware have an association relationship.

2. The method for collecting service and middleware association relationships according to claim 1, characterized in that: After determining that the certain service has an association relationship with the certain middleware, the method further includes: After receiving the association query request for the certain service, information of all middlewares that have an association relationship with the certain service is returned.

3. The method for collecting the relationship between services and middleware according to claim 1, characterized in that: After determining that the certain service has an association relationship with the certain middleware, the method further includes: After receiving the association query request for the certain middleware, information of all services associated with the certain middleware is returned.

4. The method for collecting service and middleware association relationships according to claim 1, characterized in that: After determining that the certain service has an association relationship with the certain middleware, the method further includes: When it is found that a certain middleware has been changed, a notification is issued to restart all services associated with the certain middleware or to modify configuration contents of all services associated with the certain middleware.

5. The method for collecting the relationship between services and middleware according to claim 1, characterized in that: The service matching information includes a service name and / or a service unique identifier.

6. The method for collecting the relationship between services and middleware according to claim 1, characterized in that: The middleware matching information includes the middleware type, the middleware IP address, the middleware name, the middleware unique identifier, the parameters of the CPU used by the middleware and / or the parameters of the memory used by the middleware.

7. A device for collecting associations between services and middleware, characterized in that: It includes an information collection unit, a data receiving unit, a parsing and matching unit, and a relationship determination unit; The information collection unit is used to collect service matching information of all services and middleware matching information of all middleware, and store the collection results in a database; The data receiving unit is used to receive service metadata reported by any service through an agent package when the service is started, wherein the service metadata includes information of the service and middleware metadata included in the configuration content of the service, and the docking information of the agent package is pre-added to the startup parameters of the service, so as to complete the docking with the agent package when the service is started, and report the service metadata of the service through the agent package; The parsing and matching unit is communicatively connected to the information collecting unit and the data receiving unit, respectively, and is used to parse the service metadata to obtain the information of any service and the middleware metadata, and to match the information of any service with the service matching information in the database, and to match the middleware metadata with the middleware matching information in the database; The relationship determination unit is communicatively connected to the parsing and matching unit, and is used to determine that the certain service has an association relationship with the certain middleware if it is found that the information of any service matches the service matching information of a certain service and the middleware metadata matches the middleware matching information of a certain middleware.

8. A computer device, characterized in that: It includes a memory, a processor and a transceiver which are communicatively connected in sequence, wherein the memory is used to store a computer program, the transceiver is used to send and receive messages, and the processor is used to read the computer program to execute the service and middleware association relationship collection method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed on a computer, the method for collecting the association relationship between services and middleware according to any one of claims 1 to 6 is executed.

10. A computer program product comprising a computer program or instructions, characterized in that The computer program or the instruction, when executed by a computer, implements the method for collecting the association relationship between services and middleware as claimed in any one of claims 1 to 6.

Images