Monitoring method of assembly line tool and related equipment

Abstract

The invention discloses an assembly line tool monitoring method and related equipment, and the method comprises the steps: configuring a data source in a database, and determining the storage position of the data source in the database, the data source comprising a table structure used for counting index data generated in the operation process of an assembly line tool; collecting index data through a pre-deployed index collector, and writing the index data into the data source according to the storage position; the method comprises the steps that target index data needing to be observed by a user are obtained from a data source, a monitoring chart needed for displaying the target index data is generated in a pre-constructed monitoring display board, and when the monitoring chart is generated, monitoring content displayed by the monitoring chart is determined according to the target index data. The problems that an observation scheme of a production line tool is poor in universality and high in input cost are solved.

Description

Technical Field

[0001] The present application relates to the field of software technology, and in particular to a monitoring method and related equipment for pipeline tools. Background Art

[0002] This section is intended to provide a background or context to the embodiments of the invention recited in the claims. No admission is made that the description herein is prior art by its inclusion in this section.

[0003] In the process of software development and delivery, CI / CD (full name: continuous integration / continuous delivery or continuous deployment) pipeline tools are needed to automatically connect the software delivery model, from code migration, testing, compilation, construction to deployment to the test and production environment. There are many CI / CD pipeline tool products, such as open source Jenkins, GitFlow, GoCD, TeamCity and other pipeline tools, and there are also many closed-source pipeline tools. Some of the pipeline tools do not have the observation capability to observe the execution status of the pipeline, and although other pipeline tools have the observation capability to express the execution status of the pipeline, technical service personnel need to continuously develop targeted observation solutions for the pipeline tools used in different customer scenarios to ensure that the provided observation capabilities can objectively express the delivery status of the corresponding pipeline tools for the application software, resulting in poor versatility of the observation solutions and high investment costs. Summary of the invention

[0004] The embodiments of the present application provide a monitoring method and related equipment for pipeline tools, so as to at least solve the problems of poor versatility and high investment cost of observation schemes in the prior art.

[0005] According to one aspect of the present application, a method for monitoring a pipeline tool is also provided, characterized in that it includes:

[0006] Configuring a data source in a database and determining a storage location of the data source in the database, wherein the data source includes a table structure for counting indicator data generated during the operation of a pipeline tool;

[0007] Collecting the indicator data through a pre-deployed indicator collector, and writing the indicator data into the data source according to the storage location;

[0008] The target indicator data that the user needs to observe is obtained from the data source, and a monitoring chart required to display the target indicator data is generated in a pre-built monitoring display dashboard, wherein when generating the monitoring chart, the monitoring content displayed by the monitoring chart is determined according to the target indicator data.

[0009] In some embodiments, the indicator collector is configured with a network interface, and the step of collecting the indicator data through the pre-deployed indicator collector includes:

[0010] A network connection is established between the indicator collector and the pipeline tool based on the network interface, so that the pipeline tool sends the indicator data to the indicator collector.

[0011] In some embodiments, the pipeline tool is configured with a script for obtaining the indicator data, and the step of the pipeline tool sending the indicator data to the indicator collector includes:

[0012] When the pipeline tool initiates a network connection request to the network interface through the script, the indicator data obtained by the script is spliced ​​into the network connection request and sent to the indicator collector.

[0013] In some embodiments, the indicator data includes construction information generated by the pipeline tool in the process of building the application software, and metadata of the application software, and the step of configuring the data source in the database includes:

[0014] In the database, a pipeline status table for counting the construction information and / or an application table for counting the metadata are created to obtain the data source consisting of at least the pipeline status table and the application table;

[0015] Then, the step of the indicator collector writing the indicator data into the data source according to the storage location includes:

[0016] The construction information is written into the pipeline status table according to the storage location, and / or the metadata is written into the application table.

[0017] In some embodiments, the build information includes the number of builds, the build success status, and the build duration, wherein the monitoring chart includes:

[0018] A first table chart, wherein the monitoring content displayed in the first table chart is the pipeline status table;

[0019] and / or, a second table chart, wherein the monitoring content displayed in the second table chart is the application table;

