A method and system for remotely upgrading IT monitoring application software and monitoring data

Abstract

The invention discloses a method for remotely upgrading IT monitoring application software and monitoring data, including: S1, publishing a central service application upgrade package of an application system, and the code of the application system is managed by SVN; S2, publishing a front-end page upgrade package of the application system; the front-end page uses the NODEJS environment, and the front-end code is managed by SVN; S3, publishing an application proxy collector upgrade package; the code of the application proxy collector is managed by SVN; S4, publishing an installation package data structure upgrade file; the database for data storage is deployed using mysql8; S5, publishing a static data upgrade package; the static data represents data that cannot be changed arbitrarily during the system operation process; S6, publishing an actual environment configuration file package; the actual environment configuration file includes single sign-on, third-party interface address or KEY information; S7, uniformly compressing the program package and encrypting it; S8, the system background imports the uniform compressed package file and decrypts it, and completes the remote upgrade of IT monitoring application software and monitoring data. A corresponding system is also disclosed.

Description

Technical Field

[0001] The present invention relates to the technical field of remote software upgrade, and in particular to a method and system for remotely upgrading IT monitoring application software and monitoring data. Background Art

[0002] The demand for IT monitoring system upgrades is very high. Faced with the increase in device types, the increase in device brands, the increase in different models of the same brand, the increase or adjustment of the scope of monitoring required by customers, the upgrade or revision of applications, and other scenarios, the system is faced with a comprehensive upgrade.

[0003] The general software upgrade method is to iterate the program version one by one. Since the latest version must be fully upgraded one by one, the upgrade process uses an offline package, that is, all versions are imported one by one, and the database upgrade is partly manual operation of the database, and partly automatic upgrade of the table structure, so it is very cumbersome. In addition, because some data is processed during the system operation process, it is more complicated to adjust the data. Moreover, the upgrade system of the prior art is usually based on the characteristics of the IT monitoring industry. There are many monitoring indicators, monitoring data, monitoring alarm thresholds, industry market brands, models, instructions and other elements for the monitoring items of IT equipment. Compared with traditional technical upgrade solutions, it is very difficult to achieve the normal operation of the system after the upgrade. Summary of the invention

[0004] In order to solve the problems existing in the prior art, the present invention provides a method and system for remotely upgrading IT monitoring application software and monitoring data to solve the following technical problems:

[0005] (1) Solve the need for scenarios where human error occurs, and solve the problem of having to upgrade all the upgrade elements with one click.

[0006] (2) Resolve the issue of data being missed during upgrade.

[0007] (3) Solve the problem of network disconnection and inability to download upgrade packages.

[0008] (4) Resolved the issue where many commands related to offline upgrades could not be run.

[0009] In one aspect, the present invention provides a method for remotely upgrading IT monitoring application software and monitoring data, comprising:

[0010] S1, publishing a central service application upgrade package of an application system, wherein the code of the application system is managed using SVN;

[0011] S2, publish the application system front-end page upgrade package; wherein the front-end page uses the NODEJS environment, and the front-end code corresponding to the front-end page is managed using SVN;

[0012] S3, publishing an application proxy collector upgrade package; wherein the code of the application proxy collector is managed using SVN;

[0013] S4, publish the installation package data structure upgrade file; wherein the database for data storage is deployed using mysql8, which supports reading the entire table information and the field information of the table;

[0014] S5, releasing a static data upgrade package; wherein the static data refers to data that cannot be changed arbitrarily during the system operation process, and the static data includes one or more information of monitoring indicators, thresholds, equipment types, brands, models, and scripts;

[0015] S6, publishing an actual environment configuration file package; wherein the actual environment configuration file includes single sign-on, third-party interface address or KEY information;

[0016] S7, unified compression package and encryption;

[0017] S8, the system background imports the unified compressed package file and decrypts it to complete the remote upgrade of IT monitoring application software and monitoring data.

