Metadata script management method, device, electronic device and storage medium

Abstract

The embodiments of the present application provide a metadata script management method, device, electronic device and storage medium, which implement script-based workflow hierarchical management by pre-selecting and constructing the correspondence between script-indicator-process. Based on this management mode, users can manage massive scripts step by step, so as to find all scripts of corresponding tasks more clearly and accurately, improve operating efficiency, and at the same time, store and manage each script, indicator, process and task in the form of metadata, so as to effectively realize the standardization of script, indicator, process and task data, and ensure the accuracy and consistency of script, indicator, task and process data.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a metadata script management method, device, electronic device and storage medium. Background Art

[0002] A script is a set of codes used to replace manual completion of certain functions or operations during the execution of system tasks or other operations. Software users often come into contact with a large number of scripts in their daily work, among which different scripts are used to perform different tasks.

[0003] In the prior art, when a user uses a certain software and performs a certain operation, the user needs to find all the scripts corresponding to the operation, and package all the corresponding scripts into an executable file, and run all the scripts in the executable file by executing relevant running instructions. With the gradual increase in web projects and the increasing number of scripts, it becomes more and more difficult for users to find scripts. On this basis, it is necessary to provide an effective method to manage a large number of scripts, so that users can find all the corresponding scripts more clearly and accurately, which is conducive to improving operation efficiency.

[0004] Metadata is descriptive information about data, which describes the background information of data content, quality, status and other relevant characteristics. It can promote the efficient use of data sets and help data production units to effectively maintain and manage data. Therefore, the use of metadata technology in script management methods is more conducive to improving its operating efficiency. Summary of the invention

[0005] The embodiments of the present application provide a metadata script management method, device, electronic device and storage medium for performing structured hierarchical management of massive scripts, thereby improving operating efficiency.

[0006] In a first aspect, an embodiment of the present application provides a metadata script management method, including:

[0007] Selecting a target script set from various script sets included in a preset metadata script library, and creating a target indicator corresponding to at least the target script set;

[0008] Selecting a target indicator set from each indicator set included in a preset metadata indicator library based on the target indicator, and creating a target process corresponding to at least the target indicator set;

[0009] Selecting a target process set from each process set included in a preset metadata process library based on the target process, and creating a corresponding target task based on the target process set;

[0010] A task execution instruction triggered by a target object for the target task is received, and all scripts in the target script set are executed based on the task execution instruction.

[0011] In a second aspect, the embodiment of the present application further provides a metadata script management device, including:

[0012] A first creation module is used to select a target script set from various script sets included in a preset metadata script library, and to create a target indicator corresponding to at least the target script set;

[0013] A second creation module is used to select a target indicator set from each indicator set included in a preset metadata indicator library based on the target indicator, and to create a target process corresponding to at least the target indicator set;

[0014] A third creation module is used to select a target process set from each process set included in a preset metadata process library based on the target process, and create a corresponding target task based on the target process set;

[0015] A running module, used for receiving a task running instruction triggered by a target object for the target task, and running all scripts in the target script set based on the task running instruction;

[0016] Optionally, the first communication module is used to generate corresponding script running logs according to the running status of each script in the target script set, and send the script running logs to a designated first receiving object; the second communication module is used to generate corresponding alarm logs based on relevant information of the target object, and send the alarm logs to a designated second receiving object.

[0017] In an optional embodiment, before selecting a target script set from various script sets included in a preset metadata script library, the first creation module is further configured to:

[0018] A metadata script library is created, wherein the metadata script library includes a plurality of scripts, and the plurality of scripts are respectively stored in the metadata script library in the form of metadata.

[0019] In an optional embodiment, after creating at least a target indicator corresponding to the target script set, the first creation module is further used to:

[0020] Create information about the target indicator, wherein the information about the target indicator at least includes: an indicator name of the target indicator.

[0021] A mapping relationship between the target indicator and the information of the target indicator is created.

[0022] In an optional embodiment, when all scripts in the target script set are executed based on the task execution instruction, the execution module is specifically used to:

[0023] Get the order of each process in the target process set.

[0024] According to the arrangement order of the various processes, the running order of the various scripts in the corresponding target script set is determined, and all the scripts in the target script set are run in sequence according to the running order.