[0020] and / or, a first statistical chart, wherein the monitoring content displayed in the first statistical chart is the number of constructions;

[0021] and / or, a second statistical chart, wherein the monitoring content displayed in the second statistical chart is an average build time, wherein the average build time is data obtained based on the number of builds and the build duration;

[0022] and / or, a third statistical chart, wherein the monitoring content displayed in the third statistical chart is the construction success status when the pipeline tool is currently building the application software;

[0023] And / or, a fourth statistical chart, wherein the monitoring content displayed by the fourth statistical chart is the construction success rate of the pipeline tool, and the construction success rate is data determined according to the construction success status.

[0024] In some of the embodiments, the construction information also includes month-on-month change information of the construction success rate, and the month-on-month change information is information determined based on the construction success rate in the previous predetermined time period and the construction success rate in the next predetermined time period, and the month-on-month change information is displayed in the first table chart.

[0025] In some embodiments, the step of obtaining target indicator data that the user needs to observe from the data source includes:

[0026] The target indicator data is obtained from the database according to the storage location and a pre-written structured query language for querying the target indicator data.

[0027] According to another aspect of the present application, a monitoring device for an assembly line tool is also provided, and the device is used to implement the monitoring method for the assembly line tool.

[0028] According to another aspect of the present application, a computer device is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the pipeline tool monitoring method when executing the computer program.

[0029] According to another aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the pipeline tool monitoring method is implemented.

[0030] According to another aspect of the present application, a computer program product is also provided. The computer program product includes a computer program. When the computer program is executed by a processor, the pipeline tool monitoring method is implemented.

[0031] In the embodiment of the present application, the indicator data generated during the operation of the pipeline tool is collected by the deployed indicator collector, and the indicator data is written into the data source. Then, the monitoring content of the monitoring chart generated in the monitoring display board is determined according to the indicator data. The data collection and display logic supports the access of various types of pipeline tools. When the customer replaces the pipeline tool, there is no need to redevelop and configure the observation plan. It supports users to flexibly display the indicator data used to indicate the health of the pipeline tool through the monitoring display board according to their actual observation needs, thereby ensuring the objective expression of the delivery status of the pipeline tool for the application software, with good versatility and low investment cost. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The drawings constituting a part of the present application are used to provide a further understanding of the present application. The illustrative embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0033] Figure 1 A flow chart of a method for monitoring an assembly line tool provided by an embodiment of the present invention;

[0034] Figure 2 This is an architecture diagram of a monitoring system provided in one embodiment of the present invention. DETAILED DESCRIPTION

[0035] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0036] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0037] Although some pipeline tools have observation capabilities to express the execution status of the pipeline, the inventors of the present invention have found through in-depth research that its observation capabilities are difficult to provide reference to the responsible person through unified indicator data. For example, using the Jenkins pipeline dashboard as an example, the details that can be displayed by the Jenkins pipeline dashboard mainly include the name of the project and the overall health status. The Jenkins pipeline dashboard uses a weather icon to represent the overall health status of a pipeline / project or a branch of its repository. The overall health status cannot objectively express the delivery status of the software. If the dashboard's observation data needs to be expanded, although the monitoring items of this dashboard can be modified through the Jenkins custom interface, it only supports the use scenario of Jenkins, a pipeline tool, and cannot support other pipeline tools. If the customer uses other pipeline tools, this type of dashboard needs to be redeveloped and configured, which has poor versatility and extremely high investment costs.

[0038] In view of the above problems, the first embodiment of the present invention provides a monitoring method for pipeline tools, such as Figure 1 As shown, the method comprises the following steps:

[0039] Step S11: Configure the data source in the database and determine the storage location of the data source in the database, wherein the data source includes a table structure for the indicator data generated during the operation of the statistical pipeline tool. The database is recommended to use the relational database service (RDS for short), which is a ready-to-use, stable, reliable, and elastically scalable online database service. It has multiple security protection measures to ensure the security of the collected indicator data.

[0040] Step S12: Collect indicator data through the pre-deployed indicator collector, and write the indicator data into the data source according to the storage location. The indicator collector in the embodiment of the present invention can be a data collection service written and implemented based on Java, supporting information collection of general pipeline tools, and realizing simple and convenient deployment. In terms of resources, it only needs to rely on the database for storing the collected indicator data, and has very low resource requirements.

[0041] Step S13: Obtain the target indicator data that the user needs to observe from the data source, and generate the monitoring chart required to display the target indicator data in the pre-built monitoring display dashboard, wherein when generating the monitoring chart, the monitoring content displayed by the monitoring chart is determined according to the target indicator data. After the embodiment of the present invention stores the collected indicator data uniformly into the data source, it supports the user to flexibly select the corresponding indicator data for monitoring and display in the pre-built monitoring display dashboard according to their actual observation needs. Among them, the monitoring display dashboard can be a visualization dashboard obtained by building Grafana. Grafana is an open source monitoring data analysis and visualization suite, which is most commonly used for visualization analysis of time series data for infrastructure and application data analysis, and can also be used in other fields that require data visualization analysis. The embodiment of the present invention uses Grafana to build a monitoring display dashboard to help users better query, visualize, alarm, and analyze indicator data that users care about.

[0042] The embodiment of the present invention collects the indicator data generated during the operation of the pipeline tool through the deployed indicator collector, writes the indicator data into the data source, and then determines the monitoring content of the monitoring chart generated in the monitoring display board according to the indicator data, so as to provide reference for the person in charge. The data collection and display logic supports the access of various types of pipeline tools. When the customer replaces the pipeline tool, there is no need to redevelop and configure the observation plan. It supports users to flexibly display the indicator data used to indicate the health of the pipeline tool through the monitoring display board according to their actual observation needs, thereby ensuring the objective expression of the delivery status of the pipeline tool for the application software, with good versatility and low investment cost.

[0043] The indicator collector is configured with a network interface. In step S12, the step of collecting indicator data through the pre-deployed indicator collector includes: establishing a network connection between the indicator collector and the pipeline tool based on the network interface, so that the pipeline tool sends the indicator data to the indicator collector. That is, after the indicator collector provides the network interface to the pipeline tool, the pipeline tool directly initiates an http request to call the network interface to establish a network connection with the indicator collector, thereby ensuring that the indicator collector collects the indicator data. Among them, http is the abbreviation of HyperText Transport Protocol.

[0044] In an embodiment of the present invention, the pipeline tool is configured with a script for obtaining indicator data, and the embodiment of the present invention can continuously obtain the indicator data generated during the operation of the pipeline tool by running the script. Then, the step of the pipeline tool sending the indicator data to the indicator collector includes: when the pipeline tool initiates a network connection request to the network interface through the script, the indicator data obtained by the script is spliced ​​in the network connection request and sent to the indicator collector. While realizing the collection of indicator data, splicing the indicator data in the network connection request improves the transmission efficiency of the indicator data. Among them, the network interface can be RESTFul API, which is a REST-style interface, an architectural style, independent of programming language and platform, and usually uses http as a transmission protocol. The embodiment of the present invention uses RESTFul API to be better integrated in the indicator collector, and because RESTFul API can get rid of the limitations of the client where the pipeline tool is located, it supports different pipeline tools to send indicator data to the indicator collector by calling the RESTFul API, further ensuring the universality of the method provided by the embodiment of the present invention for different pipeline tools.

[0045] In step S11, the indicator data in the embodiment of the present invention includes the construction information generated in the process of the pipeline tool building the application software, and the metadata of the application software. The step of configuring the data source in the database includes: in the database, creating a pipeline state table for counting the construction information, and / or, an application table for counting the metadata, to obtain a data source consisting of at least the pipeline state table and the application table. Then, the step of the indicator collector writing the indicator data to the data source according to the storage location includes: writing the construction information to the pipeline state table according to the storage location, and / or, writing the metadata to the application table. The embodiment of the present invention counts and stores the metadata related to the construction information and the application software respectively, and when the relevant indicator data is needed to be retrieved later, it can be queried and obtained in the corresponding table structure. Among them, the construction information is such as the identity of the application software built by the pipeline tool, the construction time information (such as the construction time), the construction success of the built application software, and the deployment environment (container cluster, mirror, etc.) of the pipeline tool itself, the deployment frequency, the deployment success rate, the deployment time and other indicators. The metadata of the application software includes data information such as the application name of the application software built by the pipeline tool, the microservices used to build the application software, and the version number of the application software. The embodiment of the present invention can enable users to display the required application, environment, time data and other indicator data through the monitoring display board by collecting statistics on the above indicator data in the database, so as to determine the overall health status of the pipeline tool based on the displayed indicator data, and realize that the software manager can understand and evaluate the quality of the software built by the pipeline tool through the unified application, environment, time data and other indicators, thereby ensuring the efficient development efficiency.

