WO2018214320A1

WO2018214320A1 - Database service logic monitoring method and system, and storage medium

Info

Publication number: WO2018214320A1
Application number: PCT/CN2017/099334
Authority: WO
Inventors: 陈莹
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-05-22
Filing date: 2017-08-28
Publication date: 2018-11-29
Also published as: CN107678907A; CN107678907B

Abstract

Disclosed is a database service logic monitoring method, comprising: performing service logic monitoring on monitoring items written in a monitoring task table in a set time; writing the service logic monitoring result in a monitoring data table; scanning the monitoring data table every specific time to obtain abnormal data; and if the abnormal data matches with a preset warning condition, obtaining, according to the serial number ID of the monitoring item corresponding to the abnormal data, configuration information required for warning processing and performing the warning processing. Also disclosed are a database service logic monitoring system and a storage medium. According to the present invention, the abnormal data generated in a database can be automatically monitored and the warning processing is performed, so that the technical problem in the prior art that it is difficulty in timely discovery of data exception generated in the database and timely warning is solved, and the database stability is improved.

Description

Database business logic monitoring method, system, and storage medium

This application claims the priority of the Chinese Patent Application filed on May 22, 2017, the Chinese Patent Office, the application number is 201710367166.0, and the invention is entitled "Database Business Logic Monitoring Method, System, and Storage Medium", the entire contents of which are incorporated by reference. In the application.

Technical field

The present invention relates to the field of database monitoring technologies, and in particular, to a database service logic monitoring method, system, and storage medium.

Background technique

For a real-time database system, it is very necessary to monitor the running status of the system. Establishing a real-time automatic monitoring system for the database can not only reduce the work pressure of the operation and maintenance personnel, improve the management level, but also enhance the database. stability.

At this stage, the monitoring of the database is to monitor the running performance of the database. For the monitoring of the database business logic, the major database vendors provide relevant performance management views and troubleshooting commands to the database operation and maintenance personnel. U.S. personnel manage and check database business logic problems. However, as the amount of data in the database increases, it is often difficult for O&M personnel to detect and generate data anomalies and timely alarms in the database when managing and checking database business logic problems. Stability.

Summary of the invention

The main purpose of the present invention is to provide a database service logic monitoring method, system, and storage medium, which aims to solve the technical problem that it is difficult to timely discover data abnormalities and timely alarms generated by the database in the prior art, thereby affecting database stability.

To achieve the above objective, the present invention provides a database service logic monitoring method, and the database business logic monitoring method includes:

Generate monitoring items that need to be monitored every first set time, and write the monitoring item task table;

The monitoring item is started, and it is determined whether the monitoring item is currently in a ready state. If the monitoring item is currently in a ready state, performing service logic monitoring on the monitoring item;

The business logic monitoring result is written into the monitoring data table, and the monitoring data table is scanned every second set time to obtain abnormal data in the set time period;

Determining whether the abnormal data matches the preset alarm condition, and when the abnormal data matches the preset alarm condition, obtaining the configuration required for the alarm processing according to the serial number ID of the monitoring item corresponding to the abnormal data Information, and perform alarm processing according to the configuration information. .

In addition, in order to achieve the above object, the present invention further provides a database business logic monitoring system, the database business logic monitoring system comprising: a memory, a processor, and a database stored on the memory and operable on the processor The business logic monitor program, when the database business logic monitor program is executed by the processor, implements the following steps:

Determining whether the abnormal data matches the preset alarm condition, and when the abnormal data matches the preset alarm condition, obtaining the configuration required for the alarm processing according to the serial number ID of the monitoring item corresponding to the abnormal data Information, and perform alarm processing according to the configuration information.

In addition, in order to achieve the above object, the present invention further provides a storage medium, where the database business logic monitoring program is stored, and the database business logic monitoring program is executed by the processor to implement the following steps:

The database business logic monitoring method, system and storage medium provided by the invention can realize: performing business logic monitoring on the monitoring items written in the monitoring task table within a set time, and writing the business logic monitoring result The monitoring data table is entered, and the monitoring data table is scanned at a certain time to obtain abnormal data. When the abnormal data matches the preset alarm condition, the alarm is obtained according to the serial number ID of the monitoring item corresponding to the abnormal data. The present invention can automatically monitor the abnormal data generated in the database and perform alarm processing, which solves the technical problem that it is difficult to timely discover the data abnormality and timely alarm generated by the database in the prior art. Improve the stability of the database.