[0025] In an optional embodiment, after running all scripts in the target script set based on the task running instruction, the running module is further used to:

[0026] Obtain the alarm data generated when each script in the target script set is run, where:

[0027] If the alarm data meets the preset alarm condition, the target object is determined to be a target alarm object.

[0028] If the alarm data does not meet the preset alarm condition, it is determined that the target object is not a target alarm object.

[0029] In a third aspect, an embodiment of the present application further provides an electronic device comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the computer program is executed by the processor, the processor implements any one of the metadata script management methods in the first aspect above.

[0030] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the metadata script management method of the first aspect is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 A schematic diagram of a metadata script management method provided in an embodiment of the present application;

[0032] Figure 2 A logical architecture diagram of the metadata script management method provided in the embodiment of the present application;

[0033] Figure 3 A logical architecture diagram of the metadata script management method provided in the embodiment of the present application;

[0034] Figure 4 A diagram of the metadata script management system architecture provided in an embodiment of the present application;

[0035] Figure 5A schematic diagram of a first metadata script management device provided in an embodiment of the present application;

[0036] Figure 6 A schematic diagram of a second metadata script management device provided in an embodiment of the present application;

[0037] Figure 7 A schematic diagram of a third metadata script management device provided in an embodiment of the present application;

[0038] Figure 8 A schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0040] The metadata script management method provided in the embodiment of the present application realizes script-based hierarchical management of workflows by pre-selecting and constructing the correspondence between scripts, indicators and processes. Based on this management mode, users can manage massive scripts step by step, thereby facilitating clearer and more accurate identification of all scripts for corresponding tasks and improving operating efficiency.

[0041] In order to promote the efficient use of relevant data sets in the script task process management device provided in the embodiment of the present application, a relevant metadata script library is created in advance, wherein the metadata script library contains multiple scripts, and each script is stored in the metadata script library in the form of metadata. This method is conducive to the standardization of script data use, thereby ensuring the accuracy and consistency of script data.

[0042] See also Figure 1 As shown, the metadata script management method provided in the embodiment of the present application includes:

[0043] Step 101: Select a target script set from various script sets included in a preset metadata script library, and create a target indicator that at least corresponds to the target script set.

[0044] An indicator represents the smallest unit that completes a certain function through at least one script, that is, one indicator can represent multiple scripts. Therefore, by creating a target indicator corresponding to a target set, the preliminary management of the target script set can be achieved. According to the mapping relationship between the target indicator and the target script set, the purpose of finding multiple scripts in the target script set through one target indicator can be achieved, thereby reducing the amount of search operations.

[0045] In the embodiment of the present application, each script set is obtained from a preset metadata script library, and each script set contains at least one script. The obtained script set contains a target script set to be executed. Since each script in the target script set is stored in the metadata script library in the form of metadata, each obtained script set also stores related content in the form of metadata.

[0046] For example, the following script set is obtained from the preset metadata script library: {A, B}, {A, B, C}, {D, F}, where each letter represents a metadata script and is stored in the form of metadata. In the embodiment of the present application, {A, B} is specified as the target script set.

[0047] Optionally, in addition to extracting scripts from a preset metadata script library, scripts can also be obtained based on a user's operation of uploading scripts in the form of metadata. Specifically, a user manually uploads a specified number of metadata scripts, and all of the above scripts are used to construct a script set, so that the script set can also be considered as a target script set.

[0048] For example, a user uploads scripts A, B, and C in the form of metadata, and uses the scripts to construct a script set, namely {A, B, C}. The script set {A, B, C} obtained in this way can also be considered as a target script set.

[0049] In the embodiment of the present application, a target script set is selected based on each obtained script set. Similarly, the target script set stores related content in the form of metadata.

[0050] Optionally, after obtaining each script set and creating at least a target indicator corresponding to the target script set, the following operation is further performed: creating target indicator information, wherein the target indicator information includes at least: an indicator name of the target indicator. In the embodiment of the present application, at least the indicator name of the target indicator is obtained.

[0051] For example, according to the specified target script set {A, B}, a target indicator a corresponding to at least the target script set is created, and an indicator name a of the target indicator a is set, so as to facilitate management.

[0052] Optionally, the following information may also be used as information of the target indicator: the group to which the target indicator belongs, the description of the target indicator, the task running plan of the target indicator, the task running command of the target indicator, the task running node of the target indicator, etc.

[0053] Next, create a correspondence between the target indicator and its information. In this way, the target indicator information can be obtained according to the created correspondence, thereby facilitating users to understand, query and classify the target indicator based on its information, and facilitating users to manage the target indicator.

[0054] Step 102: Selecting a target indicator set from various indicator sets included in a preset metadata indicator library based on the target indicator, and creating a target process corresponding to at least the target indicator set.

[0055] A process represents the smallest unit that completes a function through at least one indicator. That is, a process can correspond to multiple indicators. In other words, it can also represent multiple indicator sets, each of which contains at least one indicator, and each indicator is stored in the form of metadata. Figure 2 As shown in the figure, since indicator sets often have different categories, it is cumbersome to directly associate related scripts based on indicators. Therefore, by dividing the task, a complete task is divided into multiple processes, each process represents a subtask, and each process contains at least one indicator set. In this way, the correspondence between the process and the indicator can be established, thereby further realizing the hierarchical management of the script. In simple terms, more scripts can be corresponding to one process.

[0056] For example, according to process 1, the indicator set {a, b}, {a, b, c}, {d, f} is selected from the metadata indicator library, where a is the target indicator. Based on this method, if a process corresponds to the indicator set {a, b}, then the script corresponding to the process, that is, the script set corresponding to indicator a and indicator b respectively, if the script set corresponding to b is {G}, then the scripts corresponding to the indicator set {a, b} include: A, B, G.

[0057] Step 103: Select a target process set from various process sets included in the preset metadata process library based on the target process, and create a corresponding target task based on the target process set.

[0058] A target process set is selected based on the target process, and a corresponding target task is created according to the target process set. In practical applications, a task often includes multiple processes. Therefore, the target task here represents a task composed of multiple process sets including the target process set.

[0059] Since when creating corresponding target tasks based on the target process set, the target process set is stored in the preset metadata process library in the form of metadata, when creating the target task, it is worth noting that the target task should also be stored in the form of metadata to facilitate the standardization of task use.

[0060] For example: based on the target process (process 1), a target process set {1, 2, 3} is selected, and a corresponding target task α is created according to the target process set {1, 2, 3}.

[0061] Step 104: Receive a task execution instruction triggered by the target object for the target task, and execute all scripts in the target script set based on the task execution instruction.

[0062] From the above, it can be seen that a task corresponds to at least one process set, a process set corresponds to at least one indicator set, and an indicator set corresponds to at least one script set, that is, a task corresponds to all scripts in multiple script sets, thereby realizing hierarchical management of tasks-processes-indicators-scripts. In this way, when a task running instruction triggered for a target task is received, all scripts corresponding to the target task, that is, all scripts in the target script set, can be run according to the task running instruction.

[0063] See also Figure 3 As shown, when a task is executed, there is a sequence between the various processes that make up this task. Therefore, optionally, the arrangement order of each process in the target process set is obtained, and according to the arrangement order of each process, the running order of each script in the corresponding target script set is determined, and all scripts in the target script set are run in sequence according to the running order. In this way, when each script is run in sequence, the execution order between the corresponding processes also meets the preset requirements.

[0064] When the task is completed, in order to further facilitate users to understand the running status of each script, the log of the task execution results is designed, specifically:

[0065] According to the running status of each script in the target script set, corresponding script running logs are generated respectively, and the script running logs are sent to the designated first receiving object.

[0066] From the perspective of the physical device, the above-mentioned first receiving object can be a connected external analysis device or the metadata script management device itself; further, the first receiving object can also be a designated mailbox or account, which can receive the script execution log and analyze the script execution status during the task execution. This method helps users quickly find faulty scripts.

[0067] Optionally, after running all scripts in the target script set based on the task running instruction, the alarm data generated when each script in the target script set is run can be obtained, and it can be confirmed whether the target object is a threatening target alarm object according to the alarm data, wherein:

[0068] If the alarm data meets the preset alarm conditions, the target object is determined to be the target alarm object.

[0069] If the alarm data does not meet the preset alarm conditions, it is determined that the target object is not the target alarm object.

[0070] Optionally, if the target object is determined to be a target alarm object, a corresponding alarm log is generated based on relevant information of the target object, and the alarm log is sent to a designated second receiving object.

[0071] The alarm data generated by the script will generate corresponding alarm logs. In this way, users can use the alarm logs to analyze whether the target object is threatening. Specifically, if an abnormality occurs during the task operation, it can be checked according to the alarm log and the target object can be determined to be dangerous, so as to avoid the same abnormal accident from happening again. This information is sent to the designated second receiving object. Similarly, the second receiving object is an object that can receive the alarm log: such as mailbox, SMS, etc.

[0072] The scheme described in the embodiment of the present application can be applied to many scenarios where a large number of scripts need to be managed. For example, in the work scenarios of some government departments, when filling in some relevant forms, it is necessary to search for some valid entries in the internal database. If the script is not effectively hierarchically managed at this time, it can only be searched directly according to the massive scripts, and the amount of calculation is too large. At this time, the metadata script management method provided by the embodiment of the present application can be used to first divide the entire retrieval task into three processes: determining the retrieval terms-retrieval of relevant terms in the internal database-presenting the retrieval results. And find the corresponding indicator sets for the above three processes respectively, and then find and execute the corresponding script set according to the obtained indicator set. This method does not need to perform a large number of script searches, but only needs to perform successive searches for each level of task-process-indicator-script, which greatly reduces the amount of calculation required for the search.

[0073] For common operational web pages, there are usually various executable operations that can be selected and confirmed by users, and different results are presented according to the user operations. Each executable operation corresponds to multiple scripts. For example, some common web games need to execute corresponding scripts according to user operations, so as to present different screen results. At this time, the metadata script management method provided in the embodiment of the present application can also be used to find and execute the corresponding scripts in sequence.

[0074] See also Figure 4As shown, the system architecture of the corresponding metadata script management system is designed based on the metadata script management method provided in the embodiment of the present application, wherein the system includes three parts: an interface module, a script indicator management module, and a task process trigger module. Each part contains relevant operations for managing each data, and the data of each module are interconnected.

[0075] In the embodiment of the present application, the task flow management module triggers the specified task based on the user's operation, and can also predetermine the specific execution time of the task through the user's operation. When the task running instruction that occurs immediately is triggered, the relevant script is selected from the script indicator management module through data transmission. Similarly, the script indicator management module is responsible for the storage and management of scripts and indicators. The relevant management personnel can perform operations such as script creation, script marking, script deletion, and script grouping in the script indicator management module to achieve the management of the script. It is also possible to manage the indicators through operations such as indicator creation, indicator editing, indicator deletion, and indicator grouping, so as to indirectly manage the lower-level scripts. Under normal circumstances, the various parts in the script indicator management module are regularly maintained by the relevant management personnel according to the specific situation, or perform relevant operations to realize the modification of relevant data. Based on the task trigger instruction, after running all scripts, corresponding alarm data is generated according to the running situation of the script, and the alarm data is fed back to the task flow management module to inform the task flow management personnel which scripts have failed, so as to facilitate the troubleshooting of the faulty script.

[0076] In the interface module, relevant personnel can select the specified script interface and trigger the interface according to the script ID, so as to realize the data interaction with the task process management module. Specifically, the script interface is determined by the relevant operations performed on the task process management module, and the interface is triggered by the corresponding script ID, so that the data is transmitted via the trigger interface. Based on the above method, the correspondence between script-indicator-process is realized, so as to realize the hierarchical management of workflow based on scripts. Based on this management mode, it is convenient for users to manage massive scripts step by step, so as to find all scripts of corresponding tasks more clearly and accurately, improve the operation efficiency, and at the same time, each script, indicator, process, and task are stored and managed in the form of metadata, so as to effectively realize the standardization of script, indicator, process, and task data, and ensure the accuracy and consistency of script, indicator, task, and process data.

[0077] See also Figure 5 As shown, a metadata script management device provided by an embodiment of the present application includes: a first creation module 501, a second creation module 502, a third creation module 503, and an operation module 504, wherein:

