WO2020015061A1 - Monitoring alarm method, device and system for weblogic server, and computer storage medium - Google Patents

Abstract

The present application provides a monitoring alarm method for a WebLogic server, the method being applied to a monitoring alarm system. The system comprises a monitoring host, a data collecting host and a plurality of WebLogic servers. The method comprises: when receiving a monitoring instruction, the monitoring host acquiring performance indexes of a corresponding WebLogic server by means of the data collecting host according to the monitoring instruction; determining a corresponding monitoring template according to the monitoring instruction, computing and integrating the performance indexes by means of the monitoring template, and detecting whether computed and integrated performance indexes meet a corresponding pre-set alarm rule; and if the computed and integrated performance indexes meet the corresponding pre-set alarm rule, giving an alarm reminder. The present application further provides a monitoring alarm device and system for a WebLogic server, and a computer storage medium. The present application can improve the timeliness in raising an exception monitoring alarm while realizing the simplification of monitoring deployment of a WebLogic server.

Description

 WebLogic server monitoring and alarming method, device, system and computer storage medium Ranch

This application claims the priority of a Chinese patent application filed on July 18, 2018 with the Chinese Patent Office, application number 201810800086.4, and the invention name "Monitoring and Alarming Method, Device, System, and Computer Storage Medium of WebLogic Server", its entire content Incorporated by reference.

Technical field

The present application relates to the technical field of monitoring and alarming of a WebLogic server, and in particular, to a monitoring and alarming method, device, system, and computer storage medium of a WebLogic server.

Background technique

WebLogic is a Java application server for developing, integrating, deploying, and managing large distributed web applications, network applications, and database applications. Enterprise (Java Enterprise) standard security is introduced into the development, integration, deployment and management of large-scale network applications. It has the advantages of easy development, strong scalability, flexibility and reliability, and is currently the best J2EE on the market. (Java 2 Platform Enterprise Edition).

In the WebLogic system, applications are deployed on a large number of WebLogic servers. Therefore, the running status of the WebLogic server may directly affect the business acceptance of front-end business. Therefore, it is important to monitor WebLogic server exceptions. At present, when monitoring a WebLogic server, a corresponding monitoring module needs to be configured on each WebLogic server to implement monitoring thereof, and the deployment is relatively complicated. In addition, when a worker wants to monitor whether a WebLogic server is running abnormally, he needs to check the corresponding monitoring data on the corresponding WebLogic server to determine whether an abnormality occurs. Therefore, the abnormality of the WebLogic server cannot be found in time. Therefore, the monitoring deployment of the WebLogic server in the prior art is complicated, and there is a problem that the abnormal monitoring alarm is not timely.

Summary of the invention

The main purpose of this application is to provide a method, device, system and computer storage medium for monitoring and alarming of a WebLogic server, which aims to improve the timeliness of abnormal monitoring alarms while simplifying the monitoring and deployment of the WebLogic server.

To achieve the above purpose, the present application provides a method for monitoring and alarming a WebLogic server. The method for monitoring and alarming a WebLogic server is applied to a monitoring and alarming system. The monitoring and alarming system includes a monitoring host, a data collection host, and multiple middleware WebLogic servers. The monitoring host is communicatively connected to the data acquisition host, and the data acquisition host is communicatively connected to multiple WebLogic servers, and the method includes:

When the monitoring host receives the monitoring instruction, it obtains the performance index of the corresponding WebLogic server through the data collection host according to the monitoring instruction;

The monitoring host determines a corresponding monitoring template according to the monitoring instruction, calculates and integrates the performance indicator through the monitoring template, and detects whether the calculated and integrated performance indicator meets a corresponding preset alarm rule;

If the calculated and integrated performance index satisfies the corresponding preset alarm rule, the monitoring host performs an alarm reminder.

In addition, in order to achieve the above object, the present application further provides a monitoring and alarming device for a WebLogic server. The monitoring and alarming device for a WebLogic server includes:

An acquisition module, configured to, when the monitoring host receives a monitoring instruction, obtain a performance indicator of a corresponding WebLogic server through the data collection host according to the monitoring instruction;

A detection module for the monitoring host to determine a corresponding monitoring template according to the monitoring instruction, calculate and integrate the performance indicator through the monitoring template, and detect whether the calculated and integrated performance indicator meets a corresponding preset alarm rule;

The alarm module is configured to: if the calculated and integrated performance index meets a corresponding preset alarm rule, the monitoring host performs an alarm reminder.

In addition, in order to achieve the above object, the present application also provides a monitoring and alarming system of a WebLogic server. The monitoring and alarming system of the WebLogic server includes a monitoring host, a data collection host, and multiple WebLogic servers. Computer-readable instructions on the memory and executable by the processor, wherein when the computer-readable instructions are executed by the processor, the steps of the method for monitoring and alerting of a WebLogic server as described above are implemented.

In addition, in order to achieve the above object, the present application further provides a computer storage medium, where the computer storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by a processor, the WebLogic server as described above is implemented. Steps of the monitoring alert method.

The present application provides a method and device for monitoring and alarming a WebLogic server, and a computer storage medium. The method for monitoring and alarming a WebLogic server is applied to a monitoring and alarm system. The monitoring and alarming system includes a monitoring host, a data collection host, and multiple WebLogic servers. The monitoring host has a built-in monitoring template set. The monitoring template set includes multiple monitoring templates. When receiving a monitoring instruction, the monitoring host can directly obtain the performance indicators of the corresponding WebLogic server through the data collection host in the system. The monitoring template calculates and integrates the obtained performance indicators, and detects whether the calculated and integrated performance indicators meet the corresponding preset alarm rules; if the corresponding preset alarm rules are met, an alarm reminder is performed to remind the corresponding operation and maintenance Personnel perform maintenance inspections in a timely manner. Therefore, this application does not need to install a monitoring module on each WebLogic server, which is more convenient to deploy. At the same time, it is not necessary to go to the corresponding WebLogic server to check the corresponding monitoring data to determine whether an abnormality occurs, thereby improving the timeliness of the abnormality monitoring alarm.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic structural diagram of a terminal in a hardware operating environment according to an embodiment of the present application;

2 is a schematic flowchart of a first embodiment of a method for monitoring and alarming a WebLogic server of this application;

FIG. 3 is a schematic architecture diagram of a monitoring and alarm system according to an embodiment of the present application; FIG.

4 is a schematic flowchart of a second embodiment of a monitoring and alarming method of a WebLogic server of this application;

5 is a schematic flowchart of a third embodiment of a monitoring and alarming method of a WebLogic server of this application;

FIG. 6 is a functional module diagram of a first embodiment of a monitoring and alarming device of a WebLogic server of the present application.

The implementation, functional features and advantages of the purpose of this application will be further described with reference to the embodiments and the drawings.

detailed description

It should be understood that the specific embodiments described herein are only used to explain the application, and are not used to limit the application.

Please refer to FIG. 1. FIG. 1 is a schematic structural diagram of a terminal in a hardware operating environment according to an embodiment of the present application.

In the embodiment of the present application, the terminal is a monitoring host. The monitoring host may be a terminal device such as a PC, a tablet computer, or a portable computer. The monitoring host has a built-in monitoring template set. The monitoring template set includes multiple monitoring templates, such as the JVM. CPU usage monitoring template, JDBC connection number monitoring template, blocked thread monitoring template, abnormal request monitoring template, GC monitoring template, and 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. The communication bus 1002 is used to implement connection and communication between these components. The user interface 1003 may include a display, an input unit such as a keyboard, and the optional user interface 1003 may further include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a Wi-Fi interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory. memory), such as disk storage. The memory 1005 may optionally be a storage device independent of the foregoing processor 1001.

Those skilled in the art can understand that the terminal structure shown in FIG. 1 does not constitute a limitation on the terminal, and may include more or fewer components than shown in the figure, or some components may be combined, or different components may be arranged.

With continued reference to FIG. 1, the memory 1005 as a computer storage medium in FIG. 1 may include an operating system, a network communication module, and computer-readable instructions. In the terminal shown in FIG. 1, a network communication module may be used to connect to a data collection host and perform data communication with the data collection host; and the processor 1001 may be used to call computer-readable instructions stored in the memory 1005 and execute the implementation of the present invention The example provides the monitoring and alarm method of the WebLogic server.

Based on the above hardware structure, various embodiments of the method for monitoring and alarming of the WebLogic server of the present application are proposed.

This application provides a method for monitoring and alarming a WebLogic server.

Please refer to FIG. 2, which is a schematic flowchart of a first embodiment of a monitoring and alarming method of a WebLogic server of this application.

In this embodiment, the monitoring and alarming method of the WebLogic server is applied to a monitoring and alarming system. The monitoring and alarming system includes a monitoring host, a data collection host, and multiple WebLogic servers. The monitoring host is in communication with the data collection host, and the data collection host is respectively Communicates with multiple WebLogic servers. The monitoring and alarm methods of the WebLogic server include:

In step S10, when the monitoring host receives the monitoring instruction, it obtains the performance index of the corresponding WebLogic server through the data collection host according to the monitoring instruction;

In this embodiment, the monitoring and alarming method of the WebLogic server is applied to a monitoring and alarming system. For details, please refer to FIG. 3. FIG. 3 is a schematic diagram of a monitoring and alarming system architecture according to an embodiment of the present application. The monitoring and alarming system includes a monitoring host. 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 multiple WebLogic servers. A monitoring template set is built into the monitoring host, and the monitoring template set includes multiple monitoring templates, for example, the JVM CPU (Java Virtual Machine Central Processing Unit) usage monitoring template, JDBC (Java DataBase Connectivity (Java database connection) connection number monitoring template, blocked thread monitoring template, exception request monitoring template, GC (Garbage Collection (garbage collection) monitoring template and slow request monitoring template. Each monitoring template will be configured with corresponding monitoring alarm rules. The monitoring host is used to obtain the performance indicators of the corresponding WebLogic server from the data collection host according to the received monitoring instructions, and then Calculate and integrate the performance indicators of this WebLogic server through the monitoring template to detect whether there is an abnormal situation; the data collection host is used to receive and store the performance indicators reported by each WebLogic server, and is also used to receive the monitoring instructions from the monitoring host. Send performance indicators corresponding to the WebLogic server to the monitoring host. By constructing the monitoring alarm system, the monitoring host can directly obtain the performance indicators of each WebLogic server through the data collection host in the system, without having to go to the corresponding WebLogic server to check the corresponding monitoring data to determine whether an abnormality occurs, which can improve Timeliness of anomaly monitoring alarms.

In this embodiment, when the monitoring host receives a monitoring instruction, the monitoring instruction may be sent by the management terminal or a preset timing monitoring instruction. The monitoring instruction may include a monitoring type and a WebLogic server name. Among them, the monitoring type can include but is not limited to the JVM CPU usage monitoring, JDBC connection monitoring, blocked thread monitoring, abnormal request monitoring, GC monitoring and slow request monitoring. The WebLogic server name can be the system name or number set in the monitoring alarm system of the server, or IP address. Of course, the monitoring instruction may include only the WebLogic server name, and at this time, all abnormal conditions are monitored by default.

Then, the monitoring host obtains the performance index of the corresponding WebLogic server from the data collection host according to the monitoring instruction. The performance index may include the number of completed requests, the number of JDBC connections, the number of idle threads, the number of execution threads, and the hogging (exclusive) thread. Number, JVM CPU usage, pending number, and heap usage. Among them, the number of completed requests refers to the number of completed requests processed within a preset time, for monitoring the amount of abnormal requests; the number of JDBC connections refers to the number of Java database connections, used for monitoring JDBC connections and slow request monitoring; the number of idle threads refers to the current idle The number of threads, the number of idle threads is generally> 50; the number of execution threads refers to the number of threads currently executing processing requests, used to determine the load problem of WebLogic; the number of hogging threads refers to the number of threads that have not completed the request for more than 30s, and For blocking thread monitoring; JVM CPU usage, which is the Java virtual machine CPU usage, for the JVM CPU usage monitoring; pending number refers to the number of waiting requests for slow request monitoring; heap usage, which is 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 indicator through the monitoring template, and detects whether the calculated and integrated performance indicator meets a corresponding preset alarm rule;

If the calculated and integrated performance index meets the corresponding preset alarm rule, step S30 is performed: the monitoring host performs an alarm reminder.

In this embodiment, after the monitoring host receives the monitoring instruction and obtains the performance index of the corresponding WebLogic server through the data collection host according to the monitoring instruction, the monitoring host determines the corresponding monitoring template according to the monitoring instruction and passes the monitoring instruction. The monitoring template calculates and integrates the obtained performance indicators, and detects whether the calculated and integrated performance indicators meet the corresponding preset alarm rules. If the calculated and integrated performance index meets the corresponding preset alarm rules, an alarm reminder is performed to prompt the corresponding operation and maintenance personnel to perform maintenance inspections in a timely manner, or to notify the corresponding responsible person of the abnormal situation and prompt them to solve it. If the calculated and integrated performance index does not satisfy the corresponding preset alarm rule, no alarm reminder is performed.

It should be noted that when the monitoring host obtains the performance indicators, it can obtain the performance indicators corresponding to the WebLogic server, and then determine the corresponding monitoring template according to the control instructions, and then select the corresponding indicators from the performance indicators for calculation through the monitoring template. Integration. Of course, in a specific embodiment, a performance indicator that needs to be obtained may also be determined first according to the monitoring instruction. For example, when the monitoring instruction is for the JVM When monitoring the CPU usage, you can only obtain the JVM CPU usage data for a period of time, and then use the corresponding monitoring template (such as the JVM CPU usage monitoring template) to analyze the JVM for a period of time. Corresponding calculation integration of CPU usage data.

The application provides a method for monitoring and alarming a WebLogic server. The method for monitoring and alarming a WebLogic server is applied to a monitoring and alarming system. The monitoring and alarming system includes a monitoring host, a data collection host, and multiple WebLogic servers. The monitoring host has a monitoring template built-in. The monitoring template set includes multiple monitoring templates. When the monitoring host receives the monitoring instruction, it can directly obtain the performance indicators of the corresponding WebLogic server through the data collection host in the system; and then use the monitoring template to obtain the obtained performance indicators. Perform calculation integration and check whether the calculated performance indicators meet the corresponding preset alarm rules; if the corresponding preset alarm rules are met, an alarm reminder is issued to prompt the corresponding operation and maintenance personnel to perform maintenance inspections in a timely manner. Therefore, this application does not need to install a monitoring module on each WebLogic server, which is more convenient to deploy. At the same time, it is not necessary to go to the corresponding WebLogic server to check the corresponding monitoring data to determine whether an abnormality occurs, thereby improving the timeliness of the abnormality monitoring alarm.

Further, since the monitoring template includes the JVM CPU usage monitoring template, JDBC connection number monitoring template, blocked thread monitoring template, abnormal request monitoring template, GC monitoring template, and slow request monitoring template. The performance indicators monitored by different monitoring templates are different, and the calculation and integration rules of the monitored performance indicators and the corresponding preset alarm rules are also different. Therefore, step S20 may include:

Step S21, if the monitoring template is a JVM A CPU usage monitoring template, or a JDBC connection number monitoring template, or a blocked thread monitoring template, or an abnormal request volume monitoring template, or a GC monitoring template, and the monitoring template is used to calculate a corresponding indicator in the performance indicator within a preset time. An average value of, and detecting whether the average value is greater than a corresponding first preset threshold;

At this time, if the average value is greater than the corresponding first preset threshold, step S30 is executed: the monitoring host performs an alarm reminder.

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 usage monitoring template, or JDBC connection number monitoring template, or blocked thread monitoring template, or abnormal request volume monitoring template, or GC monitoring template, the corresponding indicators in the performance index within a preset time are calculated by the corresponding monitoring template. An average value, and detect whether the average value is greater than a corresponding first preset threshold; if the average value is greater than the corresponding first preset threshold, an alarm is issued. If the average value is less than or equal to the corresponding first preset threshold value, no alarm reminder is performed.

Specifically, the preset alarm rule corresponding to the JVM CPU usage monitoring template is JVM within 5 minutes. If the average value of the CPU usage is higher than 80%, an alarm is triggered. If the monitoring template is the JVM CPU usage monitoring template, the JVM is executed through the JVM CPU usage monitoring template. When monitoring the CPU usage, you can select the JVM CPU usage data within 5 minutes from the current performance index and calculate the JVM within 5 minutes. The average value of CPU usage, and then check whether the average value is greater than 80%, and if it is greater than that, an alarm is issued.

The preset alarm rule corresponding to the JDBC connection number monitoring template is that an alarm is triggered if the number of JDBC connections exceeds 10 within 5 minutes. If the monitoring template is a JDBC connection number monitoring template, when monitoring the JDBC connection number through the JDBC connection number monitoring template, From the obtained performance indicators, select the JDBC connection data within 5 minutes from the current time, and calculate the average value of the JDBC connection number within 5 minutes, and then check whether the average value is greater than 10, and if it is greater, an alarm reminder is performed.

The preset alarm rule corresponding to the blocked thread monitoring template is to trigger an alarm if the number of hogging threads is greater than 5 within 5 minutes. If the monitoring template is a blocked thread monitoring template, you can obtain the In the performance index, the data of the number of hogging threads within 5 minutes from the current time is selected, and the average value of the number of hogging threads within 5 minutes is calculated, and then it is detected whether the average value is greater than 5, and if it is greater, an alarm reminder is performed.

The preset alarm rule corresponding to the abnormal request volume monitoring template is to trigger an alarm when the number of completed requests is higher than 10 within 5 minutes. If the monitoring template is an abnormal request volume monitoring template, you can monitor the abnormal request volume through the abnormal request volume monitoring template. From the obtained performance indicators, select the number of completed requests within 5 minutes from the current time, and calculate the average of the number of completed requests within 5 minutes, and then check whether the average is greater than 10, and if it is greater, an alarm reminder is performed.

The preset alarm rule corresponding to the GC monitoring template triggers an alarm when the heap usage rate is continuously higher than 80% within 10 minutes. If the monitoring template is a GC monitoring template, the performance indicators can be obtained when performing GC monitoring through the GC monitoring template. Select the heap usage data within 5 minutes from the current time, and calculate the average value of the heap usage within 5 minutes, and then check whether the average value is greater than 80%, and if it is greater than that, an alarm is issued.

In addition, step S20 may further include:

Step S22: If the monitoring template is a slow request monitoring template, use the slow request monitoring template to detect whether the currently pending pending number in the performance indicator is greater than a second preset threshold, and detect the current in the performance indicator. Whether the number of JDBC connections is greater than a third preset threshold;

At this time, if the number of pending pending is greater than the second preset threshold and the current number of JDBC connections is greater than the third preset threshold, step S30 is performed: an alarm reminder is performed.

In this embodiment, after the monitoring host determines a 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 higher than 5 pending and the number of JDBC connections When it exceeds 10, an alarm is triggered. When performing slow request monitoring through the slow request monitoring template, the real-time pending number and JDBC connection number (that is, the current pending number and the current JDBC connection number) can be obtained from the obtained performance indicators, and the current detection is performed. Whether the number of pending is greater than 5 and whether the current number of JDBC connections is greater than 10. If the current pending number is greater than 5, and the current number of JDBC connections is greater than 10, an alarm is issued. If only one of the monitoring alarm conditions is met, that is, only when the current pending number is greater than 5 or the current JDBC connection number is greater than 10, no alarm reminder is performed.

In this embodiment, the performance indicators of the Weblogic server are calculated and integrated through a monitoring template, such as determining whether to alarm based on the average value of a certain performance indicator within a preset time, or performing a combined monitoring alarm on different performance indicators instead of The alarm is reminded once according to a certain performance index once a preset range, so that this application can achieve more accurate alarms and reduce the alarm false alarm rate.

Further, referring to FIG. 4, FIG. 4 is a schematic flowchart of a second embodiment of a monitoring and alarming method of a WebLogic server of the present application.

Based on the first embodiment shown in FIG. 2 above, in this embodiment, step S30 may include:

Step S31: if the calculated and integrated performance index satisfies a corresponding preset alarm rule, the monitoring host determines a corresponding alarm level according to the monitoring template;

In step S32, the monitoring host determines a corresponding alarm mode according to the alarm level, and performs an alarm reminder according to the corresponding alarm mode.

In this embodiment, since the abnormality of the WebLogic server is divided into urgency levels, different alarm levels can be set according to the types of abnormalities monitored by different monitoring templates. When an abnormal situation is detected through a monitoring template and an alarm is required, the alarm is performed according to the alarm level corresponding to the monitoring template. The alarm levels can include critical (very severe), major (warning), warning (info). The corresponding relationship between each monitoring template and alarm level can be: JVM A CPU usage monitoring template corresponds to a critical level alarm, a JDBC connection number monitoring template corresponds to a major level alarm, a blocked thread monitoring template corresponds to a critical level alarm, an abnormal request volume monitoring template corresponds to a warning level alarm, a GC monitoring template corresponds to a warning level alarm, and a slow request monitoring The template corresponds to critical alarms. Of course, the corresponding relationship between each monitoring template and the alarm level is not limited to the above-mentioned relationship, and can be specifically set according to the actual situation.

Then, the corresponding alarm mode is determined according to the alarm level, and the alarm is reminded according to the corresponding alarm mode. Among them, different alarm levels correspond to different alarm methods. The alarm methods may include alarm forms, alarm times, and alarm objects. The alarm forms include email alerts, SMS alerts, and phone alerts. For example, the critical level only corresponds to the email reminder, the reminder number is 5 times, and the alert object is the first responsible person; Major level corresponds to email reminders and SMS reminders, each with 5 reminders, and the alert object is the first responsible person; warning level corresponds to email reminders and SMS reminders, each with 10 reminders, and the alert objects are the first and second responsible persons. ; Critical level corresponds to email reminder, SMS reminder and phone reminder, 10 times each for email reminder and SMS reminder, 2 times for phone reminder, and the alert object is the first responsible person and the second responsible person. Of course, in the actual situation, you can only remind once, if you haven't checked your email or SMS or missed calls, you will continue to be reminded. In addition, the first responsible person can be reminded first. When the reminder reaches a certain number of times, it can be changed to remind the second responsible person. For example, if a single alarm continues to send 10 emails and none have been consulted, it will be automatically sent to the second responsible person. Mail, or call the second owner if the first owner does not answer the call. The corresponding relationship between the alarm level and the alarm mode can be specifically set according to the actual situation, and is not specifically limited here.

Since some monitored performance indicators meet preset alarm conditions within a certain period of time, they are not abnormal situations. To avoid alarm reminders in such cases, the following steps may be included before step S32:

Step S33: The monitoring host determines a corresponding alarm mask time period according to the alarm level, and detects whether the current time is within the alarm mask time period;

If the current time is not within the alarm mask period, step S32 is performed: the monitoring host determines a corresponding alarm mode according to the alarm level, and performs an alarm reminder according to the corresponding alarm mode;

If the current time is within the alarm masking time period, step S34 is performed: the monitoring host does not perform an alarm reminder.

In this embodiment, after the corresponding alarm level is determined according to the monitoring template, the corresponding alarm mask time period is determined according to the alarm level, and it is detected whether the current time (that is, the time when the abnormality is detected) is in the alarm mask time period. If the current time is not within the alarm mask period, the subsequent step S32 is performed. If the current time is within the alarm mask time period, no alarm reminder will be performed. The alarm masking time period can be set according to actual needs, or the default setting can be adopted. Of course, in specific embodiments, the corresponding alarm masking time period may also be determined directly according to the monitoring template, without first determining the alarm level corresponding to the monitoring template, and then determining the corresponding alarm masking time period according to the alarm level.

In this embodiment, different alarm levels are set according to the urgency of the abnormality of the WebLogic server, thereby achieving hierarchical alarms, making the monitoring and alarm system more standardized and humane.

Further, please refer to FIG. 5, which is a schematic flowchart of a third embodiment of a method for monitoring and alarming a WebLogic server of the present application.

Based on the first embodiment shown in FIG. 2 above, after step S30, the method for monitoring and alarming of a WebLogic server further includes:

Step S40: The monitoring host records a corresponding alarm event in a preset alarm log according to the alarm condition, and 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 personnel to understand the specific situation of the alarm, the monitoring host will also record the alarm situation after the alarm is performed. Specifically, an alarm log is set in the monitoring host in advance to record alarm events. Of course, in this embodiment, since the monitoring host monitors multiple different WebLogic servers, multiple different alarms can be set. Log for separate alarm recording. When the monitoring host reports an alarm, the corresponding alarm event will be recorded in the alarm log. The alarm event may include the abnormal time (the time when the WebLogic server generates the exception), the type of the abnormality, and the alarm method.

Step S50: The monitoring host determines a high-frequency alarm time and / or a high-frequency anomaly type within a preset statistical period according to the preset alarm log, and according to the high-frequency alarm time and / or the high-frequency anomaly type Generate corresponding high-frequency alarm reports for the corresponding monitoring data.

Further, in order to facilitate the operation and maintenance personnel to understand the alarm conditions caused by the abnormality of each WebLogic server from a macro perspective, the monitoring server may also calculate data such as high-frequency alarm time and high-frequency abnormality within a certain period of time according to a preset alarm log. Among them, the high-frequency alarm time is the time of frequent occurrence of the alarm. For example, there were 300 alarms in June, and 200 alarms occurred from 9 am to 10 am. The high-frequency alarm time in April was 9 am to 10 am. Of course, in practice, the statistical period can be set according to the actual situation, such as one month as a statistical cycle, or one week as a statistical cycle; for the "high frequency" standard, it can also be It is set according to the actual situation. For example, a certain number of thresholds can be used as the "high frequency" judgment standard, or a certain percentage threshold can be used as the "high frequency" judgment standard. The high-frequency exception type is the multiple type of abnormal conditions. For example, there were 300 alarms in June, and 200 exception types were JVM. If the CPU usage is abnormal, the high-frequency exception type in April is JVM The CPU usage is abnormal; similarly, the statistical cycle time and the "high frequency" judgment criteria can also be set according to the actual situation. When obtaining these macroscopic statistical analysis results, the monitoring host can also provide relevant reports for operation and maintenance personnel to view; for example, the monitoring host can count the high-frequency alarm time and / Or high-frequency anomaly types, the monitoring data corresponding to these high-frequency alarm times and / or high-frequency anomaly types will be obtained, and corresponding high-frequency alarm reports will be generated for operation and maintenance personnel to view. The report performs maintenance and related optimizations to ensure the normal operation of the WebLogic server.

The application also provides a monitoring and alarm device for a WebLogic server.

Referring to FIG. 6, FIG. 6 is a schematic diagram of functional modules of a first embodiment of a monitoring and alarm device of a WebLogic server of the present application.

In this embodiment, the monitoring and alarm device of the WebLogic server includes:

The obtaining module 10 is configured to, when the monitoring host receives the monitoring instruction, obtain the performance index of the corresponding WebLogic server through the data collection host according to the monitoring instruction;

A detection module 20 is configured for the monitoring host to determine a corresponding monitoring template according to the monitoring instruction, calculate and integrate the performance indicator through the monitoring template, and detect whether the calculated and integrated performance indicator meets a corresponding preset Alarm rules

The alarm module 30 is configured to, if the calculated and integrated performance index meets a corresponding preset alarm rule, the monitoring host performs an alarm reminder.

The virtual function modules of the monitoring and alarming device of the WebLogic server are stored in the memory 1005 of the monitoring host shown in FIG. 1 and are used to implement all functions of the computer-readable instructions. When each module is executed by the processor 1001, it can be implemented through The data collection host obtains the performance indicators of each WebLogic server, and then calculates and integrates the performance indicators through a monitoring template, and performs an alarm reminder function when it is detected that the calculated and integrated performance indicators meet the corresponding preset alarm rules.

Further, the monitoring template includes a Java virtual machine central processor JVM CPU usage monitoring template, Java database connection JDBC connection number monitoring template, blocked thread monitoring template, abnormal request monitoring template, garbage collection GC monitoring template, and slow request monitoring template.

Further, the detection module 20 is specifically configured to be used if the monitoring template is a JVM. A CPU usage monitoring template, or a JDBC connection number monitoring template, or a blocked thread monitoring template, or an abnormal request volume monitoring template, or a GC monitoring template, and the monitoring template is used to calculate a corresponding indicator in the performance indicator within a preset time An average value of, and detecting whether the average value is greater than a corresponding first preset threshold;

The alarm module 30 is specifically configured to, if the average value is greater than a corresponding first preset threshold, the monitoring host performs an alarm reminder.

Further, the detection module 20 is specifically configured to detect, if the monitoring template is a slow request monitoring template, 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 number of JDBC connections in the performance index is greater than a third preset threshold;

The alarm module 30 is specifically configured to: if the current number of pending pending is greater than a second preset threshold and the current number of JDBC connections is greater than a third preset threshold, the monitoring host performs an alarm reminder.

Further, the alarm module 30 includes:

A level determining unit, configured to: if the calculated and integrated performance index meets a corresponding preset alarm rule, the monitoring host determines a corresponding alarm level according to the monitoring template;

An alarm reminding unit is used for the monitoring host to determine a corresponding alarm mode according to the alarm level, and to perform an alarm reminder according to the corresponding alarm mode.

Further, the alarm module 30 further includes:

A time detection unit, configured to determine, by the monitoring host, a corresponding alarm mask time period according to the alarm level, and detect whether the current time is within the alarm mask time period;

The alarm module 30 is specifically configured to: if the current time is within the alarm blocking time period, the monitoring host does not perform an alarm reminder.

Further, the monitoring and alarm device of the WebLogic server further includes:

A recording module for the monitoring host to record a corresponding alarm event in a preset alarm log according to an alarm situation, where the alarm event includes an abnormal time, an abnormal type, and an alarm mode;

A reporting module for the monitoring host to determine a high-frequency alarm time and / or a high-frequency anomaly type within a preset statistical period according to the preset alarm log, and according to the high-frequency alarm time and / or the high-frequency The monitoring data corresponding to the abnormality type generates corresponding high-frequency alarm reports.

The function implementation of each module in the monitoring and alarming device of the WebLogic server corresponds to the steps in the embodiment of the monitoring and alarming method of the WebLogic server, and the functions and implementation processes thereof will not be repeated here.

The application also provides a monitoring and alarming system of a WebLogic server. The monitoring and alarming system of the WebLogic server includes a monitoring host, a data collection host, and multiple WebLogic servers. The monitoring and alarm system also includes a memory, a processor, and a storage device stored in the storage device. The computer-readable instructions running on the processor are described, and when the computer-readable instructions are executed by the processor, the steps of the method for monitoring and alarming of the WebLogic server according to any one of the above embodiments are implemented.

The specific embodiments of the monitoring and alarming system of the WebLogic server of this application are basically the same as the above embodiments of the monitoring and alarming method of the WebLogic server, and will not be repeated here.

The present application also provides a computer storage medium, and the computer-readable storage medium may be a non-volatile readable storage medium. The computer storage medium stores computer-readable instructions. When the computer-readable instructions are executed by a processor, the steps of the method for monitoring and alarming a WebLogic server according to any one of the foregoing embodiments are implemented.

The specific embodiments of the computer storage medium of this application are basically the same as the above embodiments of the method of monitoring and alarming of the WebLogic server, and are not described herein again.

The above are only preferred embodiments of the present application, and thus do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made by using the contents of the specification and drawings of the present application, or directly or indirectly used in other related technical fields Are included in the scope of patent protection of this application.

Claims (20)

1. A monitoring and alarming method of a WebLogic server, characterized in that the monitoring and alarming method of the WebLogic server is applied to a monitoring and alarming system, and the monitoring and alarming system includes a monitoring host, a data collection host, and multiple middleware WebLogic servers. The host is communicatively connected to the data acquisition host, and the data acquisition host is communicatively connected to multiple WebLogic servers, and the method includes the following steps:

   When the monitoring host receives the monitoring instruction, it obtains the performance index of the corresponding WebLogic server through the data collection host according to the monitoring instruction;

   The monitoring host determines a corresponding monitoring template according to the monitoring instruction, calculates and integrates the performance indicator through the monitoring template, and detects whether the calculated and integrated performance indicator meets a corresponding preset alarm rule;

   If the calculated and integrated performance index satisfies the corresponding preset alarm rule, the monitoring host performs an alarm reminder.
2. The method for monitoring and alarming a WebLogic server according to claim 1, wherein the monitoring template comprises a Java virtual machine central processor (JVM) CPU usage monitoring template, Java database connection JDBC connection number monitoring template, blocked thread monitoring template, abnormal request monitoring template, garbage collection GC monitoring template, and slow request monitoring template.
3. The method for monitoring and alarming of a WebLogic server according to claim 2, wherein the performance indicator is calculated and integrated through the monitoring template, and it is detected whether the calculated and integrated performance indicator meets a corresponding preset alarm The steps of the rule include:

   If the monitoring template is a JVM A CPU usage monitoring template, or a JDBC connection number monitoring template, or a blocked thread monitoring template, or an abnormal request volume monitoring template, or a GC monitoring template, and the monitoring template is used to calculate a corresponding indicator in the performance indicator within a preset time. An average value of, and detecting whether the average value is greater than a corresponding first preset threshold;

   If the calculated and integrated performance index satisfies a corresponding preset alarm rule, the step of performing alarm reminding by the monitoring host includes:

   If the average value is greater than the corresponding first preset threshold, the monitoring host performs an alarm reminder.
4. The method for monitoring and alarming of a WebLogic server according to claim 2, wherein the performance indicator is calculated and integrated through the monitoring template, and it is detected whether the calculated and integrated performance indicator meets a corresponding preset alarm The steps of the rule also include:

   If the monitoring template is a slow request monitoring template, use the slow request monitoring template to detect whether the number of currently pending pending in the performance indicator is greater than a second preset threshold, and detect the current number of JDBC connections in the performance indicator. Whether it is greater than a third preset threshold;

   If the calculated and integrated performance index satisfies a corresponding preset alarm rule, the step of performing alarm reminding by the monitoring host includes:

   If the number of pending pending is greater than the second preset threshold and the current number of JDBC connections is greater than the third preset threshold, the monitoring host performs an alarm reminder.
5. The method for monitoring and alarming a WebLogic server according to claim 1, wherein, if the calculated and integrated performance index satisfies a corresponding preset alarm rule, the step of performing an alarm reminding by the monitoring host comprises:

   If the calculated and integrated performance index satisfies a corresponding preset alarm rule, the monitoring host determines a corresponding alarm level according to the monitoring template;

   The monitoring host determines a corresponding alarm mode according to the alarm level, and performs an alarm reminder according to the corresponding alarm mode.
6. The method for monitoring and alarming a WebLogic server according to claim 5, wherein before the step of the monitoring host determining a corresponding alarm mode according to the alarm level and performing an alarm reminder according to the corresponding alarm mode, further comprising:

   The monitoring host determines a corresponding alarm mask period according to the alarm level, and detects whether the current time is within the alarm mask period;

   If the current time is not within the alarm masking time period, performing the steps: the monitoring host determines a corresponding alarm mode according to the alarm level, and performs an alarm reminder according to the corresponding alarm mode;

   If the current time is within the alarm masking time period, the monitoring host does not perform an alarm reminder.
7. The method of monitoring and alarming a WebLogic server according to claim 1, wherein the method of monitoring and alarming a WebLogic server further comprises:

   The monitoring host records a corresponding alarm event in a preset alarm log according to an alarm condition, and the alarm event includes an abnormal time, an abnormal type, and an alarm mode;

   The monitoring host determines a high-frequency alarm time and / or a high-frequency anomaly type within a preset statistical period according to the preset alarm log, and respectively corresponding to the high-frequency alarm time and / or the high-frequency anomaly type. The monitoring data generates corresponding high-frequency alarm reports.
8. A monitoring and alarm device for a WebLogic server, characterized in that the monitoring and alarm device for a WebLogic server includes:

   An acquisition module, configured to, when the monitoring host receives a monitoring instruction, obtain a performance indicator of a corresponding WebLogic server through the data collection host according to the monitoring instruction;

   A detection module for the monitoring host to determine a corresponding monitoring template according to the monitoring instruction, calculate and integrate the performance indicator through the monitoring template, and detect whether the calculated and integrated performance indicator meets a corresponding preset alarm rule;

   The alarm module is configured to: if the calculated and integrated performance index meets a corresponding preset alarm rule, the monitoring host performs an alarm reminder.
9. The monitoring and alarming device for a WebLogic server according to claim 8, wherein the monitoring template comprises a Java virtual machine central processor (JVM) CPU usage monitoring template, Java database connection JDBC connection number monitoring template, blocked thread monitoring template, abnormal request monitoring template, garbage collection GC monitoring template, and slow request monitoring template. Ranch
10. The monitoring and alarming device for a WebLogic server according to claim 9, wherein the detection module is specifically configured to use a JVM if the monitoring template is a JVM A CPU usage monitoring template, or a JDBC connection number monitoring template, or a blocked thread monitoring template, or an abnormal request volume monitoring template, or a GC monitoring template, and the monitoring template is used to calculate a corresponding indicator in the performance indicator within a preset time. An average value of, and detecting whether the average value is greater than a corresponding first preset threshold;

    The alarm module is specifically configured to: if the average value is greater than a corresponding first preset threshold, the monitoring host performs an alarm reminder.
11. The monitoring and alarm device for a WebLogic server according to claim 9, wherein the detection module is further specifically configured to detect the performance index through the slow request monitoring template if the monitoring template is a slow request monitoring template Whether the current number of pending pending in the server is greater than a second preset threshold, and detecting whether the current number of JDBC connections in the performance index is greater than a third preset threshold;

    The alarm module is further specifically configured to: if the current number of pending pending is greater than a second preset threshold and the current number of JDBC connections is greater than a third preset threshold, the monitoring host performs an alarm reminder.
12. The monitoring and alarm device of the WebLogic server according to claim 8, wherein the monitoring and alarm device of the WebLogic server further comprises:

    A level determining unit, configured to: if the calculated and integrated performance index meets a corresponding preset alarm rule, the monitoring host determines a corresponding alarm level according to the monitoring template;

    An alarm reminding unit is used for the monitoring host to determine a corresponding alarm mode according to the alarm level, and to perform an alarm reminder according to the corresponding alarm mode.
13. A monitoring and alarm system of a WebLogic server, characterized in that the monitoring and alarm system of the WebLogic server includes a monitoring host, a data acquisition host, and multiple WebLogic servers, and further includes a memory, a processor, and a memory that can be stored on the memory and can be Computer-readable instructions executed by the processor, wherein when the computer-readable instructions are executed by the processor, the following steps are implemented:

    When the monitoring host receives the monitoring instruction, it obtains the performance index of the corresponding WebLogic server through the data collection host according to the monitoring instruction;

    The monitoring host determines a corresponding monitoring template according to the monitoring instruction, calculates and integrates the performance indicator through the monitoring template, and detects whether the calculated and integrated performance indicator meets a corresponding preset alarm rule;

    If the calculated and integrated performance index satisfies the corresponding preset alarm rule, the monitoring host performs an alarm reminder.
14. The monitoring and alarm system of the WebLogic server according to claim 13, wherein the monitoring template comprises a Java virtual machine central processor (JVM) CPU usage monitoring template, Java database connection JDBC connection number monitoring template, blocked thread monitoring template, abnormal request monitoring template, garbage collection GC monitoring template, and slow request monitoring template.
15. The monitoring and alarm system of the WebLogic server according to claim 14, wherein when the computer-readable instructions are executed by the processor, the following steps are further implemented:

    If the monitoring template is a JVM A CPU usage monitoring template, or a JDBC connection number monitoring template, or a blocked thread monitoring template, or an abnormal request volume monitoring template, or a GC monitoring template, and the monitoring template is used to calculate a corresponding indicator in the performance indicator within a preset time. An average value of, and detecting whether the average value is greater than a corresponding first preset threshold;

    If the average value is greater than the corresponding first preset threshold, the monitoring host performs an alarm reminder.
16. The monitoring and alarm system of the WebLogic server according to claim 14, wherein when the computer-readable instructions are executed by the processor, the following steps are further implemented:

    If the monitoring template is a slow request monitoring template, use the slow request monitoring template to detect whether the number of currently pending pending in the performance indicator is greater than a second preset threshold, and detect the current number of JDBC connections in the performance indicator. Whether it is greater than a third preset threshold;

    If the number of pending pending is greater than the second preset threshold and the current number of JDBC connections is greater than the third preset threshold, the monitoring host performs an alarm reminder.
17. A computer storage medium is characterized in that computer readable instructions are stored on the computer storage medium, and when the computer readable instructions are executed by a processor, the following steps are implemented:

    When the monitoring host receives the monitoring instruction, it obtains the performance index of the corresponding WebLogic server through the data collection host according to the monitoring instruction;

    The monitoring host determines a corresponding monitoring template according to the monitoring instruction, calculates and integrates the performance indicator through the monitoring template, and detects whether the calculated and integrated performance indicator meets a corresponding preset alarm rule;

    If the calculated and integrated performance index satisfies the corresponding preset alarm rule, the monitoring host performs an alarm reminder.
18. The computer storage medium of claim 17, wherein the monitoring template comprises a Java virtual machine central processing unit (JVM) CPU usage monitoring template, Java database connection JDBC connection number monitoring template, blocked thread monitoring template, abnormal request monitoring template, garbage collection GC monitoring template, and slow request monitoring template.
19. The computer storage medium of claim 18, wherein when the computer-readable instructions are executed by a processor, the following steps are further implemented:

    If the monitoring template is a JVM A CPU usage monitoring template, or a JDBC connection number monitoring template, or a blocked thread monitoring template, or an abnormal request volume monitoring template, or a GC monitoring template, and the monitoring template is used to calculate a corresponding indicator in the performance indicator within a preset time. An average value of, and detecting whether the average value is greater than a corresponding first preset threshold;

    If the average value is greater than the corresponding first preset threshold, the monitoring host performs an alarm reminder.
20. The computer storage medium of claim 18, wherein when the computer-readable instructions are executed by a processor, the following steps are further implemented:

    If the monitoring template is a slow request monitoring template, use the slow request monitoring template to detect whether the number of currently pending pending in the performance indicator is greater than a second preset threshold, and detect the current number of JDBC connections in the performance indicator. Whether it is greater than a third preset threshold;

    If the number of pending pending is greater than the second preset threshold and the current number of JDBC connections is greater than the third preset threshold, the monitoring host performs an alarm reminder.