[0018] Preferably, the S1 comprises:

[0019] S11, determining a central service application upgrade package, including: packaging the code that has passed the white box test to form a formal release package of the central service application upgrade package, and submitting the SVN code of the formal release package of the central service application upgrade package;

[0020] S12, performing pre-release preparations, before preparing to release the central service application upgrade package of the application, defining the command of the latest version of the central service application upgrade package according to the date, and then packaging the central service application upgrade package based on the ANT packaging program to form ANT packaging programs corresponding to multiple customers, and the naming method of the ANT packaging program corresponding to the customer is Server.{date}.war;

[0021] S13, determining to release the central service application upgrade package of the application system when the pre-release preparation is completed, including: firstly defining the XML upgrade configuration file of ANT according to the customer, wherein the configuration file content with the same configuration does not need to be rewritten; then executing the ANT packaging program corresponding to the corresponding customer, generating the corresponding customer upgrade package after execution, and placing the customer upgrade package in the corresponding customer folder; finally updating the SVN code to the local, and updating the version number of the configuration file according to the current date, completing the naming of the version, reading the configuration environment variables of the customer and replacing the configuration file attributes inside the program with the configuration environment variables of the customer, wherein the configuration environment variables of the customer include database configuration;

[0022] Preferably, S2 includes:

[0023] S21, determining the application system front-end page upgrade package, including: packaging the code that has passed the white box test to form a formal release package of the application system front-end page upgrade package, and submitting the SVN code of the formal release package of the application system front-end page upgrade package;

[0024] S22, prepare before publishing, before preparing to publish the application system front-end page upgrade package, define the latest version of the application system front-end page upgrade package by date, and then package the application system front-end page upgrade package based on the NODEJS packaging program to form multiple NODEJS packaging programs corresponding to customers, and the naming method of the NODEJS packaging program corresponding to the customer is Web.{date}.zip;

[0025] S23, determining to release the central service application upgrade package of the application system after completing the pre-release preparation, including: first, defining the JSON upgrade configuration file of VUE according to the customer, wherein the configuration file content with the same configuration does not need to be rewritten; then executing the corresponding npm build packaging program corresponding to the customer, generating the corresponding customer upgrade package after execution, and placing the customer upgrade package in the corresponding customer folder; finally, updating the SVN code to the local, and updating the version number of the configuration file according to the current date, completing the version naming, reading the customer's configuration environment variables and replacing the configuration file properties inside the program with the customer's configuration environment variables, wherein the customer's configuration environment variables include database configuration.

[0026] Preferably, S3 includes:

[0027] S31, determining an application proxy collector upgrade package, including: packaging the code that has passed the white box test to form a formal release package of the application proxy collector upgrade package, and submitting the SVN code of the formal release package of the application proxy collector upgrade package;

[0028] S32, performing pre-release preparations, before preparing to release the application proxy collector upgrade package, defining the command of the latest version of the application proxy collector upgrade package according to the date, and then packaging the application system front-end page upgrade package based on the ANT packaging program to form ANT packaging programs corresponding to multiple customers, and the naming method of the ANT packaging program corresponding to the customer is Server.{date}.war;

[0029] S33, determining to release the application agent collector upgrade package after completing the pre-release preparation, including: firstly, defining the XML upgrade configuration file of ANT according to the customer, wherein the configuration file content with the same configuration does not need to be rewritten; then executing the ANT packaging program corresponding to the customer, generating the corresponding customer upgrade package after execution, and placing the customer upgrade package in the corresponding customer folder; finally, updating the SVN code to the local, and updating the version number of the configuration file according to the current date, completing the version naming, reading the customer's configuration environment variables and replacing the configuration file attributes inside the program with the customer's configuration environment variables, wherein the customer's configuration environment variables include database configuration.

[0030] Preferably, S4 includes:

[0031] S41, read all tables and fields in the database and combine them to form an XML file;

[0032] S42, the current XML file is ordered according to the date and stored in the corresponding customer folder to publish the installation package data structure upgrade file.

[0033] Preferably, S5 includes:

[0034] S51, the name of the static data table related to configuration during system development;

[0035] S52, traverse all the static data table names, and export the tables corresponding to all the static data table names to sql files to publish static data upgrade packages. The export method adopts the export command provided by mysql to ensure that all mysql environments can be used.

[0036] Preferably, S6 includes:

[0037] S61, before releasing the actual environment configuration file package, register the customer's information in the ledger;

[0038] S62, obtaining the configuration corresponding to the customer from the ledger, generating an independent configuration file to publish the actual environment configuration file package.

[0039] Preferably, the S7 includes:

[0040] S71, compress all the file packages or files released by S1-S6 into a compressed package file;

[0041] S72, encrypting the compressed file.

[0042] Preferably, the S8 includes:

[0043] S81, importing the compressed file from the system background that needs to be upgraded;

[0044] S82, after determining that the import is completed, decrypting the compressed package file;

[0045] S83, if it is determined that the compressed package file is successfully decrypted, the IT monitoring application software and monitoring data are executed; after the decryption is successful, all the file packages or files corresponding to the upgrade have corresponding names, and for the program upgrade package, they are returned to the original program deployment directory, and then the command is automatically restarted; for the database upgrade, the corresponding tables and structures are compared, tables and fields are added but not allowed to be deleted, and the field types are modified at the same time, the static data table is cleared, and the latest static data file is imported into the library, that is, the remote upgrade process of the entire IT monitoring application software and monitoring data is completed;

[0046] If it is determined that the compressed file decryption is unsuccessful, an abnormal error alarm prompt is sent.

[0047] A second aspect of the present invention is to provide a system for remotely upgrading IT monitoring application software and monitoring data, comprising:

[0048] A central service application upgrade package publishing module is used to publish a central service application upgrade package for an application system, wherein the code of the application system is managed using SVN;

[0049] The application system front-end page upgrade package publishing module is used to publish the application system front-end page upgrade package; wherein the front-end page uses the NODEJS environment, and the front-end code corresponding to the front-end page is managed using SVN;

[0050] An application proxy collector upgrade package publishing module, used to publish an application proxy collector upgrade package; wherein the code of the application proxy collector is managed using SVN;

[0051] The installation package data structure upgrade file publishing module is used to publish the installation package data structure upgrade file; wherein the database for data storage is deployed using mysql8, and mysql8 supports reading the entire table information and the field information of the table;

[0052] A static data upgrade package publishing module, used to publish static data upgrade packages; wherein the static data refers to data that cannot be changed arbitrarily during the system operation process, and the static data includes one or more information of monitoring indicators, thresholds, equipment types, brands, models, and scripts;

[0053] An actual environment configuration file package publishing module is used to publish an actual environment configuration file package; wherein the actual environment configuration file includes single sign-on, third-party interface address or KEY information, the actual environment configuration file is different from the program configuration file, the actual environment configuration file does not need to be referenced when the program is running, and can be modified at will, and the modification does not affect the operation of the program;

[0054] Compression and encryption module, used to unify and encrypt program packages;

[0055] The remote upgrade module is used to import and decrypt the unified compressed package file in the system background to complete the remote upgrade of IT monitoring application software and monitoring data.

[0056] A third aspect of the present invention provides an electronic device, comprising a processor and a memory, wherein the memory stores a plurality of instructions, and the processor is configured to read the instructions and execute the method described in the first aspect.

[0057] A fourth aspect of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores a plurality of instructions, and the plurality of instructions can be read by a processor and execute the method described in the first aspect.

[0058] The method, system and electronic device provided by the present invention have the following beneficial effects:

[0059] 1. Low upgrade difficulty: It solves the problem of uneven technical levels of technical personnel, allowing non-professional technicians to achieve one-click upgrade of professional software, saving labor costs and reducing erroneous upgrade methods caused by non-professional operations.

[0060] 2. Comprehensive upgrade and high data coverage.

[0061] 3. The upgrade method is automated.

[0062] 4. As monitoring devices increase day by day, the brands, models and types of inspection equipment increase, and static data upgrade packages can be accumulated into data resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] Figure 1 This is a flow chart of the method for remotely upgrading IT monitoring application software and monitoring data according to the present invention;

[0064] Figure 2 The figure is a schematic diagram of the structure of the electronic device described in the present invention. DETAILED DESCRIPTION

[0065] In order to better understand the above technical solution, the above technical solution will be described in detail below in conjunction with the accompanying drawings and specific implementation methods.

[0066] Embodiment 1

[0067] This embodiment provides a method and system for remotely upgrading IT monitoring application software and monitoring data to solve the following technical problems:

[0068] (1) Solve the need for scenarios where human error occurs, and solve the problem of having to upgrade all the upgrade elements with one click.

[0069] (2) Resolve the issue of data being missed during upgrade.

[0070] (3) Solve the problem of network disconnection and inability to download upgrade packages.

[0071] (4) Resolved the issue where many commands related to offline upgrades could not be run.

[0072] like Figure 1 As shown, this embodiment provides a method for remotely upgrading IT monitoring application software and monitoring data, including:

[0073] S1, publishing a central service application upgrade package of an application system, wherein the code of the application system is managed using SVN.

[0074] As a preferred embodiment, the S1 includes:

[0075] S11, determining a central service application upgrade package, including: packaging the code that has passed the white box test to form a formal release package of the central service application upgrade package, and submitting the SVN code of the formal release package of the central service application upgrade package;

[0076] S12, performing pre-release preparations, before preparing to release the central service application upgrade package of the application, defining the command of the latest version of the central service application upgrade package according to the date, and then packaging the central service application upgrade package based on the ANT packaging program to form ANT packaging programs corresponding to multiple customers, and the naming method of the ANT packaging program corresponding to the customer is Server.{date}.war;

[0077] S13, determining that the central service application upgrade package of the application system is released after the pre-release preparation is completed, including: first, defining the XML upgrade configuration file of ANT according to the customer, wherein the configuration file content with the same configuration does not need to be rewritten; then executing the ANT packaging program corresponding to the corresponding customer, generating the corresponding customer upgrade package after execution, and placing the customer upgrade package in the corresponding customer folder; finally, updating the SVN code to the local, and updating the version number of the configuration file according to the current date, completing the version naming, reading the customer's configuration environment variables and replacing the configuration file attributes inside the program with the customer's configuration environment variables, the customer's configuration environment variables include database configuration, etc. Of course, those skilled in the art can read other configuration environment variables of the customer as needed, which are all within the protection scope of the present invention.

[0078] S2, publish the application system front-end page upgrade package; wherein, the front-end page uses the NODEJS environment, and the front-end code corresponding to the front-end page is managed using SVN.

[0079] As a preferred embodiment, the S2 includes:

[0080] S21, determining the application system front-end page upgrade package, including: packaging the code that has passed the white box test to form a formal release package of the application system front-end page upgrade package, and submitting the SVN code of the formal release package of the application system front-end page upgrade package;

[0081] S22, prepare before publishing, before preparing to publish the application system front-end page upgrade package, define the latest version of the application system front-end page upgrade package by date, and then package the application system front-end page upgrade package based on the NODEJS packaging program to form multiple NODEJS packaging programs corresponding to customers, and the naming method of the NODEJS packaging program corresponding to the customer is Web.{date}.zip;

[0082] S23, determining that the central service application upgrade package of the application system is released after the pre-release preparation is completed, including: first, defining a JSON upgrade configuration file of VUE according to the customer, wherein the configuration file content with the same configuration does not need to be rewritten; then executing the corresponding npm build packaging program corresponding to the customer, generating a corresponding customer upgrade package after execution, and placing the customer upgrade package in the corresponding customer folder; finally, updating the SVN code to the local, and updating the version number of the configuration file according to the current date, completing the version naming, reading the customer's configuration environment variables and replacing the configuration file properties inside the program with the customer's configuration environment variables, the customer's configuration environment variables include database configuration, etc. Of course, those skilled in the art can read other configuration environment variables of the customer as needed, which are all within the protection scope of the present invention.

[0083] S3, publishing an application proxy collector upgrade package; wherein the code of the application proxy collector is managed using SVN.

[0084] As a preferred implementation, S3 includes:

[0085] S31, determining an application proxy collector upgrade package, including: packaging the code that has passed the white box test to form a formal release package of the application proxy collector upgrade package, and submitting the SVN code of the formal release package of the application proxy collector upgrade package;

[0086] S32, performing pre-release preparations, before preparing to release the application proxy collector upgrade package, defining the command of the latest version of the application proxy collector upgrade package according to the date, and then packaging the application system front-end page upgrade package based on the ANT packaging program to form ANT packaging programs corresponding to multiple customers, and the naming method of the ANT packaging program corresponding to the customer is Server.{date}.war;

[0087] S33, determining to release the application agent collector upgrade package after completing the pre-release preparation, including: first, defining the XML upgrade configuration file of ANT according to the customer, wherein the configuration file content with the same configuration does not need to be rewritten; then executing the ANT packaging program corresponding to the corresponding customer, generating the corresponding customer upgrade package after execution, and placing the customer upgrade package in the corresponding customer folder; finally, updating the SVN code to the local, and updating the version number of the configuration file according to the current date, completing the version naming, reading the customer's configuration environment variables and replacing the configuration file attributes inside the program with the customer's configuration environment variables, the customer's configuration environment variables include database configuration, etc. Of course, those skilled in the art can read other configuration environment variables of the customer as needed, all of which are within the protection scope of the present invention.

[0088] S4, publish the installation package data structure upgrade file; wherein, the database for data storage is deployed using mysql8, and mysql8 supports reading the entire table information and the field information of the table.

[0089] As a preferred implementation, the S4 includes:

[0090] S41, read all tables and fields in the database and combine them to form an XML file;

[0091] S42, the current XML file is ordered according to the date and stored in the corresponding customer folder to publish the installation package data structure upgrade file.

[0092] S5, release the static data upgrade package; wherein the static data refers to the data that cannot be changed arbitrarily during the system operation process. In this embodiment, the static data includes one or more information of monitoring indicators, thresholds, equipment types, brands, models, and scripts.

[0093] As a preferred implementation, S5 includes:

[0094] S51, the name of the static data table related to configuration during system development;

[0095] S52, traverse all the static data table names, and export the tables corresponding to all the static data table names to sql files to publish static data upgrade packages. The export method adopts the export command provided by mysql to ensure that all mysql environments can be used.

[0096] S6, publish the actual environment configuration file package; wherein, the actual environment configuration file includes single sign-on, third-party interface address or KEY information, the actual environment configuration file is different from the program configuration file, the actual environment configuration file does not need to be referenced when the program is running, and can be modified at will, and the modification does not affect the operation of the program.

[0097] As a preferred implementation, S6 includes:

[0098] S61, before releasing the actual environment configuration file package, register the customer's information in the ledger;

[0099] S62, obtaining the configuration corresponding to the customer from the ledger, generating an independent configuration file to publish the actual environment configuration file package.

[0100] S7, unified compression package and encryption.

[0101] As a preferred implementation, the S7 includes:

[0102] S71, at this time, all the file packages or files published by S1-S6 can be generated into an independent file package, but since the independent file package is not conducive to transmission or downloading, this operation will not be performed, but all the file packages or files published by S1-S6 are compressed into a compressed package file (zip file in this embodiment);

[0103] S72, for security reasons, encrypt the compressed file to prevent information leakage. Those skilled in the art should know that any usable encryption method can be used, and all digital encryption methods are within the protection scope of the present invention.

[0104] S8, the system background imports the unified compressed package file and decrypts it to complete the remote upgrade of IT monitoring application software and monitoring data.

[0105] As a preferred implementation, the S8 includes:

[0106] S81, importing the compressed file from the system background that needs to be upgraded;

[0107] S82, after determining that the import is completed, decrypting the compressed package file;

[0108] S83, if it is determined that the compressed package file is successfully decrypted, the IT monitoring application software and monitoring data are executed; after the decryption is successful, all the file packages or files corresponding to the upgrade have corresponding names, and for the program upgrade package, they are returned to the original program deployment directory, and then the command is automatically restarted; for the database upgrade, the corresponding tables and structures are compared, tables and fields are added but not allowed to be deleted, and the field types are modified at the same time, the static data table is cleared, and the latest static data file is imported into the library, that is, the remote upgrade process of the entire IT monitoring application software and monitoring data is completed;

[0109] If it is determined that the compressed file decryption is unsuccessful, an abnormal error alarm prompt is sent.

[0110] Embodiment 2

[0111] This embodiment provides a system for remotely upgrading IT monitoring application software and monitoring data, including:

[0112] A central service application upgrade package publishing module is used to publish a central service application upgrade package for an application system, wherein the code of the application system is managed using SVN;

[0113] The application system front-end page upgrade package publishing module is used to publish the application system front-end page upgrade package; wherein the front-end page uses the NODEJS environment, and the front-end code corresponding to the front-end page is managed using SVN;

[0114] An application proxy collector upgrade package publishing module, used to publish an application proxy collector upgrade package; wherein the code of the application proxy collector is managed using SVN;

[0115] The installation package data structure upgrade file publishing module is used to publish the installation package data structure upgrade file; wherein the database for data storage is deployed using mysql8, and mysql8 supports reading the entire table information and the field information of the table;

[0116] A static data upgrade package publishing module, used to publish static data upgrade packages; wherein the static data refers to data that cannot be changed arbitrarily during the system operation process. In this embodiment, the static data includes one or more information of monitoring indicators, thresholds, device types, brands, models, and scripts;

[0117] An actual environment configuration file package publishing module is used to publish an actual environment configuration file package; wherein the actual environment configuration file includes single sign-on, third-party interface address or KEY information, the actual environment configuration file is different from the program configuration file, the actual environment configuration file does not need to be referenced when the program is running, and can be modified at will, and the modification does not affect the operation of the program;

[0118] Compression and encryption module, used to unify and encrypt program packages;

[0119] The remote upgrade module is used to import and decrypt the unified compressed package file in the system background to complete the remote upgrade of IT monitoring application software and monitoring data.

[0120] The present invention also provides a memory storing a plurality of instructions, wherein the instructions are used to implement the method as in the first embodiment.

[0121] like Figure 2 As shown, the present invention also provides an electronic device, including a processor 301 and a memory 302 connected to the processor 301, the memory 302 stores a plurality of instructions, and the instructions can be loaded and executed by the processor so that the processor can execute the method as in the first embodiment.