DRAWINGS

1 is a schematic flowchart of a first embodiment of a database service logic monitoring method according to the present invention;

2 is a schematic diagram of a system structure of a software running environment involved in a database service logic monitoring system according to the present invention.

The implementation, functional features, and advantages of the present invention will be further described in conjunction with the embodiments.

detailed description

The preferred embodiments of the present invention are described in conjunction with the accompanying drawings, and the preferred embodiments described herein are intended to illustrate and explain the invention, and not to limit the invention, and The embodiments and the features in the embodiments can be combined with each other.

The invention provides a database business logic monitoring method, in which a business logic monitoring is performed on a monitoring item written in a monitoring task table within a set time, and a business logic monitoring result is written into a monitoring data table, and The monitoring data table is scanned at a certain time to obtain abnormal data. When the abnormal data matches the preset alarm condition, the configuration information required for the alarm processing is obtained according to the serial number ID of the monitoring item corresponding to the abnormal data. And the alarm processing is performed, that is, the invention can automatically monitor the abnormal data generated in the database, and perform alarm processing, without requiring personnel to participate, saving time and effort.

1 is a schematic flowchart of a first embodiment of a database service logic monitoring method according to the present invention. In this embodiment, the database service logic monitoring method includes:

In step S10, a monitoring item that needs to be monitored is generated every first set time, and is written into the monitoring item task table.

After the monitoring item change starts, the monitoring platform needs to add a new monitoring item. Specifically, the dml (DatamanIpulationLanguage, data manipulation language) scripting language is added to the monitor item base table monitor_tbl. The monitoring item base table monitor_tbl is mainly used to record the execution time of the monitoring item, the monitoring frequency, and the configuration information required by the monitoring platform for subsequent monitoring and processing, such as the monitoring item name, detailed description information, effective time, expiration time, monitoring keyword, Alarm mode, alarm, frequency, running time period, non-running time period, monitoring type, alarm level, etc.

The above monitoring platform may preferably be an Elis monitoring platform.

