CN110766374A

CN110766374A - Asset automation control method, device, system, equipment and storage medium

Info

Publication number: CN110766374A
Application number: CN201910831530.3A
Authority: CN
Inventors: 蔡顺志
Original assignee: Huayun Data (xiamen) Network Co Ltd
Current assignee: Huayun Data (xiamen) Network Co Ltd
Priority date: 2019-09-04
Filing date: 2019-09-04
Publication date: 2020-02-07

Abstract

The application provides an asset automation control method, device, system, equipment and storage medium, which comprises the steps of receiving asset change information (carrying information of changed assets in the asset change information) sent by an asset management module, determining to-be-executed operation corresponding to the asset change information from a preset operation table according to the asset change information, and further operating the changed assets according to the to-be-executed operation. Therefore, the automatic operation and maintenance of the assets are realized, and the method can be applied to the scene of operation and maintenance of large computer clusters. And because the operation and maintenance are automatic, the method has the advantages of high operation and maintenance efficiency and low possibility of errors. In addition, the operation to be executed corresponding to the asset transition information is determined in the embodiment of the application, so that the operation to be executed later is matched with the received asset transition information, and the operation and maintenance reliability of the asset is improved.

Description

Asset automation control method, device, system, equipment and storage medium

Technical Field

The application relates to the technical field of operation and maintenance, in particular to an asset automation control method, device, system, equipment and storage medium.

Background

With the rapid and continuous development of the information age, IT operation and maintenance have become the most important components in IT services. In recent years, technologies such as cloud computing and big data are mature day by day, and automation operation and maintenance of production and application are pushed to the wave tip of the tuyere. In the conventional operation and maintenance mode, the assets to be managed and controlled are logged in manually for operation and maintenance operation, and for a large computer cluster, the operation and maintenance efficiency is very low and errors are easy to make mistakes, so that the demand of automatically managing and controlling the assets is urgent.

Disclosure of Invention

An object of the embodiments of the present application is to provide an asset automation control method, apparatus, system, device, and storage medium, so as to solve the problems in the related art that, for a large computer cluster, operation and maintenance efficiency is very low and errors are easily caused.

The embodiment of the application provides an asset automation control method, which comprises the following steps: receiving asset change information sent by an asset management module; the asset transition information carries information of the asset which is changed; determining an operation to be executed corresponding to the asset change information from a preset operation table according to the asset change information; and operating the changed assets according to the operation to be executed.

In the implementation process, after the asset change information sent by the asset management module is received, the to-be-executed operation corresponding to the asset change information can be automatically determined from the preset operation table according to the asset change information, and the asset changed is operated according to the to-be-executed operation, so that the automatic operation and maintenance of the asset are realized, and the method can be applied to a scene of performing operation and maintenance on a large computer cluster. And because the operation and maintenance are automatic, the method has the advantages of high operation and maintenance efficiency and low possibility of errors. In addition, the operation to be executed corresponding to the asset transition information is determined in the embodiment of the application, so that the operation to be executed later is matched with the received asset transition information, and the operation and maintenance reliability of the asset is improved.

Further, the asset transition information also carries the asset status of the asset that has transitioned; the asset change information is newly added assets; the determining of the operation to be executed corresponding to the asset transition information includes: determining an operation to be executed corresponding to the asset transition information, and deploying a monitoring client on the asset which is changed when the asset state of the asset which is changed is a starting state; and the changed assets are newly added assets.

In the implementation process, when the new asset is added, the asset management module sends asset change information of 'new asset' and carries the asset state of the new asset. And when the asset state of the newly added asset is started, the monitoring client is deployed on the newly added asset, so that the newly added asset is monitored. The whole process is automatically triggered through the asset change information sent by the asset management module and automatically deployed, so that the method is simple to implement, and the deployment process of the monitoring client is simple and reliable.

Further, the asset transition information is that the asset state of the asset undergoing transition is changed into an enabled state; the determining of the operation to be executed corresponding to the asset transition information includes: and determining that the operation to be executed corresponding to the asset transition information is to deploy a monitoring client on the asset which is transitioned.

It should be noted that, in the embodiment of the present application, the asset management module is used for managing assets. When the asset information of the asset is changed, the asset management module sends the asset change information. In the implementation process, when the asset state of the asset is changed into the enabled state, the asset management module sends asset change information informing of the asset change information. At this time, since the changed assets are enabled, the deployment monitoring client needs to be supervised for operation and maintenance. The whole process is automatically triggered through the asset change information sent by the asset management module and automatically deployed, so that the method is simple to implement, and the deployment process of the monitoring client is simple and reliable.

Further, the asset transition information also carries an asset tag of the asset that has transitioned; the asset tag is used for marking the service to be monitored in the changed asset; said deploying a monitoring client on said changed asset comprises: deploying the monitoring client corresponding to each asset tag on the changed asset; and each monitoring client is respectively used for monitoring the service marked by the corresponding asset tag.

It should be understood that in practical applications, the assets may be servers and the like that can provide a variety of services. For such devices, special supervision may be made for the services provided. Therefore, when asset management is carried out, corresponding asset tags can be configured for all assets, and services needing to be monitored in the assets are marked by the asset tags. In the implementation process, the asset tag of the asset which changes is carried in the asset change information, so that when the monitoring client is deployed on the changed asset, the monitoring client can be deployed according to the service corresponding to the asset tag, the asset monitoring is more targeted, and the data obtained in the monitoring process better meets the actual requirement.

Further, the asset transition information is that the asset state of the asset which is changed from an enabled state to a non-enabled state; the determining of the operation to be executed corresponding to the asset transition information includes: and determining the operation to be executed corresponding to the asset change information, and deleting the monitoring client deployed on the changed asset.

It should be understood that in practice, when an asset is in an inactive state, it indicates that the asset is not being serviced for a while, and therefore, no monitoring is required. In the implementation process, when the asset state of the asset is changed from the enabled state to the non-enabled state, the monitoring client deployed on the changed asset is deleted, so that the monitoring resource is saved.

Further, the asset transition information is that the asset tag of the transitioned asset is changed; the asset tag is used for marking the service to be monitored in the changed asset; the determining of the operation to be executed corresponding to the asset transition information includes: when the asset tag is changed to be deleted, determining that the operation to be executed corresponding to the asset change information is to be executed, and deleting the monitoring client deployed on the changed asset; the deleted monitoring client is the monitoring client corresponding to the deleted asset tag; when the asset tag is changed into a newly added asset tag, determining an operation to be executed corresponding to the asset change information, and deploying a monitoring client corresponding to the newly added asset tag on the changed asset; when the asset tag is changed from a first tag to a second tag, determining to-be-executed operation corresponding to the asset change information, deleting a monitoring client corresponding to the first tag deployed on the changed asset, and deploying a monitoring client corresponding to the second tag on the changed asset; the monitoring client is used for monitoring the service marked by the corresponding asset tag.

As described above, in practical applications, when asset management is performed, a corresponding asset tag may be configured for each asset, and the asset tag may be used to mark a service that needs to be monitored in the asset. In the implementation process, when the asset tag is changed, if the changed asset tag is deleted, the monitoring client corresponding to the deleted asset tag is also deleted; if the change is the addition of the asset tag, deploying a monitoring client corresponding to the added asset tag on the changed asset; if the asset tag is changed from one tag to another tag, the monitoring client corresponding to the tag before the change is deleted, and the monitoring client corresponding to the tag after the change is redeployed. Therefore, automatic deployment and deletion of the monitoring client can be realized according to actual needs, so that the monitoring of assets is more targeted, and meanwhile, the effective management of the monitoring client is ensured.

Further, when deploying a monitoring client on the asset that is subject to change according to the operation to be executed, the method further includes: and registering the deployed monitoring client to a preset registration center.

In the implementation process, the deployed monitoring client is registered and registered through a preset registration center, so that the deployed monitoring client can be managed controllably. Meanwhile, when the monitoring client is deployed on the changed asset according to the operation to be executed, the deployed monitoring client is registered in a preset registration center, and automatic registration of the monitoring client is also realized.

Further, when deleting the monitoring client deployed on the changed asset according to the operation to be executed, the method further includes: and deleting the deleted registration information of the monitoring client from a preset registration center.

In the implementation process, when the monitoring client deployed on the changed asset is deleted, the registration information of the deleted monitoring client needs to be deleted from a preset registration center, so that the deployed monitoring client can be managed controllably. Meanwhile, when the monitoring client deployed on the changed asset is deleted according to the operation to be executed, the registration information of the deleted monitoring client is automatically deleted from the preset registration center, and the automatic management of the monitoring client is also realized.

The embodiment of the application further provides an asset automation control method, which comprises the following steps: when the assets change, determining the operation to be executed corresponding to the change from a preset operation table according to the change; and sending the information of the changed assets and the operation to be executed to an operation and maintenance management module so that the operation and maintenance management module can operate the changed assets according to the operation to be executed.

In the implementation process, when the asset changes, the operation to be executed corresponding to the changed asset can be determined automatically according to the changed asset from the preset operation table, and the information of the changed asset and the operation to be executed are sent to the operation and maintenance management module, so that the operation and maintenance management module can operate the changed asset according to the operation to be executed. Therefore, the automatic operation and maintenance of the assets are realized, and the method can be applied to the scene of operation and maintenance of large computer clusters. And because the operation and maintenance are automatic, the method has the advantages of high operation and maintenance efficiency and low possibility of errors. In addition, the operation to be executed corresponding to the asset transition information is determined in the embodiment of the application, so that the operation to be executed later is matched with the received asset transition information, and the operation and maintenance reliability of the asset is improved.

Further, the generated change is a new asset; the determining of the operation to be executed corresponding to the generated change includes: when the asset state of the changed asset is the starting state, determining the operation to be executed corresponding to the changed asset, and deploying a monitoring client on the changed asset; and the changed assets are newly added assets.

In the implementation process, when the assets are newly added and the asset state of the newly added assets is enabled, the operation and maintenance management module is instructed to deploy the monitoring client on the newly added assets, so that the newly added assets are monitored. The whole process is automatically triggered through the asset management module, and the operation and maintenance management module automatically deploys, so that the method is simple to implement, and the deployment process of the monitoring client is simple and reliable.

Further, the changed asset is changed into an enabled state according to the asset state of the changed asset; the determining of the operation to be executed corresponding to the generated change includes: and determining that the operation to be executed corresponding to the changed change is to deploy a monitoring client on the changed asset.

In the implementation process, when the asset state of the asset is changed into the enabled state, the operation and maintenance management module is instructed to deploy the monitoring client on the changed asset for supervision, so as to facilitate operation and maintenance. The whole process is automatically triggered by the asset management module, and the operation and maintenance management module automatically deploys the assets, so that the method is simple to implement, and the deployment process of the monitoring client is simple and reliable.

Further, the deploying a monitoring client on the changed asset includes: deploying the monitoring client corresponding to the asset tag of the changed asset on the changed asset; the asset tag is used for marking the service to be monitored in the changed asset; and the monitoring client is used for monitoring the service marked by the corresponding asset tag.

In the implementation process, when the operation and maintenance management module is instructed to deploy the monitoring client on the changed asset, the monitoring client is deployed according to the service corresponding to the asset tag, so that the asset monitoring is more targeted, and the data obtained in the monitoring process is more in line with the actual needs.

Further, the change is that the asset state is changed from an enabled state to a non-enabled state; the determining of the operation to be executed corresponding to the generated change includes: and determining the operation to be executed corresponding to the changed change, and deleting the monitoring client deployed on the changed asset.

In the implementation process, when the asset state of the asset is changed from the enabled state to the non-enabled state, the operation and maintenance management module is instructed to delete the monitoring client deployed on the changed asset, so that the monitoring resource is saved.

Further, the changed asset is an asset tag change of the changed asset; the asset tag is used for marking the service to be monitored in the changed asset; the determining of the operation to be executed corresponding to the generated change includes: when the asset tag is changed to be deleted, determining that the operation to be executed corresponding to the changed change is to delete the monitoring client deployed on the changed asset; the deleted monitoring client is the monitoring client corresponding to the deleted asset tag; when an asset tag is changed into a newly added asset tag, determining an operation to be executed corresponding to the changed asset, and deploying a monitoring client corresponding to the newly added asset tag on the changed asset; when the asset tag is changed from a first tag to a second tag, determining to-be-executed operation corresponding to the changed asset, deleting a monitoring client corresponding to the first tag deployed on the changed asset, and deploying a monitoring client corresponding to the second tag on the changed asset; the monitoring client is used for monitoring the service marked by the corresponding asset tag.

In the implementation process, when the asset tag is changed, if the asset tag is changed to be deleted, the operation and maintenance management module is instructed to delete the monitoring client corresponding to the deleted asset tag; if the change is the addition of the asset tag, the operation and maintenance management module is instructed to deploy a monitoring client corresponding to the added asset tag on the changed asset; if the asset tag is changed from one tag to another tag, the operation and maintenance management module is instructed to delete the monitoring client corresponding to the tag before the change, and redeploy the monitoring client corresponding to the tag after the change. Therefore, automatic deployment and deletion of the monitoring client can be realized according to actual needs, so that the monitoring of assets is more targeted, and meanwhile, the effective management of the monitoring client is ensured.

The embodiment of the present application further provides an asset automation management and control device, including: the device comprises a receiving module, a first operation determining module and an operation executing module; the receiving module is used for receiving the asset change information sent by the asset management module; the asset transition information carries information of the asset which is changed; the first operation determining module is used for determining to-be-executed operation corresponding to the asset change information from a preset operation table according to the asset change information; the operation execution module is used for operating the changed assets according to the operation to be executed.

The embodiment of the present application further provides an asset automation management and control device, including: a second operation determining module and a sending module; the second operation determining module is used for determining to-be-executed operation corresponding to the change from a preset operation table according to the change when the asset changes; the sending module is used for sending the information of the changed assets and the operation to be executed to the operation and maintenance management module so that the operation and maintenance management module can operate the changed assets according to the operation to be executed.

The embodiment of the present application further provides an asset automation management and control system, including: the system comprises an asset management module and an operation and maintenance management module;

the asset management module is used for inputting and managing asset information, generating asset change information when the asset information changes, and sending the asset change information to the operation and maintenance management module; the asset transition information carries information of the asset which is changed; and the operation and maintenance management module is used for determining to-be-executed operation corresponding to the asset change information according to the asset change information when receiving the asset change information sent by the asset management module, and operating the changed asset according to the to-be-executed operation.

Or the asset management module is used for inputting and managing asset information, determining to-be-executed operation corresponding to the change according to the change when the asset information changes, and sending the information of the changed asset and the to-be-executed operation to the operation and maintenance management module; and the operation and maintenance management module is used for operating the changed assets according to the operation to be executed.

The implementation process realizes the automatic operation and maintenance of the assets, and can be applied to the operation and maintenance scene of a large computer cluster. And because the operation and maintenance are automatic, the method has the advantages of high operation and maintenance efficiency and low possibility of errors. In addition, the operation to be executed corresponding to the asset transition information is determined in the embodiment of the application, so that the operation to be executed later is matched with the received asset transition information, and the operation and maintenance reliability of the asset is improved.

Further, the asset management module comprises a collection unit and a verification unit; the collecting unit is used for collecting asset information; the verification unit is used for verifying the collected asset information and recording the asset information after the verification is passed.

In the implementation process, the asset management module needs to verify the collected asset information after collecting the asset information, and the asset information is input after the verification is passed. This improves the accuracy of entry of asset information and system security.

Further, the collection unit is specifically configured to execute a preset script to collect the asset information.

In the implementation process, the automatic collection of the asset information is realized by executing the preset script, so that the labor cost is further saved, and the asset information collection efficiency is improved.

Further, the asset information includes an asset tag and an asset status; the asset tag is used for marking a service to be monitored in the asset; the asset status is used to indicate the current usage status of the asset.

In the implementation process, the collected asset information contains the asset tag and the asset state, so that the state of the asset and the service needing to be monitored can be managed conveniently.

The embodiment of the application also provides electronic equipment, which comprises a processor, a memory and a communication bus; the communication bus is used for realizing connection communication between the processor and the memory; the processor is configured to execute one or more programs stored in the memory to implement the steps of the first asset automation management and control method or the steps of the second asset automation management and control method.

Also provided in an embodiment of the present application is a readable storage medium storing one or more programs, which are executable by one or more processors to implement the steps of the asset automation management method of the first kind or the steps of the asset automation management method of the second kind.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.

Fig. 1 is a schematic flowchart of an asset automation management and control process provided in an embodiment of the present application;

fig. 2 is a schematic structural diagram of an asset automation management and control system according to an embodiment of the present application;

FIG. 3 is a schematic structural diagram of an asset management module according to an embodiment of the present disclosure;

fig. 4 is a schematic structural diagram of a more specific asset automation management and control system according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of an asset automation management and control device 100 according to an embodiment of the present disclosure;

fig. 6 is a schematic structural diagram of an asset automation management and control device 200 according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

The first embodiment is as follows:

in order to solve the problems that operation and maintenance efficiency is very low and errors are easy to occur in a large computer cluster in the related art, the embodiment of the application provides an asset automation management and control system and a corresponding method thereof. See fig. 1 for an illustration:

s101: and the asset management module is used for inputting and managing asset information.

In the embodiment of the present application, as shown in fig. 2, the asset automation management and control system includes two parts, namely an asset management module 1 and an operation and maintenance management module 2. The asset management module 1 is used for inputting and managing asset information, and the operation and maintenance management module 2 is used for performing automatic management and control on a monitoring client on an asset.

In the embodiment of the present application, as shown in fig. 3, the asset management module 1 may include a collection unit 11 and a verification unit 12, where the collection unit is configured to collect asset information, and the verification unit is configured to verify the collected asset information, and enter verified asset information after the verification is passed.

It is noted that in the embodiment of the present application, the collection of the asset information may be manually collected by the user and then imported into the collection unit. For example, the asset management module may provide a csm (Comma-Separated Values) template for a user to download, and after the user downloads the csv template, fill the collected asset information in the template, and then guide the edited csv template into a collection unit (the collection unit is an interface), thereby realizing collection of the asset information. In addition, in the embodiment of the present application, a script may be configured in advance, and the collection unit executes the script to collect the asset information. In this embodiment of the present application, the collecting unit may collect the asset information in a json format, for example, the asset information may be collected in the following format (it should be noted that the asset information collected in the following data is only one possible asset information, and the data actually collected should be used as the standard in practical applications):

{

“name”：“server1”，

“ip”：“192.168.123.2”，

“port”：“2012”，

“label”：“apache，mysql”，

“sn”：“7M580K2”，

“cpu_type”：“Intel(R)Xeon(R)CPU E5-4610 v4@1.80GHz”，

“cpu_num”：“10”，

“memory”：“515.575G”，

“disk”：“558.38G”，

“disk_info”：“‘sda’：‘558.38GB’”，

“os”：“CentOS”，

“os_version”：“7.1.1503”

}

it is further noted that, in the embodiment of the present application, the collected asset information may include information such as an asset tag and an asset status, for example, as shown in the following table a, information corresponding to the table a is specific content of the collected asset information (that is, the asset information may include an asset name, an IP number, a port number, an asset status, an asset tag, a serial number, a CPU (central processing unit) model, a CPU core number, a memory size, a hard disk size, hard disk information, and the like). It should be noted that the asset information shown in table one is only one possible example, and in practical applications, the specific content contained in the asset information may be different from that of table one, and may include, for example, an operating system (i.e., OS), an operating system version (i.e., OS version), and the like in addition to the above content. The specific content required to be collected can be set by an engineer according to the actual requirement.

Watch 1

It should be noted that, in the embodiment of the present application, the asset tag is used to indicate a service that needs to be monitored in the asset, and the content of the asset tag may be directly a service name, such as "apache", "mysql", and the like shown in one table. The asset status is used to indicate the current usage status of the asset, such as "enabled", "disabled", "on shelf", etc. It should be understood that, in practical applications, corresponding characterization values may also be predefined to characterize different services or states, for example, the service "apache" may be characterized by the character "a", and the service "mysql" may be characterized by the character "B"; the service "nginx" is characterized by the character "C"; "Enable" is characterized by the number "1"; characterization of "deactivation" by the number "2"; the number "3" characterizes "on shelf", etc.

It is also worth noting that in practical applications, if the asset information is automatically collected by using the preset script, there may be a case that some services cannot collect the related information through the script, for example, for apache and mysql services, the related information cannot be collected through the script. At this time, the script can be manually specified in a parameter manner when being executed. For example, if the asset runs apache and mysql services and the two services need to be monitored, the asset tag may be designated as "apache, mysql" when the script is executed, for example, by python get. It is also noted that the status of the asset may be set to "enabled" by default when executing the script, and further, whether the relevant service is running on the asset may be determined when collecting the asset information, and if running, the status of the asset is set to "enabled", otherwise, the status of the asset is set to "disabled", and so on.

It should be further noted that, in the embodiment of the present application, the collected assets may be verified by comparing the collected assets with reference information in a preset reference information base according to the reference information in the collected asset information, and if the collected assets are consistent with the reference information in the reference information base, the collected assets pass the verification, otherwise, the collected assets do not pass the verification (it is understood that the collected assets do not pass the verification (the collected assets include some characteristic information inherent to the collected assets, such as asset name, IP, serial number, CPU model, CPU core number, memory size, hard disk size, and hard disk information).

It should be noted that the verification process of the collected asset information is not a necessary process for implementing the embodiments of the present application. It should be understood that it is also possible to enter the collected asset information directly without verification, but only for a scheme with higher system security.

S102: when the asset information changes, generating asset change information;

note that, after the collected asset information is imported, there may be a case where an asset is newly added in the asset management module 1. In addition, if the collected asset is originally entered, part of the newly collected asset information may be changed from the originally entered asset information. Whether an asset is newly added or the original recorded asset information is changed is referred to as the asset information being changed for the embodiment of the present application. In addition, a corresponding modification interface can be provided in the embodiment of the application, so that the user can change the entered asset information. Such changes due to active modification by the user will also cause the asset management module 1 to generate asset change information.

It should be noted that the generated asset transition information should carry information of the asset which has transitioned, that is, information which can clearly indicate which asset the asset which has transitioned is, such as one or more of asset name, IP number of the asset, serial number of the asset, and the like.

S103: sending the asset change information to an operation and maintenance management module 2;

in the embodiment of the present application, the operation and maintenance management module 2 may be implemented by an open-source automatic operation and maintenance tool, for example, an idle automatic operation and maintenance tool may be implemented.

S104: and when receiving the asset change information sent by the asset management module 1, the operation and maintenance management module 2 determines the operation to be executed corresponding to the asset change information according to the asset change information.

In the embodiment of the application, an operation table may be preset in the operation and maintenance management module 2, and the operation to be executed corresponding to the asset transition information is configured in the operation table in advance, so as to determine the corresponding operation to be executed according to the received asset transition information.

In an optional implementation manner of the embodiment of the present application, the asset transition information may be a newly added asset (at this time, the newly added asset is an asset that has undergone transition), and the asset transition information may also carry an asset state of the asset that has undergone transition. At this time, it may be determined that the operation to be performed corresponding to the asset transition information includes: and when the asset state of the changed asset is the enabled state, deploying the monitoring client on the changed asset.

In yet another alternative implementation of the embodiments of the present application, the asset transition information may be an asset state transition to an enabled state (e.g., from an on-shelf state to an enabled state, or from a disabled state to an enabled state) for the asset undergoing the transition. At this time, it may be determined that the operation to be performed corresponding to the asset transition information includes: deploying the monitoring client on the changed assets.

It is noted that in the two aforementioned alternative implementations of the embodiments of the present application, the asset transition information may also carry an asset tag of the asset that has undergone the transition. Further, when the monitoring client is deployed on the asset that has changed, the monitoring client corresponding to each asset tag may be deployed on the asset that has changed. At this time, each monitoring client is respectively used for monitoring the service marked by the corresponding asset tag.

It should be noted that the monitoring client described in the embodiment of the present application is not a physical entity terminal in the conventional concept, but refers to a program control configured on an asset and capable of monitoring the operation condition of the asset. During deployment, the operation and maintenance management module 2 may install a monitoring client on the asset in a remote control manner or the like, thereby completing the deployment.

In yet another alternative implementation of the embodiments of the present application, the asset transition information may be that the asset status is changed from an enabled status to a disabled status. At this time, it may be determined that the operation to be performed corresponding to the asset transition information includes: the monitoring clients deployed on the assets undergoing the change are deleted. It should be noted that, in this alternative embodiment, all the monitoring clients deployed on the changed assets may be deleted, so as to achieve the purpose of saving resources better.

In yet another alternative implementation of the embodiments of the present application, the asset transition information may be that the asset tag of the transitioning asset has changed. At this time, the following three variations exist:

the first condition is as follows: the change that occurs to the asset tag is that the asset tag is deleted. At this time, it may be determined that the operation to be executed corresponding to the asset transition information deletes the monitoring client deployed on the asset that has undergone transition. The deleted monitoring client is the monitoring client corresponding to the deleted asset tag.

Case two: the change that occurs to the asset tag is a new asset tag. At this time, it may be determined that the operation to be executed corresponding to the asset transition information is to deploy a monitoring client corresponding to the newly added asset tag on the asset that has transitioned.

Case three: the change in the asset tag occurs to change the asset tag from a first tag to a second tag. At this time, it may be determined that the operation to be executed corresponding to the asset transition information is to delete the monitoring client corresponding to the first tag deployed on the transitioned asset, and deploy the monitoring client corresponding to the second tag on the transitioned asset. It should be noted that the first tag and the second tag described in the embodiments of the present application are not specifically referred to as a specific asset tag, but when an asset tag is changed from one tag to another, the asset tag before being changed is referred to as a first tag, and the asset tag after being changed is referred to as a second tag.

It should be noted that in the fourth alternative embodiment, the asset status of the changed asset may be limited to be enabled before the execution is performed according to the above-mentioned manner.

S105: and operating the changed assets according to the operation to be executed.

It should be noted that, in the embodiment described in fig. 1, the operation to be performed is determined by the operation and maintenance management module 2. In another implementation of the embodiment of the present application, the operation to be performed may also be determined by the asset management module 1, and then the determined operation to be performed and the information of the changed asset are sent to the operation and maintenance management module 2, and then the operation and maintenance management module 2 operates the changed asset according to the sent operation to be performed. In this embodiment, the operation to be executed may be sent to the operation and maintenance management module 2 in the form of a program script. The information of the asset that has changed is information that clearly indicates which asset the changed asset is, and may be one or more of asset name, asset IP number, asset serial number, and the like.

Specifically, in the present embodiment, when the asset is changed, the asset management module 1 may determine, from a preset operation table, an operation to be executed corresponding to the changed asset according to the changed asset. And then, the information of the changed assets and the operation to be executed are sent to the operation and maintenance management module 2, so that the operation and maintenance management module 2 can operate the changed assets according to the operation to be executed.

In this case, the following four alternative embodiments are also included in the present embodiment, but not limited thereto:

the first optional implementation mode: when the changed asset is a new added asset, when the asset state of the changed asset is an enabled state, the operation to be executed corresponding to the changed asset may be determined, and a monitoring client may be deployed on the changed asset (i.e., the new added asset).

Optional embodiment two: when the changed asset state is changed into the enabled state, the operation to be executed corresponding to the changed asset can be determined to be the deployment of the monitoring client on the changed asset.

In the first and second optional embodiments, if the asset that has been changed has an asset tag, when the monitoring client is deployed on the asset that has been changed, the monitoring client corresponding to the asset tag of the asset that has been changed may be deployed on the asset that has been changed.

Optional embodiment three: when the changed asset state is changed from the enabled state to the non-enabled state, the to-be-executed operation corresponding to the asset change information may be determined to delete the monitoring client deployed on the changed asset. For example, the operation to be performed may be to delete all the monitoring clients deployed on the monitoring client on the asset that has undergone the change.

Optional implementation mode four: when the changed asset tag of the changed asset is changed, and when the changed asset tag is deleted, determining that the operation to be executed corresponding to the changed asset is to delete the monitoring client corresponding to the deleted asset tag deployed on the changed asset; when the asset tag is changed into a newly added asset tag, determining an operation to be executed corresponding to the change, and deploying a monitoring client corresponding to the newly added asset tag on the changed asset; when the asset tag is changed from a first tag to a second tag, determining to-be-executed operation corresponding to the change, deleting the monitoring client corresponding to the first tag deployed on the changed asset, and deploying the monitoring client corresponding to the second tag on the changed asset.

It should be noted that, in the embodiment of the present application, referring to fig. 4, the asset automation management and control system may further be provided with a registry 3 for legally managing the monitoring client. For example, when a monitoring client is deployed on an asset that has been changed according to an operation to be performed, the deployed monitoring client may be registered in the preset registry 3. When a monitoring client deployed on a changed asset is deleted according to an operation to be executed, the registration information of the deleted monitoring client is deleted from the preset registry 3. The above registration and deletion processes may be automated via predefined interfaces. In this embodiment of the present application, when registering a deployed monitoring client to a preset registration center 3, the registered information may include information such as a unique identifier (e.g., a serial number) of the monitoring client, a corresponding asset tag, an asset name of an asset where the deployed monitoring client is located, an IP number, and a port number of the monitoring client.

In the embodiment of the present application, still referring to fig. 4, the asset automation management and control system may further configure corresponding monitoring service 4 and alarm service 5. The monitoring service 4 may implement monitoring and alarm functions for assets. For example, the monitoring service 4 may discover, in real time, related information of the monitoring client (e.g., an asset name, an ip number, a port number of the monitoring client, and the like of an asset where the deployed monitoring client is located) from the registry 3, and may further pull monitoring data from the corresponding monitoring client, store and analyze the monitoring data, push the monitoring data exceeding a preset threshold to the alarm service 5, and send alarm information to remind an engineer by the alarm service 5. It should be noted that the preset threshold may be set by an engineer according to actual needs, and the set threshold may be different for different monitoring services 4. It should be further noted that, in the embodiment of the present application, the monitoring data acquired by the monitoring service 4 and the alarm information generated by the alarm service 5 may be displayed to the user in the form of a web interface, so that the user can more intuitively know the operation condition of the current asset.

It should be noted that, in the embodiment of the present application, for assets such as a switch, a firewall, and the like, the switch asset tag may be labeled as switch, and the firewall asset tag may be labeled as firewall. For the assets such as the switch, the firewall and the like, the operation and maintenance management module 2 only needs to start the snmp function (the program for operating the snmp function can be regarded as a monitoring client), and registers the asset information such as the switch, the firewall and the like to the registration center, and the monitoring service can directly acquire the monitoring data through the snmp protocol.

In summary, according to the asset automation control method and system provided by the embodiment of the application, the user can complete all-around automation monitoring on the server only by simply managing assets through the asset management module 1, and the human input is low. The scheme can be applied to the operation and maintenance scene of the large computer cluster, and has the advantages of high operation and maintenance efficiency and low possibility of errors due to automatic operation and maintenance. In addition, the operation to be executed corresponding to the asset transition information is determined in the embodiment of the application, so that the operation to be executed later is matched with the received asset transition information, and the operation and maintenance reliability of the asset is improved.

Example two:

based on the first embodiment, the present embodiment further illustrates the present application by taking a specific asset automation management and control system as an example.

Referring to fig. 4, the system includes an asset management module 1, an operation and maintenance management module 2, a registry 3, a server (asset), a monitoring service 4, an alarm service 5 and a web interface.

In the embodiment of the present application, before performing the automatic management and control of the asset, the asset information needs to be imported into the asset management module 1. The import mode comprises manual import and script import.

When the asset information is imported manually, a user needs to download a csv template from a webpage interface corresponding to the asset management module 1; filling related information of the assets to be imported according to the prompt information of the csv template, and separating the assets by commas if a plurality of asset tags exist; and finally, uploading and importing the csv template to the asset management module 1, and analyzing, verifying and warehousing the imported csv template by the asset management module 1. The csv template may be as shown in table two below:

watch two

When the asset information is imported in a script mode, the pre-programmed asset information collection script can be downloaded to the server where the asset management module 1 is located and executed. When the script is executed, the asset information is automatically collected and the collected asset information is acquired into the asset management module 1 in a json format. And the asset management module 1 analyzes, verifies and stores the acquired data in the json format. For asset information which cannot be collected through the script, the asset information is manually specified in a parameter mode when the script is executed, if the apache and mysql services are run on the asset and need to be monitored, the tag of the asset can be specified as "apache, mysql" when the script is run, for example: py — label "apache, mysql". In addition, the asset state can be defaulted to be 'enabled' through the imported asset by the script.

In addition, in the embodiment of the present application, the asset management module 1 may provide an asset adjustment interface, so that a user may adjust the related information of the asset in the web interface corresponding to the asset management module 1.

After the assets are imported or the asset information is modified, if the related change (newly added asset information or the original asset information is changed) triggers the preset automatic deployment condition, the operation to be executed can be correspondingly determined and sent to the operation and maintenance management module 2 for execution.

In this embodiment of the present application, the operation and maintenance management module 2 may be implemented by an open-source automation operation and maintenance tool. after receiving the operation to be executed, the ansable may remotely connect to the corresponding asset and execute the operation to be executed, and return the execution result to the asset management module 1.

In the embodiment of the present application, the correspondence between the preset automatic deployment condition and the corresponding operation to be executed may be as shown in table three below:

watch III

In the embodiment of the present application, the monitoring service 4 may find information of the monitoring client (such as an asset name and an IP number of an asset where the monitoring client belongs, an IP number of the monitoring client, and a port number of the monitoring client) from the registry 3 in real time, so that the monitoring service 4 may pull monitoring data from the monitoring client, store and analyze the monitoring data, push the monitoring data exceeding a threshold to the alarm service 5, and send an alarm by the alarm service 5. Meanwhile, the display service is provided, and the monitoring data and the alarm information can be displayed to the user through a webpage interface.

Illustratively, the monitoring service 4 may discover the information of the monitoring client from the registry 3 by:

scrape_configs：

-job_name：‘consul’

consul_sd_configs：

-server: service. challenge: 8500' # registry 3 Address

Through the scheme, the user can complete the automatic monitoring of the server in all directions only by simply managing the assets through the asset management module, the labor input is lower, and the method and the system can be suitable for more application scenes.

Example three:

based on the same inventive concept, the embodiments of the present application also provide asset automation management and

control devices

100 and 200. Referring to fig. 5 and 6, fig. 5 shows the asset automation control device 100 corresponding to the steps executed by the operation and maintenance management module in the method shown in fig. 1, and fig. 6 shows the asset automation control device 200 corresponding to the steps executed by the asset management module in the scenario where the operation to be performed is determined by the asset management module. It should be understood that the specific functions of the

apparatuses

100 and 200 can be referred to the above description, and the detailed description is omitted here as appropriate to avoid redundancy. The

devices

100 and 200 include at least one software functional module that can be stored in a memory in the form of software or firmware or solidified in an operating system of the

devices

100 and 200. Specifically, the method comprises the following steps:

referring to fig. 5, the apparatus 100 includes: a receiving module 101, a first operation determining module 102, and an operation executing module 103;

the receiving module 101 is configured to receive asset transition information sent by an asset management module; the asset transition information carries information of the asset which is changed;

the first operation determining module 102 is configured to determine, according to the asset transition information, an operation to be executed corresponding to the asset transition information from a preset operation table;

the operation executing module 103 is configured to operate the asset that is changed according to the operation to be executed.

In the embodiment of the present application, the asset transition information also carries the asset status of the asset that has undergone transition; the asset change information is newly added assets; the first operation determining module 102 is specifically configured to determine that an operation to be executed corresponding to the asset transition information is to deploy a monitoring client on a changed asset when an asset state of the changed asset is an enabled state; the changed assets are newly added assets.

In the embodiment of the application, the asset transition information is that the asset state of the asset which is changed into the starting state; the first operation determining module 102 is specifically configured to determine that an operation to be executed corresponding to the asset transition information is to deploy a monitoring client on a changed asset.

In the embodiment of the present application, the asset transition information further carries an asset tag of the asset which has undergone transition; the asset tag is used for marking the service to be monitored in the changed asset;

when the first operation determining module 102 deploys the monitoring client on the changed asset, the method specifically includes: deploying monitoring clients corresponding to the asset tags on the changed assets; and each monitoring client is respectively used for monitoring the service marked by the corresponding asset tag.

In the embodiment of the application, the asset transition information is that the asset state is changed from an enabled state to a non-enabled state; the first operation determining module 102 is specifically configured to determine that an operation to be executed corresponding to the asset transition information is to delete a monitoring client deployed on a changed asset.

In the embodiment of the application, the asset transition information is that the asset tag of the changed asset is changed; the asset tag is used for marking the service to be monitored in the changed asset;

the first operation determining module 102 is specifically configured to:

when the asset tag is changed to be deleted, determining the operation to be executed corresponding to the asset change information, and deleting the monitoring client deployed on the changed asset; the deleted monitoring client is the monitoring client corresponding to the deleted asset tag;

when the asset tag is changed into a newly added asset tag, determining an operation to be executed corresponding to the asset change information, and deploying a monitoring client corresponding to the newly added asset tag on the changed asset;

when the asset tag is changed from a first tag to a second tag, determining a to-be-executed operation corresponding to the asset change information, deleting a monitoring client corresponding to the first tag deployed on the changed asset, and deploying a monitoring client corresponding to the second tag on the changed asset;

the monitoring client is used for monitoring the service marked by the corresponding asset tag.

In this embodiment of the present application, the operation execution module 103 is further configured to register the deployed monitoring client with a preset registration center when the monitoring client is deployed on the asset that is changed according to the operation to be executed.

In this embodiment of the application, the operation execution module 103 is further configured to delete the registration information of the deleted monitoring client from the preset registry when the monitoring client deployed on the changed asset is deleted according to the operation to be executed.

Referring to fig. 6, the apparatus 200 includes: a second operation determination module 201 and a sending module 202;

the second operation determining module 201 is configured to determine, according to a change occurring when an asset changes, an operation to be executed corresponding to the change occurring from a preset operation table;

the sending module 202 is configured to send the information of the changed asset and the operation to be executed to the operation and maintenance management module, so that the operation and maintenance management module operates the changed asset according to the operation to be executed.

In the embodiment of the application, the generated change is a new asset; the second operation determining module 201 is specifically configured to, when the asset state of the asset that is subject to change is the enabled state, determine that an operation to be executed corresponding to the change is to be performed, and deploy a monitoring client on the asset that is subject to change; the changed assets are newly added assets.

In the embodiment of the application, the changed asset is changed into an enabled state according to the asset state of the changed asset; the second operation determining module 201 is specifically configured to determine that the to-be-executed operation corresponding to the changed change is to deploy a monitoring client on the changed asset. In this embodiment of the application, when the asset includes an asset tag, the second operation determining module 201 is specifically configured to deploy, on the asset that changes, a monitoring client corresponding to the asset tag of the asset that changes; the asset tag is used for marking the service to be monitored in the changed asset; the monitoring client is used for monitoring the service marked by the corresponding asset tag.

In the embodiment of the application, the change is that the asset state is changed from an enabled state to a non-enabled state; the second operation determining module 201 is specifically configured to determine that an operation to be executed corresponding to the changed asset is to delete the monitoring client deployed on the changed asset.

In the embodiment of the application, the changed asset is the changed asset tag of the changed asset; the asset tag is used for marking the service to be monitored in the changed asset;

the second operation determining module 201 is specifically configured to:

when the asset tag is changed to be deleted, determining the operation to be executed corresponding to the change, and deleting the monitoring client deployed on the changed asset; the deleted monitoring client is the monitoring client corresponding to the deleted asset tag;

when the asset tag is changed into a newly added asset tag, determining an operation to be executed corresponding to the change, and deploying a monitoring client corresponding to the newly added asset tag on the changed asset;

when the asset tag is changed from a first tag to a second tag, determining to-be-executed operation corresponding to the change, deleting the monitoring client corresponding to the first tag deployed on the changed asset, and deploying the monitoring client corresponding to the second tag on the changed asset;

Example four:

the present embodiment provides an electronic device, which is shown in fig. 7 and includes a processor 701, a memory 702, and a communication bus 703. Wherein:

the communication bus 703 is used for connecting communication between the processor 701 and the memory 702.

The processor 701 is configured to execute one or more first programs stored in the memory 702 to implement the steps performed by the operation and maintenance management module in the scheme determined by the operation and maintenance management module for determining the operation to be performed in the first embodiment;

or, the processor 701 is configured to execute one or more second programs stored in the memory 702 to implement the steps performed by the asset management module in the scenario in which the operation to be performed is determined by the asset management module in the first embodiment.

It will be appreciated that the configuration shown in fig. 7 is merely illustrative and that the electronic device may include more or fewer components than shown in fig. 7 or have a different configuration than shown in fig. 7.

The present embodiment further provides a readable storage medium, such as a floppy disk, an optical disk, a hard disk, a flash Memory, a usb (secure digital Card), an MMC (Multimedia Card), etc., in which one or more programs for implementing the above steps are stored, where the one or more programs are executable by one or more processors to implement the steps executed by the operation and maintenance management module in the scheme that the determination of the operation to be performed is determined by the operation and maintenance management module in the first embodiment, or to implement the steps executed by the asset management module in the scheme that the operation to be performed is determined by the asset management module in the first embodiment. And will not be described in detail herein.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.

In addition, units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

Furthermore, the functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

In this document, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.

In this context, a plurality means two or more.

The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. An asset automation management and control method is characterized by comprising the following steps:

receiving asset change information sent by an asset management module; the asset transition information carries information of the asset which is changed;

determining an operation to be executed corresponding to the asset change information from a preset operation table according to the asset change information;

and operating the changed assets according to the operation to be executed.

2. The asset automation management and control method according to claim 1, wherein the asset transition information further carries an asset status of the asset that has undergone the transition; the asset change information is newly added assets;

the determining of the operation to be executed corresponding to the asset transition information includes:

determining an operation to be executed corresponding to the asset transition information, and deploying a monitoring client on the asset which is changed when the asset state of the asset which is changed is a starting state; and the changed assets are newly added assets.

3. The asset automation management and control method according to claim 1, wherein the asset transition information is an asset state transition to an enabled state for the asset that has undergone a transition;

and determining that the operation to be executed corresponding to the asset transition information is to deploy a monitoring client on the asset which is transitioned.

4. The asset automation management and control method according to claim 2 or 3, wherein the asset transition information further carries an asset tag of the asset that has undergone the transition; the asset tag is used for marking the service to be monitored in the changed asset;

said deploying a monitoring client on said changed asset comprises:

deploying the monitoring client corresponding to each asset tag on the changed asset; and each monitoring client is respectively used for monitoring the service marked by the corresponding asset tag.

5. The asset automation management and control method according to claim 1, wherein the asset transition information is that the asset status is changed from an enabled status to a non-enabled status;

and determining the operation to be executed corresponding to the asset change information, and deleting the monitoring client deployed on the changed asset.

6. The asset automation management and control method according to claim 1, wherein the asset transition information is that an asset tag of the asset which has undergone the transition is changed; the asset tag is used for marking the service to be monitored in the changed asset;

when the asset tag is changed to be deleted, determining that the operation to be executed corresponding to the asset change information is to be executed, and deleting the monitoring client deployed on the changed asset; the deleted monitoring client is the monitoring client corresponding to the deleted asset tag;

when the asset tag is changed from a first tag to a second tag, determining to-be-executed operation corresponding to the asset change information, deleting a monitoring client corresponding to the first tag deployed on the changed asset, and deploying a monitoring client corresponding to the second tag on the changed asset;

7. The asset automation management and control method according to claim 2, 3 or 6, when deploying a monitoring client on the asset which is subject to change according to the operation to be executed, further comprising:

and registering the deployed monitoring client to a preset registration center.

8. The asset automation management and control method according to claim 5 or 6, when deleting the monitoring client deployed on the asset which is subject to change according to the operation to be executed, further comprising:

and deleting the deleted registration information of the monitoring client from a preset registration center.

9. An asset automation management and control method is characterized by comprising the following steps:

when the assets change, determining the operation to be executed corresponding to the change from a preset operation table according to the change;

and sending the information of the changed assets and the operation to be executed to an operation and maintenance management module so that the operation and maintenance management module can operate the changed assets according to the operation to be executed.

10. The asset automation management and control method according to claim 9, wherein the change is a new asset;

the determining of the operation to be executed corresponding to the generated change includes:

when the asset state of the changed asset is the starting state, determining the operation to be executed corresponding to the changed asset, and deploying a monitoring client on the changed asset; and the changed assets are newly added assets.

11. The asset automation management and control method according to claim 9, wherein the changed asset is an asset state transition of the changed asset to an enabled state;

and determining that the operation to be executed corresponding to the changed change is to deploy a monitoring client on the changed asset.

12. The asset automation management and control method according to claim 10 or 11, wherein said deploying a monitoring client on said asset under change comprises:

deploying the monitoring client corresponding to the asset tag of the changed asset on the changed asset; the asset tag is used for marking the service to be monitored in the changed asset; and the monitoring client is used for monitoring the service marked by the corresponding asset tag.

13. The asset automation management and control method according to claim 9, wherein the change occurred is a transition of the asset status from an enabled status to a non-enabled status;

and determining the operation to be executed corresponding to the changed change, and deleting the monitoring client deployed on the changed asset.

14. The asset automation management and control method according to claim 9, wherein the changed asset is a change in an asset tag of the changed asset; the asset tag is used for marking the service to be monitored in the changed asset;

when the asset tag is changed to be deleted, determining that the operation to be executed corresponding to the changed change is to delete the monitoring client deployed on the changed asset; the deleted monitoring client is the monitoring client corresponding to the deleted asset tag;

when an asset tag is changed into a newly added asset tag, determining an operation to be executed corresponding to the changed asset, and deploying a monitoring client corresponding to the newly added asset tag on the changed asset;

when the asset tag is changed from a first tag to a second tag, determining to-be-executed operation corresponding to the changed asset, deleting a monitoring client corresponding to the first tag deployed on the changed asset, and deploying a monitoring client corresponding to the second tag on the changed asset;

15. An asset automation management and control device, comprising: the device comprises a receiving module, a first operation determining module and an operation executing module;

the receiving module is used for receiving the asset change information sent by the asset management module; the asset transition information carries information of the asset which is changed;

the first operation determining module is used for determining to-be-executed operation corresponding to the asset change information from a preset operation table according to the asset change information;

the operation execution module is used for operating the changed assets according to the operation to be executed.

16. An asset automation management and control device, comprising: a second operation determining module and a sending module;

the second operation determining module is used for determining to-be-executed operation corresponding to the change from a preset operation table according to the change when the asset changes;

the sending module is used for sending the information of the changed assets and the operation to be executed to the operation and maintenance management module so that the operation and maintenance management module can operate the changed assets according to the operation to be executed.

17. An asset automation management and control system, comprising: the system comprises an asset management module and an operation and maintenance management module;

the asset management module is used for inputting and managing asset information, generating asset change information when the asset information changes, and sending the asset change information to the operation and maintenance management module; the asset transition information carries information of the asset which is changed;

the operation and maintenance management module is used for determining to-be-executed operation corresponding to the asset change information according to the asset change information when receiving the asset change information sent by the asset management module, and operating the changed asset according to the to-be-executed operation;

or the like, or, alternatively,

the asset management module is used for inputting and managing asset information, determining to-be-executed operation corresponding to the change according to the change when the asset information changes, and sending the information of the changed asset and the to-be-executed operation to the operation and maintenance management module;

and the operation and maintenance management module is used for operating the changed assets according to the operation to be executed.

18. The asset automation management and control system of claim 17, said asset management module comprising a collection unit and a verification unit;

the collecting unit is used for collecting asset information;

the verification unit is used for verifying the collected assets and recording the asset information after the assets are verified.

19. The asset automation management and control system of claim 18 wherein the collection unit is specifically configured to execute a preset script to collect asset information.

20. The asset automation management and control system according to any one of claims 17 to 19, characterized in that the asset information includes an asset tag and an asset status; the asset tag is used for marking a service to be monitored in the asset; the asset status is used to indicate the current usage status of the asset.

21. An electronic device comprising a processor, a memory, and a communication bus;

the communication bus is used for realizing connection communication between the processor and the memory;

the processor is configured to execute one or more programs stored in the memory to implement the steps of the asset automation management method according to any one of claims 1 to 8 or to implement the steps of the asset automation management method according to any one of claims 9 to 14.

22. A readable storage medium storing one or more programs, the one or more programs being executable by one or more processors to implement the steps of the asset automation management method according to any one of claims 1 to 8 or the steps of the asset automation management method according to any one of claims 9 to 14.