[0122] Although preferred embodiments of the present invention have been described, additional changes and modifications may be made to these embodiments by those skilled in the art once the basic inventive concepts are known. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention. Obviously, those skilled in the art may make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A method for remotely upgrading IT monitoring application software and monitoring data, characterized in that: include: S1, publishing a central service application upgrade package of an application system, wherein the code of the application system is managed using SVN; S2, publish the application system front-end page upgrade package; wherein the front-end page uses the NODEJS environment, and the front-end code corresponding to the front-end page is managed using SVN; S3, release the application proxy collector upgrade package; the code of the application proxy collector is managed using SVN; S4, publish the installation package data structure upgrade file; wherein the database for data storage is deployed using mysql8, which supports reading the entire table information and the field information of the table; S5, release a static data upgrade package; wherein the static data refers to data that cannot be changed arbitrarily during the system operation process, and the static data includes one or more information of monitoring indicators, thresholds, equipment types, brands, models, and scripts; S6, publishing an actual environment configuration file package; wherein the actual environment configuration file includes single sign-on, third-party interface address or KEY information; S7, unified compression package and encryption; S8, the system background imports the unified compressed package file and decrypts it to complete the remote upgrade of IT monitoring application software and monitoring data; The S1 includes: S11, determining a central service application upgrade package, including: packaging the code that has passed the white box test to form a formal release package of the central service application upgrade package, and submitting the SVN code of the formal release package of the central service application upgrade package; S12, performing pre-release preparations, before preparing to release the central service application upgrade package of the application, defining the command of the latest version of the central service application upgrade package according to the date, and then packaging the central service application upgrade package based on the ANT packaging program to form ANT packaging programs corresponding to multiple customers, and the naming method of the ANT packaging program corresponding to the customer is Server.{date}.war; S13, determining to release the central service application upgrade package of the application system when the pre-release preparation is completed, including: firstly defining the XML upgrade configuration file of ANT according to the customer, wherein the configuration file content with the same configuration does not need to be rewritten; then executing the ANT packaging program corresponding to the corresponding customer, generating the corresponding customer upgrade package after execution, and placing the customer upgrade package in the corresponding customer folder; finally updating the SVN code to the local, and updating the version number of the configuration file according to the current date, completing the naming of the version, reading the configuration environment variables of the customer and replacing the configuration file attributes inside the program with the configuration environment variables of the customer, wherein the configuration environment variables of the customer include database configuration; The S2 includes: S21, determining the application system front-end page upgrade package, including: packaging the code that has passed the white box test to form a formal release package of the application system front-end page upgrade package, and submitting the SVN code of the formal release package of the application system front-end page upgrade package; S22, prepare before publishing, before preparing to publish the application system front-end page upgrade package, define the latest version of the application system front-end page upgrade package by date, and then package the application system front-end page upgrade package based on the NODEJS packaging program to form multiple NODEJS packaging programs corresponding to customers, and the naming method of the NODEJS packaging program corresponding to the customer is Web.{date}.zip; S23, determining to release the central service application upgrade package of the application system when the pre-release preparation is completed, including: first, defining the JSON upgrade configuration file of VUE according to the customer, wherein the configuration file content with the same configuration does not need to be rewritten; then executing the corresponding npm build packaging program corresponding to the customer, generating the corresponding customer upgrade package after execution, and placing the customer upgrade package in the corresponding customer folder; finally, updating the SVN code to the local, and updating the version number of the configuration file according to the current date, completing the version naming, reading the customer's configuration environment variables and replacing the configuration file properties inside the program with the customer's configuration environment variables, wherein the customer's configuration environment variables include database configuration; The S3 includes: S31, determining an application proxy collector upgrade package, including: packaging the code that has passed the white box test to form a formal release package of the application proxy collector upgrade package, and submitting the SVN code of the formal release package of the application proxy collector upgrade package; S32, performing pre-release preparations, before preparing to release the application proxy collector upgrade package, defining the command of the latest version of the application proxy collector upgrade package according to the date, and then packaging the application system front-end page upgrade package based on the ANT packaging program to form ANT packaging programs corresponding to multiple customers, and the naming method of the ANT packaging program corresponding to the customer is Server.{date}.war; S33, determining that the application agent collector upgrade package is released when the pre-release preparation is completed, including: first, defining an XML upgrade configuration file of ANT according to the customer, wherein the configuration file content with the same configuration does not need to be rewritten; then executing the ANT packaging program corresponding to the customer, generating a corresponding customer upgrade package after execution, and placing the customer upgrade package in the corresponding customer folder; finally, updating the SVN code to the local, and updating the version number of the configuration file according to the current date, completing the version naming, reading the configuration environment variables of the customer and replacing the configuration file attributes inside the program with the configuration environment variables of the customer, wherein the configuration environment variables of the customer include database configuration; The S5 includes: S51, the name of the static data table related to configuration during system development; S52, traverse all the static data table names, and export the tables corresponding to all the static data table names to sql files to publish static data upgrade packages. The export method adopts the export command provided by mysql to ensure that all mysql environments can be used.