The database JOB function is started every first set time (for example, at 22 o'clock every day), and the monitoring items that need to be monitored are uniformly generated, and the monitoring item task table is written.

Step S20: Start the monitoring item, and determine whether the monitoring item is currently in a ready state. If the monitoring item is currently in a ready state, perform business logic monitoring on the monitoring item.

In this embodiment, the monitoring item is started periodically, and it is determined whether the monitoring item is currently in the ready state. If the monitoring item is currently in the ready state, the monitoring item is monitored by the service logic.

The process of determining whether the monitoring item is currently in the ready state is: first determining whether the current monitoring platform is in an open state. If the current monitoring platform is in an open state, determining whether the monitoring module corresponding to the monitoring platform and the monitoring function corresponding to the monitoring module are Normally, if the monitoring module corresponding to the monitoring platform and the monitoring function corresponding to the monitoring module can work normally, it is determined that the monitoring item is currently in the ready state; otherwise, the monitoring item is considered to be not ready, and the monitoring item monitoring task is directly ended. .

Further, in this embodiment, the step of starting the foregoing monitoring item includes:

The monitoring item is started according to a pre-configured startup condition, where the startup condition includes when the time corresponding to the database is the same as the preset startup time, or when the time corresponding to the database matches the preset startup time period, Start the monitoring item.

That is, in this embodiment, the monitoring item can be started to be activated at any time point or time period to monitor the business logic of the database. For example, it is set to start the above monitoring items at 23 o'clock every night, monitor the business logic of the database, and then set the monitoring duration. For example, after the time of starting the above monitoring items reaches half an hour, the monitoring items are closed.

The monitoring item may be started at regular intervals, for example, the monitoring item is started every hour, and the monitoring item is turned off after the monitoring item is started for half an hour.

The startup time period may also be set. When the time corresponding to the database is in the startup time period, the monitoring item is started. For example, the startup time period is set to be from 8:00 am to 6:00 pm, during the startup time period. Start the above monitoring items.

The business logic monitoring task of the monitoring item in the monitoring item task table is uniformly scheduled by the database JOB function.

Step S30, the business logic monitoring result is written into the monitoring data table, and the monitoring data table is scanned every second set time to obtain abnormal data in the set time period.

In this embodiment, the service logic monitoring result is written into the monitoring data table by calling the corresponding interface of the monitoring platform, and the monitoring data table is scanned every second set time (for example, every 2 minutes) to obtain the setting. Abnormal data within a time period (eg, within the current time to 2 minutes before the current time).

In step S40, it is determined whether the abnormal data matches the preset alarm condition. When the abnormal data matches the preset alarm condition, the alarm processing station is obtained according to the serial number ID of the monitoring item corresponding to the abnormal data. The required configuration information is used to perform alarm processing according to the configuration information.

In this embodiment, after the abnormal data is obtained, it is determined whether the abnormal data matches the preset alarm condition. If the abnormal data is matched, the configuration required for the alarm processing is obtained according to the serial number ID of the monitoring item corresponding to the abnormal data. The information is processed and alarmed; otherwise, the monitoring item monitoring task is directly ended.

The database service logic monitoring method described in this embodiment performs business logic monitoring on the monitoring items written in the monitoring task table within a set time, and writes the business logic monitoring result into the monitoring data table, and at a certain time The time is scanned for the monitoring data table to obtain the abnormal data. When the abnormal data matches the preset alarm condition, the configuration information required for the alarm processing is obtained according to the serial number ID of the monitoring item corresponding to the abnormal data, and the alarm is generated. The invention can automatically monitor the abnormal data generated in the database and perform alarm processing, which solves the technical problem that it is difficult to timely discover the data abnormality and timely alarm generated by the database in the prior art, and improves the stability of the database.

Further, based on the first embodiment described in FIG. 1 above, in the second embodiment of the database service logic monitoring method of the present invention, the service logic monitoring result is written in the monitoring data table as described in step S30 of FIG. The steps also include:

The business logic monitoring result is written into a pre-established monitoring detail data table.

The monitoring detail data table is mainly used to record detailed information corresponding to the abnormal data, such as the serial number, the error information, the execution user, the execution time, the SID of the running database JOB, the monitoring item ID, and the like.

Further, after the step of performing alarm processing according to the configuration information in step S40 shown in FIG. 1 , the method further includes:

Deriving the monitoring data table and/or the monitoring detail data table, wherein the monitoring data table includes at least one of a startup time of a monitoring item, a monitoring frequency, and a monitoring status, where the monitoring detail data table includes Detailed information corresponding to the abnormal data.

After the step of performing alarm processing according to the configuration information, if the monitoring data table and/or the monitoring detail data table need to be viewed, the monitoring data table and/or the monitoring detail data table may be derived.

Among them, when exporting the above monitoring data table and/or monitoring the obvious data table, you can use the fetching SQL.

(StructuredQueryLanguage, Structured Query Language) to export. It is possible to export only the monitoring data table, or only the monitoring detail data table, or both the monitoring data table and the monitoring detail data table.

Specifically, the monitoring data table includes at least one of a startup time, a monitoring frequency, and a monitoring state of the monitoring item. In addition, the monitoring data table further includes a serial number, a monitoring item ID, a batch execution identifier, and a batch processing start time. , batch processing end time, business processing start time, business processing end time, number of pieces, amount, execution user, execution time, exception identifier, SID of running database JOB, execution result summary information, processing status, and so on.

The database service logic monitoring method in this embodiment also writes the service logic monitoring result into the pre-established monitoring detail data table, and after performing the alarm processing, may select to export the monitoring data table and/or the monitoring details. The data table facilitates the database operation and maintenance technician information to understand the database abnormal data, which greatly improves the operation and maintenance work efficiency and saves labor costs.

Further, based on the first embodiment described in FIG. 1 above, in the third embodiment of the database service logic monitoring method of the present invention, the abnormal data and the preset alarm condition are determined in step S40 shown in FIG. The steps to match are:

Determining whether the quantity value corresponding to the abnormal data is greater than a preset first threshold, and/or determining whether the data item specified in the abnormal data is greater than a preset second threshold;

When the quantity value is greater than the first threshold, and/or the data item is greater than the second threshold, determining that the abnormal data matches the preset alarm condition.

Specifically, when determining whether the abnormal data matches the preset alarm condition, whether the quantity value corresponding to the abnormal data is greater than a preset first threshold, and whether the specified data item in the abnormal data is greater than a preset may be simultaneously determined. And the second threshold value, when the quantity value corresponding to the abnormal data is greater than a preset first threshold, and the data item specified in the abnormal data is greater than a preset second threshold, determining the abnormal data and the preset alarm condition Or matching, or determining whether the quantity value corresponding to the abnormal data is greater than a preset first threshold, or determining whether the data item specified in the abnormal data is greater than a preset second threshold, when the abnormal data corresponds to When the quantity value is greater than the preset first threshold, or the data item specified in the abnormal data is greater than the preset second threshold, it is determined that the abnormal data matches the preset alarm condition.

Among them, the proc_count and proc_premium fields in the database can be used to control the threshold, wherein proc_count is used to control the quantity value corresponding to the abnormal data, and proc_premium is used to control the data item (such as the sales amount) specified in the abnormal data. The configuration format of the configuration item is: proc_count>n or proc_premium>nm. For example, if a monitoring item is for monitoring the non-distributed file, you need to set the alarm to "proc_count>5". .

The threshold value corresponding to the quantity value corresponding to the abnormal data and the data item specified in the abnormal data may be simultaneously monitored. For example, if a monitoring item is used to monitor the situation of non-distribution, it needs to be alarmed if the number of undistributed disks exceeds 5 and the amount exceeds 1000.0, then configure ("proc_count>5 And Proc_premium>1000.0)"; In addition, it is also possible to perform threshold monitoring on the quantity value corresponding to the abnormal data or the data item specified in the abnormal data. For example, if the number of undistributed disks exceeds 5 or the amount exceeds 1000.0, the alarm is configured. for "(proc_count>5 or proc_premium>1000.0)".

The database service logic monitoring method in this embodiment determines the abnormality when the quantity value corresponding to the abnormal data is greater than a preset first threshold, and/or the data item specified in the abnormal data is greater than a preset second threshold. The data is matched with the preset alarm condition, wherein the first threshold and the second threshold are set by the operation and maintenance personnel according to actual needs, thereby arbitrarily adjusting the accuracy of the database service logic monitoring.

Further, based on the first, second, and third embodiments of the database service logic monitoring method of the present invention, in the fourth embodiment of the database service logic monitoring method of the present invention, according to the foregoing step S40 shown in FIG. The steps for configuring alarm processing are as follows:

Determining an alarm level corresponding to the alarm processing, and performing alarm processing according to the alarm level.

Among them, according to the operational monitoring platform specification, the alarm level of the monitoring platform can be configured in advance from high to low as CRITICAL, MAJOR, MINOR, WARNING, and INFO.

Further, the step of performing alarm processing according to the alarm level includes:

When the number of alarms that are queued at any time is greater than the preset maximum concurrency threshold, the alarm processing with a high alarm level is prioritized.

Further, the alarm manner corresponding to the alarm processing includes one or more of an email alarm, a call alarm, and an automatic transfer IT service management system alarm.

According to the monitoring platform specification, the alarm mode corresponding to the alarm processing includes: 1-mail, 2-call (telephone), 3-automatic transfer ITSM (IT) ServiceManagement, IT Service Management) system. You can choose one of the alarm modes, or you can select one of the two alarm modes, or select the three alarm modes to select at the same time.

In addition, the alarm manner corresponding to the foregoing alarm processing further includes: 4-message subscription, and 5-custom script alarm mode.

The database service logic monitoring method in this embodiment needs to determine the alarm level corresponding to the alarm processing before performing alarm processing, and then perform alarm processing according to the alarm level, wherein the alarm processing is queued at any time point. When the number of alarms is greater than the preset maximum concurrency threshold, the alarm processing with a high alarm level is preferentially performed. The alarm processing corresponding to the alarm processing includes one or more of email alarm, call alarm, and automatic transfer of IT service management system alarms. That is, in this embodiment, when a large number of alarm processes are generated, the alarm processing with a higher alarm level can be preferentially performed, thereby minimizing the loss caused by the database abnormal data and ensuring the stability of the database operation.

The present invention also provides a database business logic monitoring system, the system comprising: a memory, a processor, and a database business logic monitoring program stored on the memory and operable on the processor; the system can implement: Within a certain period of time, the business logic of the monitoring items written in the monitoring task table is monitored, and the business logic monitoring result is written into the monitoring data table, and the monitoring data table is scanned at regular intervals to obtain abnormal data. When the abnormal data matches the preset alarm condition, the configuration information required for the alarm processing is obtained according to the serial number ID of the monitoring item corresponding to the abnormal data, and the alarm processing is performed, that is, the present invention can automatically monitor the abnormal data generated in the database. And the alarm processing solves the technical problem that it is difficult to timely discover the data abnormality and timely alarm generated by the database in the prior art, and improves the stability of the database.

Specifically, when the foregoing database service logic monitoring program is executed by the processor, the following steps are implemented:

Further, the step of starting the monitoring item includes:

Further, the step of writing the service logic monitoring result to the monitoring data table further includes:

Further, the step of determining whether the abnormal data matches a preset alarm condition comprises:

Further, the step of performing alarm processing according to the configuration information includes:

Further, when the database service logic monitoring program is executed by the processor, the following steps are also implemented:

For a better understanding of the present invention, referring to FIG. 2, FIG. 2 is a schematic diagram of a system structure of a software running environment involved in a database service logic monitoring system according to the present invention. In this embodiment, the database service logic monitoring system may include: a processor 1001, For example, CPU, network interface 1004, user interface 1003, memory 1005, communication bus 1002. The communication bus 1002 is configured to implement connection communication between the components; the user interface 1003 may include a display, an input unit such as a keyboard, and the optional user interface 1003 may further include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (such as a WI-FI interface); the memory 1005 may be a high-speed RAM memory or a stable memory (non-volatile) Memory, such as a disk storage; the memory 1005 may alternatively be a storage device independent of the processor 1001 described above.

Those skilled in the art will appreciate that the system structure illustrated in FIG. 2 does not constitute a limitation to the above described system, and may include more or fewer components than those illustrated, or some components may be combined, or different component arrangements.

As shown in FIG. 2, a memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a database service logic monitor program.

As shown in FIG. 2, the network interface 1004 is mainly used to connect to a background server for data communication with a background server; the user interface 1003 is mainly used to connect a client (user end) to perform data communication with the client; and the processor 1001 can use The database business logic monitor program stored in the memory 1005 is called and the corresponding operation is performed.

The embodiments of the database service logic monitoring system are basically the same as the corresponding embodiments of the database service logic monitoring method, and therefore are not described here.

The present invention further provides a storage medium, wherein the storage medium stores a database service logic monitoring program, and the storage medium can implement: performing service logic monitoring on the monitoring items written in the monitoring task table within a set time, And the service logic monitoring result is written into the monitoring data table, and the monitoring data table is scanned at a certain time to obtain abnormal data. When the abnormal data matches the preset alarm condition, the monitoring item is corresponding according to the abnormal data. The serial number ID obtains the configuration information required for the alarm processing and performs alarm processing. That is, the present invention can automatically monitor the abnormal data generated in the database and perform alarm processing, which solves the problem that it is difficult to timely discover the data generated by the database in the prior art. And the technical problems of timely warnings improve the stability of the database.

Further, the step of starting the monitoring item includes:

Further, when the database business logic monitor program is executed by the processor, the following steps are also implemented:

The embodiments corresponding to the storage medium are basically the same as the corresponding embodiments of the foregoing database service logic monitoring method, and therefore are not described herein again.

It is to be understood that the term "comprises", "comprising", or any other variants thereof, is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes those elements. It also includes other elements that are not explicitly listed, or elements that are inherent to such a process, method, article, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

The serial numbers of the embodiments of the present invention are merely for the description, and do not represent the advantages and disadvantages of the embodiments.

Through the description of the above embodiments, those skilled in the art can clearly understand that the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better. Implementation. Based on such understanding, portions of the technical solution of the present invention that contribute substantially or to the prior art may be embodied in the form of a software product stored in a storage medium (such as a ROM/RAM as described above). , a disk, an optical disk, including a number of instructions for causing a terminal device to perform the method described in various embodiments of the present invention.

The above are only the preferred embodiments of the present invention, and are not intended to limit the scope of the invention, and the equivalent structure or equivalent process transformations made by the description of the present invention and the drawings are directly or indirectly applied to other related technical fields. The same is included in the scope of patent protection of the present invention.

Claims

A database business logic monitoring method, wherein the database business logic monitoring method comprises:

Generate monitoring items that need to be monitored every first set time, and write the monitoring item task table;

The monitoring item is started, and it is determined whether the monitoring item is currently in a ready state. If the monitoring item is currently in a ready state, performing service logic monitoring on the monitoring item;

The business logic monitoring result is written into the monitoring data table, and the monitoring data table is scanned every second set time to obtain abnormal data in the set time period;

Determining whether the abnormal data matches the preset alarm condition, and when the abnormal data matches the preset alarm condition, obtaining the configuration required for the alarm processing according to the serial number ID of the monitoring item corresponding to the abnormal data Information, and perform alarm processing according to the configuration information.
The method for monitoring a database service logic according to claim 1, wherein the step of starting the monitoring item comprises:

The monitoring item is started according to a pre-configured startup condition, where the startup condition includes when the time corresponding to the database is the same as the preset startup time, or when the time corresponding to the database matches the preset startup time period, Start the monitoring item.
The method of monitoring the database service logic according to claim 1, wherein the step of writing the service logic monitoring result to the monitoring data table further comprises:

The business logic monitoring result is written into a pre-established monitoring detail data table.
The method for monitoring a database service logic according to claim 1, wherein the step of determining whether the abnormal data matches a preset alarm condition comprises:

Determining whether the quantity value corresponding to the abnormal data is greater than a preset first threshold, and/or determining whether the data item specified in the abnormal data is greater than a preset second threshold;

When the quantity value is greater than the first threshold, and/or the data item is greater than the second threshold, determining that the abnormal data matches the preset alarm condition.
The method of monitoring the database service logic according to claim 1, wherein the step of performing alarm processing according to the configuration information comprises:

Determining an alarm level corresponding to the alarm processing, and performing alarm processing according to the alarm level.
The method of monitoring the database service logic according to claim 5, wherein the step of performing alarm processing according to the configuration information further comprises:

Deriving the monitoring data table and/or the monitoring detail data table, wherein the monitoring data table includes at least one of a startup time of a monitoring item, a monitoring frequency, and a monitoring status, where the monitoring detail data table includes Detailed information corresponding to the abnormal data.
The method of monitoring the database service logic according to claim 5, wherein the step of performing alarm processing according to the alarm level comprises:

When the number of alarms that are queued at any time is greater than the preset maximum concurrency threshold, the alarm processing with a high alarm level is prioritized.
The database service logic monitoring method according to claim 5, wherein the alarm mode corresponding to the alarm processing comprises one or more of an email alert, a call alert, and an automatic transfer IT service management system alert.
A database business logic monitoring system, comprising: a memory, a processor, and a database business logic monitoring program stored on the memory and operable on the processor, The database business logic monitor is implemented by the processor to implement the following steps:

Generate monitoring items that need to be monitored every first set time, and write the monitoring item task table;

The monitoring item is started, and it is determined whether the monitoring item is currently in a ready state. If the monitoring item is currently in a ready state, performing service logic monitoring on the monitoring item;

The business logic monitoring result is written into the monitoring data table, and the monitoring data table is scanned every second set time to obtain abnormal data in the set time period;

Determining whether the abnormal data matches the preset alarm condition, and when the abnormal data matches the preset alarm condition, obtaining the configuration required for the alarm processing according to the serial number ID of the monitoring item corresponding to the abnormal data Information, and perform alarm processing according to the configuration information.
The database business logic monitoring system according to claim 9, wherein the step of starting the monitoring item comprises:

The monitoring item is started according to a pre-configured startup condition, where the startup condition includes when the time corresponding to the database is the same as the preset startup time, or when the time corresponding to the database matches the preset startup time period, Start the monitoring item.
The database business logic monitoring system of claim 9, wherein the step of writing the business logic monitoring result to the monitoring data table further comprises:

The business logic monitoring result is written into a pre-established monitoring detail data table.
The database service logic monitoring system according to claim 9, wherein the step of determining whether the abnormal data matches a preset alarm condition comprises:

Determining whether the quantity value corresponding to the abnormal data is greater than a preset first threshold, and/or determining whether the data item specified in the abnormal data is greater than a preset second threshold;

When the quantity value is greater than the first threshold, and/or the data item is greater than the second threshold, determining that the abnormal data matches the preset alarm condition.
The database service logic monitoring system according to claim 9, wherein the step of performing alarm processing according to the configuration information comprises:

Determining an alarm level corresponding to the alarm processing, and performing alarm processing according to the alarm level.
The database business logic monitoring system according to claim 13, wherein when the database business logic monitoring program is executed by the processor, the following steps are further implemented:

Deriving the monitoring data table and/or the monitoring detail data table, wherein the monitoring data table includes at least one of a startup time of a monitoring item, a monitoring frequency, and a monitoring status, where the monitoring detail data table includes Detailed information corresponding to the abnormal data.
The database service logic monitoring system according to claim 13, wherein the step of performing alarm processing according to the alarm level comprises:

When the number of alarms that are queued at any time is greater than the preset maximum concurrency threshold, the alarm processing with a high alarm level is prioritized.
The database service logic monitoring system according to claim 13, wherein the alarm mode corresponding to the alarm processing comprises one or more of an email alert, a call alert, and an automatic transfer IT service management system alert.
A storage medium is characterized in that: a database business logic monitoring program is stored on the storage medium, and the database business logic monitoring program is executed by the processor to implement the following steps:

Generate monitoring items that need to be monitored every first set time, and write the monitoring item task table;

The monitoring item is started, and it is determined whether the monitoring item is currently in a ready state. If the monitoring item is currently in a ready state, performing service logic monitoring on the monitoring item;

The business logic monitoring result is written into the monitoring data table, and the monitoring data table is scanned every second set time to obtain abnormal data in the set time period;

Determining whether the abnormal data matches the preset alarm condition, and when the abnormal data matches the preset alarm condition, obtaining the configuration required for the alarm processing according to the serial number ID of the monitoring item corresponding to the abnormal data Information, and perform alarm processing according to the configuration information.
The storage medium of claim 17, wherein the step of initiating the monitoring item comprises:

The monitoring item is started according to a pre-configured startup condition, where the startup condition includes when the time corresponding to the database is the same as the preset startup time, or when the time corresponding to the database matches the preset startup time period, Start the monitoring item.
The storage medium of claim 17, wherein the step of writing the business logic monitoring result to the monitoring data table further comprises:

The business logic monitoring result is written into a pre-established monitoring detail data table.
The storage medium according to claim 17, wherein the step of determining whether the abnormal data matches a preset alarm condition comprises:

Determining whether the quantity value corresponding to the abnormal data is greater than a preset first threshold, and/or determining whether the data item specified in the abnormal data is greater than a preset second threshold;

When the quantity value is greater than the first threshold, and/or the data item is greater than the second threshold, determining that the abnormal data matches the preset alarm condition.
The storage medium according to claim 17, wherein the step of performing alarm processing according to the configuration information comprises:

Determining an alarm level corresponding to the alarm processing, and performing alarm processing according to the alarm level.
The storage medium of claim 21, wherein when the database business logic monitor is executed by the processor, the following steps are further implemented:

Deriving the monitoring data table and/or the monitoring detail data table, wherein the monitoring data table includes at least one of a startup time of a monitoring item, a monitoring frequency, and a monitoring status, where the monitoring detail data table includes Detailed information corresponding to the abnormal data.
The storage medium according to claim 21, wherein the step of performing alarm processing according to the alarm level comprises:

When the number of alarms that are queued at any time is greater than the preset maximum concurrency threshold, the alarm processing with a high alarm level is prioritized.
The storage medium according to claim 21, wherein the alarm mode corresponding to the alarm processing comprises one or more of an email alert, a call alert, and an automatic transfer IT service management system alert.