[0046] Specifically, the construction information in the embodiment of the present invention includes the number of constructions, the state of successful construction, and the construction duration, wherein the monitoring chart includes a first table chart, a second table chart, a first statistical chart, a second statistical chart, a third statistical chart, and a fourth statistical chart. Among them, the monitoring content displayed by the first table chart is the pipeline state table. The monitoring content displayed by the second table chart is the application table. The monitoring content displayed by the first statistical chart is the number of constructions. The monitoring content displayed by the second statistical chart is the average construction time, and the average construction time is the data obtained according to the number of constructions and the construction duration. The monitoring content displayed by the third statistical chart is the state of successful construction when the pipeline tool currently builds the application software. The monitoring content displayed by the fourth statistical chart is the construction success rate of the pipeline tool, and the construction success rate is data determined according to the successful construction state. If the number of successful and failed constructions within a period of time is known, the construction success rate and the construction failure rate can be calculated according to the number of successes and failures. The fourth statistical chart can be a pie chart that simultaneously displays the construction success rate and the construction failure rate. The above-mentioned monitoring charts provided by the embodiments of the present invention can cover the health indicators concerned by the software development state, and realize the display of the build success status (success or failure), average build time, build success rate, and container clusters, images, branch names, microservice names, operators, etc. on the monitoring display board. At the same time, the creation time, modification time, namespace and other information of the application software can also be added to the second table chart. The information in the above-mentioned monitoring charts supports users to display flexibly according to their actual needs. After completing the system construction, users can use the monitoring display board to know the overall health status of the pipeline tool when it is executed, so as to achieve the purpose of out-of-the-box use. Relevant personnel can understand and evaluate the quality of the software built by the pipeline tool through each monitoring chart at the first time, thereby ensuring the efficient development efficiency.

[0047] In an embodiment of the present invention, the build information also includes month-on-month change information of the build success rate, which is information determined based on the build success rate in the previous predetermined time period and the build success rate in the next predetermined time period, and the month-on-month change information is displayed in the first table chart. Thus, the user can quickly obtain the month-on-month change information indicator by monitoring the first table chart in the display dashboard, ensuring that relevant personnel can obtain the performance status of the pipeline tool from the perspective of month-on-month change.

[0048] In step S13, the step of obtaining the target indicator data that the user needs to observe from the data source includes: obtaining the target indicator data from the database according to the storage location and the pre-written structured query language for querying the target indicator data. After the database completes the data collection, the embodiment of the present invention writes the corresponding structured query language (SQL statement for short) to query the indicator data to be output, and generates the monitoring chart required to display the indicator data on the monitoring display board, so that the user can view the information on the health of the pipeline on the monitoring display board.

[0049] The monitoring method of the pipeline tool provided by the embodiment of the present invention writes the collected indicator data into the configured data source through the indicator collector. The user only needs to obtain the corresponding indicator data from the data source according to his actual observation needs, and then display the indicator data through a unified monitoring display dashboard. It can support the access of various pipeline tools. The user only needs to slightly change the indicator data to be observed to observe the pipeline tool, and obtain more comprehensive content for measuring the performance of the pipeline tool, such as time-related content: the time of the last successful construction of the application software, the time spent on the application software construction, the average construction time spent on the average construction cost, etc., and can also determine the success of the application software construction through the construction success status displayed by the third statistical chart, and determine the construction success rate generated by the pipeline tool to build the application software through the fourth statistical chart, whether the success rate has changed month-on-month, etc. It can also determine the lack of operators who execute the pipeline tool through the first table chart showing the pipeline status table, and display the final environment deployed by the pipeline, etc. Therefore, the embodiment of the present invention manages software quality through unified indicator data and a unified visualization dashboard, reduces the investment of technical service personnel, and does not need to continuously invent targeted observation schemes in different customer scenarios.

[0050] The second embodiment of the present invention further provides a monitoring device for an assembly line tool, and the device is used to implement a monitoring method for an assembly line tool. For details of the monitoring method for the assembly line tool, please refer to the contents provided in the first embodiment of the present invention, and the embodiment of the present invention will not be repeated here.

[0051] The device provided in the embodiment of the present invention collects the indicator data generated during the operation of the pipeline tool through the deployed indicator collector, and writes the collected indicator data into the data source, and then determines the monitoring content of the monitoring chart generated in the monitoring display board for reference by the person in charge based on the indicator data. The data collection and display logic supports the access of various types of pipeline tools. When the customer replaces the pipeline tool, there is no need to redevelop and configure the observation plan. It supports users to flexibly display the indicator data used to indicate the health of the pipeline tool through the monitoring display board according to their actual observation needs, thereby ensuring the objective expression of the delivery status of the pipeline tool for the application software, with good versatility and low investment cost.

[0052] The third embodiment of the present invention further provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, a method for monitoring a pipeline tool is implemented. For details of the monitoring method for the pipeline tool, please refer to the contents provided in the first embodiment of the present invention, and the embodiments of the present invention will not be repeated here.

[0053] The fourth embodiment of the present invention further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements a monitoring method for a pipeline tool. For details of the monitoring method for the pipeline tool, please refer to the content provided in the first embodiment of the present invention, and the embodiment of the present invention will not be repeated here.

[0054] The fifth embodiment of the present invention also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements a monitoring method for a pipeline tool. For details of the monitoring method for the pipeline tool, please refer to the content provided in the first embodiment of the present invention, and the embodiment of the present invention will not be repeated here.

[0055] The sixth embodiment of the present invention provides an application embodiment of a method for monitoring a pipeline tool. Figure 2 The monitoring system shown in the figure implements the monitoring method of the pipeline tool. The monitoring system includes the pipeline tool itself, the indicator collector, the data source configured by the database, and the monitoring display board built by Grafana. Among them, the core indicator collector is a data collection service build-metrics-collector developed by Java as the programming language, and the monitoring display board creates various monitoring charts. When the user needs to monitor the delivery status of the pipeline tool, the indicator collector, the relevant database, and the monitoring display board need to be deployed in the running environment of the pipeline tool first, and the RDS database can be used as the storage database.

[0056] Step 1. It is necessary to configure the data source. The embodiment of the present invention configures the data source in the database. The data source creates a table structure for statistical indicator data, including an application master table, an application version table, and a pipeline status table. The application master table and the application version table can be the application table in the first embodiment of the present invention. The application table can be split according to the different contents to be displayed on demand, or it can be split when one application table is not enough to display all the contents. The embodiment of the present invention does not make a sole limitation on this. Generally speaking, the definition of the metadata of the application software is the most important (generally including the application name, microservice name, description, responsible team, dependencies, etc.). The pipeline status table is the core of the project. Since the application software and the pipeline tool are in a one-to-many relationship, and because the pipeline tool of an application software will be executed many times, the state generated by each execution, the deployed environment, the operator, the version number of the application software, etc. are all different, which requires the pipeline status table to record the above indicator data. The indicator data recorded in the application table statistics in the embodiment of the present invention may include: application name (app_name), microservice name (microservice_name), creation time (gmt_create), modification time (gmt_modify), etc. The indicator data recorded in the pipeline status table may include: application id (app_id), pipeline name (pipeline_name), pipeline url (pipeline_url), container cluster (ack_cluster), namespace (namespace), build number (build_number), build success status (state), duration (duration), message (message), operator (operator), creation time (gmt_create), modification time (gmt_modify), etc. The indicator data recorded in the application version table statistics include: application id (app_id), step (sldc_stage), container cluster (ack_cluster), namespace (namespace), branch name (branch_name), revision (git_revision), creation time (gmt_create), modification time (gmt_modify), etc.

[0057] Step 2, after the data source configuration is completed, the corresponding indicator data is collected during the operation of the pipeline tool through the deployed indicator collector. The indicator collector of the embodiment of the present invention provides services to the pipeline tool through the RESTFul API, so the client where the pipeline tool CI / CD is located can collect indicator data by calling the RESTFul API. The client uses wget, curl, python, groovy and other languages ​​to directly initiate HTTP requests to the indicator collector to call the RESTFul API to transmit the indicator data. For example, when the pipeline tool is Jenkins, the embodiment of the present invention obtains various indicator data during the operation of Jenkins through the configured script report-pipeline-state.sh, uses the HTTP POST Method method to send the indicator data to the indicator collector, splices the POST request content according to different indicator data, and sends the indicator data to the back-end indicator collector along with the initiated HTTP request.

[0058] The indicator collector can not only collect indicator data of Jenkins, but also can be integrated with other types of pipeline tools CI / CD, because all network interfaces of the indicator collector are REST-style interfaces. When called through HTTP, no dependencies are required, which is convenient for integration and deployment. To deploy the indicator collector, a cloud server instance of about 4C8G (i.e., ECS instance) is sufficient. The cloud server instance needs to install Java version 11. The embodiment of the present invention uses two cloud server instances for basic high-availability deployment. The indicator collectors deployed on the two cloud server instances have the same functions. When one of them cannot run for some reason, the other one continues to collect indicator data through the deployed indicator collector as a substitute, thereby improving the stability of the entire monitoring system.

[0059] Step 3: Write the indicator data to the data source by using the indicator collector created by Java.

[0060] Step 4: After the indicator collector completes the collection of indicator data, enter the account and password of the data source to connect the Grafana dashboard with the Mysql data source, and then select the corresponding dashboard (i.e., monitoring chart) and write the corresponding structured query language according to the indicator data to be output as needed. In this way, users can view the information on the health of the pipeline tool in the monitoring display dashboard, which includes: application name, microservice name, container cluster name, namespace, branch name, revision, image name and other information. At the same time, it is also necessary to count the number of builds, build evaluation rate, build time, build success rate, deployment frequency, deployment success rate, deployment time and other statistical indicators. In this regard, the embodiment of the present invention provides six monitoring charts to show the health of the pipeline tool, including a first table chart, a second table chart, a first statistical chart, a second statistical chart, a third statistical chart and a fourth statistical chart. Among them, the monitoring content displayed in the first table chart is the pipeline status table. The monitoring content displayed in the second table chart is the application table. The monitoring content displayed in the first statistical chart is the number of builds. The monitoring content displayed in the second statistical chart is the average build time, which is the data obtained based on the number of builds and the build duration. The monitoring content displayed in the third statistical chart is the build success status when the pipeline tool currently builds the application software. The monitoring content displayed in the fourth statistical chart is the build success rate of the pipeline tool, which is the data determined based on the build success status. For example, if the number of successful and failed builds within a period of time is known, the build success rate and the build failure rate can be calculated based on the number of successes and failures. The fourth statistical chart can be a pie chart that simultaneously displays the build success rate and the build failure rate. From the above monitoring chart, users can learn key indicators such as the overall build failure rate is 40%, the result of the last build is successful, and the average build time is 1.07 minutes. At the same time, the details of each application can also be entered by clicking on the application name. Among them, the original second table chart can be split into the application version table chart and the application main table table chart for separate display. It supports users to flexibly display more customized charts of pipeline health according to their actual needs, and select appropriate indicator data and corresponding monitoring chart types through custom structured query language.

