CN115729777A - Monitoring and early warning method and device, electronic equipment and computer readable storage medium - Google Patents

Abstract

The application provides a monitoring and early warning method, a monitoring and early warning device, electronic equipment and a computer readable storage medium, which are used for monitoring and early warning a monitored object in a target system, wherein the method comprises the following steps: acquiring an early warning object identifier corresponding to the target system; acquiring an early warning condition corresponding to each monitoring object in the target system, wherein the monitoring object in the target system comprises at least one of an interface, a database and middleware; for each monitoring object, when the monitoring object meets the early warning condition corresponding to the monitoring object, generating early warning information and sending the early warning information to an early warning queue corresponding to the monitoring object; and consuming the early warning queue corresponding to the monitoring object so as to push the early warning information to the early warning object corresponding to the early warning object identifier. By configuring the early warning condition, the monitoring and early warning of each monitored object in the system can be realized without modifying codes.

Description

Monitoring and early warning method, device, electronic equipment, and computer-readable storage medium

technical field

The application relates to the technical field of system monitoring and early warning, logistics transportation, and in particular to a monitoring and early warning method and related devices.

Background technique

For various systems including the branch system, if there is an abnormality in the business function, the user of the function must report the problem to the developer, and the developer is passively informed of the abnormal situation. The status quo of this passive discovery of problems mainly has the following problems: ① Abnormal use of functions affects user experience; ② Developers cannot obtain real-time system operation status and resource usage, resulting in failure to find problems in time, and there is a lag in problem resolution; ③ Development It is difficult for personnel to check and locate problems, and the efficiency of solving problems is low, which affects business development.

For example, after the user finds that the function is abnormal, the problem will be reported to the developer. The developer will then troubleshoot, locate, and fix the problem according to the user's description. The feedback deviation and the timeliness of the feedback will also affect the problem repair effect, and the user experience is not good. On the other hand, some timing scripts execute in the background and cross-system call interfaces. Once a problem occurs, it is difficult to troubleshoot. In addition, there are server resources used by functions (such as Redis, My SQL, MQ), etc. Developers cannot grasp the usage of these resources in real time. When resources are occupied too much, functions may become unavailable, which has a great impact on business.

Based on this, the present application provides a monitoring and early warning method and related devices to improve the above-mentioned deficiencies in the prior art.

Contents of the invention

The purpose of this application is to provide a monitoring and early warning method and related devices. By configuring the early warning conditions, the monitoring and early warning of each monitoring object in the system can be realized without modifying the code.

The purpose of this application adopts following technical scheme to realize:

In the first aspect, the present application provides a monitoring and early warning method for monitoring and early warning of monitoring objects in the target system, the method comprising:

Obtain an early warning object identifier corresponding to the target system, where the early warning object identifier includes at least one of a digital account number, an email address, and a telephone number of the early warning object;

Obtaining an early warning condition corresponding to each monitoring object in the target system, where the monitoring object in the target system includes at least one of an interface, a database, and middleware;

For each of the monitored objects, when the monitored object satisfies its corresponding early warning condition, generate early warning information and send it to the corresponding early warning queue of the monitored object;

Consuming the warning queue corresponding to the monitoring object, so as to push the warning information to the warning object corresponding to the warning object identifier.

The beneficial effect of the technical solution is that by configuring the early warning conditions, the monitoring and early warning of each monitoring object in the system can be realized without modifying codes.

First, obtain the warning object identifier of the warning object corresponding to the target system that receives the warning information. Weibo account, Alipay account, etc.), email address, phone number, etc.; secondly, obtain the warning conditions corresponding to each monitoring object in the target system. There can be one or more monitoring objects in the target system, and these monitoring objects can be, for example, Interface, database, middleware, etc., each monitoring object has its corresponding early warning conditions. Generally speaking, the corresponding early warning conditions of different monitoring objects are different; after that, for each monitoring object, it is judged whether the monitoring object satisfies its own If the corresponding warning conditions are met, the warning information will be generated and sent to the warning queue corresponding to the monitoring object, that is, the corresponding warning queue is set for each monitoring object, and the warning queues corresponding to different monitoring objects are different; Then, consume the warning queue corresponding to each monitoring object, so as to push the warning information in the warning queue to the warning object (corresponding to the warning object identifier).

The advantage of this is that for the field of early warning notification, the system monitoring function and early warning information push function are realized by configuring early warning rules (ie early warning conditions) for monitoring objects such as interfaces, databases, and middleware. Developers can grasp the specific situation of interfaces and server resources (such as Redis, MySQL, MQ, etc.) used by functions in real time. When resources are occupied too much, they can promptly warn and troubleshoot and deal with them, reducing the impact of unavailable functions on business and ensuring business of normal operation. On the one hand, it can reduce the impact of abnormal function usage on user experience; on the other hand, developers can obtain real-time system operation status and resource usage, and find and solve problems in a timely manner; on the other hand, it is convenient for developers to troubleshoot and locate problems. The efficiency of problem solving is high, and the impact of system failure on business development is reduced.

In some optional implementation manners, the warning conditions corresponding to the interface include at least one of the following:

The number of request failures of the interface within the target time period is greater than a preset number of times threshold;

The ratio of the number of failed requests of the interface to the total number of requests within the target time period is greater than a preset ratio threshold.

The beneficial effect of this technical solution is that: the warning condition corresponding to the interface can be: the number of request failures within the target time period is greater than the preset number threshold (that is, the number of request failures is too many), and/or, the number of request failures within the target time period The ratio to the total number of requests is greater than the preset ratio threshold (that is, the proportion of request failures is too large). On the one hand, different time granularities such as 1 minute, 10 minutes, 30 minutes, and 1 hour can be used for the target time period, that is, different time granularities can be set according to the actual situation of the interface; on the other hand, according to the actual situation of the interface, Taking the number of request failures itself and/or the proportion of request failures as an early warning condition has a wide range of applications.

In some optional implementation manners, the process of obtaining the number of request failures and the total number of requests of the interface within the target time period includes:

In response to the configuration operation for the request success condition, determine the request success condition corresponding to the response parameter returned by the interface;

Use the log monitoring script to obtain the interface log data in the target time period from the log table corresponding to the target system, and the interface log data is used to indicate the response parameters returned by the interface corresponding to each request in the target time period ;

For each request, detect whether the response parameter returned by the interface corresponding to the request satisfies the request success condition; if so, add one to the number of successful requests of the interface within the target time period; if not, Add one to the number of request failures of the interface within the target time period;

The number of successful requests and the number of failed requests of the interface within the target time period are summed to obtain the total number of requests of the interface within the target time period.

The beneficial effect of this technical solution is: firstly configure the request success condition corresponding to the response parameter returned by the interface; secondly, use the log monitoring script to obtain the interface log data in the target time period from the log table; Request, check whether the response parameters returned by the interface corresponding to the request meet the configured request success conditions, if yes, add one to the number of successful requests, if not, add one to the number of failed requests; calculate the number of successful requests and the number of failed requests and get the total number of requests, from which you can get the number of request failures and the total number of requests for the interface within the target time period. The advantage of this is that the log monitoring script can be used to obtain the interface log data corresponding to the target system from the log table corresponding to the target system without modifying the code. The operation is simple, easy to implement, and the interface log data acquisition efficiency is high. Overall On the one hand, the monitoring efficiency and early warning efficiency are improved; on the other hand, the number of successful requests, the number of failed requests and the total number of requests are counted separately, and the statistical results are highly accurate. This interface early warning method is scientific and reasonable.

In some optional implementation manners, the use of log monitoring scripts to obtain interface log data within a target time period from a log table corresponding to the target system includes:

In a multi-process manner, using the log monitoring script to obtain the interface log data corresponding to each system in the target time period from log tables corresponding to multiple systems;

Wherein, the target system is one of multiple systems, and the durations of the target time periods corresponding to different systems are the same or different.

The beneficial effect of this technical solution is that: when multiple systems need monitoring and early warning, the same log monitoring script can be used to obtain the target time period corresponding to each system from the log table corresponding to each system in a multi-process manner Interface log data within the interface, the acquisition efficiency of interface log data is high; in addition, for different systems, the same or different target time periods can be set, that is to say, the duration of the target time periods corresponding to different systems can be the same or different, The start time and end time of the target time periods corresponding to different systems may also be the same or different. The advantage of this is that based on the actual situation of each system, different systems are monitored at the same or different time granularity, which can meet the performance requirements and cost requirements in practical applications. The multiple systems may include, for example, an outlet system, an order system, and a supply chain system in the field of logistics and transportation.

In some optional implementation manners, the warning conditions corresponding to the database include at least one of the following:

The query duration of the slow query in the database is greater than a preset duration threshold;

The number of threads in the database is greater than a preset number threshold.

The beneficial effect of this technical solution is: for the database, if the query time of the slow query is too long, it will greatly occupy the database resources. In addition, if the number of threads is too large, it will also greatly occupy the database resources. Therefore, for the database The configured early warning condition needs to take into account at least one of the query duration and the number of threads of the slow query. The advantage of this is that when the query time of the slow query is too long and/or the number of threads is too large, early warning information can be generated in time and pushed to the corresponding developer, so that the developer can check the actual situation of the database in a timely manner.

In some optional implementation manners, the warning conditions corresponding to the middleware include at least one of the following:

The queue length of the middleware is greater than the preset length threshold corresponding to the middleware.

The beneficial effect of the technical solution is: for each middleware, its corresponding preset length threshold is configured, and when the queue length of the middleware is greater than the corresponding preset length threshold, it indicates that the queue length of the middleware is too long. At this time, early warning information can be generated and pushed to developers, which is convenient for developers to check the actual situation of middleware in time and intervene in time to avoid slow or even stagnant consumption of middleware for a long period of time. In addition, the preset length thresholds corresponding to different middleware may be the same or different.

In some optional implementation manners, the middleware includes RabbitMQ middleware and/or Redis middleware.

The beneficial effect of this technical solution is that: the middleware applicable to the monitoring and early warning method in this application includes RabbitMQ middleware and/or Redis middleware. For RabbitMQ middleware and Redis middleware, the corresponding preset length thresholds can be the same or different. For example, the preset length thresholds corresponding to RabbitMQ middleware can be 3000, 5000, 8000, etc., and Redis middleware corresponds to The preset length threshold can be 90, 100, 110, etc.

In the second aspect, the present application provides a monitoring and early warning device for monitoring and early warning of monitoring objects in the target system, and the device includes:

An identification acquisition module, configured to acquire an early warning object identification corresponding to the target system, where the early warning object identification includes at least one of a digital account number, an email address and a telephone number of the early warning object;

A condition acquisition module, configured to acquire an early warning condition corresponding to each monitoring object in the target system, where the monitoring object in the target system includes at least one of an interface, a database, and a middleware;

A monitoring module, for each of the monitored objects, when the monitored object meets its own corresponding early warning conditions, generate early warning information and send it to the corresponding early warning queue of the monitored object;

The early warning module is configured to consume the early warning queue corresponding to the monitoring object, so as to push the early warning information to the early warning object corresponding to the early warning object identifier.

In some optional implementation manners, the warning conditions corresponding to the interface include at least one of the following:

The number of request failures of the interface within the target time period is greater than a preset number of times threshold;

The ratio of the number of failed requests of the interface to the total number of requests within the target time period is greater than a preset ratio threshold.

In some optional implementation manners, the process of obtaining the number of request failures and the total number of requests of the interface within the target time period includes:

In response to the configuration operation for the request success condition, determine the request success condition corresponding to the response parameter returned by the interface;

Use the log monitoring script to obtain the interface log data in the target time period from the log table corresponding to the target system, and the interface log data is used to indicate the response parameters returned by the interface corresponding to each request in the target time period ;

For each request, detect whether the response parameter returned by the interface corresponding to the request satisfies the request success condition; if so, add one to the number of successful requests of the interface within the target time period; if not, Add one to the number of request failures of the interface within the target time period;

The number of successful requests and the number of failed requests of the interface within the target time period are summed to obtain the total number of requests of the interface within the target time period.

In some optional implementation manners, the process of obtaining interface log data within a target time period includes:

In a multi-process manner, using the log monitoring script to obtain the interface log data corresponding to each system in the target time period from log tables corresponding to multiple systems;

Wherein, the target system is one of multiple systems, and the durations of the target time periods corresponding to different systems are the same or different.

In some optional implementation manners, the warning conditions corresponding to the database include at least one of the following:

The query duration of the slow query in the database is greater than a preset duration threshold;

The number of threads in the database is greater than a preset number threshold.

In some optional implementation manners, the warning conditions corresponding to the middleware include at least one of the following:

The queue length of the middleware is greater than the preset length threshold corresponding to the middleware.

In some optional implementation manners, the middleware includes RabbitMQ middleware and/or Redis middleware.

In a third aspect, the present application provides an electronic device, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of any one of the above methods when executing the computer program.

In a fourth aspect, the present application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of any one of the above-mentioned methods are implemented.

Description of drawings

The present application will be further described below in conjunction with the accompanying drawings and embodiments.

Fig. 1 shows a schematic flowchart of a monitoring and early warning method provided by an embodiment of the present application.

FIG. 2 shows a schematic flowchart of obtaining the number of request failures and the total number of requests provided by the embodiment of the present application.

Fig. 3 shows a schematic flowchart of another monitoring and early warning method provided by the embodiment of the present application.

Fig. 4 shows a schematic structural diagram of a monitoring and early warning device provided by an embodiment of the present application.

FIG. 5 shows a structural block diagram of an electronic device provided by an embodiment of the present application.

FIG. 6 shows a schematic structural diagram of a program product provided by an embodiment of the present application. .

Detailed ways

The following will describe the technical solutions in this application in conjunction with the description, drawings and specific implementation methods of the application. Any combination forms a new embodiment.

In this application, "at least one" means one or more, and "multiple" means two or more. "And/or" describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the contextual objects are an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one item (piece) of a, b or c can represent: a, b, c, a and b, a and c, b and c, a and b and c, wherein a, b and c can be It can be single or multiple. It should be noted that "at least one item (item)" can also be interpreted as "one item (item) or multiple items (item)".

It should also be noted that in this application, words such as "exemplary" or "for example" are used to represent examples, illustrations or illustrations. Any implementation or design described herein as "exemplary" or "for example" should not be construed as being preferred or advantageous over other implementations or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete manner.

method embodiment

Referring to FIG. 1 , FIG. 1 shows a schematic flowchart of a monitoring and early warning method provided by an embodiment of the present application.

The embodiment of the present application provides a monitoring and early warning method for monitoring and early warning of monitoring objects in the target system, the method comprising:

Step S101: Obtain the warning object identifier corresponding to the target system, and the warning object identifier includes at least one of the digital account number, email address and telephone number of the warning object;

Step S102: Obtain an early warning condition corresponding to each monitoring object in the target system, where the monitoring object in the target system includes at least one of an interface, a database, and a middleware;

Step S103: For each monitored object, when the monitored object meets its corresponding early warning condition, generate early warning information and send it to the corresponding early warning queue of the monitored object;

Step S104: Consume the warning queue corresponding to the monitoring object, so as to push the warning information to the warning object corresponding to the warning object identifier.

The embodiment of the present application does not limit the warning object, which may be, for example, an individual user or a group user of a developer.

The embodiment of the present application does not limit the digital account, which may include, for example, one or more of WeChat account, QQ account, DingTalk account, Weibo account and Alipay account.

The embodiment of the present application does not limit the target system, which may be, for example, an outlet system, an order system, a supply chain system, etc. in the field of logistics and transportation.

As an example, the target system is an outlet system, and the warning object identifier corresponding to the outlet system is the DingTalk group account (ie, the DingTalk group number) of the developer corresponding to the outlet system.

As another example, the target system is an order system, and the warning object identifier corresponding to the order system is the personal email address of the developer corresponding to the order system.

The embodiment of the present application does not limit the types of monitoring objects corresponding to the target system and the quantity of each type of monitoring objects. There may be one or more types of monitoring objects, and one or more types of monitoring objects may be used.

In the embodiment of the present application, the manner of obtaining the warning condition corresponding to each monitored object in the target system may be manual configuration or intelligent configuration. When manual configuration is adopted, for example, the target system and warning condition corresponding to each monitoring object can be manually configured to each option in the warning configuration menu corresponding to the monitoring object. When intelligent configuration is adopted, the default values of the system can be read to fill the options in the alarm configuration menu.

As an example, the target system is a network system. The monitoring objects in the network system include interfaces, databases, RabbitMQ middleware, and Redis middleware. At this time, the number of monitoring objects is 4, and each monitoring object has its corresponding warning. Queues, the number of early warning queues corresponding to the network point system is also four, namely the interface early warning queue, database early warning queue, RabbitMQ middleware early warning queue and Redis middleware early warning queue. For example, for Redis middleware, when the Redis middleware meets its own corresponding warning conditions, it generates warning information and sends it to the Redis middleware warning queue; consumes the Redis middleware warning queue, and pushes the warning information to the corresponding developer of the network point system. DingTalk group users.

Among them, the middleware refers to software used by different application programs to communicate with each other, and is software that provides general services and functions for applications. Data management, application serving, messaging, authentication, and API management often go through middleware.

In the embodiment of the present application, the way of pushing the early warning information is, for example, SMS push, email push, in-app push, phone notification, etc., and the application is, for example, DingTalk APP, Enterprise WeChat APP, applet, etc.

Therefore, by configuring the early warning conditions, the monitoring and early warning of each monitoring object in the system can be realized without modifying the code.

First, obtain the warning object identifier of the warning object corresponding to the target system that receives the warning information. Weibo account, Alipay account, etc.), email address, phone number, etc.; secondly, obtain the warning conditions corresponding to each monitoring object in the target system. There can be one or more monitoring objects in the target system, and these monitoring objects can be, for example, Interface, database, middleware, etc., each monitoring object has its corresponding early warning conditions. Generally speaking, the corresponding early warning conditions of different monitoring objects are different; after that, for each monitoring object, it is judged whether the monitoring object satisfies its own If the corresponding warning conditions are met, the warning information will be generated and sent to the warning queue corresponding to the monitoring object, that is, the corresponding warning queue is set for each monitoring object, and the warning queues corresponding to different monitoring objects are different; Then, consume the warning queue corresponding to each monitoring object, so as to push the warning information in the warning queue to the warning object (corresponding to the warning object identifier).

The advantage of this is that for the field of early warning notification, the system monitoring function and early warning information push function are realized by configuring early warning rules (ie early warning conditions) for monitoring objects such as interfaces, databases, and middleware. Developers can grasp the specific situation of interfaces and server resources (such as Redis, MySQL, MQ, etc.) used by functions in real time. When resources are occupied too much, they can promptly warn and troubleshoot and deal with them, reducing the impact of unavailable functions on business and ensuring business of normal operation. On the one hand, it can reduce the impact of abnormal function usage on user experience; on the other hand, developers can obtain real-time system operation status and resource usage, and find and solve problems in a timely manner; on the other hand, it is convenient for developers to troubleshoot and locate problems. The efficiency of problem solving is high, and the impact of system failure on business development is reduced.

MySQL is a relational database management system that is widely used.

MQ (Message Queue) message queue is a "first in, first out" data structure in the basic data structure. It is generally used to solve problems such as application decoupling, asynchronous messages, and traffic peak clipping to achieve high performance, high availability, and scalability. and eventually consistent architecture.

In some optional implementation manners, the warning conditions corresponding to the interface include at least one of the following:

The number of request failures of the interface within the target time period is greater than a preset number of times threshold;

The ratio of the number of failed requests of the interface to the total number of requests within the target time period is greater than a preset ratio threshold.

Therefore, the early warning condition corresponding to the interface may be: the number of request failures within the target time period is greater than the preset number of thresholds (that is, the number of request failures is too many), and/or, the number of request failures and the total number of requests within the target time period The ratio is greater than the preset ratio threshold (that is, the proportion of request failures is too large). On the one hand, different time granularities such as 1 minute, 10 minutes, 30 minutes, and 1 hour can be used for the target time period, that is, different time granularities can be set according to the actual situation of the interface; on the other hand, according to the actual situation of the interface, Taking the number of request failures itself and/or the proportion of request failures as an early warning condition has a wide range of applications.

Wherein, based on different times, time granularity may be regarded as time lengths of different time units. The unit of time is the basic unit used to measure time, arranged from large to small are millennium, century, year, year, quarter, month, ten days, week, day, hour, hour, engraving, character (used in Fujian and Guangdong), Minutes, seconds, milliseconds (ms), microseconds (μs), nanoseconds (ns), picoseconds (ps), femtoseconds (fs), attoseconds (as), zetoseconds (zs). In practical applications, the time granularity may be every 30 seconds, every 1 minute, every 5 minutes, every 1 hour, every 1 week, every 1 month, every 1 quarter, every 1 year, etc.

The embodiment of the present application does not limit the length of the target time period, which can be, for example, 10 seconds, 15 seconds, 30 seconds, 1 minute, 5 minutes, 10 minutes, 30 minutes, 1 hour, 1 week, 1 month, 1 quarter, 1 year, etc.

As an example, the time granularity of the target time period is 1 minute, and the preset number of times threshold is 10 times. If the number of request failures of the interface within 1 minute is 11, it is determined that the interface satisfies its corresponding warning condition.

As another example, the time granularity of the target time period is 5 minutes, and the preset ratio threshold is 10%. If the interface has 11 failed requests and 89 successful requests within 5 minutes, the total number of requests is 100. times, the ratio of the number of request failures to the total number of requests is 11%, and it is judged that the interface meets its own corresponding warning conditions.

Referring to FIG. 2 , FIG. 2 shows a schematic flowchart of obtaining the number of request failures and the total number of requests provided by the embodiment of the present application.

In some optional implementation manners, the process of obtaining the number of request failures and the total number of requests of the interface within the target time period includes:

Step S201: In response to the configuration operation for the request success condition, determine the request success condition corresponding to the response parameter returned by the interface;

Step S202: Use the log monitoring script to obtain the interface log data within the target time period from the log table corresponding to the target system, and the interface log data is used to indicate that the interface returns corresponding to each request within the target time period The response parameter;

Step S203: For each request, detect whether the response parameter returned by the interface corresponding to the request satisfies the request success condition; if so, add one to the number of successful requests of the interface within the target time period; if If it is not satisfied, add one to the number of request failures of the interface within the target time period;

Step S204: Summing the number of successful requests and the number of failed requests of the interface within the target time period to obtain the total number of requests of the interface within the target time period.

In this embodiment of the application, the number of response parameters returned by the interface may be one or more.

As an example, the response parameters returned by the interface are "is_success" and "response_code", and the request success condition is that "is_success" is "1" and "response_code" is "0000". The format of the request success condition can be expressed as {"is_success":"1","condition":"and","response_code":"0000"}, for example. When the response parameter returned by the interface corresponding to a request is {"is_success": "1","response_code":"0000"}, it is judged that the response parameter returned by the interface corresponding to the request satisfies the request success condition; when a request corresponds to When the response parameter returned by the interface is {"is_success":"0","response_code":"0000"}, it is judged that the response parameter returned by the interface corresponding to the request does not meet the request success condition.

As another example, the response parameter returned by the interface is "is_success", and the request success condition is that "is_success" is "1". The format of the request success condition can be represented as {"is_success":"1"}, for example. When the response parameter returned by the interface corresponding to a request is {"is_success": "1"}, it is judged that the response parameter returned by the interface corresponding to the request meets the request success condition.

As yet another example, the response parameters returned by the interface are "is_success" and "response_code", and the request success condition is that "is_success" is "1" or "response_code" is "0000". The format of the request success condition can be expressed as {"is_success":"1","condition":"or","response_code":"0000"}, for example. When the response parameter returned by the interface corresponding to a request is {"is_success":"0","response_code":"0000"}, it is judged that the response parameter returned by the interface corresponding to the request meets the request success condition.

Therefore, first configure the request success conditions corresponding to the response parameters returned by the interface; secondly, use the log monitoring script to obtain the interface log data within the target time period from the log table; then, for each request in the interface log data, detect the corresponding Whether the response parameters returned by the interface meet the configured request success conditions, if yes, add one to the number of request successes, and if not, add one to the number of request failures; sum the number of successful requests and the number of failed requests to get the total number of requests , so that the number of request failures and the total number of requests of the interface within the target time period can be obtained. The advantage of this is that the log monitoring script can be used to obtain the interface log data corresponding to the target system from the log table corresponding to the target system without modifying the code. The operation is simple, easy to implement, and the interface log data acquisition efficiency is high. Overall On the one hand, the monitoring efficiency and early warning efficiency are improved; on the other hand, the number of successful requests, the number of failed requests and the total number of requests are counted separately, and the statistical results are highly accurate. This interface early warning method is scientific and reasonable.

In some optional implementation manners, the use of the log monitoring script to obtain the interface log data within the target time period from the log table corresponding to the target system (that is, step S202), includes:

In a multi-process manner, using the log monitoring script to obtain the interface log data corresponding to each system in the target time period from log tables corresponding to multiple systems;

Wherein, the target system is one of multiple systems, and the durations of the target time periods corresponding to different systems are the same or different.

In the embodiment of the present application, the multiple systems may include, for example, an outlet system, an order system, and a supply chain system in the field of logistics and transportation. As an example, the target time period corresponding to the outlet system is 1 minute, the target time period corresponding to the order system is 30 seconds, and the target time period corresponding to the supply chain system is 5 minutes.

Therefore, when multiple systems need monitoring and early warning, the same log monitoring script can be used to obtain the interface log data corresponding to each system in the target time period from the log table corresponding to each system in a multi-process manner , the interface log data acquisition efficiency is high; in addition, for different systems, the same or different target time periods can be set, that is to say, the target time periods corresponding to different systems can be the same or different, and the corresponding The start time and end time of the target time period may also be the same or different. The advantage of this is that based on the actual situation of each system, different systems are monitored at the same or different time granularity, which can meet the performance requirements and cost requirements in practical applications.

Among them, a process is the encapsulation of the runtime program, and it is the basic unit for resource scheduling and allocation of the system, which realizes the concurrency of the operating system; a thread is a subtask of the process, and is the basic unit of CPU scheduling and dispatching, which is used to ensure the operation of the program. Real-time, realizing concurrency within the process; thread is the smallest execution and scheduling unit recognizable by the operating system. Each thread has its own virtual processor: its own register set, instruction counter, and processor state. The central processing unit (CPU for short) is the computing and control core of the computer system and the final execution unit for information processing and program operation.

In some optional implementation manners, the process of obtaining the duration of the target time period corresponding to each system includes:

In response to the configuration operation for the duration of the target time period of the system, the duration of the target time period corresponding to the system is determined.

In some other optional implementation manners, the process of obtaining the duration of the target time period corresponding to each system includes:

The fault data of the system is input into the duration configuration model to obtain the duration of the target time period corresponding to the system, and the fault data of the system includes fault sequence number, fault type and fault start time.

The fault sequence number can be represented by one or more of Chinese characters, letters, numbers, and symbols, the fault type can be represented by one or more of Chinese characters, letters, numbers, and symbols, and the fault start time can be represented by, for example, Beijing time, Greenwich mean time or timestamp.

The fault types may include, for example, interface response faults, database slow query faults, database process faults, RabbitMQ middleware faults, Redis middleware faults, and the like.

Wherein, the training process of the duration configuration model may include, for example:

Obtain a training set, the training set includes a plurality of training data, each of the training data includes the fault data of a sample system and the label data of the duration of the target time period corresponding to the sample system, and the fault data of the sample system Including fault sequence number, fault type and fault start time;

For each training data in the training set, perform the following processing:

Inputting the fault data of the sample system in the training data into a preset deep learning model to obtain the prediction data of the duration of the target time period corresponding to the sample system;

updating the model parameters of the deep learning model based on the prediction data and labeling data of the duration of the target time period corresponding to the sample system;

Detect whether the preset training end condition is met; if yes, use the trained deep learning model as the duration configuration model; if not, use the next training data to continue training the deep learning model.

Therefore, by designing and establishing an appropriate amount of neuron computing nodes and a multi-layer computing hierarchy, and selecting an appropriate input layer and output layer, a preset deep learning model can be obtained. Through the learning and tuning of the deep learning model, the establishment of Starting from the functional relationship from input to output, although the functional relationship between input and output cannot be found 100%, it can approach the actual correlation as much as possible. The time configuration model obtained from this training can obtain the corresponding output data based on the input data , with a wide range of applications, and the calculation results are highly accurate and reliable.

Using the fault data of the sample system to train the deep learning model can quickly model by learning a small number of samples. The training error of the deep learning model will gradually decrease during the continuous training process, and the deep learning model can save the optimal weight. , and read the weights; record the accuracy of the training set and verification set, which is convenient for parameter adjustment (adjusting model parameters); updating the model parameters of the deep learning model can make the model better fit the data and have effective generalization Ability to improve robustness and fitting accuracy.

In some optional implementation manners, the embodiment of the present application may train a duration configuration model, and in other optional implementation manners, the present application may use a pre-trained duration configuration model.

In some optional implementation manners, data mining may be performed on the historical data to obtain fault data of the sample systems in the training set. That is to say, the fault data of these sample systems can be obtained by collecting real systems. In addition, the fault data of the sample system can also be automatically generated using the generative network of the GAN model.

Among them, the GAN model is the Generative Adversarial Network, which consists of a generation network and a discriminant network. The generator network randomly samples from the latent space as input, and its output needs to imitate the real samples in the training set as much as possible. The input of the discriminative network is the real sample or the output of the generation network, and its purpose is to distinguish the output of the generation network from the real sample as much as possible. The generative network should deceive the discriminative network as much as possible. The two networks fight against each other and constantly adjust the parameters. The ultimate goal is to make the discriminative network unable to judge whether the output of the generating network is true or not. The fault data of multiple sample systems can be generated by using the GAN model, which is used in the training process of the time-length configuration model, which can effectively reduce the amount of data collected by the original data, and greatly reduce the cost of data collection and labeling.

The embodiment of the present application does not limit the manner of obtaining the labeling data, for example, manual labeling, automatic labeling or semi-automatic labeling may be used. When the fault data of the sample system is collected from the real system, the real data can be obtained from the historical data as labeled data by means of keyword extraction.

The embodiment of the present application does not limit the training process of the duration configuration model. For example, the above-mentioned supervised learning training method, semi-supervised learning training method, or unsupervised learning training method may be used.

The embodiment of the present application does not limit the preset training end condition, which can be, for example, that the number of training times reaches the preset number of times (the preset number of times is, for example, 1 time, 3 times, 10 times, 100 times, 1000 times, 10000 times, etc.), Or it may be that all the training data in the training set have completed one or more trainings, or it may be that the total loss value obtained in this training is not greater than the preset loss value.

In some optional implementation manners, the warning conditions corresponding to the database include at least one of the following:

The query duration of the slow query in the database is greater than a preset duration threshold;

The number of threads in the database is greater than a preset number threshold.

Slow query refers to the SQL in the database whose query time exceeds the specified time threshold (for example, it can be set to 100 milliseconds, 1 second, 10 seconds, etc.). Slow query is the performance killer of the database and an important starting point for business optimization database access. With the rapid growth of the logistics and transportation business, the order of magnitude of the average daily slow query volume can reach hundreds of thousands, millions or even billions, and the faults caused by slow queries account for more than 10% of the total database faults, and high-level faults There is an increasing trend. Therefore, optimization of slow queries has become urgent. Among them, SQL is a special-purpose programming language used to manage relational database management systems, or stream processing in relational stream data management systems. SQL is based on relational algebra and tuple relational calculus, including a data definition language and a data manipulation language. The scope of SQL includes data insertion, query, update, and deletion, database schema creation and modification, and data access control.

The embodiment of the present application does not limit the preset duration threshold, which may be, for example, 100 milliseconds, 1 second, 10 seconds, 15 seconds, 20 seconds, or 30 seconds.

This embodiment of the present application does not limit the preset quantity threshold, which may be, for example, 10, 20, 30, 50, 80, 100, 110, 120, 150, 200, 500, 1000, and so on.

Therefore, for the database, if the query time of the slow query is too long, it will greatly occupy the database resources. In addition, if the number of threads is too large, it will also greatly occupy the database resources. Therefore, the early warning conditions configured for the database At least one of the query duration and the number of threads of the slow query needs to be considered. The advantage of this is that when the query time of the slow query is too long and/or the number of threads is too large, early warning information can be generated in time and pushed to the corresponding developer, so that the developer can check the actual situation of the database in a timely manner.

In some optional implementation manners, the warning conditions corresponding to the middleware include at least one of the following:

The queue length of the middleware is greater than the preset length threshold corresponding to the middleware.

In this embodiment of the application, the queue length of the middleware is the number of messages in the queue.

Therefore, for each middleware, its corresponding preset length threshold is configured. When the queue length of the middleware is greater than its corresponding preset length threshold, it indicates that the queue length of the middleware is too long. At this time, you can Generate early warning information to push to developers, so that developers can check the actual situation of middleware in time, intervene in time, and avoid slow consumption or even stagnant consumption of middleware for a long period of time. In addition, the preset length thresholds corresponding to different middleware may be the same or different.

The embodiment of the present application does not limit the preset length threshold, which can be, for example, 10, 20, 30, 50, 80, 90, 100, 110, 120, 150, 200, 300, 500, 800, 1000, 2000, 3000, 5000, 8000, 10000, 30000, 50000, 100000, 1000000, etc.

In some optional implementation manners, the middleware includes RabbitMQ middleware and/or Redis middleware.

Therefore, the middleware applicable to the monitoring and early warning method in this application includes RabbitMQ middleware and/or Redis middleware.

For RabbitMQ middleware and Redis middleware, the corresponding preset length thresholds can be the same or different. For example, the preset length thresholds corresponding to RabbitMQ middleware can be 3000, 5000, 8000, etc., and Redis middleware corresponds to The preset length threshold can be 90, 100, 110, etc.

RabbitMQ is an open source message broker software (also known as message-oriented middleware) that implements the Advanced Message Queuing Protocol (AMQP). The RabbitMQ server is written in the Erlang language, while the clustering and failover are built on the Open Telecom Platform framework, and all major programming languages have client libraries for communicating with the broker interface.

Redis is an open source in-memory data structure storage system that can be used as a database, cache, and message middleware. Redis is the remote dictionary service. It is an open source written in ANSI C language, supports the network, can be based on memory and can be persistent log, "Key-Value" database, and provides APIs in multiple languages; Redis will periodically Write updated data to disk or write modification operations to appended log files.

The embodiment of the present application does not limit the manner of receiving various manual operations (or user operations). Operations are divided according to input methods, for example, text input operations, audio input operations, video input operations, key operations, button operations, knob operations, mouse operations, keyboard operations, smart stylus operations, smart touchpad operations, etc. can be included. These operations include but are not limited to configuration operations for request success conditions, configuration operations for the duration of the target time period of the system, and the like.

Wherein, the configuration operation may be, for example, clicking the "configuration" control in the monitoring and early warning software. In computer programming, a control (or component, widget or control) is a graphical user interface element whose arrangement of displayed information can be changed by the user, such as a window or a text box. A control definition is characterized by providing a single point of interaction for direct manipulation of given data. A control is a basic visual building block contained in an application program that controls all data that the program processes and interacts with that data.

Referring to FIG. 3 , FIG. 3 shows a schematic flowchart of another monitoring and early warning method provided by an embodiment of the present application.

In a specific application scenario, an embodiment of the present application provides a monitoring and early warning method, including the following steps 1 to 6.

Step 1: Create a DingTalk group and associate it with the target system.

Step 2: Select the target system, configure the database, middleware and corresponding log table name corresponding to the target system.

Step 3: Configure alert rules.

① Configure interface warning rules. Specifically, configure the target system in the interface log warning configuration menu, add an interface corresponding to the target system, configure the interface name, interface value, warning time threshold (minutes), warning threshold (number of times), request success conditions, responsible person, etc. Information, the request success condition defaults to is_success=1 and response_code=0000 in the response parameter. If the interface request success condition is not is_success=1 and response_code=0000, the request success condition can be configured manually. The format is: ({ "is_success":"1","condition":"or","response_code":"0000"}), the connector uses and or or. Unconfigured fields can be left blank or filled with default values.

② Configure database warning rules. Specifically, configure the database connection configuration information (that is, the target system corresponding to the configuration database) and parameters such as the maximum number of seconds for slow queries, the maximum number of threads, and the person in charge in the database warning configuration menu.

③ Configure RabbitMQ middleware warning rules. Specifically, configure the MQ connection configuration information in the RabbitMQ early warning configuration menu (that is, configure the target system corresponding to the RabbitMQ middleware), and configure the queue name, queue, switch, and queue message quantity warning threshold on the newly created MQ connection information.

④ Configure Redis middleware warning rules. Specifically, configure the Redis connection configuration information in the Redis warning configuration menu (that is, configure the target system corresponding to the Redis middleware), and configure the queue and queue message quantity warning threshold on the newly created MQ connection information.

Step Four: Monitoring.

①Interface log monitoring. Specifically, the log monitoring script uses a multi-process method to obtain interface log data from the log tables corresponding to multiple systems, and counts the total number of interface requests, The number of successful requests and the number of failed requests; and after the statistics, the interface with the monitoring switch in the system with the monitoring switch turned on will push the warning information generated by triggering the warning threshold to the corresponding interface according to the warning conditions corresponding to the interface. An early warning queue, for example, the early warning queue may be a Redis queue. It should be noted that the interfaces of multiple systems can use the same warning queue or different warning queues.

②Database monitoring. Specifically, for the database (service) whose monitoring switch is turned on in the system where the monitoring switch is turned on, use the show full processlist command to query the slow query SQL and the number of threads in the database. When the number of threads reaches the warning threshold, corresponding warning information is generated, and the warning information is pushed to the warning queue corresponding to the database. The warning queue may be, for example, a Redis queue. It should be noted that the databases of multiple systems can use the same early warning queue or different early warning queues.

③RabbitMQ middleware monitoring. Specifically, for the RabbitMQ middleware (service) with the monitoring switch turned on in the system where the monitoring switch is turned on, by querying the number of messages in the queue, corresponding warning information is generated when the warning threshold is reached, and the warning information is pushed to the RabbitMQ The early warning queue corresponding to the middleware, for example, the early warning queue can be a Redis queue. It should be noted that the RabbitMQ middleware of multiple systems can use the same alert queue or different alert queues.

④Redis middleware monitoring. Specifically, for the Redis middleware (service) with the monitoring switch turned on in the system where the monitoring switch is turned on, by querying the number of messages in the queue, corresponding warning information is generated for the situation that reaches the warning threshold, and the warning information is pushed to the Redis The early warning queue corresponding to the middleware, for example, the early warning queue can be a Redis queue. It should be noted that the Redis middleware of multiple systems can use the same alert queue or different alert queues.

Step five: early warning.

Consume the data in the early warning queue corresponding to the interface, database, and middleware, and asynchronously send early warning messages to the corresponding developer group users.

Step 6: Auxiliary query.

In the interface log menu, query the log of interface request exception (or error log), and other databases and middleware can view the corresponding server resource information, which is convenient for developers to analyze specific problems.

As an example, the monitoring and early warning method is implemented by monitoring and early warning software. The monitoring and early warning software is provided with DingTalk early warning configuration menu, interface log early warning configuration menu, database early warning configuration menu, Rab bitMQ early warning configuration menu, Redis early warning configuration menu and interface Log menu, the monitoring and early warning method includes the following Step1 to Step6.

Step1: Create a DingTalk alert group corresponding to the outlet system, and configure the outlet system in the DingTalk alert configuration menu.

Step2: Configure the connection information of the network point system log library (database name is test, for example) in the database early warning configuration menu; configure the log table t_log connection information corresponding to the network point system in the interface log early warning configuration menu.

Step3: ①Configuration of interface warning rules: Select the outlet system in the interface log warning configuration menu, add the interface name "test interface", the interface value is TEST_INTERFACE, and the request success condition is: {"is_success":"1","condition": "or","response_code":"0000"}, the warning threshold is 10 times, and the warning time threshold is 1 minute (that is, if 10 requests fail within 1 minute, the warning will be triggered).

②Configuration of database early warning rules: In the database early warning configuration menu, configure the maximum number of seconds for the database slow query of the network point system to be 10, and the maximum number of threads to be 110.

③ RabbitMQ middleware early warning rule configuration: Configure the MQ connection configuration information of the network point system in the RabbitMQ early warning configuration menu and add a logistics data queue for the network point system. The EXCHANGE (switch) corresponding to the logistics data queue is test_exchange, and the QUEUE (queue) is test_queue ( This queue is used to store the logistics data of the outlet system), and the preset length threshold for triggering an alert is 5000.

④ Redis middleware early warning rule configuration: configure the Redis connection configuration information of the network point system in the Redis early warning configuration menu and add a Redis queue (named such as test_list) for the network point system. The preset length threshold for triggering the warning is 100.

Step4: ①Interface monitoring: Manually change the interface name in the log monitoring script to TEST_INTE RFACE, and set the request success condition to {"is_success":"1","condition":"or","response_code":"0000" }, if the request fails 10 times within 1 minute, an alert will be triggered.

②Database monitoring: monitor the network system database, if the maximum number of threads reaches 110, an early warning will be triggered, and if the SQL execution time (that is, the query time) reaches 10 seconds, an early warning will be triggered.

③MQ middleware monitoring: monitor the logistics data queue test_queue of the outlet system, and trigger an early warning when the amount of data accumulated in the queue reaches 5,000.

④Redis middleware monitoring: monitor the test_list queue of the network system, and trigger the early warning rule when the queue length reaches 100.

Step5: Consume the early warning information data in the early warning queues of interfaces, databases, middleware, etc., and asynchronously send the early warning information to the DingTalk early warning group corresponding to the outlet system.

The warning information is as follows:

【Network system warning】

Request interface address: http://10.172.242.66/index.php/test/interface

Interface name: test interface

Interface: TEST_INTERFACE

Statistical period: 2022-09-20 11:37:00 to 2022-09-20 11:37:59

Statistics time: 1 minute

Cumulative errors: 34 times Responsible person: Please deal with it in time! ! !

Step6: In the interface log menu, query the interface log data of interface request exceptions. For example, for the interface log data corresponding to the above warning message, the query steps are, for example: select an outlet system, the query start time is 2022-09-2011:37:00, the end time is 2022-09-20 11:37:59, the interface name For TES T_INTERFACE, the request status is Failed interface log data.

Device embodiment

Referring to FIG. 4 , FIG. 4 shows a schematic structural diagram of a monitoring and early warning device provided by an embodiment of the present application.

The embodiment of the present application provides a monitoring and early warning device, and its specific implementation mode is consistent with the implementation mode and the achieved technical effect described in the above-mentioned method embodiment, and part of the content will not be repeated.

The monitoring and early warning device is used to monitor and warn the monitoring objects in the target system, and the device includes:

An identification acquisition module 101, configured to acquire an early warning object identification corresponding to the target system, the early warning object identification including at least one of the digital account number, email address and telephone number of the early warning object;

A condition acquisition module 102, configured to acquire an early warning condition corresponding to each monitored object in the target system, where the monitored object in the target system includes at least one of an interface, a database, and middleware;

The monitoring module 103 is configured to, for each of the monitored objects, generate early warning information and send it to the corresponding early warning queue of the monitored object when the monitored object meets its corresponding early warning conditions;

The early warning module 104 is configured to consume the early warning queue corresponding to the monitored object, so as to push the early warning information to the early warning object corresponding to the early warning object identifier.

In some optional implementation manners, the warning conditions corresponding to the interface include at least one of the following:

The number of request failures of the interface within the target time period is greater than a preset number of times threshold;

The ratio of the number of failed requests of the interface to the total number of requests within the target time period is greater than a preset ratio threshold.

In some optional implementation manners, the process of obtaining the number of request failures and the total number of requests of the interface within the target time period includes:

In response to the configuration operation for the request success condition, determine the request success condition corresponding to the response parameter returned by the interface;

Use the log monitoring script to obtain the interface log data in the target time period from the log table corresponding to the target system, and the interface log data is used to indicate the response parameters returned by the interface corresponding to each request in the target time period ;

For each request, detect whether the response parameter returned by the interface corresponding to the request satisfies the request success condition; if so, add one to the number of successful requests of the interface within the target time period; if not, Add one to the number of request failures of the interface within the target time period;

The number of successful requests and the number of failed requests of the interface within the target time period are summed to obtain the total number of requests of the interface within the target time period.

In some optional implementation manners, the process of obtaining interface log data within a target time period includes:

In a multi-process manner, using the log monitoring script to obtain the interface log data corresponding to each system in the target time period from log tables corresponding to multiple systems;

Wherein, the target system is one of multiple systems, and the durations of the target time periods corresponding to different systems are the same or different.

In some optional implementation manners, the warning conditions corresponding to the database include at least one of the following:

The query duration of the slow query in the database is greater than a preset duration threshold;

The number of threads in the database is greater than a preset number threshold.

In some optional implementation manners, the warning conditions corresponding to the middleware include at least one of the following:

The queue length of the middleware is greater than the preset length threshold corresponding to the middleware.

In some optional implementation manners, the middleware includes RabbitMQ middleware and/or Redis middleware.

device embodiment

The embodiment of the present application also provides an electronic device, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of any one of the above methods when executing the computer program, wherein The specific implementation mode is consistent with the implementation mode and the achieved technical effect described in the above-mentioned method embodiments, and part of the content will not be repeated.

Referring to FIG. 5 , FIG. 5 shows a structural block diagram of an electronic device 200 provided by an embodiment of the present application.

The electronic device 200 may include, for example, at least one memory 210, at least one processor 220, and a bus 230 connecting different platform systems.

Memory 210 may include readable media in the form of volatile memory, such as random access memory (RAM) 211 and/or cache memory 212 , and may further include read only memory (ROM) 213 .

Wherein, the memory 210 also stores a computer program, and the computer program can be executed by the processor 220, so that the processor 220 implements the steps of any one of the above-mentioned methods.

Memory 210 may also include utility 214 having at least one program module 215 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some of these examples Implementations of network environments may be included in this combination.

Correspondingly, the processor 220 can execute the above-mentioned computer program, and can execute the utility tool 214 .

The processor 220 can adopt one or more application-specific integrated circuits (ASIC, Application Specific Integrated Circuit), DSP, programmable logic device (PLD, Programmable Logic Device), complex programmable logic device (CPLD, Complex Programmable Logic Device), field Programmable gate array (FPGA, Field-Programmable Gate Array) or other electronic components.

Bus 230 may be a local bus representing one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or any bus structure using a variety of bus structures.

The electronic device 200 can also communicate with one or more external devices 240 such as keyboards, pointing devices, Bluetooth devices, etc., and can also communicate with one or more devices capable of interacting with the electronic device 200, and/or communicate with the electronic device 200 200 is capable of communicating with any device (eg, router, modem, etc.) that communicates with one or more other computing devices. Such communication may occur through input-output interface 250 . Moreover, the electronic device 200 can also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN) and/or a public network such as the Internet) through the network adapter 260 . The network adapter 260 can communicate with other modules of the electronic device 200 through the bus 230 . It should be appreciated that although not shown, other hardware and/or software modules may be used in conjunction with electronic device 200, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives And data backup storage platform, etc.

Media Example

The embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of any one of the above-mentioned methods are implemented, and its specific implementation method is the same as The implementation manners and achieved technical effects described in the above-mentioned method embodiments are consistent, and part of the content will not be repeated here.

Referring to FIG. 6 , FIG. 6 shows a schematic structural diagram of a program product provided by an embodiment of the present application.

The program product is used to implement any one of the above methods. The program product may take the form of a portable compact disc read-only memory (CD-ROM) and include program code, and be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto. In the embodiments of the present application, the readable storage medium may be any tangible medium containing or storing a program, and the program may be used by or in combination with an instruction execution system, device or device. A program product may take the form of any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: electrical connection with one or more conductors, portable disk, hard disk, random access memory (RAM), read only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

A computer readable storage medium may include a data signal carrying readable program code in baseband or as part of a carrier wave traveling as part of a data signal. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A readable storage medium may also be any readable medium that can transmit, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the readable storage medium can be transmitted by any appropriate medium, including but not limited to wireless, cable, optical cable, RF, etc., or any suitable combination of the above. The program codes for performing the operations of the present invention can be written in any combination of one or more programming languages, and the programming languages include object-oriented programming languages such as Java, C++, etc., and also include conventional procedural programming languages A programming language such as C or similar. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server to execute. In cases involving a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., using an Internet service provider). business to connect via the Internet).

This application is elaborated from the perspectives of purpose of use, performance, progress and novelty, etc., and has met the function enhancement and use requirements emphasized by the Patent Law. The above description and drawings of this application are only the preferred implementation of this application. It is just an example, and this application is not limited thereto. Therefore, all the structures, devices, features, etc. that are similar to or identical to those of this application, that is, all equivalent replacements or modifications made according to the patent application scope of this application, shall belong to this application. within the scope of patent application protection.

Claims (10)

1. A method for monitoring and early warning, characterized in that, for monitoring and early warning of the monitoring object in the target system, the method comprises: Obtain an early warning object identifier corresponding to the target system, where the early warning object identifier includes at least one of a digital account number, an email address, and a telephone number of the early warning object; Obtaining an early warning condition corresponding to each monitoring object in the target system, where the monitoring object in the target system includes at least one of an interface, a database, and middleware; For each of the monitored objects, when the monitored object satisfies its corresponding early warning condition, generate early warning information and send it to the corresponding early warning queue of the monitored object; Consuming the warning queue corresponding to the monitoring object, so as to push the warning information to the warning object corresponding to the warning object identifier. 2. The monitoring and early warning method according to claim 1, wherein the early warning conditions corresponding to the interface include at least one of the following: The number of request failures of the interface within the target time period is greater than a preset number of times threshold; The ratio of the number of failed requests of the interface to the total number of requests within the target time period is greater than a preset ratio threshold. 3. The monitoring and early warning method according to claim 2, wherein the process of obtaining the number of request failures and the total number of requests of the interface within the target time period comprises: In response to the configuration operation for the request success condition, determine the request success condition corresponding to the response parameter returned by the interface; Use the log monitoring script to obtain the interface log data in the target time period from the log table corresponding to the target system, and the interface log data is used to indicate the response parameters returned by the interface corresponding to each request in the target time period ; For each request, detect whether the response parameter returned by the interface corresponding to the request satisfies the request success condition; if so, add one to the number of successful requests of the interface within the target time period; if not, Add one to the number of request failures of the interface within the target time period; The number of successful requests and the number of failed requests of the interface within the target time period are summed to obtain the total number of requests of the interface within the target time period. 4. The monitoring and early warning method according to claim 3, wherein said utilizing the log monitoring script to obtain the interface log data in the target time period from the log table corresponding to the target system includes: In a multi-process manner, using the log monitoring script to obtain the interface log data corresponding to each system in the target time period from log tables corresponding to multiple systems; Wherein, the target system is one of multiple systems, and the durations of the target time periods corresponding to different systems are the same or different. 5. The monitoring and early warning method according to claim 1, wherein the early warning conditions corresponding to the database include at least one of the following: The query duration of the slow query in the database is greater than a preset duration threshold; The number of threads in the database is greater than a preset number threshold. 6. The monitoring and early warning method according to claim 1, wherein the early warning conditions corresponding to the middleware include at least one of the following: The queue length of the middleware is greater than the preset length threshold corresponding to the middleware. 7. The monitoring and early warning method according to claim 6, wherein said middleware comprises RabbitMQ middleware and/or Redis middleware. 8. A monitoring and early warning device, characterized in that it is used for monitoring and early warning of the monitoring object in the target system, and the device includes: An identification acquisition module, configured to acquire an early warning object identification corresponding to the target system, where the early warning object identification includes at least one of a digital account number, an email address and a telephone number of the early warning object; A condition acquisition module, configured to acquire an early warning condition corresponding to each monitoring object in the target system, where the monitoring object in the target system includes at least one of an interface, a database, and a middleware; A monitoring module, for each of the monitored objects, when the monitored object meets its own corresponding early warning conditions, generate early warning information and send it to the corresponding early warning queue of the monitored object; The early warning module is configured to consume the early warning queue corresponding to the monitoring object, so as to push the early warning information to the early warning object corresponding to the early warning object identifier. 9. An electronic device, characterized in that the electronic device comprises a memory and a processor, the memory stores a computer program, and the processor implements any one of claims 1-7 when executing the computer program method steps. 10. A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1-7 are implemented.

Images