CN109726072B - WebLogic server monitoring and alarming method, device and system and computer storage medium - Google Patents
WebLogic server monitoring and alarming method, device and system and computer storage medium Download PDFInfo
- Publication number
- CN109726072B CN109726072B CN201810800086.4A CN201810800086A CN109726072B CN 109726072 B CN109726072 B CN 109726072B CN 201810800086 A CN201810800086 A CN 201810800086A CN 109726072 B CN109726072 B CN 109726072B
- Authority
- CN
- China
- Prior art keywords
- monitoring
- alarm
- template
- host
- monitoring template
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
Abstract
The invention provides a monitoring and alarming method of a WebLogic server, which is applied to a monitoring and alarming system, the system comprises a monitoring host, a data acquisition host and a plurality of WebLogic servers, and the method comprises the following steps: when the monitoring host receives the monitoring instruction, acquiring a performance index of a corresponding WebLogic server through the data acquisition host according to the monitoring instruction; determining a corresponding monitoring template according to the monitoring instruction, calculating and integrating the performance indexes through the monitoring template, and detecting whether the performance indexes after calculation and integration meet corresponding preset alarm rules; and if the performance indexes after calculation and integration meet the corresponding preset alarm rules, carrying out alarm reminding. The invention also provides a monitoring and warning device, a monitoring and warning system and a computer storage medium of the WebLogic server. The invention can simplify the monitoring deployment of the WebLogic server and improve the timeliness of abnormal monitoring and alarming.
Description
Technical Field
The invention relates to the technical field of monitoring and alarming of a WebLogic server, in particular to a monitoring and alarming method, a monitoring and alarming device, a monitoring and alarming system and a computer storage medium of the WebLogic server.
Background
WebLogic is a Java application server used for developing, integrating, deploying and managing large-scale distributed Web application, network application and database application, can introduce the dynamic function of Java and the security of Java Enterprise standard into the development, integration, deployment and management of large-scale network application, has the advantages of simple and convenient development, strong expandability, higher flexibility and reliability and the like, and is one of the best J2EE (Java 2 Platform Enterprise Edition ) tools in the current market.
In the WebLogic system, the application program is deployed on a large number of WebLogic servers, and therefore, the running state of the WebLogic server may directly affect the service acceptance of the foreground service. Therefore, anomaly monitoring for WebLogic servers is important. At present, when monitoring WebLogic servers, monitoring of the WebLogic servers can be realized only by configuring corresponding monitoring modules on the WebLogic servers, and the deployment is complex. In addition, when a worker wants to monitor whether a certain WebLogic server operates abnormally, the worker needs to check corresponding monitoring data on the corresponding WebLogic server to judge whether the abnormality occurs, so that the worker often cannot find the abnormality of the WebLogic server in time. Therefore, in the prior art, the WebLogic server is complex in monitoring and deployment, and meanwhile, the problem that abnormal monitoring and alarming are not timely exists.
Disclosure of Invention
The invention mainly aims to provide a monitoring and alarming method, a monitoring and alarming device, a monitoring and alarming system and a computer storage medium of a WebLogic server, and aims to improve the timeliness of abnormal monitoring and alarming while simplifying the monitoring and deployment of the WebLogic server.
In order to achieve the above object, the present invention provides a monitoring and warning method for a WebLogic server, which is applied to a monitoring and warning system, wherein the monitoring and warning system includes a monitoring host, a data acquisition host and a plurality of middleware WebLogic servers, the monitoring host is in communication connection with the data acquisition host, the data acquisition host is in communication connection with the plurality of WebLogic servers, respectively, and the method includes:
when the monitoring host receives a monitoring instruction, acquiring a performance index of a corresponding WebLogic server through the data acquisition host according to the monitoring instruction;
the monitoring host determines a corresponding monitoring template according to the monitoring instruction, calculates and integrates the performance index through the monitoring template, and detects whether the performance index after calculation and integration meets a corresponding preset alarm rule;
and if the performance indexes after calculation and integration meet the corresponding preset alarm rules, the monitoring host carries out alarm reminding.
Optionally, the monitoring templates include a Java virtual machine central processing unit JVM CPU utilization monitoring template, a Java database connection JDBC connection number monitoring template, a blocking thread monitoring template, an abnormal request amount monitoring template, a garbage collection GC monitoring template, and a slow request monitoring template.
Optionally, the step of calculating and integrating the performance index through the monitoring template, and detecting whether the performance index after calculation and integration meets the corresponding preset alarm rule includes:
if the monitoring template is a JVM CPU utilization monitoring template, or a JDBC connection number monitoring template, or a blocked thread monitoring template, or an abnormal request quantity monitoring template, or a GC monitoring template, calculating an average value of corresponding indexes in the performance indexes within a preset time through the monitoring template, and detecting whether the average value is greater than a corresponding first preset threshold value;
if the performance index after calculation and integration meets the corresponding preset alarm rule, the monitoring host carries out alarm reminding, and the method comprises the following steps:
and if the average value is larger than the corresponding first preset threshold value, the monitoring host carries out alarm reminding.
Optionally, the step of calculating and integrating the performance index through the monitoring template and detecting whether the performance index after calculation and integration meets the corresponding preset alarm rule further includes:
if the monitoring template is a slow request monitoring template, detecting whether the current waiting pending number in the performance index is greater than a second preset threshold value through the slow request monitoring template, and detecting whether the current JDBC connection number in the performance index is greater than a third preset threshold value;
if the performance index after calculation and integration meets the corresponding preset alarm rule, the monitoring host carries out alarm reminding, and the method comprises the following steps:
and if the current waiting pending number is larger than a second preset threshold value and the current JDBC connection number is larger than a third preset threshold value, the monitoring host machine performs alarm reminding.
Optionally, if the performance index after the calculation and the integration meets the corresponding preset alarm rule, the monitoring host performs an alarm reminding step, which includes:
if the performance indexes after calculation and integration meet corresponding preset alarm rules, the monitoring host determines the corresponding alarm level according to the monitoring template;
and the monitoring host determines a corresponding alarm mode according to the alarm level and carries out alarm reminding according to the corresponding alarm mode.
Optionally, before the step of determining, by the monitoring host, a corresponding alarm mode according to the alarm level and performing alarm reminding according to the corresponding alarm mode, the method further includes:
the monitoring host determines a corresponding alarm shielding time period according to the alarm level and detects whether the current time is within the alarm shielding time period;
if the current time is not within the alarm shielding time period, executing the following steps: the monitoring host determines a corresponding alarm mode according to the alarm level and carries out alarm reminding according to the corresponding alarm mode;
and if the current time is within the alarm shielding time period, the monitoring host does not perform alarm reminding.
Optionally, the monitoring and warning method of the WebLogic server further includes:
the monitoring host records a corresponding alarm event in a preset alarm log according to an alarm condition, wherein the alarm event comprises abnormal time, an abnormal type and an alarm mode;
and the monitoring host determines high-frequency alarm time and/or high-frequency abnormal types in a preset statistical period according to the preset alarm log, and generates corresponding high-frequency alarm reports according to the monitoring data respectively corresponding to the high-frequency alarm time and/or the high-frequency abnormal types.
In addition, in order to achieve the above object, the present invention further provides a monitoring and warning device for a WebLogic server, where the monitoring and warning device for the WebLogic server includes:
the acquisition module is used for acquiring the performance index of the corresponding WebLogic server through the data acquisition host according to the monitoring instruction when the monitoring host receives the monitoring instruction;
the detection module is used for determining a corresponding monitoring template according to the monitoring instruction by the monitoring host, calculating and integrating the performance index through the monitoring template, and detecting whether the performance index after calculation and integration meets a corresponding preset alarm rule or not;
and the alarm module is used for carrying out alarm reminding by the monitoring host if the performance indexes after calculation and integration meet the corresponding preset alarm rules.
In addition, in order to achieve the above object, the present invention further provides a monitoring and warning system of WebLogic server, where the monitoring and warning system of WebLogic server includes a monitoring host, a data acquisition host, a plurality of WebLogic servers, and further includes a memory, a processor, and a monitoring and warning program stored on the memory and executable by the processor, where when the monitoring and warning program is executed by the processor, the steps of the monitoring and warning method of WebLogic server as described above are implemented.
In addition, in order to achieve the above object, the present invention further provides a computer storage medium, where a monitoring alarm program is stored on the computer storage medium, where the monitoring alarm program, when executed by a processor, implements the steps of the monitoring alarm method of the WebLogic server as described above.
The invention provides a monitoring and alarming method, a device and a system of a WebLogic server and a computer storage medium, wherein the monitoring and alarming method of the WebLogic server is applied to a monitoring and alarming system which comprises a monitoring host, a data acquisition host and a plurality of WebLogic servers, wherein a monitoring template set is arranged in the monitoring host, the monitoring template set comprises a plurality of monitoring templates, and the monitoring host can directly acquire the performance index of the corresponding WebLogic server through the data acquisition host in the system when receiving a monitoring instruction; then, calculating and integrating the obtained performance indexes through a monitoring template, and detecting whether the performance indexes after calculation and integration meet corresponding preset alarm rules or not; and if the preset alarm rule is met, carrying out alarm reminding to prompt corresponding operation and maintenance personnel to carry out maintenance and inspection in time. Therefore, the invention does not need to install a monitoring module on each WebLogic server, is more convenient to deploy, and can judge whether the abnormity occurs without respectively checking the corresponding monitoring data on the corresponding WebLogic servers, thereby improving the timeliness of abnormity monitoring and alarming.
Drawings
Fig. 1 is a schematic terminal structure diagram of a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a monitoring alarm method of a WebLogic server according to a first embodiment of the present invention;
fig. 3 is a schematic diagram of a monitoring alarm system according to an embodiment of the present invention;
FIG. 4 is a flowchart illustrating a monitoring alarm method of a WebLogic server according to a second embodiment of the present invention;
FIG. 5 is a flowchart illustrating a monitoring and warning method of a WebLogic server according to a third embodiment of the present invention;
fig. 6 is a schematic functional module diagram of a monitoring alarm device of WebLogic server according to a first embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Referring to fig. 1, fig. 1 is a schematic diagram of a terminal structure of a hardware operating environment according to an embodiment of the present invention.
The terminal in the embodiment of the invention is a monitoring host which can be a terminal device such as a PC, a tablet computer, a portable computer and the like, and a monitoring template set is arranged in the monitoring host, wherein the monitoring template set comprises a plurality of monitoring templates, such as a JVM CPU (Java virtual machine) utilization rate monitoring template, a JDBC (java virtual data bus) connection number monitoring template, a blocked thread monitoring template, an abnormal request quantity monitoring template, a GC monitoring template and a slow request monitoring template.
As shown in fig. 1, the terminal may include: a processor 1001, such as a CPU, a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., a Wi-Fi interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the terminal structure shown in fig. 1 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
With continued reference to FIG. 1, the memory 1005 of FIG. 1, which is one type of computer storage medium, may include an operating system, a network communication module, and a monitoring alarm program.
In the terminal shown in fig. 1, the network communication module may be used to connect to the data acquisition host and perform data communication with the data acquisition host; and the processor 1001 may be configured to call the monitoring alarm program stored in the memory 1005 and perform the following operations:
when the monitoring host receives a monitoring instruction, acquiring a performance index of a corresponding WebLogic server through the data acquisition host according to the monitoring instruction;
the monitoring host determines a corresponding monitoring template according to the monitoring instruction, calculates and integrates the performance index through the monitoring template, and detects whether the performance index after calculation and integration meets a corresponding preset alarm rule;
and if the performance indexes after calculation and integration meet the corresponding preset alarm rules, the monitoring host carries out alarm reminding.
Further, the monitoring templates comprise a Java virtual machine central processing unit (JVM) CPU utilization rate monitoring template, a Java database connection JDBC connection number monitoring template, a blocking thread monitoring template, an abnormal request quantity monitoring template, a garbage collection GC monitoring template and a slow request monitoring template.
Further, the processor 1001 may call the monitoring alarm program stored in the memory 1005, and further perform the following operations:
if the monitoring template is a JVM CPU utilization monitoring template, or a JDBC connection number monitoring template, or a blocked thread monitoring template, or an abnormal request quantity monitoring template, or a GC monitoring template, calculating an average value of corresponding indexes in the performance indexes within a preset time through the monitoring template, and detecting whether the average value is greater than a corresponding first preset threshold value;
if the performance index after calculation and integration meets the corresponding preset alarm rule, the monitoring host carries out alarm reminding, and the method comprises the following steps:
and if the average value is larger than the corresponding first preset threshold value, the monitoring host carries out alarm reminding.
Further, the processor 1001 may call the monitoring alarm program stored in the memory 1005, and further perform the following operations:
if the monitoring template is a slow request monitoring template, detecting whether the current waiting pending number in the performance index is greater than a second preset threshold value through the slow request monitoring template, and detecting whether the current JDBC connection number in the performance index is greater than a third preset threshold value;
if the performance index after calculation and integration meets the corresponding preset alarm rule, the monitoring host carries out alarm reminding, and the method comprises the following steps:
and if the current waiting pending number is larger than a second preset threshold value and the current JDBC connection number is larger than a third preset threshold value, the monitoring host machine performs alarm reminding.
Further, the processor 1001 may call the monitoring alarm program stored in the memory 1005, and further perform the following operations:
if the performance indexes after calculation and integration meet corresponding preset alarm rules, the monitoring host determines the corresponding alarm level according to the monitoring template;
and the monitoring host determines a corresponding alarm mode according to the alarm level and carries out alarm reminding according to the corresponding alarm mode.
Further, the processor 1001 may call the monitoring alarm program stored in the memory 1005, and further perform the following operations:
the monitoring host determines a corresponding alarm shielding time period according to the alarm level and detects whether the current time is within the alarm shielding time period;
if the current time is not within the alarm shielding time period, executing the following steps: the monitoring host determines a corresponding alarm mode according to the alarm level and carries out alarm reminding according to the corresponding alarm mode;
and if the current time is within the alarm shielding time period, the monitoring host does not perform alarm reminding.
Further, the processor 1001 may call the monitoring alarm program stored in the memory 1005, and further perform the following operations:
the monitoring host records a corresponding alarm event in a preset alarm log according to an alarm condition, wherein the alarm event comprises abnormal time, an abnormal type and an alarm mode;
and the monitoring host determines high-frequency alarm time and/or high-frequency abnormal types in a preset statistical period according to the preset alarm log, and generates corresponding high-frequency alarm reports according to the monitoring data respectively corresponding to the high-frequency alarm time and/or the high-frequency abnormal types.
Based on the hardware structure, the invention provides various embodiments of the monitoring and alarming method of the WebLogic server.
The invention provides a monitoring and alarming method of a WebLogic server.
Referring to fig. 2, fig. 2 is a schematic flowchart of a monitoring alarm method of a WebLogic server according to a first embodiment of the present invention.
In this embodiment, the monitoring and warning method of the WebLogic server is applied to a monitoring and warning system, the monitoring and warning system includes a monitoring host, a data acquisition host and a plurality of WebLogic servers, the monitoring host is in communication connection with the data acquisition host, the data acquisition host is in communication connection with the plurality of WebLogic servers, respectively, and the monitoring and warning method of the WebLogic server includes:
step S10, when receiving a monitoring instruction, the monitoring host acquires a performance index of a corresponding WebLogic server through the data acquisition host according to the monitoring instruction;
in this embodiment, the monitoring and warning method of the WebLogic server is applied to a monitoring and warning system, and specifically, referring to fig. 3, fig. 3 is a schematic view of a monitoring and warning system architecture according to an embodiment of the present invention, where the monitoring and warning system includes a monitoring host, a data acquisition host, and multiple WebLogic servers, the monitoring host is in communication connection with the data acquisition host, and the data acquisition host is in communication connection with the multiple WebLogic servers, respectively. The monitoring host is internally provided with a monitoring template set, the monitoring template set comprises a plurality of monitoring templates, for example, a JVM CPU (Java Virtual Machine Central Processing Unit) utilization rate monitoring template, a JDBC (Java DataBase Connectivity) connection number monitoring template, a blocked thread monitoring template, an abnormal request quantity monitoring template, a GC (Garbage Collection) monitoring template and a slow request monitoring template, each monitoring template is configured with a corresponding monitoring alarm rule, and the monitoring host is used for acquiring a performance index of a corresponding WebLogic server from the data acquisition host according to a received monitoring instruction, and then calculating and integrating the performance index of the WebLogic server through the monitoring templates to detect whether an abnormal condition exists or not; the data acquisition host is used for receiving and storing the performance indexes reported by the WebLogic servers and is also used for sending the performance indexes corresponding to the WebLogic servers to the monitoring host when receiving the monitoring instruction of the monitoring host. By constructing the monitoring and alarming system, the monitoring host can directly acquire the performance index of each WebLogic server through the data acquisition host in the system, and whether the abnormity occurs can be judged without respectively checking corresponding monitoring data on the corresponding WebLogic servers, so that the timeliness of abnormity monitoring and alarming can be improved.
In this embodiment, when the monitoring host receives the monitoring instruction, the monitoring instruction may be sent by the management terminal, or may be a preset timing monitoring instruction, and the monitoring instruction may include a monitoring type and a WebLogic server name. The monitoring types can include, but are not limited to, JVM CPU usage monitoring, JDBC connection number monitoring, blocked thread monitoring, abnormal request amount monitoring, GC monitoring, and slow request monitoring, and the WebLogic server name can be a system name or number set in the monitoring alarm system for the server, or an ip address thereof. Of course, the monitoring instruction may include only WebLogic server name, and all abnormal situations are monitored by default.
And then, the monitoring host acquires the corresponding performance index of the WebLogic server from the data acquisition host according to the monitoring instruction, wherein the performance index can comprise the number of completion requests, the number of JDBC connections, the number of idle threads, the number of execution threads, the number of hogging (exclusive) threads, the usage rate of a JVM CPU, the number of pendings and the usage rate of heap. The number of the completed requests refers to the number of the completed requests processed in a preset time, and is used for monitoring the abnormal request quantity; the JDBC connection number refers to the connection number of the java database and is used for JDBC connection number monitoring and slow request monitoring; the number of idle threads refers to the number of current idle threads, and the number of idle threads is generally more than 50; the number of the execution threads refers to the number of the threads which execute the processing request at present, and is used for judging the load problem of WebLogic; the ringing thread number refers to the number corresponding to the thread which does not complete the request for more than 30s and is used for monitoring the blocked thread; the JVM CPU utilization rate, namely the Java virtual machine CPU utilization rate, is used for monitoring the JVM CPU utilization rate; pending refers to the number of waiting requests for slow request monitoring; the heap usage, i.e., heap memory usage, is used for GC monitoring.
Step S20, the monitoring host determines a corresponding monitoring template according to the monitoring instruction, calculates and integrates the performance index through the monitoring template, and detects whether the performance index after calculation and integration meets a corresponding preset alarm rule;
if the calculated and integrated performance index meets the corresponding preset alarm rule, executing step S30: and the monitoring host machine carries out alarm reminding.
In this embodiment, after the monitoring host receives the monitoring instruction and obtains the performance index of the corresponding WebLogic server through the data acquisition host according to the monitoring instruction, the monitoring host determines the corresponding monitoring template according to the monitoring instruction, calculates and integrates the obtained performance index through the monitoring template, and detects whether the calculated and integrated performance index meets the corresponding preset alarm rule. And if the performance indexes after calculation and integration meet the corresponding preset alarm rules, carrying out alarm reminding to prompt corresponding operation and maintenance personnel to carry out maintenance and inspection in time, or informing corresponding responsible persons of the abnormal conditions to prompt the responsible persons to solve the abnormal conditions. And if the performance indexes after calculation and integration do not meet the corresponding preset alarm rules, not performing alarm reminding.
It should be noted that, when the monitoring host acquires the performance index, each performance index corresponding to the WebLogic server may be acquired, then the corresponding monitoring template is determined according to the control instruction, and then the corresponding index is selected from each performance index through the monitoring template for calculation and integration. Of course, in a specific embodiment, the performance index required to be obtained may also be determined according to the monitoring instruction, for example, when the monitoring instruction is to monitor the usage rate of the JVM CPU, only the usage rate data of the JVM CPU in a period of time may be obtained, and then the usage rate data of the JVM CPU in a period of time may be correspondingly calculated and integrated through a corresponding monitoring template (e.g., a JVM CPU usage rate monitoring template).
The invention provides a monitoring and alarming method of a WebLogic server, which is applied to a monitoring and alarming system, wherein the monitoring and alarming system comprises a monitoring host, a data acquisition host and a plurality of WebLogic servers, a monitoring template set is arranged in the monitoring host, the monitoring template set comprises a plurality of monitoring templates, and the monitoring host can directly acquire the performance index of the corresponding WebLogic server through the data acquisition host in the system when receiving a monitoring instruction; then, calculating and integrating the obtained performance indexes through a monitoring template, and detecting whether the performance indexes after calculation and integration meet corresponding preset alarm rules or not; and if the preset alarm rule is met, carrying out alarm reminding to prompt corresponding operation and maintenance personnel to carry out maintenance and inspection in time. Therefore, the invention does not need to install a monitoring module on each WebLogic server, is more convenient to deploy, and can judge whether the abnormity occurs without respectively checking the corresponding monitoring data on the corresponding WebLogic servers, thereby improving the timeliness of abnormity monitoring and alarming.
Furthermore, the monitoring templates comprise a JVM CPU utilization monitoring template, a JDBC connection number monitoring template, a blocking thread monitoring template, an abnormal request amount monitoring template, a GC monitoring template and a slow request monitoring template. Different monitoring templates have different monitoring performance indexes, and the calculation integration rule of the monitoring performance indexes and the corresponding preset alarm rule are different. Therefore, step S20 may include:
step S21, if the monitoring template is a JVM CPU usage monitoring template, or a JDBC connection number monitoring template, or a blocked thread monitoring template, or an abnormal request quantity monitoring template, or a GC monitoring template, calculating an average value of corresponding indexes in the performance indexes within a preset time through the monitoring template, and detecting whether the average value is greater than a corresponding first preset threshold value;
at this time, if the average value is greater than the corresponding first preset threshold, step S30 is executed: and the monitoring host machine carries out alarm reminding.
In this embodiment, after the monitoring host determines the corresponding monitoring template according to the monitoring instruction, if the monitoring template is a JVM CPU utilization monitoring template, or a JDBC connection number monitoring template, or a blocked thread monitoring template, or an abnormal request amount monitoring template, or a GC monitoring template, the monitoring host calculates an average value of corresponding indexes in the performance indexes within a preset time through the corresponding monitoring template, and detects whether the average value is greater than a corresponding first preset threshold; and if the average value is larger than the corresponding first preset threshold value, performing alarm reminding. And if the average value is less than or equal to the corresponding first preset threshold value, not carrying out alarm reminding.
Specifically, a preset alarm rule corresponding to the JVM CPU usage monitoring template is that an average value of the JVM CPU usage within 5 minutes is continuously higher than 80%, an alarm is triggered, if the monitoring template is the JVM CPU usage monitoring template, when the JVM CPU usage monitoring is performed through the JVM CPU usage monitoring template, JVM CPU usage data within 5 minutes from the current time can be selected from the obtained performance indexes, and the average value of the JVM CPU usage within 5 minutes is calculated, and then whether the average value is greater than 80% or not is detected, and if the average value is greater than 80%, an alarm prompt is performed.
The method comprises the steps that a preset alarm rule corresponding to a JDBC connection number monitoring template triggers an alarm if the number of JDBC connections exceeds 10 in 5 minutes, if the monitoring template is the JDBC connection number monitoring template, JDBC connection number data within 5 minutes from the current time can be selected from obtained performance indexes when the JDBC connection number monitoring template monitors the JDBC connection number, the average value of the JDBC connection number within 5 minutes is calculated, then whether the average value is larger than 10 or not is detected, and if the average value is larger than 10, alarm reminding is conducted.
And if the monitoring template is the blocked thread monitoring template, selecting hogging thread number data within 5 minutes from the current time from the obtained performance indexes, calculating an average value of the hogging thread number within 5 minutes, then detecting whether the average value is greater than 5, and if the average value is greater than 5, carrying out alarm reminding.
If the preset alarm rule corresponding to the abnormal request quantity monitoring template is that the number of completed requests is higher than 10 in 5 minutes, an alarm is triggered, if the monitoring template is the abnormal request quantity monitoring template, when the abnormal request quantity monitoring is carried out through the abnormal request quantity monitoring template, the data of the number of completed requests within 5 minutes from the current time can be selected from the obtained performance indexes, the average value of the number of completed requests within 5 minutes is calculated, then whether the average value is larger than 10 is detected, and if the average value is larger than 10, alarm reminding is carried out.
If the preset alarm rule corresponding to the GC monitoring template is that the heap utilization rate is continuously higher than 80% within 10 minutes, an alarm is triggered, if the monitoring template is the GC monitoring template, when GC monitoring is carried out through the GC monitoring template, heap utilization rate data within 5 minutes from the current time can be selected from the obtained performance indexes, the average value of the heap utilization rates within 5 minutes is calculated, then whether the average value is larger than 80% or not is detected, and if the average value is larger than 80%, alarm reminding is carried out.
Further, step S20 may further include:
step S22, if the monitoring template is a slow-request monitoring template, detecting whether the current waiting pending number in the performance index is greater than a second preset threshold through the slow-request monitoring template, and detecting whether the current JDBC connection number in the performance index is greater than a third preset threshold;
at this time, if the current waiting pending number is greater than the second preset threshold and the current JDBC connection number is greater than the third preset threshold, step S30 is executed: and carrying out alarm reminding.
In this embodiment, after the monitoring host determines the corresponding monitoring template according to the monitoring instruction, if the monitoring template is a slow request monitoring template, since the preset alarm rule corresponding to the slow request monitoring template is that the number of pendings is higher than 5 and the number of JDBC connections exceeds 10, an alarm is triggered, when the slow request monitoring is performed through the slow request monitoring template, the real-time number of pendings and the number of JDBC connections (that is, the current number of pendings and the current number of JDBC connections) can be obtained from the obtained performance indexes, and whether the current number of pendings is larger than 5 or not is detected, and whether the current number of JDBC connections is larger than 10 or not is detected. And if the current pending number is greater than 5 and the current JDBC connection number is greater than 10, performing alarm reminding. And if only one monitoring alarm condition is met, namely the current pending number is greater than 5 or the current JDBC connection number is greater than 10, not performing alarm reminding.
In the embodiment, the performance indexes of the Weblogic server are calculated and integrated through the monitoring template, and whether to give an alarm or not is determined according to the average value of a certain performance index in preset time, or combined monitoring alarm is carried out among different performance indexes, instead of singly carrying out alarm reminding once a preset range is carried out according to a certain performance index, so that more accurate alarm can be realized, and the alarm false alarm rate is reduced.
Further, referring to fig. 4, fig. 4 is a flowchart illustrating a monitoring alarm method of WebLogic server according to a second embodiment of the present invention.
Based on the first embodiment shown in fig. 2, in this embodiment, step S30 may include:
step S31, if the performance index after calculation and integration meets the corresponding preset alarm rule, the monitoring host determines the corresponding alarm level according to the monitoring template;
and step S32, the monitoring host determines a corresponding alarm mode according to the alarm level and carries out alarm reminding according to the corresponding alarm mode.
In this embodiment, since the WebLogic server is in an abnormal state with a degree of urgency, different alarm levels can be set according to the abnormal types monitored by different monitoring templates. When the abnormal condition is monitored through a certain monitoring template and the alarm reminding needs to be carried out, the alarm reminding is carried out according to the alarm level corresponding to the monitoring template. The alarm levels may include critical, major, warning, info, among others. The corresponding relationship between each monitoring template and the alarm level may be: the JVM CPU utilization rate monitoring template corresponds to critical level alarm, the JDBC connection number monitoring template corresponds to major level alarm, the blocked thread monitoring template corresponds to critical level alarm, the abnormal request amount monitoring template corresponds to warning level alarm, the GC monitoring template corresponds to warning level alarm, and the slow request monitoring template corresponds to critical level alarm. Of course, the corresponding relationship between each monitoring template and the alarm level is not limited to the above relationship, and may be specifically set according to the actual situation.
And then, determining a corresponding alarm mode according to the alarm level, and carrying out alarm reminding according to the corresponding alarm mode. Wherein, different alarm levels correspond to different alarm modes, the alarm modes can include alarm forms, alarm times and alarm objects, and the alarm forms include mail alarms, short message alarms and telephone alarms. For example, the critical level only corresponds to mail reminding, the reminding times are 5 times, and the alarm object is a first person of responsibility; the major level corresponds to mail reminding and short message reminding, the reminding times are respectively 5 times, and the alarm object is a first responsible person; the warning level corresponds to mail reminding and short message reminding, the reminding times are 10 times respectively, and the warning objects are a first responsible person and a second responsible person; the critical level corresponds to mail reminding, short message reminding and telephone reminding, the times of the mail reminding and the short message reminding are respectively 10 times, the times of the telephone reminding are 2 times, and the alarm objects are a first responsible person and a second responsible person. Of course, in an actual situation, the reminding may be performed only 1 time, and if the mail is not referred or the short message is not referred or the missed call is not referred, the reminding is continued. In addition, the first person of responsibility can be reminded preferentially, when the reminding reaches a certain number of times, the reminding can be changed to remind the second person of responsibility, for example, if a single alarm continuously sends out 10 mails which are not consulted, the second person of responsibility can be sent out mails automatically, or if the first person of responsibility does not answer the call, the second person of responsibility can be called. The corresponding relationship between the alarm level and the alarm mode may be specifically set according to the actual situation, and is not specifically limited herein.
Because some monitored performance indicators satisfy the preset alarm condition within a certain time period, but do not belong to an abnormal condition, in order to avoid that the alarm reminding is still performed under such a condition, before step S32, the following steps may be further included:
step S33, the monitoring host determines the corresponding alarm shielding time section according to the alarm level and detects whether the current time is in the alarm shielding time section;
if the current time is not within the alarm masking time period, executing step S32: the monitoring host determines a corresponding alarm mode according to the alarm level and carries out alarm reminding according to the corresponding alarm mode;
if the current time is within the alarm masking time period, executing step S34: the monitoring host does not carry out alarm reminding.
In this embodiment, after determining the corresponding alarm level according to the monitoring template, then determining the corresponding alarm masking time period according to the alarm level, and detecting whether the current time (i.e. the time when the abnormality is detected) is within the alarm masking time period, if the current time is not within the alarm masking time period, the subsequent step S32 is continuously executed. And if the current time is within the alarm shielding time period, not performing alarm reminding. The alarm masking time period can be set according to actual needs, and default setting can also be adopted. Of course, in a specific embodiment, the corresponding alarm shielding time period may also be directly determined according to the monitoring template without determining the alarm level corresponding to the monitoring template first and then determining the corresponding alarm shielding time period according to the alarm level.
In the embodiment, different alarm levels are set according to the emergency degree of the WebLogic server under the abnormal condition, so that the classified alarm is realized, and the monitoring alarm system is more standardized and humanized.
Further, referring to fig. 5, fig. 5 is a flowchart illustrating a monitoring alarm method of WebLogic server according to a third embodiment of the present invention.
Based on the first embodiment shown in fig. 2, after step S30, the WebLogic server monitoring and warning method further includes:
step S40, the monitoring host records a corresponding alarm event in a preset alarm log according to the alarm condition, where the alarm event includes an abnormal time, an abnormal type, and an alarm mode.
In this embodiment, in order to facilitate the operation and maintenance staff to know the specific situation of the alarm, the monitoring host records the alarm situation after the alarm is given. Specifically, an alarm log is preset in the monitoring host for recording an alarm event; of course, in this embodiment, since the monitoring host monitors a plurality of different WebLogic servers, a plurality of different alarm logs may be set to perform alarm recording respectively. After the monitoring host performs an alarm, a corresponding alarm event is recorded in an alarm log, where the alarm event may include content such as abnormal time (time when the WebLogic server generates an abnormality), an abnormal type, and an alarm manner.
Step S50, the monitoring host determines a high-frequency alarm time and/or a high-frequency abnormal type within a preset statistical period according to the preset alarm log, and generates a corresponding high-frequency alarm report according to the monitoring data corresponding to the high-frequency alarm time and/or the high-frequency abnormal type, respectively.
Furthermore, in order to facilitate operation and maintenance personnel to macroscopically know the alarm condition caused by the abnormality of each WebLogic server, the monitoring server can also count data such as high-frequency alarm time, high-frequency abnormality types and the like within a certain time period according to a preset alarm log. Wherein, the high-frequency alarm time is the multiple time of alarm, for example, alarm 300 times in 6 months, 200 alarms occur at 9 to 10 am, and the high-frequency alarm time in 4 months is 9 to 10 am; in practice, the statistical period duration may be set according to actual conditions, for example, one month may be used as a statistical period, or one week may be used as a statistical period; the "high frequency" criterion may be set according to actual conditions, and for example, a certain count threshold may be used as the "high frequency" criterion, or a certain duty threshold may be used as the "high frequency" criterion. The high-frequency abnormal type is a frequent type of abnormal conditions, for example, the alarm is performed for 300 times in 6 months, the abnormal type for 200 times is JVM CPU utilization rate abnormal, and the high-frequency abnormal type for 4 months is JVM CPU utilization rate abnormal; similarly, the statistical cycle duration and the "high frequency" criterion may be set according to actual conditions. When the macroscopic statistical analysis results are obtained, the monitoring host can also give related reports for operation and maintenance personnel to check; for example, when the monitoring host can count the high-frequency alarm time and/or the high-frequency abnormal type in a certain time period according to the preset alarm log, the monitoring host can acquire the monitoring data corresponding to the high-frequency alarm time and/or the high-frequency abnormal type and generate a corresponding high-frequency alarm report for the operation and maintenance personnel to check, and the operation and maintenance personnel can perform maintenance and related optimization according to the report to ensure the normal operation of the WebLogic server.
The invention also provides a monitoring and warning device of the WebLogic server.
Referring to fig. 6, fig. 6 is a schematic functional module diagram of a monitoring alarm device of WebLogic server according to a first embodiment of the present invention.
In this embodiment, the monitoring and warning device of the WebLogic server includes:
the acquisition module 10 is configured to, when the monitoring host receives a monitoring instruction, acquire, by the data acquisition host, a performance index of a corresponding WebLogic server according to the monitoring instruction;
the detection module 20 is configured to determine a corresponding monitoring template according to the monitoring instruction, perform calculation and integration on the performance index through the monitoring template, and detect whether the performance index after calculation and integration meets a corresponding preset alarm rule;
and the alarm module 30 is configured to perform alarm reminding by the monitoring host if the calculated and integrated performance index meets the corresponding preset alarm rule.
Each virtual function module of the monitoring alarm device of the WebLogic server is stored in the memory 1005 of the monitoring host shown in fig. 1, and is used for implementing all functions of the monitoring alarm program; when the modules are executed by the processor 1001, the functions of acquiring the performance indexes of the WebLogic servers through the data acquisition host, calculating and integrating the performance indexes through the monitoring template, and performing alarm reminding when the performance indexes after calculation and integration are detected to meet the corresponding preset alarm rules can be realized.
Further, the detecting module 20 is specifically configured to, if the monitoring template is a JVM CPU utilization monitoring template, or a JDBC connection number monitoring template, or a blocked thread monitoring template, or an abnormal request amount monitoring template, or a GC monitoring template, calculate an average value of corresponding indexes in the performance indexes within a preset time through the monitoring template, and detect whether the average value is greater than a corresponding first preset threshold;
the alarm module 30 is specifically configured to perform alarm reminding by the monitoring host if the average value is greater than a corresponding first preset threshold.
Further, the detecting module 20 is specifically configured to, if the monitoring template is a slow request monitoring template, detect whether the current waiting pending number in the performance index is greater than a second preset threshold through the slow request monitoring template, and detect whether the current JDBC connection number in the performance index is greater than a third preset threshold;
the alarm module 30 is specifically configured to perform alarm reminding by the monitoring host if the current waiting pending number is greater than a second preset threshold and the current JDBC connection number is greater than a third preset threshold.
Further, the alarm module 30 includes:
the level determining unit is used for determining a corresponding alarm level according to the monitoring template by the monitoring host if the performance index after calculation and integration meets a corresponding preset alarm rule;
and the alarm reminding unit is used for determining a corresponding alarm mode according to the alarm level by the monitoring host and carrying out alarm reminding according to the corresponding alarm mode.
Further, the alarm module 30 further includes:
the time detection unit is used for determining a corresponding alarm shielding time period according to the alarm level by the monitoring host and detecting whether the current time is in the alarm shielding time period;
the alarm module 30 is specifically configured to not perform alarm reminding by the monitoring host if the current time is within the alarm masking time period.
Further, the monitoring and warning device of the WebLogic server further includes:
the monitoring host is used for recording corresponding alarm events in a preset alarm log according to alarm conditions, wherein the alarm events comprise abnormal time, abnormal types and alarm modes;
and the reporting module is used for determining the high-frequency alarm time and/or the high-frequency abnormal type in a preset statistical period by the monitoring host according to the preset alarm log and generating corresponding high-frequency alarm reports according to the monitoring data respectively corresponding to the high-frequency alarm time and/or the high-frequency abnormal type.
The function implementation of each module in the monitoring and warning device of the WebLogic server corresponds to each step in the monitoring and warning method embodiment of the WebLogic server, and the function and implementation process are not described in detail here.
The invention also provides a monitoring and alarming system of the WebLogic server, which comprises a monitoring host, a data acquisition host, a plurality of WebLogic servers, a memory, a processor and a monitoring and alarming program which is stored on the memory and can be operated on the processor, wherein when the monitoring and alarming program is executed by the processor, the steps of the monitoring and alarming method of the WebLogic server are realized.
The specific embodiment of the monitoring and warning system of the WebLogic server of the present invention is basically the same as the embodiments of the monitoring and warning method of the WebLogic server, and is not described herein again.
The present invention also provides a computer storage medium, on which a monitoring alarm program is stored, and when being executed by a processor, the monitoring alarm program implements the steps of the monitoring alarm method of WebLogic server according to any one of the above embodiments.
The specific embodiment of the computer storage medium of the present invention is basically the same as the embodiments of the monitoring and warning method of the WebLogic server, and is not described herein again.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system 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 system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) as described above, and includes instructions for enabling a device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (9)
1. A monitoring and alarming method of a WebLogic server is characterized in that the monitoring and alarming method of the WebLogic server is applied to a monitoring and alarming system, the monitoring and alarming system comprises a monitoring host, a data acquisition host and a plurality of middleware WebLogic servers, the monitoring host is in communication connection with the data acquisition host, the data acquisition host is in communication connection with the plurality of WebLogic servers respectively, and the method comprises the following steps:
when the monitoring host receives a monitoring instruction, acquiring a performance index of a corresponding WebLogic server through the data acquisition host according to the monitoring instruction, wherein the performance index comprises at least one of a completion request number, a JDBC connection number, an idle thread number, an execution thread number, a hogging (exclusive) thread number, a JVM CPU utilization rate, a pending number and a heap utilization rate;
the monitoring host determines a corresponding monitoring template according to the monitoring instruction, wherein the monitoring template comprises at least one of a JVM CPU (Java virtual machine) utilization rate monitoring template, a JDBC (java virtual machine connectivity count) monitoring template, a blocked thread monitoring template, an abnormal request quantity monitoring template, a GC (gas chromatography) monitoring template and a slow request monitoring template, calculates and integrates the performance index through the monitoring template, and detects whether the calculated and integrated performance index meets a corresponding preset alarm rule;
the steps of calculating and integrating the performance indexes through the monitoring template and detecting whether the performance indexes after calculation and integration meet corresponding preset alarm rules comprise:
if the monitoring template is a JVM CPU utilization monitoring template, or a JDBC connection number monitoring template, or a blocked thread monitoring template, or an abnormal request quantity monitoring template, or a GC monitoring template, calculating an average value of corresponding indexes in the performance indexes within a preset time through the monitoring template, and detecting whether the average value is greater than a corresponding first preset threshold value;
if the performance indexes after calculation and integration meet the corresponding preset alarm rules, the monitoring host carries out alarm reminding;
if the performance index after calculation and integration meets the corresponding preset alarm rule, the monitoring host carries out alarm reminding, and the method comprises the following steps:
and if the average value is larger than the corresponding first preset threshold value, the monitoring host carries out alarm reminding.
2. The WebLogic server monitoring alarm method of claim 1, wherein the monitoring templates include a Java virtual machine central processing unit JVM CPU usage monitoring template, a Java database connection JDBC connection number monitoring template, a blocked thread monitoring template, an abnormal request volume monitoring template, a garbage collection GC monitoring template, and a slow request monitoring template.
3. The WebLogic server monitoring alarm method of claim 2, wherein the step of performing calculation and integration on the performance index through the monitoring template and detecting whether the performance index after calculation and integration meets a corresponding preset alarm rule further comprises:
if the monitoring template is a slow request monitoring template, detecting whether the current waiting pending number in the performance index is greater than a second preset threshold value through the slow request monitoring template, and detecting whether the current JDBC connection number in the performance index is greater than a third preset threshold value;
if the performance index after calculation and integration meets the corresponding preset alarm rule, the monitoring host carries out alarm reminding, and the method comprises the following steps:
and if the current waiting pending number is larger than a second preset threshold value and the current JDBC connection number is larger than a third preset threshold value, the monitoring host machine performs alarm reminding.
4. The WebLogic server monitoring alarm method of claim 1, wherein if the performance index after the calculation and integration meets the corresponding preset alarm rule, the monitoring host performs an alarm prompting step, which includes:
if the performance indexes after calculation and integration meet corresponding preset alarm rules, the monitoring host determines the corresponding alarm level according to the monitoring template;
and the monitoring host determines a corresponding alarm mode according to the alarm level and carries out alarm reminding according to the corresponding alarm mode.
5. The WebLogic server monitoring alarm method of claim 4, wherein before the step of determining a corresponding alarm manner by the monitoring host according to the alarm level and performing alarm reminding according to the corresponding alarm manner, the monitoring host further comprises:
the monitoring host determines a corresponding alarm shielding time period according to the alarm level and detects whether the current time is within the alarm shielding time period;
if the current time is not within the alarm shielding time period, executing the following steps: the monitoring host determines a corresponding alarm mode according to the alarm level and carries out alarm reminding according to the corresponding alarm mode;
and if the current time is within the alarm shielding time period, the monitoring host does not perform alarm reminding.
6. The WebLogic server monitoring alarm method of any one of claims 1 to 5, further comprising:
the monitoring host records a corresponding alarm event in a preset alarm log according to an alarm condition, wherein the alarm event comprises abnormal time, an abnormal type and an alarm mode;
and the monitoring host determines high-frequency alarm time and/or high-frequency abnormal types in a preset statistical period according to the preset alarm log, and generates corresponding high-frequency alarm reports according to the monitoring data respectively corresponding to the high-frequency alarm time and/or the high-frequency abnormal types.
7. A monitoring and warning device of a WebLogic server is characterized in that the monitoring and warning device of the WebLogic server comprises:
the system comprises an acquisition module, a monitoring host and a plurality of WebLogic servers, wherein the acquisition module is used for acquiring performance indexes of the corresponding WebLogic servers through the data acquisition host according to a monitoring instruction when the monitoring host receives the monitoring instruction, the performance indexes comprise at least one of the number of finishing requests, the number of JDBC connections, the number of idle threads, the number of executing threads, the number of hogging (exclusive) threads, the usage rate of JVM CPUs (joint virtual machines), the number of pendings and the usage rate of heaps, the monitoring host is in communication connection with the data acquisition host, and the data acquisition host is in communication connection with the plurality of WebLogic servers;
the detection module is used for determining a corresponding monitoring template by the monitoring host according to the monitoring instruction, wherein the monitoring template comprises at least one of a JVMCPU (JVMCPU) utilization rate monitoring template, a JDBC (java virtual circuit configuration code) connection number monitoring template, a blocked thread monitoring template, an abnormal request quantity monitoring template, a GC (gas chromatography) monitoring template and a slow request monitoring template, calculating and integrating the performance indexes through the monitoring template, and detecting whether the performance indexes after calculation and integration meet corresponding preset alarm rules;
the detection module is further configured to calculate an average value of corresponding indexes in the performance indexes within a preset time through the monitoring template if the monitoring template is a JVM CPU utilization monitoring template, or a JDBC connection number monitoring template, or a blocked thread monitoring template, or an abnormal request amount monitoring template, or a GC monitoring template, and detect whether the average value is greater than a corresponding first preset threshold;
the alarm module is used for carrying out alarm reminding by the monitoring host if the performance indexes after calculation and integration meet corresponding preset alarm rules;
and the alarm module is further used for carrying out alarm reminding by the monitoring host if the average value is greater than a corresponding first preset threshold value.
8. A monitoring and warning system of WebLogic server, comprising a monitoring host, a data acquisition host and a plurality of WebLogic servers, and further comprising a memory, a processor and a monitoring and warning program stored in the memory and executable by the processor, wherein when the monitoring and warning program is executed by the processor, the steps of the monitoring and warning method of WebLogic server according to any one of claims 1 to 6 are implemented.
9. A computer storage medium, characterized in that the computer storage medium has a monitoring alarm program stored thereon, wherein the monitoring alarm program, when executed by a processor, implements the steps of the monitoring alarm method of WebLogic server according to any one of claims 1 to 6.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810800086.4A CN109726072B (en) | 2018-07-18 | 2018-07-18 | WebLogic server monitoring and alarming method, device and system and computer storage medium |
| PCT/CN2018/103336 WO2020015061A1 (en) | 2018-07-18 | 2018-08-30 | Monitoring alarm method, device and system for weblogic server, and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810800086.4A CN109726072B (en) | 2018-07-18 | 2018-07-18 | WebLogic server monitoring and alarming method, device and system and computer storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109726072A CN109726072A (en) | 2019-05-07 |
| CN109726072B true CN109726072B (en) | 2022-01-14 |
Family
ID=66294570
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810800086.4A Active CN109726072B (en) | 2018-07-18 | 2018-07-18 | WebLogic server monitoring and alarming method, device and system and computer storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN109726072B (en) |
| WO (1) | WO2020015061A1 (en) |
Families Citing this family (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112054913B (en) * | 2019-06-05 | 2023-07-18 | 厦门网宿有限公司 | Data monitoring system and method |
| CN110543402B (en) * | 2019-09-09 | 2023-09-19 | 上海新炬网络技术有限公司 | Automatic monitoring and dynamic adjusting method based on WebLogic middleware core parameters |
| CN110727586A (en) * | 2019-09-16 | 2020-01-24 | 平安科技（深圳）有限公司 | Host anomaly monitoring method and device, storage medium and server |
| CN111290909A (en) * | 2020-01-19 | 2020-06-16 | 山东汇贸电子口岸有限公司 | System and method for monitoring and alarming ceph cluster |
| CN111324511B (en) * | 2020-02-24 | 2023-10-31 | 北京达佳互联信息技术有限公司 | Alarm rule generation method and device, electronic equipment and storage medium |
| CN111324520A (en) * | 2020-03-06 | 2020-06-23 | 五八有限公司 | Service interface monitoring method and device, electronic equipment and storage medium |
| CN111431738B (en) * | 2020-03-10 | 2022-12-16 | 广州嘉为科技有限公司 | Alarm monitoring method based on Internet operation and maintenance |
| CN111414351A (en) * | 2020-03-20 | 2020-07-14 | 中国建设银行股份有限公司 | Performance diagnosis method and device of MySQ L database |
| CN111585785B (en) * | 2020-03-27 | 2023-07-21 | 中国平安人寿保险股份有限公司 | Method and device for shielding alarm information, computer equipment and storage medium |
| CN111444074A (en) * | 2020-03-27 | 2020-07-24 | 北京贝斯平云科技有限公司 | Data monitoring method and device, electronic equipment and readable storage medium |
| CN111782433A (en) * | 2020-06-30 | 2020-10-16 | 北京百度网讯科技有限公司 | Exception troubleshooting method, device, electronic equipment and storage medium |
| CN112149975B (en) * | 2020-09-11 | 2023-04-18 | 杭州东方通信软件技术有限公司 | APM monitoring system and method based on artificial intelligence |
| CN112254842A (en) * | 2020-10-10 | 2021-01-22 | 广联达科技股份有限公司 | Temperature monitoring method and system for mass concrete and electronic equipment |
| CN112684748B (en) * | 2020-11-16 | 2023-04-07 | 航天信息股份有限公司 | Monitoring method and system compatible with various monitored devices |
| CN113064800B (en) * | 2021-04-19 | 2023-03-24 | 上海安畅网络科技股份有限公司 | Early warning method and device, electronic equipment and readable storage medium |
| CN113806166A (en) * | 2021-08-25 | 2021-12-17 | 合众人寿保险股份有限公司 | Object monitoring method and device, storage medium and electronic equipment |
| CN114973615A (en) * | 2022-05-12 | 2022-08-30 | 北京软通智慧科技有限公司 | Method and device for monitoring emergency, electronic equipment and storage medium |
| CN117395132B (en) * | 2023-12-13 | 2024-02-20 | 江西云眼视界科技股份有限公司 | Distributed alarm monitoring method, system, storage medium and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104811327A (en) * | 2014-01-26 | 2015-07-29 | 中国移动通信集团江西有限公司 | Monitoring warning voice automatic notification method and device |
| CN106161085A (en) * | 2016-06-20 | 2016-11-23 | 深圳前海微众银行股份有限公司 | The monitoring system and method for messaging bus |
| CN106649040A (en) * | 2016-12-26 | 2017-05-10 | 上海新炬网络信息技术有限公司 | Automatic monitoring method and device for performance of Weblogic middleware |
| CN107294764A (en) * | 2017-04-26 | 2017-10-24 | 中国科学院信息工程研究所 | Intelligent supervision method and intelligent monitoring system |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7376534B2 (en) * | 2004-05-21 | 2008-05-20 | Bea Systems, Inc. | Watches and notifications |
| CN104520806B (en) * | 2012-08-01 | 2016-09-14 | 英派尔科技开发有限公司 | Abnormality detection for cloud monitoring |
| CN103744771A (en) * | 2014-01-28 | 2014-04-23 | 中国工商银行股份有限公司 | Method, equipment and system for monitoring host performance benchmark deviations, equipment and system |
| CN104301159B (en) * | 2014-11-13 | 2019-01-25 | 中国建设银行股份有限公司 | A kind of monitoring method and system of server cluster |
| CN104954184A (en) * | 2015-06-15 | 2015-09-30 | 四川长虹电器股份有限公司 | Monitoring and alarming method and system for cloud background server cluster |
| CN108259270A (en) * | 2018-01-11 | 2018-07-06 | 郑州云海信息技术有限公司 | A kind of data center's system for unified management design method |
-
2018
- 2018-07-18 CN CN201810800086.4A patent/CN109726072B/en active Active
- 2018-08-30 WO PCT/CN2018/103336 patent/WO2020015061A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104811327A (en) * | 2014-01-26 | 2015-07-29 | 中国移动通信集团江西有限公司 | Monitoring warning voice automatic notification method and device |
| CN106161085A (en) * | 2016-06-20 | 2016-11-23 | 深圳前海微众银行股份有限公司 | The monitoring system and method for messaging bus |
| CN106649040A (en) * | 2016-12-26 | 2017-05-10 | 上海新炬网络信息技术有限公司 | Automatic monitoring method and device for performance of Weblogic middleware |
| CN107294764A (en) * | 2017-04-26 | 2017-10-24 | 中国科学院信息工程研究所 | Intelligent supervision method and intelligent monitoring system |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2020015061A1 (en) | 2020-01-23 |
| CN109726072A (en) | 2019-05-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109726072B (en) | WebLogic server monitoring and alarming method, device and system and computer storage medium | |
| CN110224858B (en) | Log-based alarm method and related device | |
| CN108845910A (en) | Monitoring method, device and the storage medium of extensive micro services system | |
| CN107948744B (en) | Interface detection method, interface detection device, and computer-readable storage medium | |
| WO2020024376A1 (en) | Method and device for processing operation and maintenance monitoring alarm | |
| WO2016188100A1 (en) | Information system fault scenario information collection method and system | |
| CN107193714B (en) | Alarm display method and device | |
| CN107766208B (en) | Method, system and device for monitoring business system | |
| US11799748B2 (en) | Mitigating failure in request handling | |
| CN115185777A (en) | Abnormity detection method and device, readable storage medium and electronic equipment | |
| CN114398354A (en) | Data monitoring method and device, electronic equipment and storage medium | |
| CN110674149B (en) | Service data processing method and device, computer equipment and storage medium | |
| CN111026606A (en) | Alarm method and device based on hystrix fuse monitoring and computer equipment | |
| CN111949421B (en) | SDK calling method, device, electronic equipment and computer readable storage medium | |
| CN112527543A (en) | Client starting exception handling method and device, electronic equipment and storage medium | |
| KR20110037969A (en) | Targeted user notification of messages in a monitoring system | |
| CN111710403A (en) | Medical equipment supervision method, equipment and readable storage medium | |
| CN114610560B (en) | System abnormality monitoring method, device and storage medium | |
| CN110633165B (en) | Fault processing method, device, system server and computer readable storage medium | |
| CN114371980A (en) | Call link performance monitoring method and device, computer equipment and storage medium | |
| CN110955684A (en) | Data monitoring method and device | |
| JP2003345629A (en) | System monitor device, system monitoring method used for the same, and program therefor | |
| CN111966577B (en) | Program stability detection method and device | |
| CN113778836B (en) | Cloud native application health monitoring method, device, equipment and readable storage medium | |
| JP2013003896A (en) | Information providing device, information providing method and program |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |