Alarm method and system based on interface dial test

Abstract

The invention relates to the technical field of interface monitoring, in particular to an alarm method and system based on interface dial testing. Comprising the following steps: S1, a dial test case creation stage: acquiring a planned dial test object, and creating a dial test case; s2, a dial testing task creating stage: selecting at least one dial testing case to create a dial testing plan, and configuring execution tasks for the dial testing plan to obtain a dial testing task; and S3, an alarm setting stage: configuring alarm information and an alarm mode for the trigger condition, judging whether the alarm trigger condition is triggered or not after dial testing operation is started, and generating an alarm if the alarm trigger condition is triggered. The system comprises a background part, a front end part and a communication part, the background part comprises a dial test management module and an alarm module, and the front end part comprises terminal equipment and an alarm information module. According to the method, the abnormal condition of the interface can be found in time, related personnel are notified through multiple alarm modes, and a basis is provided for optimization and improvement.

Description

Technical Field

[0001] The present invention relates to the technical field of interface monitoring, and in particular to an alarm method and system based on interface dialing test. Background Art

[0002] Dial test, as a communication engineering term, is mainly used for network performance monitoring and troubleshooting. Dial test service is a service for active application performance and user experience monitoring for Internet applications, such as Web pages or network links, and is usually provided by professional dial test tools or platforms. Interface dial test is a test behavior that completely simulates user behavior. Through a specific combination of request calls, the return status and results are analyzed to detect whether some important interfaces or services of each system are running and responding normally, and monitor the operating status of the system, so as to provide timely warnings and assist in quickly locating and solving production problems.

[0003] Alerts are the response component of the monitoring system. Alerts allow users to define scenarios that make sense for active management, while relying on the software's passive monitoring to observe changing situations. When the system detects an abnormal situation or meets the set trigger conditions, the alert function will trigger the set actions, such as sending email notifications, triggering alarms, etc., so that relevant personnel can take timely response measures.

[0004] In the prior art, the key steps of running a dial test include determining the scope and target of the dial test, creating a dial test interface and a dial test task, configuring the dial test environment, and executing the interface dial test. Although the dial test technology provides important support for performance monitoring and system troubleshooting of network services at the current stage, there are still some shortcomings and challenges. The complexity of the process and strategy of the dial test service is reflected in multiple aspects such as demand analysis and definition, test planning and design, test execution and monitoring, result analysis and reporting, etc. The complexity of the strategy also needs to take into account multiple factors such as multi-platform and multi-device adaptation, continuity and periodicity, risk assessment and response, and automation and intelligence. In order to reduce the complexity of processes and strategies, it is necessary to establish standardized test processes and strategies. At the same time, developers should formulate dial test service execution documents and clarify the execution steps of the dial test to facilitate system administrators to operate and improve test efficiency and accuracy. Summary of the invention

[0005] In order to solve the above-mentioned problems, the present invention provides an alarm method and system based on interface dialing test.

[0006] In a first aspect, the present invention provides an alarm method based on interface dialing test, comprising: S1. Create a test case phase Acquire a planned dial test object and create a dial test interface, wherein the creation of the dial test interface includes configuring different main application node information according to different network environments on the main application page, and generating at least one protocol template and at least one dial test case; S2. Create a dial test task Select at least one dial test case to create a dial test plan, configure execution tasks for the dial test plan to obtain a dial test task, run the dial test task, and check the execution status of the dial test task; S3. Set the alarm stage Configure alarm trigger conditions based on the interface error rate threshold for the dial test interface, configure alarm trigger conditions based on the response time threshold for the dial test task, configure alarm information and alarm mode for the trigger conditions, and determine whether the alarm trigger conditions are triggered after starting the dial test. If the alarm trigger conditions are triggered, an alarm alert is generated.

[0007] Furthermore, the acquisition of the planned dialing test object includes acquiring the main application name, the name of the competent unit, the main application code and the name of the operation and maintenance company of the object, and the creation of the dialing test interface includes creating it by batch importing or inputting one by one.

[0008] Furthermore, the configured different main application node information includes configuring the sub-application information of the next level of the main application, and the configured sub-application information includes configuring the interface name, interface type, interface address, interface request method, interface parameters, interface description and expected results. The interface type is an internal interface, and the interface request method is selected according to the request type of the interface address. The interface parameters are JSON or FROM.

[0009] Furthermore, the interface types include HttpClientPost for sending Post request, HttpClientGet for sending Get request, HttpClientPostJSON for sending JSON format POST request, httpClientPut for sending Put request, httpClientPutJson for sending JSON format Put request, httpClientUploadFile for uploading file, HttpURLPost for sending Post request and URLPost for sending Post request.

[0010] Furthermore, the expected result is to configure an alarm trigger condition for the dialing test interface based on an interface error rate threshold, and fuzzy matching is performed between the expected result and the return value after the dialing test interface is executed. If the return value after the dialing test interface is executed contains the expected result, the dialing test is successful; if the return value after the dialing test interface is executed does not contain the expected result, the dialing test fails and an alarm is triggered.

[0011] Furthermore, the configuration of executing the task for the dialing plan includes configuring the task name, the main application name, the dialing plan, the client, the number of client execution threads, the task timeout, the task type, the execution frequency, the execution strategy and the task status, the task type includes one of PING, TCP, HTTP and DNS, the execution frequency is a CRON expression, and the execution strategy includes default execution according to the execution frequency or automatic execution once according to the execution frequency.

[0012] Furthermore, the alarm information includes alarm time, alarm level, alarm content and related information. The alarm time includes the specific time when the alarm occurs. The alarm level includes severity level, warning level and prompt level. The alarm content includes a detailed description of the cause of the alarm, the interfaces involved and the triggering conditions. The related information includes the interface call log and server status.

[0013] Furthermore, the alarm method includes SMS notification and system notification. The alarm alert includes displaying the alarm on the system main page in the internal system through system notification. The system notification includes counting the number and content of alarms for each dialing test interface and dialing test task, and using the information provided by the alarm alert to correct errors in the dialing test interface and dialing test task.

[0014] In the second aspect, an alarm system based on interface dialing test includes a backend part, a frontend part and a communication part, the communication part is used to realize communication between the backend part and the frontend part, the backend part includes a dialing test management module and an alarm module, the dialing test management module is used to configure dialing test use cases, configure dialing test plans and configure dialing test tasks, the alarm module is used to configure the alarm trigger conditions of the interface error rate threshold and the alarm trigger conditions of the response time threshold, the frontend part includes a terminal device and an alarm information module, the terminal device responds to the alarm information module and receives the alarm information.

[0015] Furthermore, the dialing test management module includes a dialing test case center unit, a dialing test plan center and a dialing test task center. The dialing test case center includes a main application unit and a sub-application unit. The main application unit is used to configure the object of the planned dialing test, and the sub-application unit is used to configure sub-application information. The dialing test plan center is used to organize at least one dialing test case into a dialing test plan, and the dialing test task center is used to configure a dialing test task for the dialing test plan.

[0016] Furthermore, the objects of the planned dialing include the main application name, the name of the supervisory unit, the main application code and the name of the operation and maintenance company; the sub-application information includes the interface name, interface type, interface address, interface request method, interface parameters, interface description and expected results; the interface type is an internal interface; the interface request method is selected according to the request type of the interface address; and the interface parameters are JSON or FROM.

[0017] Furthermore, the configuration of the dialing task includes configuring the task name, the main application name, the dialing plan, the client, the number of client execution threads, the task timeout, the task type, the execution frequency, the execution strategy and the task status. The task type includes one of PING, TCP, HTTP and DNS. The execution frequency is a CRON expression. The execution strategy includes default execution according to the execution frequency or automatic execution once according to the execution frequency.

[0018] Furthermore, the alarm information module includes alarm time, alarm level, alarm content and related information. The alarm time includes the specific time when the alarm occurs. The alarm level includes severity level, warning level and prompt level. The alarm content includes a detailed description of the cause of the alarm, the interfaces involved and the triggering conditions. The related information includes the interface call log and server status.

[0019] Furthermore, the terminal device includes a mobile communication terminal and a display.

[0020] In summary, the present invention has the following beneficial technical effects: 1. The present invention provides an alarm method based on interface dialing test, which has a reasonable test planning design and can cover various possible business scenarios and business behaviors. By periodically dialing the dialing test interface and the dialing test task, the abnormal situation of the interface can be discovered in time, avoiding inaccurate test results due to problems with the test environment or tools, and notifying relevant personnel through multiple alarm methods, and forming a detailed test report, thereby improving the efficiency and real-time performance of interface monitoring and ensuring the stable operation of the system. At the same time, the recording and analysis of the dialing test results are helpful to better understand the operation trends and problems of the dialing test interface, and provide a basis for optimization and improvement; 2. The present invention provides an alarm system based on interface dialing test. The system is reasonably designed and runs various dialing tests and dialing test tasks in a unified system. It introduces an intelligent dialing test and monitoring alarm mechanism, and can accurately configure the dialing test object based on the analysis of needs, including business logic, performance indicators and key business processes. At the same time, factors such as the continuity and periodicity of the dialing test are also taken into account. When a network failure or equipment failure occurs, the automated dialing test can continue after the failure is resolved without reconfiguration. The results can be monitored in real time, and it is compatible with multiple platforms and multiple devices, and alarm information can be displayed on multiple devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 This is a flow chart of an alarm method based on interface dialing test according to Embodiment 1 of the present invention; Figure 2 It is a structural block diagram of an alarm system based on interface dialing test in embodiment 2 of the present invention. DETAILED DESCRIPTION

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

[0023] Example 1 An alarm method based on interface dialing test in this embodiment includes: S1. Create a test case phase The planned dial test object is obtained, and a dial test interface is created. The creation of the dial test interface includes configuring different main application node information according to different network environments on the main application page, and generating at least one protocol template and at least one dial test case.

[0024] Acquiring the planned dial test object includes acquiring the main application name, the name of the competent unit, the main application code and the name of the operation and maintenance company of the object, and creating the dial test interface includes creating it by using a batch import method or a one-by-one input method.

[0025] Configuring different main application node information includes configuring the sub-application information of the next level of the main application. Configuring the sub-application information includes configuring the interface name, interface type, interface address, interface request method, interface parameters, interface description and expected results. The interface type is an internal interface. The interface request method is selected according to the request type of the interface address. The interface parameters are JSON or FROM.

[0026] The interface types include HttpClientPost to send Post requests, HttpClientGet to send Get requests, HttpClientPostJSON to send JSON format POST requests, httpClientPut to send Put requests, httpClientPutJson to send JSON format Put requests, httpClientUploadFile to upload files, HttpURLPost to send Post requests, and URLPost to send Post requests.

[0027] For the interface request method, select HttpClientPost to send a Post request or HttpClientGet to send a Get request according to the request type of the interface address. If parameters are included, add them to FROM. If the interface sends JOSN parameters, select Send JSON for the interface request method, select JSON for the interface parameters, and fill in the parameters.

[0028] Regarding the expected result, this embodiment provides that the return value of the dial test interface contains a status code of 10000, so the expected result is filled in with %=10000. If the return value after the dial test interface is executed is fuzzy matched with the value of the expected result, if the returned result contains the expected result, it means that the dial test is successful, otherwise the dial test fails and an alarm is generated.

[0029] The expected result is to configure the alarm trigger condition based on the interface error rate threshold for the dial test interface. The expected result is fuzzy matched with the return value after the dial test interface is executed. If the return value after the dial test interface is executed contains the expected result, the dial test is successful. If the return value after the dial test interface is executed does not contain the expected result, the dial test fails and an alarm is triggered.

[0030] S2. Create a dial test task Select at least one dial test case to create a dial test plan, configure the execution task for the dial test plan to obtain the dial test task, run the dial test task and check the execution status of the dial test task. A dial test plan can select one or more dial test cases, which is equivalent to a dial test plan that can execute multiple dial test interfaces at the same time.

[0031] Configuring the execution task for the dial test plan includes configuring the task name, main application name, dial test plan, client, number of client execution threads, task timeout, task type, execution frequency, execution strategy, and task status. The task type includes one of PING, TCP, HTTP, and DNS. The execution frequency is a CRON expression. The execution strategy includes default execution according to the execution frequency or automatic execution once according to the execution frequency.

[0032] The execution frequency is a CRON expression that defines the execution time of a scheduled task. It consists of a series of fields, each of which represents a part of the time (such as minutes, hours, dates, etc.). In the dial test task of the running system, different CRON expressions can be set according to needs to control the frequency of the dial test.

[0033] After confirming the execution, check whether the dial test task is executed according to the set execution frequency and whether the execution result is successful.

[0034] S3. Set the alarm stage Configure alarm trigger conditions based on the interface error rate threshold for the dial test interface, configure alarm trigger conditions based on the response time threshold for the dial test task, configure alarm information and alarm mode for the trigger conditions, and determine whether the alarm trigger conditions are triggered after starting the dial test. If the alarm trigger conditions are triggered, an alarm alert is generated.

[0035] The error rate exceeds the preset threshold. If the error rate of an interface continues to rise and exceeds the preset threshold, it indicates that there is a logic error or configuration problem on the interface and an alarm needs to be triggered to attract attention.

[0036] Response time exceeds the preset threshold means that when the response time of the interface exceeds the set time limit, it indicates that there is a performance problem with the interface or the server load is too high, and an alarm is triggered.

[0037] In the dial test service of the running system, when creating the dial test interface, the expected result is set to verify whether the interface dial test is successful. In addition, the preset dial test task timeout time can be configured in the application rule to verify whether the dial test task execution time has timed out.

[0038] The alarm information includes the alarm time, alarm level, alarm content and related information. The alarm time includes the specific time when the alarm occurs. The alarm level includes the severity level, warning level and prompt level. The alarm content includes a detailed description of the cause of the alarm, the interfaces involved and the triggering conditions. The related information includes the interface call log and server status.

[0039] The alarm time refers to the specific time when the alarm occurs, which helps to locate the moment when the problem occurs.

[0040] Alarm level refers to the classification of alarms into different levels according to the severity of the problem, such as severe, warning, prompt, etc., so that relevant personnel can take corresponding handling measures according to the alarm level.

[0041] The alarm content refers to a detailed description of the cause of the alarm, the interfaces involved, the triggering conditions, and other information to help relevant personnel quickly locate the problem.

[0042] Correlation information refers to other information related to the alarm, such as interface call logs, server status, etc., to further analyze the problem.

[0043] Alarm methods include SMS notification and system notification. Alarm alerts include being displayed on the system home page through the internal system through system notifications. System notifications include counting the number and content of alarms for each dial test interface and dial test task, and using the information provided by the alarm alerts to correct errors in the dial test interface and dial test tasks.

[0044] After receiving the alarm information, relevant personnel need to perform the following processing steps: Check the alarm details, carefully check the alarm information, and understand the specific situation and cause of the problem through the dial test execution results.

[0045] Locate the problem: Locate the specific location and cause of the problem based on the associated information in the alarm information.

[0046] Solve the problem and take appropriate measures to deal with the problem, such as adjusting interface configuration, optimizing performance, fixing logical errors, etc.

[0047] Verify the result. After the problem is resolved, re-dial the test to verify whether the performance and availability of the interface have returned to normal.

[0048] Record and feedback: record the process and results for subsequent analysis and summary. At the same time, feedback the results to relevant personnel to ensure that the problem is properly resolved.

[0049] Example 2 This embodiment provides an alarm system based on interface dialing test, including a backend part, a frontend part and a communication part. The communication part is used to realize communication between the backend part and the frontend part. The backend part includes a dialing test management module and an alarm module. The dialing test management module is used to configure a dialing test case, a dialing test plan and a dialing test task. The alarm module is used to configure the alarm trigger condition of the interface error rate threshold and the alarm trigger condition of the response time threshold. The frontend part includes a terminal device and an alarm information module. The terminal device responds to the alarm information module and receives the alarm information.

[0050] The dial test management module includes a dial test case center, a dial test plan center and a dial test task center. The dial test case center includes a main application unit and a sub-application unit. The main application unit is used to configure the object of the planned dial test, and the sub-application unit is used to configure the sub-application information. The dial test plan center is used to form a dial test plan with at least one dial test case, and the dial test task center is used to configure the dial test task for the dial test plan.

[0051] The objects of the planned dial test include the main application name, the name of the competent unit, the main application code and the name of the operation and maintenance company. The sub-application information includes the interface name, interface type, interface address, interface request method, interface parameters, interface description and expected results. The interface type is internal interface. The interface request method is selected according to the request type of the interface address. The interface parameters are JSON or FROM.

[0052] Configuring a dial test task includes configuring the task name, main application name, dial test plan, client, number of client execution threads, task timeout, task type, execution frequency, execution strategy, and task status. The task type includes one of PING, TCP, HTTP, and DNS. The execution frequency is a CRON expression. The execution strategy includes default execution according to the execution frequency or automatic execution once according to the execution frequency.

[0053] The alarm information module includes alarm time, alarm level, alarm content and related information. The alarm time includes the specific time when the alarm occurs. The alarm level includes severity level, warning level and prompt level. The alarm content includes a detailed description of the cause of the alarm, the interfaces involved and the triggering conditions. The related information includes the interface call log and server status. The terminal equipment includes a mobile communication terminal and a display.

[0054] The alarm information is displayed in the internal system, and relevant personnel can log in to the system to view and process it. The alarm list displayed on the terminal records the alarm information of the dial-up interface in detail. The dial-up test personnel can quickly locate the problem based on the relevant information. The command and dispatch display will also promptly count and display the total number of alarms for each application system, so that administrators can detect alarms and take measures in a timely manner.

[0055] The above are all preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention. Therefore, any equivalent changes made based on the structure, shape, and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. An alarm method based on interface dialing test, It is characterized in that The steps include: S1. Create a test case phase Acquire a planned dial test object and create a dial test interface, wherein the creation of the dial test interface includes configuring different main application node information according to different network environments on the main application page, and generating at least one protocol template and at least one dial test case; S2. Create a dial test task Select at least one dial test case to create a dial test plan, configure execution tasks for the dial test plan to obtain a dial test task, run the dial test task, and check the execution status of the dial test task; S3. Set the alarm stage Configure alarm trigger conditions based on the interface error rate threshold for the dial test interface, configure alarm trigger conditions based on the response time threshold for the dial test task, configure alarm information and alarm mode for the trigger conditions, and determine whether the alarm trigger conditions are triggered after starting the dial test. If the alarm trigger conditions are triggered, an alarm alert is generated.

2. According to claim 1, an alarm method based on interface dialing test, It is characterized in that The acquisition of the planned dial test object includes acquiring the main application name, the name of the competent unit, the main application code and the name of the operation and maintenance company of the object, and the creation of the dial test interface includes creating it by batch importing or inputting one by one.

3. The alarm method based on interface dialing test according to claim 1, It is characterized in that The configured different main application node information includes configuring the sub-application information of the next level of the main application, and the configured sub-application information includes configuring the interface name, interface type, interface address, interface request method, interface parameters, interface description and expected results. The interface type is an internal interface, and the interface request method is selected according to the request type of the interface address. The interface parameters are JSON or FROM.

4. The alarm method based on interface dialing test according to claim 3, It is characterized in that The interface types include HttpClientPost to send Post request, HttpClientGet to send Get request, HttpClientPostJSON to send JSON format POST request, httpClientPut to send Put request, httpClientPutJson to send JSON format Put request, httpClientUploadFile to upload file, HttpURLPost to send Post request and URLPost to send Post request.

5. The alarm method based on interface dialing test according to claim 3, It is characterized in that The expected result is to configure an alarm trigger condition for the dialing test interface based on the interface error rate threshold, and fuzzy matching is performed between the expected result and the return value after the dialing test interface is executed. If the return value after the dialing test interface is executed contains the expected result, the dialing test is successful; if the return value after the dialing test interface is executed does not contain the expected result, the dialing test fails and an alarm is triggered.

6. The alarm method based on interface dialing test according to claim 1, It is characterized in that The configuration of executing tasks for the dialing test plan includes configuring the task name, the main application name, the dialing test plan, the client, the number of client execution threads, the task timeout, the task type, the execution frequency, the execution strategy and the task status. The task type includes one of PING, TCP, HTTP and DNS. The execution frequency is a CRON expression. The execution strategy includes default execution according to the execution frequency or automatic execution once according to the execution frequency.

7. The alarm method based on interface dialing test according to claim 1, It is characterized in that The alarm information includes alarm time, alarm level, alarm content and related information. The alarm time includes the specific time when the alarm occurs. The alarm level includes severity level, warning level and prompt level. The alarm content includes a detailed description of the cause of the alarm, the interfaces involved and the triggering conditions. The related information includes the interface call log and server status.

8. The alarm method based on interface dialing test according to claim 1, It is characterized in that The alarm method includes SMS notification and system notification. The alarm alert includes displaying it on the system main page in the internal system through system notification. The system notification includes counting the alarm quantity and alarm content of each dialing test interface and dialing test task, and using the information provided by the alarm alert to correct the errors of the dialing test interface and dialing test task.

9. An alarm system based on interface dialing test, It is characterized in that It includes a backend part, a frontend part and a communication part. The communication part is used to realize communication between the backend part and the frontend part. The backend part includes a dialing test management module and an alarm module. The dialing test management module is used to configure dialing test cases, dialing test plans and dialing test tasks. The alarm module is used to configure the alarm trigger conditions of the interface error rate threshold and the alarm trigger conditions of the response time threshold. The frontend part includes a terminal device and an alarm information module. The terminal device responds to the alarm information module and receives the alarm information.

10. An alarm system based on interface dialing test according to claim 9, It is characterized in that The configuration of the dial test use case includes configuring the main application information and the sub-application information. The configuration of the dial test task includes configuring the task name, the main application name, the dial test plan, the client, the number of client execution threads, the task timeout, the task type, the execution frequency, the execution strategy and the task status. The task type includes one of PING, TCP, HTTP and DNS. The execution frequency is a CRON expression. The execution strategy includes default execution according to the execution frequency or automatic execution once according to the execution frequency. The alarm information module includes the alarm time, alarm level, alarm content and related information.

Images