[0078] The first creation module 501 is used to select a target script set from various script sets included in a preset metadata script library, and to create a target indicator corresponding to at least the target script set.

[0079] The second creation module 502 is used to select a target indicator set from various indicator sets included in the preset metadata indicator library based on the target indicator, and to create a target process corresponding to at least the target indicator set.

[0080] The third creation module 503 is used to select a target process set from various process sets included in the preset metadata process library based on the target process, and create a corresponding target task based on the target process set.

[0081] The running module 504 is used to receive a task running instruction triggered by the target object for the target task, and run all scripts in the target script set based on the task running instruction.

[0082] Optional, see Figure 6 As shown, the metadata script management device further includes:

[0083] The first communication module 505 is used to generate corresponding script running logs according to the running status of each script in the target script set, and send the script running logs to a designated first receiving object.

[0084] Optional, see Figure 7 As shown, the metadata script management device further includes:

[0085] The second communication module 506 is used to generate a corresponding alarm log based on the relevant information of the target object, and send the alarm log to a designated second receiving object.

[0086] In an optional embodiment, before selecting a target script set from various script sets included in a preset metadata script library, the first creation module 501 is further used to:

[0087] A metadata script library is created, wherein the metadata script library includes a plurality of scripts, and the plurality of scripts are respectively stored in the metadata script library in the form of metadata.

[0088] In an optional embodiment, after creating at least the target indicator corresponding to the target script set, the first creation module 501 is further used to:

[0089] Create information about the target indicator, wherein the information about the target indicator at least includes: an indicator name of the target indicator.

[0090] A mapping relationship between the target indicator and the information of the target indicator is created.

[0091] In an optional embodiment, when all scripts in the target script set are executed based on the task execution instruction, the execution module 504 is specifically used to:

[0092] Get the order of each process in the target process set.

[0093] According to the arrangement order of the various processes, the running order of the various scripts in the corresponding target script set is determined, and all the scripts in the target script set are run in sequence according to the running order.

[0094] In an optional embodiment, after running all scripts in the target script set based on the task running instruction, the running module 504 is further used to:

[0095] Obtain the alarm data generated when each script in the target script set is run, where:

[0096] If the alarm data meets the preset alarm condition, the target object is determined to be a target alarm object.

[0097] If the alarm data does not meet the preset alarm condition, it is determined that the target object is not a target alarm object.

[0098] Based on the same inventive concept as the above-mentioned application embodiment, the present application embodiment also provides an electronic device, which can be used for script management. In one embodiment, the electronic device can be a server, or a terminal device or other electronic device. In this embodiment, the structure of the electronic device can be as follows: Figure 8 As shown, it includes a memory 801 , a communication interface 803 and one or more processors 802 .

[0099] The memory 801 is used to store computer programs executed by the processor 802. The memory 801 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system and programs required for running the instant messaging function, etc.; the data storage area may store various instant messaging information and operation instruction sets, etc.

[0100] The memory 801 may be a volatile memory, such as a random-access memory (RAM); the memory 801 may also be a non-volatile memory, such as a read-only memory, a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD), or the memory 801 may be any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 801 may be a combination of the above memories.

[0101] The processor 802 may include one or more central processing units (CPU) or a digital processing unit, etc. The processor 802 is used to implement the above metadata script management method when calling the computer program stored in the memory 801 .

[0102] The communication interface 803 is used to communicate with terminal devices and other servers.

[0103] The specific connection medium between the memory 801, the communication interface 803 and the processor 802 is not limited in the embodiment of the present application. Figure 8 In the embodiment, the memory 801 and the processor 802 are connected via a bus 804. The bus 804 is Figure 8 The connections between other components are shown in bold lines, and are not intended to be limiting. Bus 804 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 8 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0104] According to one aspect of the present application, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. The processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes any one of the metadata script management methods in the above-mentioned embodiments. The program product can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, - but not limited to - an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0105] The metadata script management method provided in the embodiment of the present application realizes script-based hierarchical management of workflows by pre-selecting and constructing the correspondence between scripts, indicators, and processes. Based on this management mode, users can conveniently manage massive scripts step by step, thereby facilitating clearer and more accurate identification of all scripts for corresponding tasks and improving operating efficiency. At the same time, each script, indicator, process, and task are stored and managed in the form of metadata, thereby effectively realizing the standardization of the use of script, indicator, process, and task data, and ensuring the accuracy and consistency of script, indicator, task, and process data.

[0106] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0107] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0108] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0109] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0110] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A metadata script management method, characterized in that: include: A target script set is selected from various script sets contained in a preset metadata script library, and a target indicator corresponding to at least the target script set is created, wherein an indicator represents a minimum unit of a function completed by at least one script, and one indicator represents one or more scripts; the target indicator corresponds to information of the target indicator, and the information of the target indicator includes: a group to which the target indicator belongs, a description of the target indicator, a task running plan of the target indicator, a task running command of the target indicator, and a task running node of the target indicator; Selecting a target indicator set from each indicator set included in a preset metadata indicator library based on the target indicator, and creating a target process corresponding to at least the target indicator set, wherein a process represents a minimum unit that completes a function through at least one indicator, and one process corresponds to one or more indicators; Selecting a target process set from each process set included in a preset metadata process library based on the target process, and creating a corresponding target task based on the target process set; A task execution instruction triggered by a target object for the target task is received, and all scripts in the target script set are executed based on the task execution instruction.

2. The method according to claim 1, characterized in that Before selecting the target script collection from the various script collections included in the preset metadata script library, the following are also included: A metadata script library is created, wherein the metadata script library includes a plurality of scripts, and the plurality of scripts are respectively stored in the metadata script library in the form of metadata.

3. The method according to claim 1, characterized in that After creating at least a target indicator corresponding to the target script set, the method further includes: information for creating said target indicators; A mapping relationship between the target indicator and the information of the target indicator is created.

4. The method according to claim 1, 2 or 3, characterized in that: Run all scripts in the target script collection, including: Obtaining the arrangement order of each process in the target process set; According to the arrangement order of the various processes, the running order of the various scripts in the corresponding target script set is determined, and all the scripts in the target script set are run in sequence according to the running order.

5. The method according to claim 4, characterized in that After running all the scripts in the target script set based on the task running instruction, the method further includes: According to the running status of each script in the target script set, corresponding script running logs are generated respectively, and the script running logs are sent to a designated first receiving object.

6. The method according to claim 5, characterized in that After running all the scripts in the target script set based on the task running instruction, the method further includes: Obtain the alarm data generated when each script in the target script set is run, where: If the alarm data meets the preset alarm condition, the target object is determined to be a target alarm object; If the alarm data does not meet the preset alarm condition, it is determined that the target object is not a target alarm object.

7. The method according to claim 6, characterized in that If at least one of the scripts in the target script set fails when the scripts in the target script set are executed, after determining that the target object is a target alarm object, the method further includes: Based on the relevant information of the target object, a corresponding alarm log is generated, and the alarm log is sent to a designated second receiving object.

8. A metadata script management device, characterized in that: include: A first creation module is used to select a target script set from various script sets included in a preset metadata script library, and to create a target indicator corresponding to at least the target script set, wherein an indicator represents a minimum unit for completing a function through at least one script, and one indicator corresponds to one or more scripts; the target indicator corresponds to information of the target indicator, and the information of the target indicator includes: a group to which the target indicator belongs, a description of the target indicator, a task running plan of the target indicator, a task running command of the target indicator, and a task running node of the target indicator; A second creation module is used to select a target indicator set from each indicator set included in a preset metadata indicator library based on the target indicator, and to create a target process corresponding to at least the target indicator set, wherein a process represents a minimum unit that completes a function through at least one indicator, and one process corresponds to one or more indicators; A third creation module is used to select a target process set from each process set included in a preset metadata process library based on the target process, and create a corresponding target task based on the target process set; A running module, used for receiving a task running instruction triggered by a target object for the target task, and running all scripts in the target script set based on the task running instruction; The first communication module is used to generate corresponding script running logs according to the running status of each script in the target script set, and send the script running logs to a designated first receiving object; the second communication module is used to generate corresponding alarm logs based on relevant information of the target object, and send the alarm logs to a designated second receiving object.

9. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the metadata script management method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images