2. A method for remotely upgrading IT monitoring application software and monitoring data according to claim 1, characterized in that: The S4 includes: S41, read all tables and fields in the database and combine them to form an XML file; S42, the current XML file is ordered according to the date and stored in the corresponding client folder to publish the installation package data structure upgrade file.

3. A method for remotely upgrading IT monitoring application software and monitoring data according to claim 2, characterized in that: The S6 includes: S61, before releasing the actual environment configuration file package, register the customer's information in the ledger; S62, obtaining the configuration corresponding to the customer from the ledger, generating an independent configuration file to publish the actual environment configuration file package.

4. A method for remotely upgrading IT monitoring application software and monitoring data according to claim 3, characterized in that: The S7 includes: S71, compress all the file packages or files released by S1-S6 into a compressed package file; S72, encrypting the compressed file.

5. A method for remotely upgrading IT monitoring application software and monitoring data according to claim 4, characterized in that: The S8 includes: S81, importing the compressed file from the system background that needs to be upgraded; S82, after determining that the import is completed, decrypting the compressed package file; S83, if it is determined that the compressed package file is successfully decrypted, the IT monitoring application software and monitoring data are executed; after the decryption is successful, all the file packages or files corresponding to the upgrade have corresponding names, and for the program upgrade package, they are returned to the original program deployment directory, and then the command is automatically restarted; for the database upgrade, the corresponding tables and structures are compared, tables and fields are added but not allowed to be deleted, and the field types are modified at the same time, the static data table is cleared, and the latest static data file is imported into the library, that is, the remote upgrade process of the entire IT monitoring application software and monitoring data is completed; If it is determined that the compressed file decryption is unsuccessful, an abnormal error alarm prompt is sent.

6. A system for remotely upgrading IT monitoring application software and monitoring data, used to implement the method of any one of claims 1 to 5, characterized in that: include: A central service application upgrade package publishing module is used to publish a central service application upgrade package for an application system, wherein the code of the application system is managed using SVN; The application system front-end page upgrade package publishing module is used to publish the application system front-end page upgrade package; wherein the front-end page uses the NODEJS environment, and the front-end code corresponding to the front-end page is managed using SVN; An application proxy collector upgrade package publishing module, used to publish an application proxy collector upgrade package; wherein the code of the application proxy collector is managed using SVN; The installation package data structure upgrade file publishing module is used to publish the installation package data structure upgrade file; wherein the database for data storage is deployed using mysql8, and mysql8 supports reading the entire table information and the field information of the table; A static data upgrade package publishing module, used to publish static data upgrade packages; wherein the static data refers to data that cannot be changed arbitrarily during the system operation process, and the static data includes one or more information of monitoring indicators, thresholds, equipment types, brands, models, and scripts; An actual environment configuration file package publishing module is used to publish an actual environment configuration file package; wherein the actual environment configuration file includes single sign-on, third-party interface address or KEY information, the actual environment configuration file is different from the program configuration file, the actual environment configuration file does not need to be referenced when the program is running, and can be modified at will, and the modification does not affect the operation of the program; Compression and encryption module, used to unify and encrypt program packages; The remote upgrade module is used to import and decrypt the unified compressed package file in the system background to complete the remote upgrade of IT monitoring application software and monitoring data.

Images