CA3141565A1 - Method and system for automatically monitoring business systems - Google Patents
Method and system for automatically monitoring business systems Download PDFInfo
- Publication number
- CA3141565A1 CA3141565A1 CA3141565A CA3141565A CA3141565A1 CA 3141565 A1 CA3141565 A1 CA 3141565A1 CA 3141565 A CA3141565 A CA 3141565A CA 3141565 A CA3141565 A CA 3141565A CA 3141565 A1 CA3141565 A1 CA 3141565A1
- Authority
- CA
- Canada
- Prior art keywords
- monitoring
- inspection
- business
- configuration
- service
- 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
Links
- 238000012544 monitoring process Methods 0.000 title claims abstract description 74
- 238000000034 method Methods 0.000 title claims abstract description 29
- 238000007689 inspection Methods 0.000 claims abstract description 90
- 230000035945 sensitivity Effects 0.000 claims description 14
- 238000013507 mapping Methods 0.000 claims description 8
- 238000013024 troubleshooting Methods 0.000 claims description 5
- 230000002159 abnormal effect Effects 0.000 claims description 4
- 238000012795 verification Methods 0.000 claims description 4
- 230000001960 triggered effect Effects 0.000 claims description 2
- 230000005856 abnormality Effects 0.000 abstract description 4
- 238000012423 maintenance Methods 0.000 description 6
- 230000001419 dependent effect Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/50—Testing arrangements
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Debugging And Monitoring (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
A method and a system for automatically monitoring business systems are disclosed. The method includes: automatically collecting dependency property information of a business system through JAR packages of a monitoring and inspecting component and reporting the dependency property information to a service end; after the service end configures the relevant business system according to the dependency property information, automatically generating inspection case tasks and issuing the inspection case tasks to the monitoring and inspecting component; executing the inspection case tasks and reporting inspection results by the monitoring and inspecting component; and locating problems and giving alerts by the service end according to the inspection results. The method and the system solve the technical problems raised from complexity and ineffectiveness in recognizing and locating abnormalities of business services as seen in existing methods for monitoring business systems.
Description
METHOD AND SYSTEM FOR AUTOMATICALLY MONITORING BUSINESS
SYSTEMS
BACKGROUND OF THE INVENTION
Technical Field [0001] The present invention relates to the technical field of E-business, and more particularly to a method and a system for automatically monitoring business systems.
Description of Related Art
SYSTEMS
BACKGROUND OF THE INVENTION
Technical Field [0001] The present invention relates to the technical field of E-business, and more particularly to a method and a system for automatically monitoring business systems.
Description of Related Art
[0002] In early days where systems are of relatively small scales, maintenance and operation of these systems mainly relied on manual processing of maintenance and operation staff. With the rapid growth of business and increasing diverseness of services, building networks has become more and more complicated. A single system may involve multiple devices and need to deploy plural instances, making manual checking and locating problems by maintenance and operation staff become more difficult and more inefficient. Increase of the number of devices also means that communication between maintenance and operation teams are becoming costly. Since various logs and alerts are distributed over different devices, checking statistical data and then prompting relevant businesses to take action are time- and effort-consuming.
[0003] The traditional business systems lack for a consistent monitoring solution, and usually rely on third-party systems for measurement of various indicators, making it complicated for businesses to adopt. Besides, since its indicator monitoring data and alert-related configuration are scattered over different systems, though such known systems can configure several monitoring alerts, it is difficult for them to see the root causes of problems and to estimate affected ranges. Additionally, even if such known systems give alerts, the alert information is nevertheless too blurred for maintenance and operation staff to locate problems directly. In this case, businesses have to check all the suspected part one by one, making troubleshooting time-and effort-consuming.
[0004] Hence, there is a pressing need for a method or a system that is easy to adopt and can provide business systems with automated inspection to fast identify problems.
Date recue / Date received 2021-12-09 SUMMARY OF THE INVENTION
Date recue / Date received 2021-12-09 SUMMARY OF THE INVENTION
[0005] To address the defects of the prior art, the objective of the present invention is to provide a method and a system for automatically monitoring business systems that solve the technical problems raised from complexity and ineffectiveness in recognizing and locating abnormalities of business services as seen in existing methods for monitoring business systems.
[0006] In a first aspect, the present invention provides a method for automatically monitoring business systems. The method comprises: automatically collecting dependency property information of a business system through JAR packages of a monitoring and inspecting component and reporting the dependency property information to a service end;
[0007] after the service end configures the relevant business system according to the dependency property information, automatically generating inspection case tasks and issuing the inspection case tasks to the monitoring and inspecting component;
[0008] executing the inspection case tasks and reporting inspection results by the monitoring and inspecting component; and
[0009] locating problems and giving alerts by the service end according to the inspection results.
[0010] Further, the configuration comprises: custom configuration of business system cases, configuration of user access authority, configuration of sensitivity of early warning and alerts, and configuration of inspection task strategies.
[0011] Further, the monitoring and inspecting component according to different business system services, configures different parameters and task strategies and performs task scheduling on the monitoring and inspecting component, the monitoring and inspecting component periodically executes inspection case tasks.
[0012] Further, the custom configuration of business system cases comprises mapping rules for inspection tasks, and service names of service machines are acquired through the mapping rules, thereby locating inspected abnormal services.
[0013] Further, the service end actively gives troubleshooting instructions to business nodes determined as having failures, so as to acquire information required by relevant troubleshooting, Date recue / Date received 2021-12-09 which includes acquiring memory dump documents and acquiring JVM thread running states.
[0014] Further, the service end provides component expansion service ports.
According to different business system services, the service end provides parameters to configure the component expansion service ports and control a monitoring and inspecting component to monitor different case tasks.
According to different business system services, the service end provides parameters to configure the component expansion service ports and control a monitoring and inspecting component to monitor different case tasks.
[0015] Further, for indicator-type inspection results, calculation is made based on baseline values from historical inspections and the configured sensitivity so as to determine whether an early warning and an alert are to be triggered.
[0016] Further, and for middleware-type inspection results, fault sources are identified by means of multi-machine cross inspection.
[0017] Further, the monitoring and inspecting component further verifies a post-alert processed business problem, and, after verification, gives a feedback instruction to the service end, to make the service end cancel the early warning or the alert for the business problem.
[0018] In another aspect, the present invention provides a system for automatically monitoring business systems. The system comprises:
[0019] a monitoring and inspecting component, automatically collecting dependency property information of a business system through component JAR packages and reporting the dependency property information to a configuration service module, executing inspection case tasks issued by the configuration service module, and reporting inspection results; and
[0020] the configuration service module, configuring relevant business systems according to the dependency property information, generating the inspection case tasks issued to the monitoring and inspecting component, and receiving the inspection results reported by the monitoring and inspecting component so as to locate problems and give an alert.
[0021] Further, the system further comprises: inspection query module, for making queries for inspection case information according to a query interface provided by the configuration service module.
[0022] As compared to the prior art, the method and system for automatically monitoring business systems of the present invention accomplish the following technical effects:
[0023] Adoption is easy and less intrusive to existing business systems, and only needs Date recue / Date received 2021-12-09 introducing JAR packages of the component, by which information related to service-dependency link properties can be automatically collected and reported to the service end through the JAR packages of the introduced component.
[0024] 2. The present invention supports custom inspection tasks, and is capable of issuing operational states of the process nodes processed by the business system itself in a quasi-real-time manner, and accurately identifies which process node has failure and underlying reason according to predetermined rules.
[0025] 3. By using system sensitivity parameters as the benchmark values for early warning and alerts, the present invention eliminates the need of separate configuration of thresholds for early warning and alerts, while enhancing accuracy of early warning and alerts, thereby reducing the risk of false positives.
BRIEF DESCRIPTION OF THE DRAWINGS
BRIEF DESCRIPTION OF THE DRAWINGS
[0026] FIG. 1 is a flowchart of a method for automatically monitoring business systems according to one embodiment of the present invention.
[0027] FIG. 2 is a structural diagram of a system for automatically monitoring business systems according to one embodiment of the present invention.
DETAILED DESCRIPTION OF THE INVENTION
DETAILED DESCRIPTION OF THE INVENTION
[0028] The following description details some embodiments of the present invention, and illustrations of these embodiments are shown in the accompanying drawings.
Therein, the embodiments described with reference to the drawings are exemplary and intended to explain the present invention, and shall by no means be understood as limitation to the present invention.
Therein, the embodiments described with reference to the drawings are exemplary and intended to explain the present invention, and shall by no means be understood as limitation to the present invention.
[0029] FIG. 1 is a flowchart of a method for automatically monitoring business systems according to one embodiment of the present invention.
[0030] As shown in FIG. 1, a method for automatically monitoring business systems comprises the following steps.
[0031] The step Si 1 involves automatically collecting dependency property information of a Date recue / Date received 2021-12-09 business system through JAR packages of a monitoring and inspecting component and reporting the dependency property information to a service end.
[0032] In a business system, the monitoring and inspecting component are introduced for collecting dependency service link property information through JAR packages, and reporting the dependency property information to a service end. The existing solutions for business monitoring, system monitoring, and custom monitoring have to connect multiple client ends, and have to be upgraded separately with the upgrading of these client ends, so the operation is relatively complicated. The present invention uses a single component that can be easily introduced into business systems in a consistent, less-intrusive manner, thereby eliminating the need of additional configuration of information related to service-dependent link properties of system at the business system. Instead, adoption can be simply accomplished using JAR
packages of the monitoring and inspecting component. The JAR packages, designed as plug-in elements, support not only business monitoring but also support system monitoring and custom expansion monitoring. Therein, the dependency property information specifically refers to two things, namely dependency services and property information. The dependency services mainly refer to information of data exchange between the present system and the exterior, including databases, caches, and external system ports accessed. The property information refers to information of addresses or authorization required by linking to databases, such as domain names, IP addresses, ports, instance names, and URLs of services. These details will be sent to the service end for storage. The monitoring and inspecting component, based on agreed rules, automatically detects systems, services, and middleware, including Java virtual machines, and Docker containers. For example, it recognizes whether MySQL, Redis, or MQ is used, initiates linking according to its property information, and regularly performs instructions about default detection.
packages of the monitoring and inspecting component. The JAR packages, designed as plug-in elements, support not only business monitoring but also support system monitoring and custom expansion monitoring. Therein, the dependency property information specifically refers to two things, namely dependency services and property information. The dependency services mainly refer to information of data exchange between the present system and the exterior, including databases, caches, and external system ports accessed. The property information refers to information of addresses or authorization required by linking to databases, such as domain names, IP addresses, ports, instance names, and URLs of services. These details will be sent to the service end for storage. The monitoring and inspecting component, based on agreed rules, automatically detects systems, services, and middleware, including Java virtual machines, and Docker containers. For example, it recognizes whether MySQL, Redis, or MQ is used, initiates linking according to its property information, and regularly performs instructions about default detection.
[0033] At the step S12, the method involves, after the service end configures the relevant business system according to the dependency property information, automatically generating inspection case tasks and issuing the inspection case tasks to the monitoring and inspecting component.
[0034] The monitoring component sends the dependency property information of individual Date recue / Date received 2021-12-09 business systems collected in a real-time manner to the service end. After receiving the dependency property information from the monitoring and inspecting component, the service end first verifies consistency. The latest information received by the service end is compared with the previously stored information, and if the information is about a newly added dependency service link, updating is performed at the service end, such as updating the IP
address of a database. After verification, the relevant business system is configured. With the received service link property information of an introduced system, the service end can learn what are the services the system depends on, and generate corresponding inspection cases according to these services.
address of a database. After verification, the relevant business system is configured. With the received service link property information of an introduced system, the service end can learn what are the services the system depends on, and generate corresponding inspection cases according to these services.
[0035] The configuration as described above comprises: custom configuration of business system cases, configuration of sensitivity of early warning and alerts, access authority configuration of the systems, and inspection strategies of the monitoring and inspecting component, etc. Therein, different business service ports are configured with different contents.
[0036] The custom configuration is mainly about configuring services, ports, or local business code logics designated to be inspected by the relevant business system, so as to achieve custom inspection. Therein, the custom configuration further covers mapping rules of different business services, separation into standalone machines according to rules, and their service names.
Depending on business service ports, different parameters can be configured.
For example, the parameters required by a money-transfer port include two test bank account numbers and the amount to be transferred, etc. The parameters required by an order query service port include a user ID, and start and end time. Through these configuration operations, the subsequent detection queries and information feedback for the monitoring and inspecting component are facilitated.
The sensitivity configuration for early warning and alerts is about setting different sensitivity for different business systems according to practical needs, with the aim to reduce false positives in subsequent determination, and particularly effective to determination for indicator-type results.
The access authority configuration for the system is about setting access authorities of maintenance and operation staff. The inspection strategies provide the combinations of inspection items of different business types and the inspection frequencies for the monitoring and inspecting component to perform inspection. For example, in order to check whether a Date recue / Date received 2021-12-09 certain system is normal, inspection for all items may be set as being performed automatically at a set interval, and cross inspection may be also set.
Depending on business service ports, different parameters can be configured.
For example, the parameters required by a money-transfer port include two test bank account numbers and the amount to be transferred, etc. The parameters required by an order query service port include a user ID, and start and end time. Through these configuration operations, the subsequent detection queries and information feedback for the monitoring and inspecting component are facilitated.
The sensitivity configuration for early warning and alerts is about setting different sensitivity for different business systems according to practical needs, with the aim to reduce false positives in subsequent determination, and particularly effective to determination for indicator-type results.
The access authority configuration for the system is about setting access authorities of maintenance and operation staff. The inspection strategies provide the combinations of inspection items of different business types and the inspection frequencies for the monitoring and inspecting component to perform inspection. For example, in order to check whether a Date recue / Date received 2021-12-09 certain system is normal, inspection for all items may be set as being performed automatically at a set interval, and cross inspection may be also set.
[0037] After custom configuration of inspection tasks of business systems, the disclosed system can automatically generate inspection case tasks based on the set inspection rules and task strategies, and issue the inspection case tasks to the monitoring and inspecting component.
[0038] Therein, the set rules can be briefed as below:
1) The Jar packages of the monitoring and inspecting components automatically acquire JNDI name of a database, and automatically partition and extract a read JNDI and a write JNDI according to the abbreviation of the relevant system and JNDI naming rules, automatically. For example, assuming that the system abbreviation is pgmcms, the corresponding reading and writing JNDI are:
pgmcmsRDS and pgmcmsWDS, respectively. The contents extracted from the petitioning rules are: pgmcmsRDS 1, pgmcmsRDS 2, .........................
and pgmcmsWDS 1, pgmcmsWDS 2, ..............................................................
After the data source is determined, the dependent default verification SQL is performed according to the database type. For example, SELECT VERSION() is for MySQL, and SELECT*FROM DUAL is for ORACLE.
2) The Jar packages of the monitoring and inspecting components automatically acquire the redis sharding name, and configure familiar information such as links in documents and keys according to the abbreviation of the relevant system and Redis redis.conf. For example, assuming that the system abbreviation is pgmcms, the corresponding redis sharding is pgmcms 1, pgmcms 2, .....
1) The Jar packages of the monitoring and inspecting components automatically acquire JNDI name of a database, and automatically partition and extract a read JNDI and a write JNDI according to the abbreviation of the relevant system and JNDI naming rules, automatically. For example, assuming that the system abbreviation is pgmcms, the corresponding reading and writing JNDI are:
pgmcmsRDS and pgmcmsWDS, respectively. The contents extracted from the petitioning rules are: pgmcmsRDS 1, pgmcmsRDS 2, .........................
and pgmcmsWDS 1, pgmcmsWDS 2, ..............................................................
After the data source is determined, the dependent default verification SQL is performed according to the database type. For example, SELECT VERSION() is for MySQL, and SELECT*FROM DUAL is for ORACLE.
2) The Jar packages of the monitoring and inspecting components automatically acquire the redis sharding name, and configure familiar information such as links in documents and keys according to the abbreviation of the relevant system and Redis redis.conf. For example, assuming that the system abbreviation is pgmcms, the corresponding redis sharding is pgmcms 1, pgmcms 2, .....
[0039] By setting rule examples, accurate problem locating can be realized.
Assuming that 5 databases (each machine is installed with a database) provide a VIP outgoing service, it is impossible to tell the database having problems is on which machine by directly inspecting VIP.
Therefore, the names of service provided on the individual machines have to be found according to the VIP service names. This process is achieved using the mapping rules.
Without rule mapping, inspection can only depend on domain names known to the public. In this case, even if it is certain that there are problems, it is impossible to tell the faulty machine from all the machines providing services to the site having that domain name.
Date recue / Date received 2021-12-09
Assuming that 5 databases (each machine is installed with a database) provide a VIP outgoing service, it is impossible to tell the database having problems is on which machine by directly inspecting VIP.
Therefore, the names of service provided on the individual machines have to be found according to the VIP service names. This process is achieved using the mapping rules.
Without rule mapping, inspection can only depend on domain names known to the public. In this case, even if it is certain that there are problems, it is impossible to tell the faulty machine from all the machines providing services to the site having that domain name.
Date recue / Date received 2021-12-09
[0040] The set task strategies can be briefed as below:
[0041] The monitoring and inspecting component automatically generates a time interval of inspection according to the level of the relevant business system (e.g., Level 1, 2, or 3, in which Level 1 has the top priority, and when a Level 1 system has problems, the service provision is interrupted) and whether the relevant system is on a core link. Therein, the default inspection interval is the mean of intervals of inspections of the connected systems having the same system level, the same link, and the same inspection task dimensions. The inspection intervals may be customly configured at the service end.
[0042] In addition, the service end further performs task scheduling on the monitoring and inspecting component, so as to control plural monitoring and inspecting components to conduct inspections for different task instances. The task scheduling mainly includes:
1. The monitoring and inspecting component is loaded with all available case tasks of the introduced system, and executes them at a set frequency; and 2. the service end may alternatively initiate a case inspection on a certain machine in the business system, or it may initiate case inspections on all the machines in this system. Since the service end further provides component expansion service ports allowing introduce of different business systems and provision of services of various types, the only thing has to be done at this time is to issue new parameters through the ports or adjust parameters and reschedule tasks, so that operations of different business services can be easily recognized.
1. The monitoring and inspecting component is loaded with all available case tasks of the introduced system, and executes them at a set frequency; and 2. the service end may alternatively initiate a case inspection on a certain machine in the business system, or it may initiate case inspections on all the machines in this system. Since the service end further provides component expansion service ports allowing introduce of different business systems and provision of services of various types, the only thing has to be done at this time is to issue new parameters through the ports or adjust parameters and reschedule tasks, so that operations of different business services can be easily recognized.
[0043] In the step S13, the monitoring and inspecting component executes an inspection task and reports inspection result.
[0044] The monitoring and inspecting component executes an inspection case and reports the results of its execution of this case through RESTFUL. RESTFUL is connected to different services through ports defined in advance, and thus features excellent capability of expansion.
When a depend service inspection reveals abnormality, it is natural to accurately tell which is the problematic dependency service. For example, when Redis has a fault, the inspecting component will inform the service end of which machine has problems about Redis services or is unable to connect link. When the inspecting component finds early warning about abnormality of a JVM (java virtual machine), such as early warning for memory usage, the inspection Date recue / Date received 2021-12-09 component can automatically generate a dump document for memory usage, thereby facilitating fasting locating the problems. Objects of inspections may be usability inspection of an entire cluster, or may be services of service of every machine in a cluster.
When a depend service inspection reveals abnormality, it is natural to accurately tell which is the problematic dependency service. For example, when Redis has a fault, the inspecting component will inform the service end of which machine has problems about Redis services or is unable to connect link. When the inspecting component finds early warning about abnormality of a JVM (java virtual machine), such as early warning for memory usage, the inspection Date recue / Date received 2021-12-09 component can automatically generate a dump document for memory usage, thereby facilitating fasting locating the problems. Objects of inspections may be usability inspection of an entire cluster, or may be services of service of every machine in a cluster.
[0045] At the step S14, the service end according to inspection results locates the problem and give alerts.
[0046] The service end according to the cases reported in a real-time manner executes and store log information, and gives alerts. Specifically, the service end analyzes the log of inspection results, and calculates early warning and alerts according to sensitivity settings of individual business systems. The results are them sent to the user. Besides, the service end can further accurately locate problems. With the previously set rules, the specific machine providing some certain service can be identified through mapping, so that it is possible to accurately locate which machine is the one having failure.
[0047] Another example is about middleware-type inspection results. Herein, multi-machine cross inspection is performed on middleware to identify the final fault source. For example, when three JBOSS machines are separately inspected for database usability, if two of them are normal and the other one is abnormal, it can be certain that the abnormal JBOSS machine has problems.
[0048] A further example is about indicator-type inspection results. To inspect indicators such as memory usage or threads, the baseline values based on historical inspections and the sensitivity level set at the system are combined to get criteria for giving early warning and alerts.
For example, assuming that the baseline value of memory usage is 60%, and the sensitivity level set for the system is 0.3, early warning will be issued when the memory usage reaches 78%.
Different systems may have different sensitivity levels to errors. By introducing system sensitivity parameters as basic values for early warning and alerts, the need of directly configuring thresholds for early warning and alerts is eliminated, and the accuracy of early warning and alerts is improved, with reduced false positives.
For example, assuming that the baseline value of memory usage is 60%, and the sensitivity level set for the system is 0.3, early warning will be issued when the memory usage reaches 78%.
Different systems may have different sensitivity levels to errors. By introducing system sensitivity parameters as basic values for early warning and alerts, the need of directly configuring thresholds for early warning and alerts is eliminated, and the accuracy of early warning and alerts is improved, with reduced false positives.
[0049] Referring to FIG. 2, another embodiment of the present invention provides a system for automatically monitoring business systems. The system comprises:
[0050] a monitoring and inspecting component, automatically collecting dependency property Date recue / Date received 2021-12-09 information of a business system through component JAR packages and reporting the dependency property information to a configuration service module, executing inspection case tasks issued by the configuration service module, and reporting inspection results; and
[0051] the configuration service module, configuring relevant business systems according to the dependency property information, generating the inspection case tasks issued to the monitoring and inspecting component, and receiving the inspection results reported by the monitoring and inspecting component so as to locate problems and give an alert. In addition, the configuration service module further stores configuration information and inspection result records of the individual business systems.
[0052] There is also an inspection query module for making queries for inspection case information according to a query interface provided by the configuration service module. The queries may include queries for alert notification information, inspection records, and analysis records.
[0053] The disclosed system may be introduced through simulating a monitoring and inspecting component in a business system, while expanding custom inspection case configuration and system sensitivity setting. Then the information of results of the inspection cases of the business system can be reported through the monitoring and inspecting component in a real-time manner, for the disclosed system to analyze the result information, thereby accurately detecting whether any business inspected needs early warning or alert.
[0054] The present invention has been described with reference to the preferred embodiments and it is understood that the embodiments are not intended to limit the scope of the present invention. Moreover, as the contents disclosed herein should be readily understood and can be implemented by a person skilled in the art, all equivalent changes or modifications which do not depart from the concept of the present invention should be encompassed by the appended claims.
Hence, the scope of the present invention shall only be defined by the appended claims.
Date recue / Date received 2021-12-09
Hence, the scope of the present invention shall only be defined by the appended claims.
Date recue / Date received 2021-12-09
Claims (10)
1. A method for automatically monitoring business systems, the method comprising:
automatically collecting dependency property information of a business system through JAR
packages of a monitoring and inspecting component and reporting the dependency property information to a service end;
after the service end configures the relevant business system according to the dependency property information, automatically generating inspection case tasks and issuing the inspection case tasks to the monitoring and inspecting component;
executing the inspection case tasks and reporting inspection results by the monitoring and inspecting component; and locating problems and giving alerts by the service end according to the inspection results.
automatically collecting dependency property information of a business system through JAR
packages of a monitoring and inspecting component and reporting the dependency property information to a service end;
after the service end configures the relevant business system according to the dependency property information, automatically generating inspection case tasks and issuing the inspection case tasks to the monitoring and inspecting component;
executing the inspection case tasks and reporting inspection results by the monitoring and inspecting component; and locating problems and giving alerts by the service end according to the inspection results.
2. The method of claim 1, wherein the configuration comprises: custom configuration of business system cases, configuration of user access authority, configuration of sensitivity of early warning and alerts, and configuration of inspection task strategies.
3. The method of claim 2, wherein the monitoring and inspecting component according to different business system services, configures different parameters and task strategies and performs task scheduling on the monitoring and inspecting component, the monitoring and inspecting component periodically executes inspection case tasks.
4. The method of claim 2 or 3, wherein the custom configuration of business system cases Date recue / Date received 2021-12-09 comprises mapping rules for inspection tasks, and service names of service machines are acquired through the mapping rules, thereby locating inspected abnormal services.
The method of claim 4, wherein the service end actively gives troubleshooting instructions to business nodes determined as having failures, so as to acquire information required by relevant troubleshooting, which includes acquiring memory dump documents and acquiring JVM thread running states.
6. The method of claim 3, wherein the service end further provides component expansion service ports.
7. The method of claim 4, wherein for indicator-type inspection results, calculation is made based on baseline values from historical inspections and the configured sensitivity so as to determine whether an early warning and an alert are to be triggered; and for middleware-type inspection results, fault sources are identified by means of multi-machine cross inspection.
8. The method of claim 4, wherein the monitoring and inspecting component further verifies a post-alert processed business problem, and, after verification, gives a feedback instruction to the service end, to make the service end cancel the early warning or the alert for the business problem.
9. A system for automatically monitoring business systems, the system comprising:
a monitoring and inspecting component, automatically collecting dependency property information of a business system through component JAR packages and reporting the dependency property information to a configuration service module, executing inspection case tasks issued by the configuration service module, and reporting inspection results; and the configuration service module, configuring relevant business systems according to the dependency property information, generating the inspection case tasks issued to the monitoring Date recue / Date received 2021-12-09 and inspecting component, and receiving the inspection results reported by the monitoring and inspecting component so as to locate problems and give an alert.
a monitoring and inspecting component, automatically collecting dependency property information of a business system through component JAR packages and reporting the dependency property information to a configuration service module, executing inspection case tasks issued by the configuration service module, and reporting inspection results; and the configuration service module, configuring relevant business systems according to the dependency property information, generating the inspection case tasks issued to the monitoring Date recue / Date received 2021-12-09 and inspecting component, and receiving the inspection results reported by the monitoring and inspecting component so as to locate problems and give an alert.
10. The system of claim 9, further comprising: an inspection query module, for making queries for inspection case information according to a query interface provided by the configuration service module.
Date recue / Date received 2021-12-09
Date recue / Date received 2021-12-09
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011447412.1A CN112615737B (en) | 2020-12-09 | 2020-12-09 | Method and system for automatically monitoring service system |
| CN202011447412.1 | 2020-12-09 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA3141565A1 true CA3141565A1 (en) | 2022-06-09 |
Family
ID=75233408
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA3141565A Pending CA3141565A1 (en) | 2020-12-09 | 2021-12-09 | Method and system for automatically monitoring business systems |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112615737B (en) |
| CA (1) | CA3141565A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115378831A (en) * | 2022-08-19 | 2022-11-22 | 中国建设银行股份有限公司 | Monitoring method and device for message middleware server |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114118991A (en) * | 2021-11-12 | 2022-03-01 | 百果园技术(新加坡)有限公司 | Third-party system monitoring system, method, device, equipment and storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107195013A (en) * | 2017-05-11 | 2017-09-22 | 国网山东省电力公司信息通信公司 | The O＆M automation method for inspecting and its system of a kind of fine granularity control |
| CN108665237B (en) * | 2018-05-03 | 2022-05-13 | 广东电网有限责任公司广州供电局 | Method for establishing automatic inspection model and positioning abnormity based on business system |
| CN111262732A (en) * | 2020-01-11 | 2020-06-09 | 上海南洋万邦软件技术有限公司 | MSP customer-oriented public cloud resource automatic inspection system |
-
2020
- 2020-12-09 CN CN202011447412.1A patent/CN112615737B/en active Active
-
2021
- 2021-12-09 CA CA3141565A patent/CA3141565A1/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115378831A (en) * | 2022-08-19 | 2022-11-22 | 中国建设银行股份有限公司 | Monitoring method and device for message middleware server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112615737B (en) | 2023-06-09 |
| CN112615737A (en) | 2021-04-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA3141565A1 (en) | Method and system for automatically monitoring business systems | |
| US20160292028A1 (en) | Preventing and servicing system errors with event pattern correlation | |
| CN107807877B (en) | Code performance testing method and device | |
| US8661125B2 (en) | System comprising probe runner, monitor, and responder with associated databases for multi-level monitoring of a cloud service | |
| CN110362473B (en) | Test environment optimization method and device, storage medium and terminal | |
| US7814369B2 (en) | System and method for detecting combinations of perfomance indicators associated with a root cause | |
| KR20180077948A (en) | Interface Middleware System for Smart Factory Platform and Method for Operating The Same | |
| WO2021114971A1 (en) | Method for detecting whether application system based on multi-tier architecture operates normally | |
| WO2008124214A1 (en) | System and method of data harvesting | |
| KR20070080313A (en) | Method and system for analyzing performance of providing services to client terminal | |
| CN108804326A (en) | A kind of software code automatic testing method | |
| CN116719664B (en) | Application and cloud platform cross-layer fault analysis method and system based on micro-service deployment | |
| US8005638B1 (en) | Distributed test system and method | |
| US7137041B2 (en) | Methods, systems and computer program products for resolving problems in an application program utilizing a situational representation of component status | |
| US8554908B2 (en) | Device, method, and storage medium for detecting multiplexed relation of applications | |
| US7500144B2 (en) | Resolving problems in a business process utilizing a situational representation of component status | |
| US9397921B2 (en) | Method and system for signal categorization for monitoring and detecting health changes in a database system | |
| US8949669B1 (en) | Error detection, correction and triage of a storage array errors | |
| CN110874311A (en) | Database detection method and device, computer equipment and storage medium | |
| US20100251029A1 (en) | Implementing self-optimizing ipl diagnostic mode | |
| US11675647B2 (en) | Determining root-cause of failures based on machine-generated textual data | |
| CN112668159A (en) | Troubleshooting method and device based on improved FMEA system log file | |
| CN108197717B (en) | Equipment maintenance system and method signal-based | |
| CN109033446A (en) | Corrosion type method of discrimination and device | |
| JP5974905B2 (en) | Response time monitoring program, method, and response time monitoring apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request |
Effective date: 20220916 |
|
| EEER | Examination request |
Effective date: 20220916 |
|
| EEER | Examination request |
Effective date: 20220916 |
|
| EEER | Examination request |
Effective date: 20220916 |
|
| EEER | Examination request |
Effective date: 20220916 |