Configuration information acquisition method and system and medium

Abstract

The invention provides a configuration information acquisition method and system and a medium, the configuration information acquisition method comprises the following steps: determining whether an automatic probe can be deployed on a device, the automatic probe comprising a preset program, the preset program comprising an acquisition rule for a component in the device, and the acquisition rule comprising an acquisition frequency and a data acquisition range; when it is determined that the equipment can deploy the automatic probe, deploying the automatic probe for the equipment, and enabling the automatic probe to collect component configuration information according to the collection rule; and when determining that the equipment cannot deploy the automatic probe, acquiring component configuration information through the application program interface and / or the access configuration library. Through the method, accurate acquisition and batch acquisition of the component configuration information of any component can be realized.

Description

Technical Field

[0001] The present application mainly relates to configuration information collection technology, and in particular to a configuration information collection method, system and medium. Background Art

[0002] The information technology application innovation industry, namely the ICT industry, includes multiple technical routes. Therefore, the configuration information storage method, interface specifications and data format of the components related to the information technology application innovation industry, namely the ICT components, may be different.

[0003] Existing configuration information collection technologies and methods are often developed based on traditional IT architectures and have certain limitations when facing the trusted architecture. For example, traditional configuration information collection technologies may focus on supporting Windows or Linux systems, while supporting trusted components such as domestic operating systems, databases, and middleware in the trusted industry is relatively weak. This results in some key configuration information not being collected or being collected incompletely in the trusted environment, which in turn has a great adverse impact on daily operation and maintenance management and monitoring effects. On the one hand, the lack of key configuration information may cause operation and maintenance personnel to lack the necessary reference basis when troubleshooting, thereby prolonging the time for fault recovery. On the other hand, incomplete configuration information data may greatly reduce the accuracy of the monitoring system and fail to reflect the true status of the system in real time. In short, facing the different components existing in various devices, the inability to fully collect the configuration information of the components not only increases the difficulty of operation and maintenance, but also may pose a potential threat to business continuity and system stability. Summary of the Invention

[0004] The technical problem to be solved by the present application is to provide a configuration information collection method, system and medium to achieve unified collection of configuration information of components based on different technical routes.

[0005] In order to solve the above technical problems, the present application provides a configuration information collection method, which is suitable for collecting component configuration information of components in a device, and the method includes the following steps: judging whether the device can be deployed with an automated probe, wherein the automated probe includes a preset program, the preset program includes collection rules for components in the device, and the collection rules include collection frequency and data collection range; when it is determined that the device can be deployed with an automated probe, deploying the automated probe on the device, and enabling the automated probe to collect component configuration information according to the collection rules; when it is determined that the device cannot be deployed with an automated probe, obtaining component configuration information through an application program interface and / or accessing a configuration library.

[0006] Optionally, when automated probes are deployed on multiple devices, the automated probes corresponding to the respective devices may have the same or different versions, and when the automated probes have different versions, the collection rules corresponding to the automated probes with different versions may be different.

[0007] Optionally, it also includes updating the version of the automation probe on any device when the automation probe on any of the multiple devices needs to adapt to a new component, and judging in turn whether the automation probes on the remaining devices have updated versions, wherein the updated automation probe includes the collection rules corresponding to the new component that needs to be adapted.

[0008] Optionally, the step of the automated probe collecting component configuration information according to the collection rules further includes: regularly collecting and storing the component configuration information through the automated probe; comparing whether there is a difference between the configuration information collected last time and the latest collected configuration information through the automated probe, and if the comparison result is yes, the difference between the configuration information collected last time and the configuration information collected last time is used as the component configuration information.

[0009] Optionally, the component configuration information includes one or more of basic configuration information and deep configuration information, the basic configuration information includes one or more of version number, installation path, running status, process port number and operating system type, and the deep configuration information includes one or more of detailed setting options, security parameters and dependencies.

[0010] Optionally, when the component is a middleware and the basic configuration information includes a version number, an installation path, a process port number, and an operating system type, the configuration information collection method further includes obtaining the basic configuration information through the following steps: obtaining the process result of the component through a process query command; parsing the process result to obtain the installation path of the component; parsing the configuration file under the installation path to obtain the process port number of the component; obtaining the version number of the component through a version number query command; and querying the system information file to obtain the operating system type of the device where the component is located.

[0011] Optionally, when the configuration information includes the running status and the process number of the component in the last collected configuration information exists, the method also includes determining whether the process number in the latest collected configuration information exists. If the judgment result is yes, the running status in the latest collected configuration information is set to alive; if the judgment result is no, the running status in the latest collected configuration information is set to dormant.

[0012] In order to solve the above technical problems, the present application provides a configuration information management system, which is suitable for collecting component configuration information of components in a device. The configuration information management system includes: a management terminal and at least one automated probe, the automated probe includes a preset program, the preset program includes collection rules for components in the device, and the collection rules include collection frequency and data collection range, wherein the automated probe is suitable for collecting component configuration information according to the collection rules; the management terminal is respectively communicated with each automated probe, and the management terminal is suitable for judging whether the device can be deployed with an automated probe. If the judgment result is yes, the automated probe is deployed on the device to obtain component configuration information. If the judgment result is otherwise, the component configuration information is obtained through an application program interface and / or access to a configuration library.

[0013] Optionally, the automated probe is also suitable for: encrypting the component configuration information and transmitting it to the management terminal; the management terminal includes a filter list, and after receiving the encrypted component configuration information, the management terminal is also suitable for: decrypting the encrypted component configuration information, and filtering out unnecessary component configuration information from the decrypted component configuration information according to the filter list, and storing the filtered component configuration information.

[0014] Optionally, when the management terminal deploys automated probes for multiple devices, the automated probes corresponding to the various devices may have the same or different versions, and when the automated probes have different versions, the collection rules corresponding to the automated probes with different versions may be different.

[0015] Optionally, the management terminal is also suitable for: when the automation probe on any one of the multiple devices needs to adapt to a new component, updating the version of the automation probe on any one device, and judging in turn whether the automation probes on the remaining devices have updated versions, wherein the updated version of the automation probe includes the collection rules corresponding to the new component that needs to be adapted.

[0016] Optionally, the automated probe is specifically suitable for: regularly collecting and storing component configuration information; comparing whether there is a difference between the configuration information collected last time and the configuration information collected latest, and if the comparison result is yes, using the difference between the configuration information collected last time and the configuration information collected latest as the component configuration information.

[0017] Optionally, the component configuration information includes one or more of basic configuration information and deep configuration information, the basic configuration information includes one or more of version number, installation path, running status, process port number and operating system type, and the deep configuration information includes one or more of detailed setting options, security parameters and dependencies.

[0018] Optionally, the automated probe is also used to: when the configuration information includes the running status and the process number of the component in the last collected configuration information exists, determine whether the process number in the latest collected configuration information exists; if the judgment result is yes, set the running status in the latest collected configuration information to alive; if the judgment result is no, set the running status in the latest collected configuration information to dormant.

[0019] To solve the above technical problems, the present application provides a computer-readable medium storing computer program code, which implements the above configuration information collection method when executed by a processor.

[0020] Compared with the existing technology, the present application has the following advantages: by deploying automated probes with collection rules on the device, the component configuration information of each component that needs to be collected on the device is obtained in a targeted manner; for devices where automated probes cannot be deployed, the component configuration information of the components is obtained through the application program interface and access to the configuration library, thereby realizing accurate and batch acquisition of the component configuration information of any component. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The accompanying drawings are included to provide a further understanding of the present application. They are incorporated into and constitute a part of this application. The accompanying drawings illustrate embodiments of the present application and, together with this specification, serve to explain the principles of the present application. In the accompanying drawings:

[0022] Figure 1 is a flow chart of a configuration information collection method according to an embodiment of the present application;

[0023] Figure 2 Yes Figure 1 A schematic diagram of a process for collecting component configuration information of a component through an automated probe in the illustrated embodiment;

[0024] Figure 3 Yes Figure 2 A schematic diagram of a process for an automated probe to obtain some basic configuration information according to the embodiment shown;

[0025] Figure 4 is a structural diagram of a configuration information collection system according to an embodiment of the present application; and

[0026] Figure 5 Yes Figure 4 The illustrated embodiment is a flow chart of a management terminal of a configuration information collection system collecting and managing configuration information of each component in each device. DETAILED DESCRIPTION

[0027] To more clearly illustrate the technical solutions of the embodiments of this application, the following is a brief introduction to the drawings required for describing the embodiments. Obviously, the drawings described below are merely examples or embodiments of this application. Those skilled in the art can apply this application to other similar scenarios based on these drawings without inventive effort. Unless otherwise apparent from the context or otherwise noted, the same reference numerals in the figures represent the same structure or operation.

[0028] As used in this application and the claims, unless the context clearly indicates otherwise, the words "a," "an," "an," and / or "the" are not intended to refer to the singular but may include the plural. Generally speaking, the terms "comprises" and "include" only indicate the inclusion of the steps and elements specifically identified, and these steps and elements do not constitute an exclusive list. A method or apparatus may also include other steps or elements.

[0029] Unless otherwise specifically stated, the relative arrangement of the parts and steps, numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present application. At the same time, it should be understood that, for ease of description, the sizes of the various parts shown in the drawings are not drawn according to actual proportional relationships. The techniques, methods and equipment known to those of ordinary skill in the relevant art may not be discussed in detail, but where appropriate, the techniques, methods and equipment should be considered as part of the authorization specification. In all examples shown and discussed here, any specific values ​​should be interpreted as being merely exemplary and not as limitations. Therefore, other examples of the exemplary embodiments may have different values. It should be noted that similar numbers and letters represent similar items in the following figures, and therefore, once an item is defined in one figure, it does not need to be further discussed in subsequent figures.

[0030] Flowcharts are used in this application to illustrate the operations performed by systems according to embodiments of the present application. It should be understood that the preceding or following operations are not necessarily performed in exact order. Instead, the various steps may be processed in reverse order or simultaneously. Furthermore, other operations may be added to these processes, or one or more operations may be removed from these processes.

[0031] First, the components in this application may include servers, network equipment, operating systems, middleware, databases, etc. It should be noted that the components of this application can be either trusted components or non-trusted components, that is, this application does not limit the technical routes corresponding to the components. The following describes the technical solution of this application in conjunction with specific embodiments.

[0032] Example 1

[0033] Figure 1This is a flow chart of a configuration information collection method according to an embodiment of the present application. Figure 1 As shown, the configuration information collection method 100 includes the following steps. Step S11 is to determine whether the device can be deployed with an automated probe. In this embodiment, the automated probe includes a preset program, which includes collection rules for components in the device, and the collection rules include collection frequency and data collection range. Figure 1 , step S12 is to deploy an automated probe on the device when it is determined that the device can be deployed with an automated probe, and to enable the automated probe to collect component configuration information according to the collection rules. Among them, the automated probe of this embodiment regularly collects component configuration information of the component according to the collection frequency, and collects specific component configuration information of the component according to the data collection scope. The component configuration information in this embodiment includes basic configuration information and deep configuration information. The basic configuration information includes version number, installation path, running status, process port number and operating system type, etc. The deep configuration information includes detailed setting options, security parameters and dependencies, etc. It should be noted that in other embodiments of the present application, each automated probe collects basic configuration information and selectively collects deep configuration information. While ensuring that no important configuration information is missed, it also avoids unnecessary data redundancy and improves the efficiency and accuracy of data processing. In addition, the present application does not limit the specific content of the component configuration information by the embodiments.

[0034] In this embodiment, the automated probes have different versions, and the collection rules corresponding to the automated probes with different versions are different. It is understandable that the components corresponding to the automated probes with different versions are also different, and a device may have multiple different components whose component configuration information needs to be collected. Therefore, in this embodiment, when automated probes are deployed on multiple devices, the automated probes corresponding to each device have the same or different versions. Specifically, in this embodiment, based on the components that need to be collected on each device, automated probes with appropriate versions are deployed on the device, so that the required component configuration information can be flexibly and accurately collected from different devices.

[0035] In this embodiment, components on a device can be updated, deleted, or newly added. This means that after a period of operation, the automated probe deployed on that device may be unable to accurately collect configuration information for some components, requiring re-adaptation of those components. To address this issue, in this embodiment, when the automated probe on any of the multiple devices needs to adapt to a new component, the version of the automated probe on that device is updated. In this embodiment, the updated automated probe includes the collection rules corresponding to the new component that needs to be adapted. It will be appreciated that in this embodiment, the collection rules for the automated probe on that device can be updated with the specific parameters of the new component, thereby updating the version of the automated probe. In this embodiment, a different version of the automated probe on another device that can adapt to the new component can also be deployed on that device to replace the original automated probe, thereby updating the version of the automated probe on that device. In this embodiment, after the automated probe on a device is updated, a check is performed to determine whether the automated probes on the remaining devices have been updated. If this check is successful, the automated probe on that device is also updated. This update method allows the automated probe version to be iteratively optimized as the components on the device change, thereby maintaining accurate collection of component configuration information.

[0036] Further reference below Figure 2 , the steps of collecting component configuration information of the component according to the collection rules by the automated probe in the configuration information collection method 100 are described in detail. Figure 2 As shown, step S21 involves periodically collecting and storing component configuration information via an automated probe. It should be noted that in step S21, the automated probe collects the aforementioned basic configuration information and deep configuration information according to the collection rules. Step S22 involves comparing the last collected configuration information with the latest collected configuration information to determine if there are any differences. If the comparison result is yes, the difference between the latest collected configuration information and the last collected configuration information is used as the component configuration information. It will be appreciated that in this embodiment, the automated probe performs a difference comparison and retains at least the most recently collected configuration information, i.e., the currently collected configuration information, and the previously collected configuration information, during each difference comparison. For example, for the same component, if the previously collected configuration information A includes the operating system type Linux and version number A1, and the currently collected configuration information B includes the operating type Linux and version number A2, the automated probe uses version number A2 as the current component configuration information. Through this component configuration information collection method, the automated probe can obtain modified configuration information and filter out large amounts of duplicate data, thereby streamlining the content of each collected component configuration information. It is understandable that when there is no difference, the component configuration information collected by the automated probe is empty.

[0037] The following is further combined Figure 3 , describes how the automated probe obtains some configuration information in step 21 above. Figure 3 As shown, when the component is a middleware and the basic configuration information includes the version number, installation path, process port number and operating system type, the automated probe obtains the above basic configuration information including the following steps. Step S31 is to obtain the process result of the component through the process query command. Step S32 is to parse the process result to obtain the installation path of the component. Step S33 is to parse the configuration file under the installation path to obtain the process port number of the component. Step S34 is to obtain the version number of the component through the version number query command. Step S35 is to query the system information file to obtain the operating system type of the device where the component is located. For example, for the trusted middleware component Baolande, the automated probe obtains the process result through the process query command "ps-ef|grep'instancename server-read-stdin true start'|grep-v grep" in step S31. The automated probe also parses the server.config configuration file under the installation path in step S33 to obtain the process port number of Baolande. The automated probe then queries the version number of the Boland device in step S34 using the command "cd / app / bes / bes9.5 / bin&&. / lmadm view-lic." Finally, in step S35, the automated probe queries the os-release file in the / etc directory to obtain the operating system type of the device where Boland is installed.

[0038] Regarding the process of the automated probe acquiring configuration information, it should also be noted that when the configuration information includes the running status and the process number of the component in the last collected configuration information exists, the automated probe determines whether the process number in the latest collected configuration information exists. If the judgment result is yes, the running status in the latest collected configuration information is set to alive; if the judgment result is no, the running status in the latest collected configuration information is set to dormant. Specifically, in this embodiment, the latest collected process number is compared with the process number collected last time. If the same process number exists, the corresponding running status is alive. If the process number that existed in the previous time does not exist in this time, the corresponding running status is dormant. It can be understood that if a process number that did not exist in the previous time exists in this time, the corresponding running status is alive.

[0039] Continue to refer to Figure 1In step S13, when it is determined that the device cannot deploy an automated probe, component configuration information is obtained through the application program interface and / or access to the configuration library. For example, in this embodiment, the virtualization cluster, virtualization host, virtualization storage LUN, virtual machine list information, etc. of the Xinchuang Cloud can be obtained through the application program interface API.

[0040] Example 2

[0041] Figure 4 This is a structural diagram of the configuration information management system according to an embodiment of the present application. Figure 4 As shown, the configuration information management system 200 is suitable for collecting component configuration information of components in the device 300. It should be noted that the configuration information management system 200 can collect component configuration information for multiple devices 300, and each device 300 includes at least one component. Figure 4 The configuration information management system 200 includes a management terminal 201 and multiple automated probes 202, each of which corresponds to a device 300. It should be noted that the automated probe 202 of this embodiment includes the various configurations and functions of the automated probe described in Example 1, and the same parts will not be repeated here. In addition, in this embodiment, the configuration information management system 200 corresponds to multiple devices 300, but in other embodiments of the present application, the configuration management system may also correspond to only one device. The following describes the functions of the management terminal 201 and the automated probe 202 that cooperates with the management terminal 201.

[0042] First, refer to Figure 4 and Figure 5 In this embodiment, the process of the management terminal 201 collecting and managing the configuration information of each component in each device 300 includes the following steps. Step S41 is that the management terminal 201 determines whether each device 300 can be deployed with an automated probe. Step S42 is that if the judgment result is yes, the management terminal 201 deploys the automated probe 202 to the device 300 to obtain the component configuration information. In this embodiment, the management terminal 201 is respectively connected to each automated probe 202 in communication. Step S43 is that if the judgment result is no, the management terminal 201 obtains the component configuration information through the application interface and / or accesses the configuration library. It can be understood that Figure 4The device 300 that does not include the automated probe 202 is the device 300 that cannot deploy the automated probe 202. For example, when the device 300 that cannot deploy the automated probe includes the cloud macro platform, in step S43, the management terminal 201 obtains the registered Xinchuang cloud macro platform login address through query every day, and then obtains the virtualization cluster, the number of cluster servers, the number of cluster physical cores, the cluster physical memory, the number of allocated virtual machines, the address of the virtualization platform to which it belongs, and other component configuration information by calling the virtualization cluster list interface; obtains the host machine IP address, the name of the virtualization cluster to which it belongs, the address of the virtualization platform to which it belongs, the server to which it belongs, the number of allocated virtualizations, and other component configuration information by calling the virtualization host list interface; obtains the virtualization storage name, lun name, total storage capacity, remaining capacity, and other component configuration information by calling the virtualization storage LUN list; obtains the allocated virtualization host uuid, virtualization name, virtual machine IP, number of virtual machine CPU cores, number of memory, disk capacity, virtualization cluster to which it belongs, virtualization host to which it belongs, and virtualization platform to which it belongs, and other component configuration information by calling the virtual machine list.

[0043] In this embodiment, for a device 300 deployed with an automated probe 202, the automated probe 202 collects the component configuration information of the component and sends the component configuration information to the management terminal 201, so that the management terminal 201 receives the component configuration information on the device 300. In this embodiment, the automated probe 202 collects the component configuration information once a day. It should be noted that in other embodiments of the present application, the automated probe may have a longer or shorter collection interval. In addition, referring to Example 1, the component configuration information fed back by the automated probe 202 only contains the changed configuration information, thereby optimizing the amount of transmitted data and improving data accuracy, and also facilitating the management terminal 201 to process after receiving the component configuration information. Since the component configuration information needs to be sent from the automated probe 202 to the management terminal 201, and the component configuration information contains sensitive information of the component, the automated probe 202 in this embodiment is also suitable for encrypting the component configuration information and transmitting it to the management terminal 201, thereby preventing the leakage of the component configuration information and improving security.

[0044] Continue to refer to Figure 4 and Figure 5In step S44, the management terminal 201 receives and processes the component configuration information on each device 300. It is understandable that in this embodiment, the management terminal 201 may manage hundreds of devices 300 simultaneously, potentially requiring the processing of configuration information for thousands of components. Furthermore, due to component updates, the corresponding configuration information may also change. This situation can result in inaccurate data collection relying solely on the automated probe 202. Specifically, the component configuration information collected by the automated probe 202 contains redundant data, which in turn wastes additional computing resources for the management terminal 201. Furthermore, operations and maintenance managers may adjust the configuration information to be collected based on their needs, so the management terminal 201 needs to process the received component configuration information. To this end, in this embodiment, the management terminal 201 also includes a filter list. After receiving the encrypted component configuration information from the automated probe 202, the management terminal 201 is further configured to: decrypt the encrypted component configuration information and filter out unnecessary component configuration information from the decrypted component configuration information based on the filter list. Accordingly, after the management terminal 201 obtains component configuration information through the application program interface or by accessing the configuration repository, it also uses the filter list to filter out unnecessary component configuration information. Through the above settings, the management terminal 201 can uniformly filter the component configuration information of various components received. In this embodiment, the management terminal 201 also verifies the filtered component configuration information to ensure the completeness and accuracy of the component configuration information. Step S45 is that the management terminal 201 stores the filtered component configuration information. In this embodiment, the management terminal 201 stores all the configuration information of each component that needs to be monitored. Exemplarily, the configuration information of the component includes CI name, middleware type, operating system, operating system bit number, software OS account, IP address, service port, service / instance name, application account, installation path, version number, host, process status, JDK information, last modified person, instance type, uuid, ip address, CPU allocation size, total disk capacity, connected virtualization storage, virtualization cluster, etc. In step S45, the management terminal 201 updates the stored configuration information based on the filtered component configuration information, thereby ensuring that the data of the configuration information of each component stored is the latest. It can be understood that the management terminal 201 processes the component configuration information accordingly through step S44, filters out unnecessary component configuration information and verifies the integrity and accuracy of the data. While effectively utilizing computing resources, it also avoids the pollution of stored data by abnormal component configuration information, and improves the credibility of the component configuration information updated by the management terminal 201 in step S45.

[0045] Continue to refer to Figure 4For example, when the version of the automation probe 202 needs to be updated in the first embodiment, the management terminal 201 of this embodiment updates the version of the automation probe 202 in the corresponding device 300. Specifically, the management terminal 201 can send the collection rules for the new components that need to be adapted to the automation probe 202 to achieve the version update of the automation probe 202. Alternatively, the management terminal 201 can directly retrieve and select the collection rules of the automation probe 202 in other devices 300 that can adapt to all components on the device 300, and send the collection rules to the automation probe 202 that needs to be updated, so as to completely replace the collection rules of the automation probe 202, thereby achieving the version update.

[0046] In addition, the present application also proposes a computer-readable medium storing computer program code, which implements the above-mentioned configuration information collection method when executed by a processor.

[0047] The basic concepts have been described above. It will be apparent to those skilled in the art that the above disclosures are merely examples and do not limit the present application. Although not explicitly stated herein, those skilled in the art may make various modifications, improvements, and revisions to the present application. Such modifications, improvements, and revisions are suggested in the present application and remain within the spirit and scope of the exemplary embodiments of the present application.

[0048] At the same time, this application uses specific terms to describe the embodiments of this application. For example, "one embodiment," "an embodiment," and / or "some embodiments" refer to a certain feature, structure, or characteristic related to at least one embodiment of this application. Therefore, it should be emphasized and noted that "one embodiment," "an embodiment," or "an alternative embodiment" mentioned twice or multiple times in different locations in this specification does not necessarily refer to the same embodiment. In addition, certain features, structures, or characteristics in one or more embodiments of this application may be appropriately combined.

[0049] Some aspects of the present application can be performed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The above hardware or software can be referred to as "data blocks", "modules", "engines", "units", "components" or "systems". The processor can be one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DAPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors or combinations thereof. In addition, various aspects of the present application may be expressed as computer products located in one or more computer-readable media, which include computer-readable program code. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, tapes...), optical disks (e.g., compact disks CDs, digital versatile disks DVDs...), smart cards, and flash memory devices (e.g., cards, sticks, key drives...).

[0050] A computer-readable medium may include a propagated data signal embodying computer program code, for example, in baseband or as part of a carrier wave. The propagated signal may be in a variety of forms, including electromagnetic, optical, etc., or a suitable combination thereof. A computer-readable medium may be any computer-readable medium other than a computer-readable storage medium that can be connected to an instruction execution system, apparatus, or device to communicate, propagate, or transmit the program for use. The program code on the computer-readable medium may be transmitted via any suitable medium, including radio, cable, fiber optic cable, radio frequency signal, or similar medium, or any combination of the above.

[0051] Similarly, it should be noted that, in order to simplify the description of this application and thus facilitate understanding of one or more embodiments of the application, the foregoing description of the embodiments of this application sometimes combines multiple features into a single embodiment, figure, or description thereof. However, this disclosure method does not mean that the subject matter of this application requires more features than those recited in the claims. In fact, the features of an embodiment may be fewer than all the features of the individual embodiments disclosed above.

[0052] Although the present application has been described with reference to the current specific embodiments, ordinary technicians in this technical field should recognize that the above embodiments are only used to illustrate the present application, and various equivalent changes or substitutions can be made without departing from the spirit of the present application. Therefore, as long as the changes and modifications to the above embodiments are within the scope of the essential spirit of the present application, they will fall within the scope of the claims of the present application.

Claims

1. A configuration information collection method, characterized in that: Suitable for collecting component configuration information of components in a device, the method comprises the following steps: Determining whether an automated probe can be deployed on the device, wherein the automated probe includes a preset program, the preset program includes a collection rule for the component in the device, and the collection rule includes a collection frequency and a data collection range; When it is determined that the device can be deployed with an automated probe, deploying the automated probe on the device, and enabling the automated probe to collect the component configuration information according to the collection rule; When it is determined that the automated probe cannot be deployed on the device, the component configuration information is obtained through an application program interface and / or by accessing a configuration library.

2. The configuration information collection method according to claim 1, wherein: When the automated probes are deployed on a plurality of the devices, the automated probes corresponding to the respective devices may have the same or different versions, and when the automated probes have different versions, the collection rules corresponding to the automated probes with different versions may be different.

3. The configuration information collection method according to claim 2, wherein: It also includes updating the version of the automation probe on any one of the multiple devices when the automation probe on the one device needs to adapt to the new component, and judging in turn whether the automation probes on the remaining devices have updated their versions, wherein the automation probe after the updated version includes the collection rules corresponding to the new component that needs to be adapted.

4. The configuration information collection method according to claim 1, wherein: The step of the automated probe collecting the component configuration information according to the collection rule further includes: Periodically collecting and storing configuration information of the components through the automated probe; The automated probe is used to compare the configuration information collected last time with the configuration information collected most recently to determine if there is any difference. If yes, the difference between the configuration information collected most recently and the configuration information collected last time is used as the component configuration information.

5. The configuration information collection method according to claim 4, wherein: The component configuration information includes one or more of basic configuration information and deep configuration information. The basic configuration information includes one or more of version number, installation path, running status, process port number and operating system type. The deep configuration information includes one or more of detailed setting options, security parameters and dependencies.

6. The configuration information collection method according to claim 5, wherein: When the component is middleware and the basic configuration information includes the version number, the installation path, the process port number, and the operating system type, the configuration information collection method further includes obtaining the basic configuration information through the following steps: Obtain the process result of the component through a process query command; Parsing the process result to obtain the installation path of the component; Parsing the configuration file under the installation path to obtain the process port number of the component; Obtain the version number of the component through a version number query command; Query a system information file to obtain the operating system type of the device where the component is located.

7. The configuration information collection method according to claim 5, wherein: When the configuration information includes the running status and the process number of the component in the last collected configuration information exists, the method further includes determining whether the process number in the latest collected configuration information exists; if the determination result is yes, setting the running status in the latest collected configuration information to alive; if the determination result is no, setting the running status in the latest collected configuration information to dormant.

8. A configuration information management system, characterized in that: The configuration information management system is adapted to collect component configuration information of components in a device, the configuration information management system comprising: a management terminal and at least one automated probe, the automated probe comprising a preset program, the preset program comprising collection rules for the components in the device, and the collection rules comprising a collection frequency and a data collection range, wherein the automated probe is adapted to collect the component configuration information according to the collection rule; The management terminal is respectively connected to each of the automated probes for communication, and is suitable for determining whether the device can be deployed with an automated probe. If the determination result is yes, the automated probe is deployed on the device to obtain the component configuration information. If the determination result is no, the component configuration information is obtained through an application program interface and / or access to a configuration library.

9. The configuration information management system according to claim 8, wherein: The automated probe is further adapted to: encrypt the component configuration information and transmit it to the management terminal; The management terminal includes a filter list. After receiving the encrypted component configuration information, the management terminal is also suitable for: decrypting the encrypted component configuration information, filtering out unnecessary component configuration information from the decrypted component configuration information according to the filter list, and storing the filtered component configuration information.

10. The configuration information management system according to claim 8, wherein: When the management terminal deploys the automated probes to multiple devices, the automated probes corresponding to the devices have the same or different versions, and when the automated probes have different versions, the collection rules corresponding to the automated probes with different versions are different.

11. The configuration information management system according to claim 10, wherein: The management terminal is also suitable for: when the automation probe on any one of the multiple devices needs to adapt to the new component, updating the version of the automation probe on any one of the multiple devices, and judging in turn whether the automation probes on the remaining devices have updated their versions, wherein the automation probe after the updated version includes the collection rules corresponding to the new component that needs to be adapted.

12. The configuration information management system according to claim 8, wherein: The automated probe is particularly suitable for: Periodically collecting and storing configuration information of the components; Compare the configuration information collected last time with the configuration information collected most recently to determine whether there is a difference. If yes, use the difference between the configuration information collected most recently and the configuration information collected most recently as the component configuration information.

13. The configuration information management system according to claim 12, wherein: The component configuration information includes one or more of basic configuration information and deep configuration information. The basic configuration information includes one or more of version number, installation path, running status, process port number and operating system type. The deep configuration information includes one or more of detailed setting options, security parameters and dependencies.

14. The configuration information management system according to claim 13, wherein: The automated probe is further configured to: when the configuration information includes the running status and the process ID of the component in the last collected configuration information exists, determine whether the process ID exists in the latest collected configuration information; if the determination result is yes, set the running status in the latest collected configuration information to alive; If the judgment result is no, the running state in the latest collected configuration information is set to sleep.

15. A computer-readable medium storing computer program codes, wherein the computer program codes, when executed by a processor, implement the configuration information collection method according to any one of claims 1 to 7.

Images