CN113918204A - Metadata script management method and device, electronic equipment and storage medium - Google Patents
Metadata script management method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN113918204A CN113918204A CN202111030076.5A CN202111030076A CN113918204A CN 113918204 A CN113918204 A CN 113918204A CN 202111030076 A CN202111030076 A CN 202111030076A CN 113918204 A CN113918204 A CN 113918204A
- Authority
- CN
- China
- Prior art keywords
- target
- script
- index
- scripts
- metadata
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
- G06F16/164—File meta data generation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2457—Query processing with adaptation to user needs
- G06F16/24573—Query processing with adaptation to user needs using data annotations, e.g. user-defined metadata
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Data Mining & Analysis (AREA)
- Software Systems (AREA)
- Entrepreneurship & Innovation (AREA)
- Databases & Information Systems (AREA)
- Human Computer Interaction (AREA)
- Computational Linguistics (AREA)
- Library & Information Science (AREA)
- Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Stored Programmes (AREA)
Abstract
According to the metadata script management method, the device, the electronic equipment and the storage medium, the corresponding relation between the script, the index and the flow is constructed through preselection, workflow hierarchical management based on the script is achieved, based on the management mode, a user can conveniently manage massive scripts step by step, all scripts corresponding to tasks can be conveniently and clearly found out, the operation efficiency is improved, meanwhile, all the scripts, the indexes, the flow and the tasks are stored and managed in a metadata mode, the use standardization of the scripts, the indexes, the flow and the task data is effectively achieved, and the accuracy and consistency of the scripts, the indexes, the tasks and the flow data are guaranteed.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a metadata script management method and apparatus, an electronic device, and a storage medium.
Background
A script is a set of code used to replace a human to perform some function or operation in the process of executing a task or some other operation related to the system. Software users often come in contact with a huge amount of scripts in daily work, wherein different scripts are used to perform different tasks.
In the prior art, when a user uses a certain software and executes a certain operation, the user needs to find out all scripts corresponding to the operation, package all corresponding scripts into an executable file, and execute all scripts in the executable file by executing a related execution instruction. With the increasing number of web items and scripts, it becomes increasingly difficult for users to find scripts. On the basis, an effective method is needed to be provided to manage massive scripts, so that a user can find out all corresponding scripts more clearly and accurately, and the running efficiency is improved.
Metadata is descriptive data information about data, background information that describes the content, quality, condition, and other relevant characteristics of the data, and can facilitate efficient use of data sets, helping data production units to efficiently maintain and manage the data. Therefore, the metadata technology is applied to the script management method, and the operation efficiency is improved.
Disclosure of Invention
The embodiment of the application provides a metadata script management method and device, electronic equipment and a storage medium, and aims to perform structured hierarchical management on massive scripts so as to improve the operation efficiency.
In a first aspect, an embodiment of the present application provides a metadata script management method, including:
selecting a target script set from each script set contained in a preset metadata script library, and creating at least a target index corresponding to the target script set;
selecting a target index set based on the target index from each index set contained in a preset metadata index library, and creating a target process at least corresponding to the target index set;
selecting a target flow set from each flow set contained in a preset metadata flow library based on the target flow, and creating a corresponding target task based on the target flow set;
and receiving a task running instruction triggered by a target object aiming at the target task, and running all scripts in the target script set based on the task running instruction.
In a second aspect, an embodiment of the present application further provides a metadata script management apparatus, including:
the system comprises a first establishing module, a second establishing module and a third establishing module, wherein the first establishing module is used for selecting a target script set from all script sets contained in a preset metadata script library and establishing at least a target index corresponding to the target script set;
the second establishing module is used for selecting a target index set based on the target index from each index set contained in a preset metadata index library and establishing a target process at least corresponding to the target index set;
a third creating module, configured to select a target flow set based on the target flow from each flow set included in a preset metadata flow library, and create a corresponding target task based on the target flow set;
the running module is used for receiving a task running instruction triggered by a target object aiming at the target task and running all scripts in the target script set based on the task running instruction;
optionally, the first communication module is configured to generate corresponding script running logs according to running conditions of scripts in the target script set, and send the script running logs to a specified first receiving object; and the second communication module is used for generating a corresponding alarm log based on the related information of the target object and sending the alarm log to a specified second receiving object.
In an optional embodiment, before selecting a target script set from script sets included in a preset metadata script library, the first creating module is further configured to:
and creating a metadata script library, wherein the metadata script library comprises a plurality of scripts, and the plurality of scripts are stored in the metadata script library in a metadata mode respectively.
In an optional embodiment, after creating at least one target metric corresponding to the target script set, the first creating module is further configured to:
creating information of the target index, wherein the information of the target index at least comprises: an index name of the target index.
And creating a mapping relation between the target index and the information of the target index.
In an optional embodiment, when all the scripts in the target script set are executed based on the task execution instruction, the execution module is specifically configured to:
and acquiring the arrangement sequence of each process in the target process set.
And determining the running sequence of each script in the corresponding target script set according to the arrangement sequence of each flow, and sequentially running all scripts in the target script set according to the running sequence.
In an optional embodiment, after all the scripts in the target script set are executed based on the task execution instruction, the execution module is further configured to:
acquiring alarm data generated when each script runs in the target script set, wherein:
and if the alarm data meet the preset alarm conditions, judging that the target object is the target alarm object.
And if the alarm data does not meet the preset alarm condition, judging that the target object is not the target alarm object.
In a third aspect, an embodiment of the present application further provides an electronic device, including a memory and a processor, where the memory stores a computer program executable on the processor, and when the computer program is executed by the processor, the processor is enabled to implement any one of the metadata script management methods in the first aspect.
In a fourth aspect, the present application further provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the metadata script management method of the first aspect is implemented.
Drawings
FIG. 1 is a diagram illustrating a metadata script management method according to an embodiment of the present application;
FIG. 2 is a diagram illustrating a logical architecture of a metadata script management method according to an embodiment of the present disclosure;
FIG. 3 is a diagram illustrating a logical architecture of a metadata script management method according to an embodiment of the present application;
FIG. 4 is a diagram of a metadata script management system architecture provided by an embodiment of the present application;
fig. 5 is a schematic diagram of a first metadata script management apparatus according to an embodiment of the present application;
fig. 6 is a schematic diagram of a second metadata script management apparatus according to an embodiment of the present application;
FIG. 7 is a diagram illustrating a third metadata script management apparatus according to an embodiment of the present application;
fig. 8 is a schematic view of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present invention will be described clearly and completely with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
According to the metadata script management method provided by the embodiment of the application, the corresponding relation between the script, the index and the process is constructed through preselection, the workflow hierarchical management based on the script is realized, and based on the management mode, a user can conveniently manage massive scripts step by step, so that all scripts corresponding to tasks can be conveniently, clearly and accurately found, and the operation efficiency is improved.
In order to promote efficient utilization of relevant data sets in the script task flow management device provided by the embodiment of the application, a relevant metadata script library is created in advance, wherein the metadata script library comprises a plurality of scripts, and each script is stored in the metadata script library in a metadata form, so that the method is favorable for standardization of script data use, and the accuracy and consistency of script data are ensured.
Referring to fig. 1, a metadata script management method provided in an embodiment of the present application includes:
step 101: selecting a target script set from each script set contained in a preset metadata script library, and creating at least a target index corresponding to the target script set.
The index represents the minimum unit for completing a certain function through at least one script, namely one index can correspondingly represent a plurality of scripts. Therefore, based on the target index for creating the corresponding target set, the initial management of the target script set can be realized, and according to the mapping relation between the target index and the target script set, the purpose of finding a plurality of scripts in the target script set through one target index can be realized, so that the calculation amount of searching is reduced.
In the embodiment of the application, each appointed script set is obtained from a preset metadata script library, and each script set comprises at least one script. The obtained script set comprises a target script set to be executed, and each script in the target script set is stored in the metadata script library in a metadata form, so that each obtained script set also stores related content in a metadata form.
For example, the following script sets are obtained from a preset metadata script library: { A, B }, { A, B, C }, { D, F }, wherein each letter represents a metadata script, and the metadata scripts are respectively stored in the form of metadata, and in the embodiment of the application, { A, B } is designated as a target script set.
Alternatively, in addition to extracting the script from the preset metadata script library, the script can also be obtained based on an upload script operation in the form of metadata by the user. Specifically, a user manually uploads a specified number of metadata scripts, and all the scripts are used for constructing a script set, so that the script set can also be regarded as a target script set.
For example, a user uploads scripts a, B, C in the form of metadata, and the scripts are used to construct a script set, i.e., { a, B, C }, and the script set { a, B, C } obtained based on this way can also be considered as a target script set.
In the embodiment of the application, a target script set is selected based on each obtained script set, and similarly, the target script set stores related content in a metadata manner.
Optionally, after obtaining each script set and creating at least a target index corresponding to the target script set, the following operations are further performed: creating information of a target index, wherein the information of the target index at least comprises: index name of target index. In the embodiment of the application, at least the index name of the target index is obtained.
For example, according to a specified target script set { a, B }, a target index a corresponding to at least the target script set is created, and an index name a of the target index a is set, thereby facilitating management.
Optionally, the following information may also be used as the information of the target index: grouping of the target indexes, description of the target indexes, task operation plans of the target indexes, task operation commands of the target indexes, task operation nodes of the target indexes and the like.
And then, creating a corresponding relation between the target index and the information of the target index, so that the information of the target index can be obtained according to the created corresponding relation and the target index, thereby facilitating the user to know, inquire and classify the target index based on the information of the target index and facilitating the user to manage the target index.
Step 102: selecting a target index set based on a target index from each index set contained in a preset metadata index library, and creating a target process at least corresponding to the target index set.
The process represents a minimum unit which completes a certain function through at least one index, that is, one process can represent a plurality of indexes correspondingly, in other words, a plurality of index sets can also be represented, each index set comprises at least one index, and each index is stored in a metadata form. Referring to fig. 2, since the index sets often have different categories, it is cumbersome to associate the related scripts directly based on the indexes. Therefore, by dividing the task, that is, dividing a complete task into a plurality of flows, each flow represents a subtask, and each flow includes at least one index set, the corresponding relationship between the flows and the indexes can be established, so that the hierarchical management of the scripts can be further realized, and in short, more scripts can be corresponding to one flow.
For example, according to the process 1, a set of indices { a, b }, { a, b, c }, { d, f } is selected from a metadata index database, where a is a target index. In this way, if one process corresponds to the index set { a, b }, scripts corresponding to the processes, that is, scripts corresponding to the indexes a and b, respectively, and if the script set corresponding to b is { G }, each script corresponding to the index set { a, b } includes: a, B and G.
Step 103: and selecting a target flow set from each flow set contained in a preset metadata flow library based on the target flow, and creating a corresponding target task based on the target flow set.
The method comprises the steps of selecting a target flow set based on a target flow, and creating a corresponding target task according to the target flow set.
When creating a target task, the target process set is stored in the preset metadata process library in the form of metadata, and when creating the target task, it should be noted that the target task should also be stored in the form of metadata, which facilitates standardization of task use.
For example: and selecting a target process set {1,2,3} based on the target process (process 1), and creating a corresponding target task alpha according to the target process set {1,2,3 }.
Step 104: and receiving a task running instruction triggered by the target object aiming at the target task, and running all scripts in the target script set based on the task running instruction.
As can be seen from the above description, one task corresponds to at least one process set, one process set corresponds to at least one index set, and one index set corresponds to at least one script set, that is, one task corresponds to all scripts in multiple script sets, so as to implement hierarchical management of task-process-index-scripts. Therefore, when a task running instruction triggered by the target task is received, all scripts corresponding to the target task, namely all scripts in the target script set, can be run according to the task running instruction.
As shown in fig. 3, when a task is executed, a sequence exists between the flows constituting the task, so that, optionally, the sequence of the flows in the target flow set is obtained, the running sequence of each script in the corresponding target script set is determined according to the sequence of the flows, and all scripts in the target script set are run in sequence according to the running sequence, so that when each script runs in sequence, the execution sequence between the flows corresponding to each script also meets the preset requirement.
After the task is executed, in order to further facilitate the user to know the running status of each script, a log of the task execution result is designed, specifically:
and respectively generating corresponding script running logs according to the running state of each script in the target script set, and sending each script running log to a specified first receiving object.
The first receiving object may be, from the perspective of the entity apparatus, an external analysis device connected to the first receiving object, or may be a metadata script management apparatus itself; furthermore, the first receiving object can also be a designated mailbox or account, the script running log can be received, and the running state of the script in the task running process can be analyzed.
Optionally, after all the scripts in the target script set are run based on the task running instruction, alarm data generated when each script runs in the target script set can be obtained, and whether the target object is a target alarm object with a threat or not is determined according to the alarm data, where:
and if the alarm data meet the preset alarm conditions, judging that the target object is the target alarm object.
And if the alarm data does not meet the preset alarm condition, judging that the target object is not the target alarm object.
Optionally, after the target object is determined to be the target alarm object, a corresponding alarm log is generated based on the relevant information of the target object, and the alarm log is sent to the designated second receiving object.
And correspondingly generating corresponding alarm logs through the alarm data generated by the script, so that a user can analyze whether the target object has threat or not through the alarm logs. Specifically, if an abnormality occurs in the task running process, the task can be checked according to the alarm log, and the target object is determined to be dangerous, so that the same abnormal accident is avoided from happening again. Sending the information to a designated second receiving object, wherein the second receiving object is the object capable of receiving the alarm log: such as mail box, short message, etc.
The scheme of the embodiment of the application can be applied to a plurality of scenes needing to manage the massive scripts. For example, in some government work scenarios, when filling out some relevant forms, it is necessary to search in the internal database for some valid entries. If the scripts are not effectively managed in a grading mode, searching can be conducted only according to massive scripts directly, and the calculated amount is large. At this time, by the metadata script management method provided in the embodiment of the present application, the whole search task is first divided into: determining search terms, searching relevant terms in an internal database, and presenting search results. And corresponding index sets are respectively found according to the three flows, and corresponding script sets are found and executed according to the obtained index sets, so that the method does not need to search scripts for a large number of times, only needs to execute successive search under each level of task-flow-index-script, and greatly reduces the calculation amount required by search.
For a common operable web page, the web page usually has various executable operations that can be selected and confirmed by a user, and different results are presented according to the user operations. And a plurality of scripts are corresponding to the back of each executable operation, for example, in some common web games, corresponding scripts need to be executed according to user execution operations, so as to present different screen results, and at this time, corresponding scripts can also be found and executed in sequence according to the metadata script management method provided by the embodiment of the present application.
Referring to fig. 4, a system architecture of a corresponding metadata script management system is designed based on the metadata script management method provided in the embodiment of the present application, where the system includes three parts, namely an interface module, a script index management module, and a task flow triggering module, each part includes related operations for managing each data, and the data of each module are interconnected.
In the embodiment of the application, the task flow management module triggers the designated task based on the operation of the user, and can also preset the specific execution time of the task through the operation of the user. And when an immediate task running instruction is triggered, selecting a relevant script from the script index management module through data transmission. Similarly, the script index management module is responsible for storing and managing scripts and indexes, relevant managers can execute operations such as script creation, script marking, script deletion, script grouping and the like in the script index management module to manage the scripts, and the indexes can also be managed through operations such as index creation, index editing, index deletion, index grouping and the like, so that the lower-layer scripts are indirectly managed. In general, each part in the script index management module is periodically maintained or related operations are performed by related management personnel according to specific situations to modify related data. And based on the task trigger instruction, after all the scripts are operated, generating corresponding alarm data according to the operation conditions of the scripts, feeding the alarm data back to the task flow management module, and informing task flow managers of which scripts have faults, thereby facilitating troubleshooting of the fault scripts.
In the interface module, related personnel can select a designated script interface and trigger the interface according to the script ID, so that data interaction with the task flow management module is realized. Specifically, the script interface is determined by the relevant operation executed on the task flow management module, and the interface is triggered by the corresponding script ID, so that the data is transmitted through the trigger interface. Based on the mode, the corresponding relation between the script, the index and the process is realized, and therefore the workflow hierarchical management based on the script is realized. Based on the management mode, a user can conveniently manage massive scripts step by step, so that all scripts corresponding to tasks can be conveniently and clearly found out, the operation efficiency is improved, meanwhile, all scripts, indexes, processes and tasks are stored and managed in a metadata mode, the use standardization of the scripts, the indexes, the processes and the task data is effectively achieved, and the accuracy and consistency of the scripts, the indexes, the tasks and the process data are guaranteed.
Referring to fig. 5, a metadata script management apparatus provided in an embodiment of the present application includes: a first creating module 501, a second creating module 502, a third creating module 503, and an executing module 504, wherein:
a first creating module 501, configured to select a target script set from script sets included in a preset metadata script library, and create a target index corresponding to at least the target script set.
A second creating module 502, configured to select a target index set based on the target index from each index set included in a preset metadata index library, and create a target process at least corresponding to the target index set.
A third creating module 503, configured to select a target flow set based on the target flow from each flow set included in a preset metadata flow library, and create a corresponding target task based on the target flow set.
The running module 504 is configured 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.
Optionally, as shown in fig. 6, the metadata script management apparatus further includes:
and the first communication module 505 is configured to generate corresponding script execution logs according to the execution status of each script in the target script set, and send the script execution logs to a specified first receiving object.
Optionally, as shown in fig. 7, the metadata script management apparatus further includes:
and the second communication module 506 is configured to generate a corresponding alarm log based on the relevant information of the target object, and send the alarm log to a specified second receiving object.
In an alternative embodiment, before selecting a target script set from script sets included in a preset metadata script library, the first creating module 501 is further configured to:
and creating a metadata script library, wherein the metadata script library comprises a plurality of scripts, and the plurality of scripts are stored in the metadata script library in a metadata mode respectively.
In an optional embodiment, after creating at least one target metric corresponding to the target script set, the first creating module 501 is further configured to:
creating information of the target index, wherein the information of the target index at least comprises: an index name of the target index.
And creating a mapping relation between the target index and the information of the target index.
In an optional embodiment, when all the scripts in the target script set are executed based on the task execution instruction, the execution module 504 is specifically configured to:
and acquiring the arrangement sequence of each process in the target process set.
And determining the running sequence of each script in the corresponding target script set according to the arrangement sequence of each flow, and sequentially running all scripts in the target script set according to the running sequence.
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 configured to:
acquiring alarm data generated when each script runs in the target script set, wherein:
and if the alarm data meet the preset alarm conditions, judging that the target object is the target alarm object.
And if the alarm data does not meet the preset alarm condition, judging that the target object is not the target alarm object.
Based on the same inventive concept as the embodiment of the application, the embodiment of the application also provides an electronic device, and the electronic device can be used for script management. In one embodiment, the electronic device may be a server, a terminal device, or other electronic device. In this embodiment, the electronic device may be configured as shown in FIG. 8, and include a memory 801, a communication interface 803, and one or more processors 802.
A memory 801 for storing computer programs executed by the processor 802. The memory 801 may mainly include a program storage area and a data storage area, where the program storage area may store an operating system, programs required for running an instant messaging function, and the like; the storage data area can store various instant messaging information, operation instruction sets and the like.
The memory 801 may be a volatile memory (volatile memory), such as a random-access memory (RAM); the memory 801 may also be a non-volatile memory (non-volatile memory) such as, but not limited to, a read-only memory (rom), a flash memory (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 desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 801 may be a combination of the above memories.
The processor 802 may include one or more Central Processing Units (CPUs), or be a digital Processing Unit, etc. The processor 802 is configured to implement the above-described metadata script management method when calling a computer program stored in the memory 801.
The communication interface 803 is used for communication with terminal devices and other servers.
The specific connection medium among the memory 801, the communication interface 803 and the processor 802 is not limited in the embodiments of the present application. In the embodiment of the present application, the memory 801 and the processor 802 are connected by a bus 804 in fig. 8, the bus 804 is represented by a thick line in fig. 8, and the connection manner between other components is merely illustrative and is not limited. The bus 804 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 8, but this is not intended to represent only one bus or type of bus.
According to an aspect of the application, a computer program product or computer program is provided, comprising computer instructions, the computer instructions being stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions to cause the computer device to execute any one of the metadata script management methods in the above embodiments. The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
According to the metadata script management method provided by the embodiment of the application, the corresponding relation between the script, the index and the process is constructed through preselection, the workflow hierarchical management based on the script is realized, based on the management mode, a user can conveniently manage massive scripts step by step, all scripts corresponding to tasks can be conveniently, clearly and accurately found, the operation efficiency is improved, meanwhile, all the scripts, the indexes, the process and the tasks are stored and managed in a metadata mode, the use standardization of the scripts, the indexes, the process and the task data is effectively realized, and the accuracy and consistency of the scripts, the indexes, the tasks and the process data are ensured.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such 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 intended to include such modifications and variations as well.
Claims (10)
1. A method for metadata script management, comprising:
selecting a target script set from each script set contained in a preset metadata script library, and creating at least a target index corresponding to the target script set;
selecting a target index set based on the target index from each index set contained in a preset metadata index library, and creating a target process at least corresponding to the target index set;
selecting a target flow set from each flow set contained in a preset metadata flow library based on the target flow, and creating a corresponding target task based on the target flow set;
and receiving a task running instruction triggered by a target object aiming at the target task, and running all scripts in the target script set based on the task running instruction.
2. The method of claim 1, wherein before selecting a target script set from the script sets contained in the predetermined metadata script library, the method further comprises:
and creating a metadata script library, wherein the metadata script library comprises a plurality of scripts, and the plurality of scripts are stored in the metadata script library in a metadata mode respectively.
3. The method of claim 1, wherein after creating at least a target metric corresponding to the set of target scripts, further comprising:
creating information of the target index, wherein the information of the target index at least comprises: an index name of the target index;
and creating a mapping relation between the target index and the information of the target index.
4. A method according to claim 1,2 or 3, wherein running all scripts in the set of target scripts comprises:
acquiring the arrangement sequence of each process in the target process set;
and determining the running sequence of each script in the corresponding target script set according to the arrangement sequence of each flow, and sequentially running all scripts in the target script set according to the running sequence.
5. The method of claim 4, wherein after executing all scripts in the target script set based on the task execution instructions, further comprising:
and respectively generating corresponding script running logs according to the running state of each script in the target script set, and sending each script running log to a specified first receiving object.
6. The method of claim 5, wherein after executing all scripts in the target script set based on the task execution instructions, further comprising:
acquiring alarm data generated when each script runs in the target script set, wherein:
if the alarm data meet preset alarm conditions, judging that the target object is a target alarm object;
and if the alarm data does not meet the preset alarm condition, judging that the target object is not the target alarm object.
7. The method according to claim 6, wherein if there is a failure in at least one of the scripts during the running of each script in the target script set, after determining that the target object is a target alarm object, further comprising:
and generating a corresponding alarm log based on the related information of the target object, and sending the alarm log to a specified second receiving object.
8. A metadata script management apparatus, comprising:
the system comprises a first establishing module, a second establishing module and a third establishing module, wherein the first establishing module is used for selecting a target script set from all script sets contained in a preset metadata script library and establishing at least a target index corresponding to the target script set;
the second establishing module is used for selecting a target index set based on the target index from each index set contained in a preset metadata index library and establishing a target process at least corresponding to the target index set;
a third creating module, configured to select a target flow set based on the target flow from each flow set included in a preset metadata flow library, and create a corresponding target task based on the target flow set;
the running module is used for receiving a task running instruction triggered by a target object aiming at the target task and running all scripts in the target script set based on the task running instruction;
optionally, the first communication module is configured to generate corresponding script running logs according to running conditions of scripts in the target script set, and send the script running logs to a specified first receiving object; and the second communication module is used for generating a corresponding alarm log based on the related information of the target object and sending the alarm log to a specified second receiving object.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the metadata script management method of any one of claims 1-7 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111030076.5A CN113918204A (en) | 2021-09-03 | 2021-09-03 | Metadata script management method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111030076.5A CN113918204A (en) | 2021-09-03 | 2021-09-03 | Metadata script management method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113918204A true CN113918204A (en) | 2022-01-11 |
Family
ID=79233957
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111030076.5A Pending CN113918204A (en) | 2021-09-03 | 2021-09-03 | Metadata script management method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113918204A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114637739A (en) * | 2022-03-22 | 2022-06-17 | 平安国际融资租赁有限公司 | Database management and control method, system, computer equipment and computer storage medium |
-
2021
- 2021-09-03 CN CN202111030076.5A patent/CN113918204A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114637739A (en) * | 2022-03-22 | 2022-06-17 | 平安国际融资租赁有限公司 | Database management and control method, system, computer equipment and computer storage medium |
| CN114637739B (en) * | 2022-03-22 | 2024-10-22 | 平安国际融资租赁有限公司 | Database management and control method, system, computer equipment and computer storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110928772B (en) | Test method and device | |
| CN112416645B (en) | Fault root cause deducing and positioning method and device based on artificial intelligence | |
| CN108521339B (en) | Feedback type node fault processing method and system based on cluster log | |
| CN112631913B (en) | Method, device, equipment and storage medium for monitoring operation faults of application program | |
| CN111563016A (en) | Log collection and analysis method and device, computer system and readable storage medium | |
| US11449488B2 (en) | System and method for processing logs | |
| CN112380089A (en) | Data center monitoring and early warning method and system | |
| CN112446511A (en) | Fault handling method, device, medium and equipment | |
| CN114172785A (en) | Alarm information processing method, device, equipment and storage medium | |
| CN110941632A (en) | Database auditing method, device and equipment | |
| CN108306749B (en) | Monitoring system alarming method, monitoring system and monitoring device | |
| CN113419950A (en) | Method and device for generating UI automation script, computer equipment and storage medium | |
| CN113918204A (en) | Metadata script management method and device, electronic equipment and storage medium | |
| CN115392501A (en) | Data acquisition method and device, electronic equipment and storage medium | |
| CN107330031B (en) | Data storage method and device and electronic equipment | |
| CN104539449A (en) | Handling method and related device for fault information | |
| CN116760682B (en) | Log acquisition and filtration method, device, equipment and medium | |
| CN111752838A (en) | Question checking method and device, server and storage medium | |
| KR20220020553A (en) | Method and device for monitoring application performance in multi-cloud environment | |
| CN115225470B (en) | Business abnormality monitoring method and device, electronic equipment and storage medium | |
| CN114500249B (en) | Root cause positioning method and device | |
| KR20170122874A (en) | Apparatus for managing log of application based on data distribution service | |
| US20140081972A1 (en) | System for observing and analyzing configurations using dynamic tags and queries | |
| CN116149824A (en) | Task re-running processing method, device, equipment and storage medium | |
| CN113626288A (en) | Fault processing method, system, device, storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |