Lightweight business warning management method, system and storage medium

Abstract

The present invention discloses a lightweight business early warning management method, system and storage medium, and belongs to the technical field of system supervision and management. The technical problem to be solved by the present invention is how to free developers from the current tedious and complicated work as soon as possible, let more business personnel participate in it, and reduce information handover at the same time. The technical scheme is: the method is specifically as follows: define an early warning configuration template, and uniformly integrate and manage the early warning configuration module through a dynamic proxy mode; the monitoring logic involved in the business module is stored in the same database table, and the parameter variables in the supervision SQL are uniformly replaced through a dynamic proxy; define a time monitoring timer, trigger the call of the early warning configuration module at a fixed time every day, take out all the supervision logic from the database table, execute it in the order of dependency, and store the execution result in the corresponding supervision point subtable; define a general page display template, and the general page display template supports the display of data from different supervision points.

Description

Technical Field

[0001] The present invention relates to the technical field of system supervision and management, and in particular to a lightweight business early warning management method, system and storage medium. Background Art

[0002] With the development of the tobacco industry and the deepening of informatization construction, informatization has covered all areas of the tobacco industry, played a good supporting and enhancing role in the development of business, and achieved remarkable results. However, with the rapid development of informatization construction, the requirements for market conditions and market norms will affect whether the entire tobacco industry can develop continuously, stably, healthily and rapidly.

[0003] The development method of regulatory rules has undergone many technological changes, but it has not fundamentally solved the problem of developers doing repetitive work. For each new regulatory point, developers need to develop a large amount of code to support it. Therefore, how to free developers from the current tedious and complex work as soon as possible, let more business personnel participate in it, reduce information handover, and avoid development loopholes caused by information asymmetry is an urgent problem to be solved. Summary of the invention

[0004] The technical task of the present invention is to provide a lightweight business early warning management method, system and storage medium to solve how to free developers from the current tedious and complicated work as soon as possible, let more business personnel participate in it, reduce information handover, and avoid development loopholes caused by information asymmetry.

[0005] The technical task of the present invention is achieved in the following manner: a lightweight business early warning management method, the method is as follows:

[0006] Define the warning configuration template and integrate the warning configuration modules in a unified manner through the dynamic proxy mode;

[0007] The monitoring logic for the business modules involved is stored in the same database table, and the parameter variables in the supervision SQL are uniformly replaced through dynamic proxy;

[0008] Define a time monitoring timer, trigger the call of the early warning configuration module at a fixed time every day, take out all the supervision logic from the database table, execute it in the order of dependencies, and store the execution results in the corresponding supervision point subtable; the supervision cycle of the time monitoring timer supports custom day, week, month and year;

[0009] Define a general page display template, which supports data display at different regulatory points: directly render a data table on the main page by defining query logic and display column content;

[0010] The supervision point execution logs are uniformly stored in the log table, and the execution status of the business modules is checked every day by analyzing the logs. During the supervision point execution process, manual triggering is supported for the logs of the supervision points that have not been successfully executed.

[0011] As a preference, the query logic supports fuzzy query, which includes the warning point name, warning point code and rule description; the data table supports Excel export.

[0012] As a preferred option, the main page displays all the warning points that have been maintained, and the warning points of custom types are queried. The warning points of custom types can be added, modified, deleted, and the corresponding warning rules can be added, edited, and deleted through the home page; the details are as follows:

[0013] According to the supervision link, warning point name and the organization to which the warning point belongs, query the warning point with the custom warning type. The specific logic is as follows:

[0014] MMC_ALARM_POINT_TEMPLATE and MMC_ALARM_POINT_CASE add the field "IS_CUSTOM: Whether Customized" to identify whether the warning point is a customized warning point; the main page only displays customized warning points;

[0015] Warning point list query sql;

[0016] Click the "Add" button to jump to the new warning point page;

[0017] Click the "Export" button to export the basic data of the corresponding warning point;

[0018] Click "Add Rule" to jump to the warning point warning rule maintenance page.

[0019] Preferably, the new warning points are as follows:

[0020] Click the Add button on the main page to jump to the Add page. Enter the basic information of the warning point name, warning description, warning logic SQL, warning cycle, warning organization, display days and warning parameters on the Add page.

[0021] After selecting the business type and supervision link, the warning point code is automatically generated. The specific generation rules are as follows: query the selected business type (M), supervision link (04), and then splice the 30-digit random code to form a new warning point code;

[0022] To query the group, query the MMC_ALARM_GROUP_BASE table;

[0023] Click the "Save" button to save the data to the warning point template table "MMC_ALARM_POINT_TEMPLATE" and the warning point instance table "MMC_ALARM_POINT_CASE".

[0024] Preferably, the warning points are modified as follows:

[0025] Click the main page modification button to jump to the modification page, where you can modify the basic information of the warning logic SQL, warning cycle and warning parameters;

[0026] After the modification is completed, click the Save button to save the modified information;

[0027] The details of early warning point deletion are as follows:

[0028] Click the delete button on the main page to delete the warning point and warning related information from the logic;

[0029] Set the warning to not enabled, but do not delete the data to prevent the warning from being enabled again.

[0030] Preferably, the time monitoring timer schedules the execution of the warning rules every day, replaces the warning parameters with all the warning logic SQLs maintained, and then executes them, and saves the execution results in the warning table;

[0031] Among them, the user enters the warning detail page through the warning point on the main page, and the detail page displays all the information of the warning, that is, the user can view all the currently maintained warning points and warning detail information through the warning main page.

[0032] Preferably, the operations of adding, modifying and deleting corresponding warning rules are as follows:

[0033] Query the corresponding warning rule list according to the warning point code and query sql;

[0034] Click the "Add" button to add the warning rule corresponding to the warning point;

[0035] Click the "Edit" button to update the warning rules;

[0036] Click the "Delete" button to delete the corresponding warning rule.

[0037] Preferably, the warning rules corresponding to the newly added warning points are as follows:

[0038] Warning rule codes and warning parameter codes are automatically generated, and the generation logic is as follows:

[0039] Business type (M) + regulatory link (04) + 30-digit random code;

[0040] Click the "SQL Verification" button to perform syntax verification on the warning SQL. Verification method:

[0041] Replace the string type parameters in the SQL with empty strings, and replace the numeric type parameters with 0, and execute the SQL. If the execution is successful, it will return "SQL execution successful", and if the execution fails, it will return "SQL execution failed + execution error information";

[0042] Click the "Save" button to save the data to MMC_ALARM_RULE_TEMPLATE, MMC_ALARM_RULE_CASE, MMC_ALARM_SQL_CASE, MMC_ALARM_PARAM_TEMPLATE or MMC_ALARM_PARAM_CASE.

[0043] A lightweight business early warning management system, which is based on the Inspur V6 platform architecture, uses VUE for the front end, spring boot+spring mvc+mybatis for the back end, DB2 or oracle for the database, and uses the time-quartz framework to complete the timer scheduling work; the system includes:

[0044] Definition module 1 is used to define the warning configuration template and integrate the warning configuration modules in a unified manner through the dynamic proxy mode;

[0045] The storage module is used to store the monitoring logic of the business modules involved in the same database table, and to replace the parameter variables in the supervision SQL uniformly through the dynamic proxy;

[0046] Definition module 2: define a time monitoring timer, trigger the call of the early warning configuration module at a fixed time every day, take out all the supervision logic from the database table, execute it in the order of dependencies, and store the execution results in the corresponding supervision point subtable; among them, the supervision cycle of the time monitoring timer supports custom day, week, month and year;

[0047] Definition module three is used to define the general page display template. The general page display template supports the display of data at different supervision points: the data table is directly rendered on the main page by defining the query logic and display column content; the query logic supports fuzzy query, which includes the warning point name, warning point code, and rule description; the data table supports Excel export;

[0048] The inspection module is used to uniformly store the supervision point execution logs in the log table, and check the execution status of the business modules every day by analyzing the logs; during the supervision point execution process, manual triggering is supported for the logs of the supervision points that have not been successfully executed.

[0049] A computer-readable storage medium stores a computer program, and the computer program can be executed by a processor to implement the lightweight business warning management method as described above.

[0050] The lightweight business early warning management method, system and storage medium of the present invention have the following advantages:

[0051] (1) The present invention reduces the time developers have to spend on complex code combing and maintenance, and concentrates all work in the hands of business personnel or customers, allowing business personnel or customers to directly participate in the formulation and management of regulatory rules;

[0052] (ii) Business personnel or customers can use this function to flexibly configure warning points and warning rules without writing complex codes; based on business development and business changes, warning rules can be flexibly modified and added, and rules can be used to constrain business and prevent illegal operations within the industry;

[0053] (III) The customer can flexibly configure the regulatory rules through the present invention, and the present invention automatically calculates according to the regulatory rules and displays the results to the customer after the calculation. The customer can add and modify the regulatory rules at any time to cope with the development of marketing business, which is convenient, fast and efficient;

[0054] (iv) The present invention can free developers from the current tedious and complicated work as soon as possible, allowing more business personnel to participate in it, while reducing information handover and avoiding development loopholes caused by information asymmetry. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] The present invention is further described below in conjunction with the accompanying drawings.

[0056] Attached Figure 1 The flowchart of the lightweight business early warning management method is shown in FIG. DETAILED DESCRIPTION

[0057] The lightweight service early warning management method, system and storage medium of the present invention are described in detail below with reference to the accompanying drawings and specific embodiments of the specification.

[0058] Embodiment 1:

[0059] The lightweight service early warning management method of the present invention is specifically as follows:

[0060] S1. Define the warning configuration template and integrate the warning configuration modules in a unified manner through the dynamic proxy mode;

[0061] S2. The monitoring logic for the business modules involved is stored in the same database table, and the parameter variables in the supervision SQL are uniformly replaced through dynamic proxy;

[0062] S3. Define a time monitoring timer, trigger the call of the early warning configuration module at a fixed time every day, take out all the supervision logic from the database table, execute it in the order of dependencies, and store the execution results in the corresponding supervision point subtable; the supervision cycle of the time monitoring timer supports custom day, week, month and year;

[0063] S4. Define a general page display template. The general page display template supports data display at different supervision points: directly render the data table on the main page by defining the query logic and display column content; the query logic supports fuzzy query, which includes the warning point name, warning point code and rule description; the data table supports Excel export;

[0064] S5. The execution logs of the supervision points are uniformly stored in the log table, and the execution status of the business modules is checked every day by analyzing the logs. During the execution of the supervision points, manual triggering is supported for the logs of the supervision points that have not been successfully executed.

[0065] In this embodiment, the main page displays all the warning points that have been maintained, and the warning points of the custom type are queried. The warning points of the custom type can be added, modified, deleted, and the corresponding warning rules can be added, edited, and deleted through the home page; the details are as follows:

[0066] (1) According to the supervision link, warning point name and the organization to which the warning point belongs, query the warning point with the type of custom warning. The specific logic is as follows:

[0067] MMC_ALARM_POINT_TEMPLATE and MMC_ALARM_POINT_CASE add the field "IS_CUSTOM: Whether Customized" to identify whether the warning point is a customized warning point; the main page only displays customized warning points;

[0068] (2) Query SQL for the warning point list; the key code is as follows:

[0069]

[0070] (3) Click the "Add" button to jump to the new warning point page;

[0071] (4) Click the "Export" button to export the basic data of the corresponding warning point;

[0072] (5) Click "Add Rule" to jump to the warning point warning rule maintenance page.

[0073] In this embodiment, the new warning points are as follows:

[0074] (1) Click the Add button on the main page to jump to the Add page. Enter the basic information of the warning point name, warning description, warning logic SQL, warning cycle, warning organization, display days and warning parameters on the Add page.

[0075] (2) After selecting the business type and supervision link, the warning point code is automatically generated. The specific generation rules are as follows: query the selected business type (M), supervision link (04), and then splice the 30-digit random code to form a new warning point code;

[0076] (3) Query the MMC_ALARM_GROUP_BASE table for the group to which it belongs;

[0077] (4) Click the "Save" button to save the data to the warning point template table "MMC_ALARM_POINT_TEMPLATE" and the warning point instance table "MMC_ALARM_POINT_CASE".

[0078] In this embodiment, the modification of the early warning point is as follows:

[0079] (1) Click the Modify button on the main page to jump to the Modify page. On this page, you can modify the basic information of the warning logic SQL, warning cycle, and warning parameters;

[0080] (2) After the modification is completed, click the Save button to save the modified information;

[0081] In this embodiment, the early warning point deletion is specifically as follows:

[0082] (1) Click the delete button on the main page to delete the warning point and warning related information from the logic;

[0083] (2) Set the warning to not enabled, but do not delete the data to prevent the warning from being enabled again.

[0084] In this embodiment, the time monitoring timer schedules the execution of the warning rule every day, replaces the warning parameters of all the warning logic SQLs maintained, and executes them, and saves the execution results in the warning table;

[0085] Among them, the user enters the warning detail page through the warning point on the main page, and the detail page displays all the information of the warning, that is, the user can view all the currently maintained warning points and warning detail information through the warning main page.

[0086] The operations of adding, modifying and deleting the corresponding warning rules in this embodiment are as follows:

[0087] (1) Query the corresponding warning rule list according to the warning point code and query SQL;

[0088]

[0089] (2) Click the "Add" button to add the warning rule corresponding to the warning point;

[0090] (3) Click the "Edit" button to update the warning rules;

[0091] (4) Click the “Delete” button to delete the corresponding warning rule.

[0092] The warning rules corresponding to the newly added warning points in this embodiment are as follows:

[0093] (1) Automatically generate warning rule codes and warning parameter codes, and generate logic:

[0094] (2) Business type (M) + regulatory link (04) + 30-digit random code;

[0095] (3) Click the "SQL Verification" button to perform syntax verification on the warning SQL. Verification method:

[0096] (4) Replace the string type parameters in the SQL with empty strings and the numeric type parameters with 0, and execute the SQL. If the execution is successful, it will return "SQL execution successful", and if the execution fails, it will return "SQL execution failed + execution error information";

[0097] (5) Click the "Save" button to save the data to MMC_ALARM_RULE_TEMPLATE, MMC_ALARM_RULE_CASE, MMC_ALARM_SQL_CASE, MMC_ALARM_PARAM_TEMPLATE or MMC_ALARM_PARAM_CASE.

[0098] Embodiment 2:

[0099] The lightweight business early warning management system of the present invention is based on the Inspur V6 platform architecture, uses VUE for the front end, spring boot+spring mvc+mybatis for the back end, uses DB2 or oracle for the database, and uses the time-quartz framework to complete the timer scheduling work; the system includes:

[0100] Definition module 1 is used to define the warning configuration template and integrate the warning configuration modules in a unified manner through the dynamic proxy mode;

[0101] The storage module is used to store the monitoring logic of the business modules involved in the same database table, and to replace the parameter variables in the supervision SQL uniformly through the dynamic proxy;

[0102] Definition module 2: define a time monitoring timer, trigger the call of the early warning configuration module at a fixed time every day, take out all the supervision logic from the database table, execute it in the order of dependencies, and store the execution results in the corresponding supervision point subtable; among them, the supervision cycle of the time monitoring timer supports custom day, week, month and year;

[0103] Definition module three is used to define the general page display template. The general page display template supports the display of data at different supervision points: the data table is directly rendered on the main page by defining the query logic and display column content; the query logic supports fuzzy query, which includes the warning point name, warning point code, and rule description; the data table supports Excel export;

[0104] The inspection module is used to uniformly store the supervision point execution logs in the log table, and check the execution status of the business modules every day by analyzing the logs; during the supervision point execution process, manual triggering is supported for the logs of the supervision points that have not been successfully executed.

[0105] Embodiment 3:

[0106] The embodiment of the present invention further provides a computer-readable storage medium, in which a plurality of instructions are stored, and the instructions are loaded by a processor, so that the processor executes the lightweight service early warning management method in any embodiment of the present invention. Specifically, a system or device equipped with a storage medium can be provided, on which a software program code that implements the functions of any of the above embodiments is stored, and a computer (or CPU or MPU) of the system or device reads and executes the program code stored in the storage medium.

[0107] In this case, the program code itself read from the storage medium can realize the function of any one of the above-mentioned embodiments, and thus the program code and the storage medium storing the program code constitute a part of the present invention.

[0108] The storage medium embodiments for providing the program code include a floppy disk, a hard disk, a magneto-optical disk, an optical disk (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RYM, DVD-RW, DVD+RW), a magnetic tape, a non-volatile memory card, and a ROM. Alternatively, the program code can be downloaded from a server computer via a communication network.

[0109] In addition, it should be clear that the functions of any of the above embodiments can be implemented not only by executing the program code read by the computer, but also by enabling an operating system operating on the computer to complete part or all of the actual operations based on instructions from the program code.

[0110] In addition, it can be understood that the program code read from the storage medium is written to a memory provided in an expansion board inserted into the computer or written to a memory provided in an expansion unit connected to the computer, and then based on the instructions of the program code, a CPU installed on the expansion board or the expansion unit is enabled to perform part or all of the actual operations, thereby realizing the functions of any of the above-mentioned embodiments.

[0111] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A lightweight business warning management method, characterized in that: The method is as follows: Define the warning configuration template and integrate the warning configuration modules in a unified manner through the dynamic proxy mode; The monitoring logic for the business modules involved is stored in the same database table, and the parameter variables in the supervision SQL are uniformly replaced through dynamic proxy; Define a time monitoring timer, trigger the call of the early warning configuration module at a fixed time every day, take out all the supervision logic from the database table, execute it in the order of dependencies, and store the execution results in the corresponding supervision point subtable; the supervision cycle of the time monitoring timer supports custom day, week, month and year; Define a general page display template, which supports data display at different regulatory points: directly render a data table on the main page by defining query logic and display column content; The execution logs of the supervision points are uniformly stored in the log table, and the execution status of the business modules is checked every day by analyzing the logs. During the execution of the supervision points, manual triggering is supported for the logs of the supervision points that have not been successfully executed. The main page displays all the warning points that have been maintained, and you can query the warning points of custom types. You can add, modify, delete the warning points of custom types through the home page, and add, edit, and delete the corresponding warning rules; the details are as follows: According to the supervision link, warning point name and the organization to which the warning point belongs, query the warning point with the custom warning type. The specific logic is as follows: MMC_ALARM_POINT_TEMPLATE and MMC_ALARM_POINT_CASE add the field "IS_CUSTOM: Whether Customized" to identify whether the warning point is a customized warning point; the main page only displays customized warning points; Warning point list query sql; Click the "Add" button to jump to the new warning point page; Click the "Export" button to export the basic data of the corresponding warning point; Click "Add rule" to jump to the warning point warning rule maintenance page; The warning rules corresponding to the newly added warning points are as follows: Warning rule codes and warning parameter codes are automatically generated, and the generation logic is as follows: Business type + regulatory link + 30-digit random code; Click the "SQL Verification" button to perform syntax verification on the warning SQL. Verification method: Replace the string type parameters in the SQL with empty strings, and replace the numeric type parameters with 0, and execute the SQL. If the execution is successful, "SQL execution is successful" will be returned, and if the execution fails, "SQL execution failed + execution error information" will be returned; Click the "Save" button to save the data to MMC_ALARM_RULE_TEMPLATE, MMC_ALARM_RULE_CASE, MMC_ALARM_SQL_CASE, MMC_ALARM_PARAM_TEMPLATE or MMC_ALARM_PARAM_CASE.

2. The lightweight business warning management method according to claim 1, characterized in that: The query logic supports fuzzy query, which includes warning point name, warning point code and rule description; the data table supports Excel export.

3. The lightweight business warning management method according to claim 1 is characterized in that: The new warning points are as follows: Click the Add button on the main page to jump to the Add page. Enter the basic information of the warning point name, warning description, warning logic SQL, warning cycle, warning organization, display days and warning parameters on the Add page. After selecting the business type and supervision link, the warning point code is automatically generated. The specific generation rules are as follows: query the selected business type and supervision link, and then splice the 30-digit random code to form a new warning point code; To query the group, query the MMC_ALARM_GROUP_BASE table; Click the "Save" button to save the data to the warning point template table and warning point instance table.

4. The lightweight business warning management method according to claim 1, characterized in that: The changes to the warning points are as follows: Click the main page modification button to jump to the modification page, where you can modify the basic information of the warning logic SQL, warning cycle and warning parameters; After the modification is completed, click the Save button to save the modified information; The details of early warning point deletion are as follows: Click the delete button on the main page to delete the warning point and warning related information from the logic; Set the warning to not enabled, but do not delete the data to prevent the warning from being enabled again.

5. The lightweight business warning management method according to claim 1, characterized in that: The time monitoring timer schedules the execution of warning rules every day, replaces the warning parameters with all the warning logic SQL maintained, and then executes them, and saves the execution results in the warning table; Among them, the user enters the warning detail page through the warning point on the main page, and the detail page displays all the information of the warning, that is, the user can view all the currently maintained warning points and warning detail information through the warning main page.

6. The lightweight business warning management method according to claim 1, characterized in that: The operations for adding, modifying, and deleting corresponding warning rules are as follows: Query the corresponding warning rule list according to the warning point code and query sql; Click the "Add" button to add the warning rule corresponding to the warning point; Click the "Edit" button to update the warning rules; Click the "Delete" button to delete the corresponding warning rule.

7. A lightweight business warning management system, characterized in that: The system is used to implement the lightweight business warning management method as described in any one of claims 1 to 6; the system is based on the Inspur V6 platform architecture, uses VUE for the front end, uses spring boot + spring mvc + mybatis for the back end, uses DB2 or oracle for the database, and uses the time-quartz framework to complete the timer scheduling work; the system includes, Definition module 1 is used to define the warning configuration template and integrate the warning configuration modules in a unified manner through the dynamic proxy mode; The storage module is used to store the monitoring logic of the business modules involved in the same database table, and to replace the parameter variables in the supervision SQL uniformly through the dynamic proxy; Definition module 2: define a time monitoring timer, trigger the call of the early warning configuration module at a fixed time every day, take out all the supervision logic from the database table, execute it in the order of dependencies, and store the execution results in the corresponding supervision point subtable; among them, the supervision cycle of the time monitoring timer supports custom day, week, month and year; Definition module three is used to define the general page display template. The general page display template supports the display of data at different supervision points: the data table is directly rendered on the main page by defining the query logic and display column content; the query logic supports fuzzy query, which includes the warning point name, warning point code, and rule description; the data table supports Excel export; The inspection module is used to uniformly store the supervision point execution logs in the log table, and check the execution status of the business modules every day by analyzing the logs; during the supervision point execution process, manual triggering is supported for the logs of the supervision points that have not been successfully executed.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which can be executed by a processor to implement the lightweight service early warning management method according to any one of claims 1 to 6.

Images