[0061] By deploying the RESTFul API for the indicator collector, the embodiment of the present invention can get rid of the limitation of the client where the pipeline tool is located, so that the indicator collector can support the access of various pipeline tools. No matter which pipeline tool is used, it can evaluate and audit the health of its application software when it is built. The method provided by the embodiment of the present invention improves the reliability and security of the data of the entire system by using the RDS database and Grafana components. Users can deploy it in a self-built computer room or other cloud platforms. The default 6 charts provided by the solution can cover the health indicators concerned by the software development state, and can display the number of successful builds, success rate, time consumption, application status, etc. on a large screen, supporting users to flexibly display according to their actual needs. After completing the construction of the monitoring system, users can obtain the health status of software applications through a large screen. The indicator collector can support information collection of common pipeline tools. This component can be implemented based on Java language and spring boot. Spring boot is used to simplify the initial construction and development process of new Spring applications. The framework uses a specific method for configuration, so that developers no longer need to define boilerplate configurations. Through spring boot, it is easy and convenient to write and deploy indicator collectors based on Java language. The deployed indicator collector has very low resource requirements and only relies on the database RDS instance that stores data.

[0062] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0063] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A method for monitoring an assembly line tool, characterized in that: include: Configuring a data source in a database and determining a storage location of the data source in the database, wherein the data source includes a table structure for counting indicator data generated during the operation of a pipeline tool; Collecting the indicator data through a pre-deployed indicator collector, and writing the indicator data into the data source according to the storage location; The target indicator data that the user needs to observe is obtained from the data source, and a monitoring chart required to display the target indicator data is generated in a pre-built monitoring display dashboard, wherein when generating the monitoring chart, the monitoring content displayed by the monitoring chart is determined according to the target indicator data.

2. The method according to claim 1, characterized in that The indicator collector is configured with a network interface, and the step of collecting the indicator data through the pre-deployed indicator collector includes: A network connection is established between the indicator collector and the pipeline tool based on the network interface, so that the pipeline tool sends the indicator data to the indicator collector.

3. The method according to claim 2, characterized in that The pipeline tool is configured with a script for obtaining the indicator data, and the step of the pipeline tool sending the indicator data to the indicator collector includes: When the pipeline tool initiates a network connection request to the network interface through the script, the indicator data obtained by the script is spliced ​​into the network connection request and sent to the indicator collector.

4. The method according to claim 1, characterized in that The indicator data includes construction information generated in the process of the pipeline tool building the application software and metadata of the application software. The step of configuring the data source in the database includes: In the database, a pipeline status table for counting the construction information and / or an application table for counting the metadata are created to obtain the data source consisting of at least the pipeline status table and the application table; Then, the step of the indicator collector writing the indicator data into the data source according to the storage location includes: The construction information is written into the pipeline status table according to the storage location, and / or the metadata is written into the application table.

5. The method according to claim 4, characterized in that The build information includes the number of builds, build success status, and build duration, wherein the monitoring chart includes: A first table chart, wherein the monitoring content displayed in the first table chart is the pipeline status table; and / or, a second table chart, wherein the monitoring content displayed in the second table chart is the application table; and / or, a first statistical chart, wherein the monitoring content displayed in the first statistical chart is the number of constructions; and / or, a second statistical chart, wherein the monitoring content displayed in the second statistical chart is an average build time, wherein the average build time is data obtained based on the number of builds and the build duration; and / or, a third statistical chart, wherein the monitoring content displayed in the third statistical chart is the construction success status when the pipeline tool is currently building the application software; And / or, a fourth statistical chart, wherein the monitoring content displayed by the fourth statistical chart is the construction success rate of the pipeline tool, and the construction success rate is data determined according to the construction success status.

6. The method according to claim 5, characterized in that The construction information also includes month-on-month change information of the construction success rate, which is information determined based on the construction success rate in the previous predetermined time period and the construction success rate in the next predetermined time period, and the month-on-month change information is displayed in the first table chart.

7. The method according to claim 1, characterized in that The step of obtaining target indicator data that the user needs to observe from the data source includes: The target indicator data is obtained from the database according to the storage location and a pre-written structured query language for querying the target indicator data.

8. A monitoring device for assembly line tools, characterized in that: The device is used to implement the monitoring method of the assembly line tool described in any one of claims 1 to 7.

9. A computer 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 method steps described in any one of claims 1 to 7 are implemented.

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

Images