CN113076333A - Service abnormity monitoring method and device - Google Patents

Service abnormity monitoring method and device Download PDF

Info

Publication number
CN113076333A
CN113076333A CN202110446341.1A CN202110446341A CN113076333A CN 113076333 A CN113076333 A CN 113076333A CN 202110446341 A CN202110446341 A CN 202110446341A CN 113076333 A CN113076333 A CN 113076333A
Authority
CN
China
Prior art keywords
monitoring
data
abnormal
monitoring data
time
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110446341.1A
Other languages
Chinese (zh)
Inventor
王鑫茂
申***
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Construction Bank Corp
Original Assignee
China Construction Bank Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Construction Bank Corp filed Critical China Construction Bank Corp
Priority to CN202110446341.1A priority Critical patent/CN113076333A/en
Publication of CN113076333A publication Critical patent/CN113076333A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/242Query formulation
    • G06F16/2433Query languages
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3065Monitoring arrangements determined by the means or processing involved in reporting the monitored data
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/32Monitoring with visual or acoustical indication of the functioning of the machine
    • G06F11/324Display of status information
    • G06F11/327Alarm or error message display

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Mathematical Physics (AREA)
  • Computational Linguistics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The invention discloses a method and a device for monitoring business abnormity, which relate to the technical field of automatic program design, and the method comprises the following steps: acquiring a monitoring date, a monitoring start time and a monitoring end time, and a monitoring data general query statement; replacing corresponding variables in the general query statement of the monitoring data according to the monitoring date, the monitoring start time and the monitoring end time to obtain a specified monitoring data query statement; querying the abnormal data quantity and the total quantity of the monitoring data in a target time period from the monitoring data by using a specified monitoring data query statement, wherein the target time period is a time period from monitoring start time to monitoring end time in a set monitoring date; and determining whether to send out transaction abnormal alarm information according to the quantity of the abnormal data and the total quantity of the monitoring data. The invention can find out more transaction failures in time, so that the staff can deal with the problem of transaction failure in time, the normal operation of subsequent transactions is ensured, and the user experience is improved.

Description

Service abnormity monitoring method and device
Technical Field
The invention relates to the technical field of automatic program design, in particular to a method and a device for monitoring business abnormity.
Background
This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.
In production, transaction failure often occurs due to system problems or dirty data problems, and when the problem causing the transaction failure cannot be processed in time, the failed transaction will continuously occur, so that the user experience is poor.
Disclosure of Invention
The embodiment of the invention provides a service abnormity monitoring method, which is used for timely finding out more transaction failures so as to facilitate staff to timely handle the problem of transaction failure, ensure the normal operation of subsequent transactions and improve the user experience, and comprises the following steps:
acquiring a monitoring date, a monitoring start time and a monitoring end time, and a monitoring data general query statement;
replacing corresponding variables in the general query statement of the monitoring data according to the monitoring date, the monitoring start time and the monitoring end time to obtain a specified monitoring data query statement;
querying the abnormal data quantity and the total quantity of the monitoring data in a target time period from the monitoring data by using a specified monitoring data query statement, wherein the target time period is a time period from monitoring start time to monitoring end time in a set monitoring date;
and determining whether to send out transaction abnormal alarm information according to the quantity of the abnormal data and the total quantity of the monitoring data.
In an implementation manner of the embodiment of the present invention, before acquiring a monitoring date, a monitoring start time, a monitoring end time, and a general query statement for monitoring data, the method further includes:
when the abnormal service monitoring state is started, acquiring transaction data occurring in a preset time before the current moment at intervals of a preset time as monitoring data;
and recording the monitoring date, the monitoring starting time and the monitoring ending time of the monitoring data.
In an implementation manner of the embodiment of the present invention, after querying the number of abnormal data and the total number of monitored data in a target time period from the monitored data by using a specified monitored data query statement, the method further includes:
and changing the monitoring state of the abnormal service from starting to monitoring, wherein the monitoring is used for indicating that the number of abnormal data and the total number of the monitored data in the current monitored data are inquired.
In an implementation manner of the embodiment of the present invention, after determining whether to send out transaction abnormal warning information according to the abnormal data quantity and the total quantity of the monitoring data, the method further includes:
and if the transaction abnormity warning information is determined to be sent out, setting the service abnormity monitoring state to be closed, wherein in the closed state, the monitoring data is not acquired.
In an implementation manner of the embodiment of the present invention, after the service anomaly monitoring state is set to be closed, the method further includes:
and when receiving a service abnormity monitoring command started by a user, setting the service abnormity monitoring state as start.
In an implementation manner of the embodiment of the present invention, after determining whether to send out transaction abnormal warning information according to the abnormal data quantity and the total quantity of the monitoring data, the method further includes:
and if the transaction abnormity warning information is determined not to be sent, setting the service abnormity monitoring state to be started.
In an implementation manner of the embodiment of the present invention, determining whether to send out transaction abnormal alarm information according to the abnormal data quantity and the total quantity of the monitoring data includes:
calculating the ratio of the number of the abnormal data to the total number of the monitoring data to be used as an abnormal proportion;
judging whether the abnormal proportion is larger than a preset alarm threshold value or not;
and if the abnormal proportion is larger than the alarm threshold value, sending out transaction abnormal alarm information.
The embodiment of the present invention further provides a service anomaly monitoring device, which is used for timely finding out a plurality of transaction failures, so that a worker can timely deal with the problem of transaction failure, the normal operation of subsequent transactions is ensured, and the user experience is improved, wherein the device comprises:
the acquisition module is used for acquiring a monitoring date, a monitoring starting time and a monitoring ending time, and a monitoring data general query statement;
the query module is used for replacing corresponding variables in the universal query statement of the monitoring data according to the monitoring date, the monitoring start time and the monitoring end time to obtain a specified monitoring data query statement;
the query module is further used for querying the number of abnormal data and the total number of the monitoring data in a target time period from the monitoring data by using a specified monitoring data query statement, wherein the target time period is a time period from the monitoring start time to the monitoring end time in a set monitoring date;
and the determining module is used for determining whether to send out transaction abnormal alarm information according to the abnormal data quantity and the total quantity of the monitoring data.
In one implementation of an embodiment of the present invention,
the acquisition module is also used for acquiring transaction data occurring within a preset time before the current moment at intervals of a preset time when the abnormal service monitoring state is started, and taking the transaction data as monitoring data;
and the recording module is used for recording the monitoring date, the monitoring starting time and the monitoring ending time of the monitoring data.
In an implementation manner of the embodiment of the present invention, the apparatus further includes:
and the state changing module is used for changing the abnormal monitoring state of the service from the starting state to the monitoring state after the specified monitoring data query statement is used for querying the abnormal data quantity and the total quantity of the monitoring data in the target time period from the monitoring data, wherein the monitoring state is used for indicating that the abnormal data quantity and the total quantity of the monitoring data in the current monitoring data are queried.
In an implementation manner of the embodiment of the present invention, the state change module is further configured to:
after determining whether to send out transaction abnormal alarm information according to the quantity of the abnormal data and the total quantity of the monitoring data, if the transaction abnormal alarm information is determined to be sent out, setting a service abnormal monitoring state to be closed, wherein in the closed state, the monitoring data are not obtained.
In an implementation manner of the embodiment of the present invention, the state change module is further configured to:
after the monitoring state of the abnormal service is set to be closed, when a command for starting the monitoring state of the abnormal service by a user is received, the monitoring state of the abnormal service is set to be started.
In an implementation manner of the embodiment of the present invention, the state change module is further configured to:
after determining whether to send out transaction abnormal alarm information according to the quantity of the abnormal data and the total quantity of the monitoring data, if determining not to send out the transaction abnormal alarm information, setting the monitoring state of the service abnormality to be started.
In an implementation manner of the embodiment of the present invention, the determining module is configured to:
calculating the ratio of the number of the abnormal data to the total number of the monitoring data to be used as an abnormal proportion;
judging whether the abnormal proportion is larger than a preset alarm threshold value or not;
and if the abnormal proportion is larger than the alarm threshold value, sending out transaction abnormal alarm information.
The embodiment of the invention also provides computer equipment which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor realizes the service abnormity monitoring method when executing the computer program.
The embodiment of the invention also provides a computer readable storage medium, which stores a computer program for executing the service anomaly monitoring method.
In the embodiment of the invention, when a user needs to monitor transaction data, parameters such as required monitoring date, monitoring starting time, monitoring ending time and the like can be set, the parameters and the general query statement of the monitoring data are combined into the specified monitoring data query statement, the specified monitoring data query statement is used for querying the monitoring data in the target time interval, the quantity of abnormal data and the total quantity of the monitoring data are determined, and further whether transaction abnormal alarm information needs to be sent is determined. By the method, the abnormal conditions of the service in each target time period can be monitored and determined in time, and more transaction failure conditions can be found in time, so that the problem of transaction failure caused by staff in time can be conveniently solved, normal operation of subsequent transactions can be guaranteed, and user experience can be improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts. In the drawings:
fig. 1 is a flowchart of a method for monitoring a service anomaly according to an embodiment of the present invention;
fig. 2 is a flowchart of another method for monitoring service anomaly according to an embodiment of the present invention;
fig. 3 is a flowchart of another method for monitoring service anomaly according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a service anomaly monitoring apparatus according to an embodiment of the present invention;
FIG. 5 is a schematic structural diagram of a computer device according to an embodiment of the present invention;
fig. 6 is a system architecture diagram of a computer device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings. The exemplary embodiments and descriptions of the present invention are provided to explain the present invention, but not to limit the present invention.
The embodiment of the invention provides a method for monitoring service exception, as shown in fig. 1, the method comprises steps 101 to 104:
step 101, acquiring a monitoring date, a monitoring start time and a monitoring end time, and monitoring a general query statement of data.
The monitoring date, the monitoring start time and the monitoring end time can be set by a user, the user can set the monitoring date, the monitoring start time and the monitoring end time for one time, and can also set a total start time and an interval time, and the abnormal monitoring of the service is performed from the start time at intervals.
In the embodiment of the present invention, before acquiring the monitoring date, the monitoring start time, the monitoring end time, and the general query statement of the monitoring data, as shown in fig. 2, the following steps 201 to 202 may also be performed:
step 201, when the monitoring state of the abnormal service is on, acquiring transaction data occurring within a preset time before the current time as monitoring data at intervals of a preset time.
Step 202, recording the monitoring date, the monitoring start time and the monitoring end time of the monitoring data.
The service abnormity monitoring state is used for describing the working state of service abnormity monitoring, including opening, monitoring and closing. Wherein, the starting is used for indicating the working state of normally acquiring the monitoring data; the monitoring is used for indicating that the number of abnormal data and the total number of the monitoring data in the current monitoring data are inquired, namely, the monitoring data are marked to be processed; the close is used for indicating that the service exception monitoring is not started.
It should be noted that the opening, monitoring, and closing are named as one of the above operating states, and other naming manners may be adopted to distinguish the above three operating states.
That is to say, all transaction data in the previous preset time are acquired at preset time intervals, for example, the preset time is set to 10 minutes, all transaction data in the previous 10 minutes are acquired at intervals of 10 minutes, and meanwhile, the monitoring date, the monitoring start time and the monitoring end time are recorded, so that the occurrence time of the monitoring data is determined, and the monitoring data corresponding to the query time is determined quickly when query is facilitated.
And 102, replacing corresponding variables in the universal query statement of the monitoring data according to the monitoring date, the monitoring start time and the monitoring end time to obtain the specified monitoring data query statement.
Wherein, the monitoring data general query statement defines the query logic, does not define the specific query time, and identifies the query time by a variable, such as? 1 variable represents the monitoring date,? 2 variable represents the monitoring start time,? And 3, representing the monitoring ending time, and replacing variables by using the parameters set by the user after the parameters set by the user are obtained to obtain a specified monitoring data query statement for querying the monitoring data in the target time period.
And 103, querying the abnormal data quantity and the total quantity of the monitoring data in the target time period from the monitoring data by using a specified monitoring data query statement.
The target time interval is the time interval between the monitoring starting time and the monitoring ending time in the set monitoring date.
After the number of abnormal data and the total number of the monitored data in the target time period are inquired from the monitored data by using the appointed monitored data inquiry statement, the monitoring state of the abnormal service can be changed from the starting state to the monitoring state, so that the monitored data are reminded of being processed, and the situation that the same batch of monitored data is processed repeatedly is avoided.
And step 104, determining whether to send out transaction abnormal alarm information according to the quantity of the abnormal data and the total quantity of the monitoring data.
Specifically, as shown in fig. 3, step 104 may be executed as following steps 301 to 303:
step 301, calculating the ratio of the number of abnormal data to the total number of monitoring data as an abnormal proportion;
step 302, judging whether the abnormal proportion is larger than a preset alarm threshold value;
and step 303, if the abnormal proportion is larger than the alarm threshold value, sending out transaction abnormal alarm information.
The alarm threshold is set by the user, for example, 0.1, 0.3, etc. are set as the alarm threshold. The alarm threshold value can be set according to the actual condition of the service, and if the fault tolerance rate of the service is high, a larger value can be set as the alarm threshold value; if the service fault tolerance rate is low, a smaller value can be set as the alarm threshold.
The transaction abnormity warning information can be assembled by a general information template with variables, for example, the warning threshold value actual value is used for replacing the variable #1 in the general information template, and the abnormity ratio calculated value is used for replacing the variable # 2; and then, the assembled information passes through maintenance personnel through formats such as short messages, call voice broadcast, frame popping messages and the like.
In an implementation manner of the embodiment of the present invention, after determining whether to send out transaction abnormality alarm information according to the number of abnormal data and the total number of monitoring data, if it is determined to send out the transaction abnormality alarm information, the service abnormality monitoring state is set to be closed, wherein in the closed state, the monitoring data is not acquired. Because the staff need certain time to get rid of the trouble, if know when having the anomaly, still every interval when presetting time and carrying out the acquirement of monitoring data and unusual judgement, then will send many abnormal alarm information in the short time, cause certain harassment effect, reduce user experience, and then can not utilize repeated information harassment user after closing the control to promote user experience.
In another implementation manner, in the closed state, when a user opening a service anomaly monitoring instruction is received, the service anomaly monitoring state is set to be opened, meanwhile, the monitoring time is updated to be the current time, and the monitoring frequency is set, namely the preset time.
In another implementation mode, if the transaction abnormity warning information is determined not to be sent, the service abnormity monitoring state is set to be started. It should be noted that the monitoring state of the current service anomaly is changed from monitoring to monitoring, the monitoring time is updated to the current time, and the monitoring frequency is set.
In consideration of the fact that the monitoring data of different transaction types are respectively stored and the alarm thresholds set respectively are different, the abnormal conditions of different types of transactions can be respectively counted in the embodiment of the invention. Several parameter setting and monitoring statements for common transactions are given as follows:
(1) customer payment result notification failure transaction statistics
Alarm threshold value: 0.1
Monitoring frequency (preset time): 1
Monitoring date and time: 20200824080000 (the first 8 bits are the monitoring date and the last 6 bits are the monitoring end time)
Monitoring the state: 00
And (3) warning information: customer Payment result Notification failure alarm! The monitoring alarm value is #1, and the actual statistical proportion is #2
Monitoring statement:
firstly, a table is searched: S00T1_ MSG _ RELEASE _ INF message publish table.
Specifying query conditions: the number of retries of the lookup issue table is greater than one, the subject is equal to MPSP-outbys, the status is equal to 2, and the time range (i.e., the monitoring start time and the monitoring end time) is set.
(iii) total number query condition: the theme is equal to MPSP-OUTSYSIS, time horizon.
Illustratively, the monitoring statement is as follows:
Select count(*)from S00T1_MSG_RELEASE_INF where MSG_TOPC=’MPSP-OUTSYS’and MSG_STCD=’2’and RTRSM_CNT>0and TXN_DT=’?1’and TXN_TM betwen‘?2’and’?3’;#Select count(*)from S00T1_MSG_RELEASE_INF where TXN_DT=’?1’and TXN_TM betwen‘?2’and’?3’;
(2) payment result timeout transaction statistics
Alarm threshold value: 0.1
Monitoring frequency (preset time): 30
Monitoring date and time: 20200824080000
Monitoring the state: 00
And (3) warning information: payment result time-out alarm! The monitoring alarm value is #1, and the actual statistical proportion is #2
Monitoring statement:
the unconventional is single:
firstly, a table is searched: S51T1_ ORDER payment ORDER table.
Specifying query conditions: the order status equals 6 timeout, Super _ Ordr _ NO empty, time range.
(iii) total number query condition: super _ Ordr _ NO is empty, time range.
And (3) non-contract combination:
firstly, a table is searched: S51T1_ MERGE _ ORDER MERGEs ORDER tables.
Specifying query conditions: the order status equals 6 timeout, time horizon.
(iii) total number query condition: time range.
Contract:
firstly, a table is searched: S51T1_ PY _ JRNL payment flow meter.
Specifying query conditions: the payment status is equal to 6 timeout, time range.
(iii) total number query condition: time range.
Illustratively, the monitoring statement is as follows:
Select count(*)from S51T1_ORDER where Ordr_Stcd=’6’and Supr_Ordr_No is null and TXN_DT=’?1’and TXN_TM betwen‘?2’and’?3’;select count(*)from S51T1_MEGRE_ORDER where Ordr_Stcd=’6’and TXN_DT=’?1’and TXN_TM betwen‘?2’and’?3’;select count(*)from S51T1_PY_JRNL where PY_STCD=’6’and TXN_DT=’?1’and TXN_TM betwen‘?2’and’?3’;#Select count(*)from S51T1_ORDER where TXN_DT=’?1’and TXN_TM betwen‘?2’and’?3’;select count(*)from S51T1_MEGRE_ORDER where TXN_DT=’?1’and TXN_TM betwen‘?2’and’?3’;select count(*)from S51T1_PY_JRNL where TXN_DT=’?1’and TXN_TM betwen‘?2’and’?3’;
(3) statistics of transactions to be paid
Alarm threshold value: 0.1
Monitoring frequency (preset time): 30
Monitoring date and time: 20200824080000
Monitoring the state: 00
And (3) warning information: unpaid transaction alert! The monitoring alarm value is #1, and the actual statistical proportion is #2
Monitoring statement:
the unconventional is single:
firstly, a table is searched: S51T1_ ORDER payment ORDER table.
Specifying query conditions: the order status equals 1 to be paid, Super _ Ordr _ NO is empty, time range.
(iii) total number query condition: super _ Ordr _ NO is empty, time range.
And (3) non-contract combination:
firstly, a table is searched: S51T1_ MERGE _ ORDER MERGEs ORDER tables.
Specifying query conditions: the order status equals 1 to be paid, time range.
(iii) total number query condition: time range.
Contract:
firstly, a table is searched: S51T1_ PY _ JRNL payment flow meter.
Specifying query conditions: the payment status is equal to 1 to be paid, time range.
(iii) total number query condition: time range.
Illustratively, the monitoring statement is as follows:
Select count(*)from S51T1_ORDER where Ordr_Stcd=’1’and Supr_Ordr_No is null and TXN_DT=’?1’and TXN_TM betwen‘?2’and’?3’;select count(*)from S51T1_MEGRE_ORDER where Ordr_Stcd=’1’and TXN_DT=’?1’and TXN_TM betwen‘?2’and’?3’;select count(*)from S51T1_PY_JRNL where PY_STCD=’1’and TXN_DT=’?1’and TXN_TM betwen‘?2’and’?3’;#Select count(*)from S51T1_ORDER where TXN_DT=’?1’and TXN_TM betwen‘?2’and’?3’;select count(*)from S51T1_MEGRE_ORDER where TXN_DT=’?1’and TXN_TM betwen‘?2’and’?3’;select count(*)from S51T1_PY_JRNL where TXN_DT=’?1’and TXN_TM betwen‘?2’and’?3’;
it should be noted that the "contract", "non-contract merge" and "non-contract single" indicate different data tables divided according to different contracts, and the different data tables store monitoring data of corresponding contract types respectively.
In the embodiment of the invention, when a user needs to monitor transaction data, parameters such as required monitoring date, monitoring starting time, monitoring ending time and the like can be set, the parameters and the general query statement of the monitoring data are combined into the specified monitoring data query statement, the specified monitoring data query statement is used for querying the monitoring data in the target time interval, the quantity of abnormal data and the total quantity of the monitoring data are determined, and further whether transaction abnormal alarm information needs to be sent is determined. By the method, the abnormal conditions of the service in each target time period can be monitored and determined in time, and more transaction failure conditions can be found in time, so that the problem of transaction failure caused by staff in time can be conveniently solved, normal operation of subsequent transactions can be guaranteed, and user experience can be improved.
The embodiment of the invention also provides a service abnormity monitoring device, which is described in the following embodiment. Because the principle of the device for solving the problems is similar to the business anomaly monitoring method, the implementation of the device can refer to the implementation of the business anomaly monitoring method, and repeated parts are not described again.
As shown in fig. 4, the apparatus 400 includes an obtaining module 401, a querying module 402, and a determining module 403.
An obtaining module 401, configured to obtain a monitoring date, a monitoring start time, a monitoring end time, and a monitoring data general query statement;
the query module 402 is configured to replace a corresponding variable in the general query statement of the monitoring data according to the monitoring date, the monitoring start time, and the monitoring end time to obtain a specified monitoring data query statement;
the query module 402 is further configured to query, by using a specified monitoring data query statement, the number of abnormal data and the total number of monitoring data in a target time period from the monitoring data, where the target time period is a time period from a monitoring start time to a monitoring end time in a set monitoring date;
the determining module 403 is configured to determine whether to send out transaction abnormal warning information according to the abnormal data quantity and the total quantity of the monitoring data.
In one implementation of an embodiment of the present invention,
the obtaining module 401 is further configured to obtain, as monitoring data, transaction data occurring within a preset time before a current time every preset time when the monitoring state of the service anomaly is on;
and a recording module 404, configured to record a monitoring date, a monitoring start time, and a monitoring end time of the monitoring data.
In one implementation manner of the embodiment of the present invention, the apparatus 400 further includes:
the state changing module 405 is configured to change the monitoring state of the abnormal service from open to monitoring after the specified monitoring data query statement is used to query the number of abnormal data and the total number of monitoring data in the target time period from the monitoring data, where the monitoring is used to indicate that the number of abnormal data and the total number of monitoring data in the current monitoring data have been queried.
In an implementation manner of the embodiment of the present invention, the state changing module 405 is further configured to:
after determining whether to send out transaction abnormal alarm information according to the quantity of the abnormal data and the total quantity of the monitoring data, if the transaction abnormal alarm information is determined to be sent out, setting a service abnormal monitoring state to be closed, wherein in the closed state, the monitoring data are not obtained.
In an implementation manner of the embodiment of the present invention, the state changing module 405 is further configured to:
after the monitoring state of the abnormal service is set to be closed, when a command for starting the monitoring state of the abnormal service by a user is received, the monitoring state of the abnormal service is set to be started.
In an implementation manner of the embodiment of the present invention, the state changing module 405 is further configured to:
after determining whether to send out transaction abnormal alarm information according to the quantity of the abnormal data and the total quantity of the monitoring data, if determining not to send out the transaction abnormal alarm information, setting the monitoring state of the service abnormality to be started.
In an implementation manner of the embodiment of the present invention, the determining module 403 is configured to:
calculating the ratio of the number of the abnormal data to the total number of the monitoring data to be used as an abnormal proportion;
judging whether the abnormal proportion is larger than a preset alarm threshold value or not;
and if the abnormal proportion is larger than the alarm threshold value, sending out transaction abnormal alarm information.
In the embodiment of the invention, when a user needs to monitor transaction data, parameters such as required monitoring date, monitoring starting time, monitoring ending time and the like can be set, the parameters and the general query statement of the monitoring data are combined into the specified monitoring data query statement, the specified monitoring data query statement is used for querying the monitoring data in the target time interval, the quantity of abnormal data and the total quantity of the monitoring data are determined, and further whether transaction abnormal alarm information needs to be sent is determined. By the method, the abnormal conditions of the service in each target time period can be monitored and determined in time, and more transaction failure conditions can be found in time, so that the problem of transaction failure caused by staff in time can be conveniently solved, normal operation of subsequent transactions can be guaranteed, and user experience can be improved.
An embodiment of the present invention further provides a computer device, and fig. 5 is a schematic diagram of a computer device in an embodiment of the present invention, where the computer device is capable of implementing all steps in the service abnormality monitoring method in the embodiment, and the computer device specifically includes the following contents:
a processor (processor)501, a memory (memory)502, a communication Interface (Communications Interface)503, and a communication bus 504;
the processor 501, the memory 502 and the communication interface 503 complete mutual communication through the communication bus 504; the communication interface 503 is used for implementing information transmission between related devices;
the processor 501 is configured to call a computer program in the memory 502, and when the processor executes the computer program, the service exception monitoring method in the above embodiment is implemented.
The embodiment of the invention also provides a computer readable storage medium, which stores a computer program for executing the service anomaly monitoring method.
Fig. 6 is a schematic diagram of a system configuration of a computer device according to an embodiment of the present invention. As shown in fig. 6, the computer device 600 may include a processor 601 and a memory 602; a memory 602 is coupled to the processor 601. Notably, this FIG. 6 is exemplary; other types of structures may also be used in addition to or in place of the structure to implement telecommunications or other functions.
In one embodiment, the functions implemented by the traffic anomaly monitoring method may be integrated into the processor 601. Wherein the processor 601 may be configured to control as follows: acquiring a monitoring date, a monitoring start time and a monitoring end time, and a monitoring data general query statement; replacing corresponding variables in the general query statement of the monitoring data according to the monitoring date, the monitoring start time and the monitoring end time to obtain a specified monitoring data query statement; querying the abnormal data quantity and the total quantity of the monitoring data in a target time period from the monitoring data by using a specified monitoring data query statement, wherein the target time period is a time period from monitoring start time to monitoring end time in a set monitoring date; and determining whether to send out transaction abnormal alarm information according to the quantity of the abnormal data and the total quantity of the monitoring data.
As can be seen from the above, the computer device provided in the embodiment of the present invention obtains the monitoring date, the monitoring start time, the monitoring end time, and the general query statement for the monitoring data; replacing corresponding variables in the general query statement of the monitoring data according to the monitoring date, the monitoring start time and the monitoring end time to obtain a specified monitoring data query statement; querying the abnormal data quantity and the total quantity of the monitoring data in a target time period from the monitoring data by using a specified monitoring data query statement, wherein the target time period is a time period from monitoring start time to monitoring end time in a set monitoring date; and determining whether to send out transaction abnormal alarm information according to the quantity of the abnormal data and the total quantity of the monitoring data.
By the computer equipment provided by the embodiment of the invention, more transaction failures can be found in time, so that the problem of transaction failure caused by staff in time can be conveniently solved, the normal operation of subsequent transactions is ensured, and the user experience is improved.
In another embodiment, the service exception monitoring apparatus may be configured separately from the processor 601, for example, the service exception monitoring apparatus may be configured as a chip connected to the processor 601, and the function based on the service exception monitoring method may be implemented by the control of the processor.
As shown in fig. 6, the computer device 60 may further include: a communication module 603, an input unit 604, an audio processing unit 605, a display 606, a power supply 603. It is noted that the computer device 60 does not necessarily have to include all of the components shown in fig. 6; furthermore, the computer device 60 may also comprise components not shown in fig. 6, as can be seen in the prior art.
As shown in FIG. 6, processor 601, also sometimes referred to as a controller or operational control, may comprise a microprocessor or other processor device and/or logic device, which processor 601 receives input and controls the operation of the various components of computer device 60.
The memory 602 may be, for example, one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, or other suitable device. The information relating to the failure may be stored, and a program for executing the information may be stored. And the processor 601 may execute the program stored in the memory 602 to realize information storage or processing, or the like.
An input unit 604 provides input to the processor 601. The input unit 604 is, for example, a key or a touch input device. The power supply 603 is used to provide power to the computer device 60. The display 606 displays display objects such as images and characters. The display may be, for example, an LCD display, but is not limited thereto.
The memory 602 may be a solid state memory such as Read Only Memory (ROM), Random Access Memory (RAM), a SIM card, or the like. There may also be a memory that holds information even when power is off, can be selectively erased, and is provided with more data, an example of which is sometimes called an EPROM or the like. The memory 602 may also be some other type of device. Memory 602 includes buffer memory 6021 (sometimes referred to as a buffer). The memory 602 may include an application/function storage portion 6022 for storing application programs and function programs or a flow for executing the operation of the computer device 600 by the processor 601.
The memory 602 may also include a data store 6023 that stores data such as contacts, digital data, pictures, sounds, and/or any other data used by the computer device. The driver store 6024 of the memory 602 may include various drivers for the computer device for communication functions and/or for performing other functions of the computer device, such as messaging applications, address book applications, and the like.
The communication module 603 is a transmitter/receiver that transmits and receives signals via the antenna 608. A communication module (transmitter/receiver) 603 is coupled to the processor 601 to provide an input signal and receive an output signal, which may be the same as in the case of a conventional mobile communication terminal.
Based on different communication technologies, a plurality of communication modules 603, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, may be provided in the same computer device. The communication module (transmitter/receiver) 603 is also coupled to a speaker 609 and a microphone 610 via an audio processing unit 605 to provide audio output via the speaker 609 and to receive audio input from the microphone 610 to implement general telecommunications functions. The audio processing unit 605 may include any suitable buffers, decoders, amplifiers and so forth. In addition, audio processing unit 605 is also coupled to processor 601 so that locally stored sound can be recorded by microphone 610 and played by speaker 609.
An embodiment of the present invention further provides a computer-readable storage medium for implementing all the steps in the service anomaly monitoring method in the foregoing embodiment, where the computer-readable storage medium stores a computer program, and the computer program, when executed by a processor, implements all the steps in the service anomaly monitoring method in the foregoing embodiment, for example, when the processor executes the computer program, the processor implements the following steps: acquiring a monitoring date, a monitoring start time and a monitoring end time, and a monitoring data general query statement; replacing corresponding variables in the general query statement of the monitoring data according to the monitoring date, the monitoring start time and the monitoring end time to obtain a specified monitoring data query statement; querying the abnormal data quantity and the total quantity of the monitoring data in a target time period from the monitoring data by using a specified monitoring data query statement, wherein the target time period is a time period from monitoring start time to monitoring end time in a set monitoring date; and determining whether to send out transaction abnormal alarm information according to the quantity of the abnormal data and the total quantity of the monitoring data.
As can be seen from the above, the computer-readable storage medium provided in the embodiment of the present invention obtains the monitoring date, the monitoring start time, the monitoring end time, and the monitoring data general query statement; replacing corresponding variables in the general query statement of the monitoring data according to the monitoring date, the monitoring start time and the monitoring end time to obtain a specified monitoring data query statement; querying the abnormal data quantity and the total quantity of the monitoring data in a target time period from the monitoring data by using a specified monitoring data query statement, wherein the target time period is a time period from monitoring start time to monitoring end time in a set monitoring date; and determining whether to send out transaction abnormal alarm information according to the quantity of the abnormal data and the total quantity of the monitoring data.
By the computer-readable storage medium provided by the embodiment of the invention, more transaction failures can be found in time, so that a worker can timely deal with the problem of transaction failure, the normal operation of subsequent transactions is guaranteed, and the user experience is improved.
Although the present invention provides method steps as described in the examples or flowcharts, more or fewer steps may be included based on routine or non-inventive labor. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or client product executes, it may execute sequentially or in parallel (e.g., in the context of parallel processors or multi-threaded processing) according to the embodiments or methods shown in the figures.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, apparatus (system) or computer program product. Accordingly, embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment. In this document, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. The terms "upper", "lower", and the like, indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, and are only for convenience in describing the present invention and simplifying the description, but do not indicate or imply that the referred devices or elements must have a specific orientation, be constructed and operated in a specific orientation, and thus, should not be construed as limiting the present invention. Unless expressly stated or limited otherwise, the terms "mounted," "connected," and "connected" are intended to be inclusive and mean, for example, that they may be fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood by those skilled in the art according to specific situations. It should be noted that the embodiments and features of the embodiments may be combined with each other without conflict. The present invention is not limited to any single aspect, nor is it limited to any single embodiment, nor is it limited to any combination and/or permutation of these aspects and/or embodiments. Each aspect and/or embodiment of the invention can be used alone or in combination with one or more other aspects and/or embodiments.
The above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; such modifications and substitutions do not depart from the spirit and scope of the present invention, and they should be construed as being included in the following claims and description.

Claims (16)

1. A method for monitoring service exception is characterized in that the method comprises the following steps:
acquiring a monitoring date, a monitoring start time and a monitoring end time, and a monitoring data general query statement;
replacing corresponding variables in the general query statement of the monitoring data according to the monitoring date, the monitoring start time and the monitoring end time to obtain a specified monitoring data query statement;
querying the abnormal data quantity and the total quantity of the monitoring data in a target time period from the monitoring data by using a specified monitoring data query statement, wherein the target time period is a time period from monitoring start time to monitoring end time in a set monitoring date;
and determining whether to send out transaction abnormal alarm information according to the quantity of the abnormal data and the total quantity of the monitoring data.
2. The method of claim 1, wherein prior to obtaining the monitoring date, the monitoring start time, and the monitoring end time, and the monitoring data general query statement, the method further comprises:
when the abnormal service monitoring state is started, acquiring transaction data occurring in a preset time before the current moment at intervals of a preset time as monitoring data;
and recording the monitoring date, the monitoring starting time and the monitoring ending time of the monitoring data.
3. The method of claim 2, wherein after querying the monitoring data for the number of abnormal data and the total number of monitoring data in the target period using the specified monitoring data query statement, the method further comprises:
and changing the monitoring state of the abnormal service from starting to monitoring, wherein the monitoring is used for indicating that the number of abnormal data and the total number of the monitored data in the current monitored data are inquired.
4. The method of claim 3, wherein after determining whether to send out transaction abnormal alarm information according to the abnormal data quantity and the total monitoring data quantity, the method further comprises:
and if the transaction abnormity warning information is determined to be sent out, setting the service abnormity monitoring state to be closed, wherein in the closed state, the monitoring data is not acquired.
5. The method of claim 4, wherein after setting the traffic anomaly monitoring state to OFF, the method further comprises:
and when receiving a service abnormity monitoring command started by a user, setting the service abnormity monitoring state as start.
6. The method of claim 3, wherein after determining whether to send out transaction abnormal alarm information according to the abnormal data quantity and the total monitoring data quantity, the method further comprises:
and if the transaction abnormity warning information is determined not to be sent, setting the service abnormity monitoring state to be started.
7. The method according to any one of claims 1 to 6, wherein the determining whether to send out transaction abnormal alarm information according to the abnormal data quantity and the total monitoring data quantity comprises:
calculating the ratio of the number of the abnormal data to the total number of the monitoring data to be used as an abnormal proportion;
judging whether the abnormal proportion is larger than a preset alarm threshold value or not;
and if the abnormal proportion is larger than the alarm threshold value, sending out transaction abnormal alarm information.
8. A traffic anomaly monitoring apparatus, comprising:
the acquisition module is used for acquiring a monitoring date, a monitoring starting time and a monitoring ending time, and a monitoring data general query statement;
the query module is used for replacing corresponding variables in the universal query statement of the monitoring data according to the monitoring date, the monitoring start time and the monitoring end time to obtain a specified monitoring data query statement;
the query module is further used for querying the number of abnormal data and the total number of the monitoring data in a target time period from the monitoring data by using a specified monitoring data query statement, wherein the target time period is a time period from the monitoring start time to the monitoring end time in a set monitoring date;
and the determining module is used for determining whether to send out transaction abnormal alarm information according to the abnormal data quantity and the total quantity of the monitoring data.
9. The apparatus of claim 8,
the acquisition module is also used for acquiring transaction data occurring within a preset time before the current moment at intervals of a preset time when the abnormal service monitoring state is started, and taking the transaction data as monitoring data;
and the recording module is used for recording the monitoring date, the monitoring starting time and the monitoring ending time of the monitoring data.
10. The apparatus of claim 9, further comprising:
and the state changing module is used for changing the abnormal monitoring state of the service from the starting state to the monitoring state after the specified monitoring data query statement is used for querying the abnormal data quantity and the total quantity of the monitoring data in the target time period from the monitoring data, wherein the monitoring state is used for indicating that the abnormal data quantity and the total quantity of the monitoring data in the current monitoring data are queried.
11. The apparatus of claim 10, wherein the state change module is further configured to:
after determining whether to send out transaction abnormal alarm information according to the quantity of the abnormal data and the total quantity of the monitoring data, if the transaction abnormal alarm information is determined to be sent out, setting a service abnormal monitoring state to be closed, wherein in the closed state, the monitoring data are not obtained.
12. The apparatus of claim 11, wherein the state change module is further configured to:
after the monitoring state of the abnormal service is set to be closed, when a command for starting the monitoring state of the abnormal service by a user is received, the monitoring state of the abnormal service is set to be started.
13. The apparatus of claim 10, wherein the state change module is further configured to:
after determining whether to send out transaction abnormal alarm information according to the quantity of the abnormal data and the total quantity of the monitoring data, if determining not to send out the transaction abnormal alarm information, setting the monitoring state of the service abnormality to be started.
14. The apparatus according to any one of claims 8 to 13, wherein the determining means is configured to:
calculating the ratio of the number of the abnormal data to the total number of the monitoring data to be used as an abnormal proportion;
judging whether the abnormal proportion is larger than a preset alarm threshold value or not;
and if the abnormal proportion is larger than the alarm threshold value, sending out transaction abnormal alarm information.
15. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any one of claims 1 to 7 when executing the computer program.
16. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for executing the method of any one of claims 1 to 7.
CN202110446341.1A 2021-04-25 2021-04-25 Service abnormity monitoring method and device Pending CN113076333A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110446341.1A CN113076333A (en) 2021-04-25 2021-04-25 Service abnormity monitoring method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110446341.1A CN113076333A (en) 2021-04-25 2021-04-25 Service abnormity monitoring method and device

Publications (1)

Publication Number Publication Date
CN113076333A true CN113076333A (en) 2021-07-06

Family

ID=76618630

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110446341.1A Pending CN113076333A (en) 2021-04-25 2021-04-25 Service abnormity monitoring method and device

Country Status (1)

Country Link
CN (1) CN113076333A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115470229A (en) * 2022-08-30 2022-12-13 昆仑数智科技有限责任公司 Data table processing method and device, electronic equipment and storage medium

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115470229A (en) * 2022-08-30 2022-12-13 昆仑数智科技有限责任公司 Data table processing method and device, electronic equipment and storage medium

Similar Documents

Publication Publication Date Title
CN108549671B (en) Method and device for realizing real-time data acquisition and visualization
US8199900B2 (en) Automated performance monitoring for contact management system
CN103634149B (en) A kind of monitoring method for distributed system
US10241883B1 (en) Method and apparatus of establishing customized network monitoring criteria
US20230029544A1 (en) Custom data aggregation and integration processing
CN104967537A (en) Alarm information pushing method and device
EP3780700B1 (en) Power consumption anomaly prompting method, server, and terminal
CN105471932A (en) Front-end application monitoring method, front-end application and front-end application monitoring system
CN111740860A (en) Log data transmission link monitoring method and device
CN113076333A (en) Service abnormity monitoring method and device
CN110990222A (en) Cross-platform graphical operation monitoring method and device based on mainframe
CN109861843B (en) Method, device and equipment for completely collecting and confirming log files
CN110647417A (en) Energy internet abnormal data processing method, device and system
EP1622310A2 (en) Administration system for network management systems
CN111190761B (en) Log output method and device, storage medium and electronic equipment
US8442947B2 (en) Management of performance data
US20220278912A1 (en) Data Obtaining Method and Apparatus
CN109753399B (en) Automatic notification and response method for system unit state change
CN113835961B (en) Alarm information monitoring method, device, server and storage medium
CN112988867A (en) Supervision data sending method and device
CN112929191B (en) Service monitoring method, system, related equipment and device
CN109756351B (en) Automatic notification and response system for system unit state change
CN114595135A (en) Log data processing method, device, equipment, storage medium and program product
CN112764992A (en) Thread pool monitoring method, device and equipment
CN111459115A (en) Information management method, manufacturing execution system, electronic device, and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination