CN115080192A - JVM performance monitoring method, system, equipment and medium - Google Patents
JVM performance monitoring method, system, equipment and medium Download PDFInfo
- Publication number
- CN115080192A CN115080192A CN202211009295.XA CN202211009295A CN115080192A CN 115080192 A CN115080192 A CN 115080192A CN 202211009295 A CN202211009295 A CN 202211009295A CN 115080192 A CN115080192 A CN 115080192A
- Authority
- CN
- China
- Prior art keywords
- jvm
- garbage collection
- garbage
- network data
- bytes
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
- G06F12/023—Free address space management
- G06F12/0253—Garbage collection, i.e. reclamation of unreferenced memory
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45591—Monitoring or debugging support
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Abstract
The invention provides a method, a system, equipment and a medium for monitoring JVM performance, wherein the method comprises the following steps: a garbage collection event monitor provided by Java is adopted to periodically acquire garbage collection events generated in the JVM; analyzing the garbage collection event, and serializing the garbage collection event into a network data packet with a custom format; acquiring the garbage recycling condition of each application program in the JVM based on the network data packet; and early warning the security risk of the JVM based on the garbage recovery condition. The method has the effects of carrying out risk warning on the operation of the JVM and improving the operation stability of the JVM.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a JVM performance monitoring method, a JVM performance monitoring system, JVM performance monitoring equipment and a JVM performance monitoring medium.
Background
JVM is an abbreviation of Java Virtual Machine, a Java Virtual Machine, which is a computer based on the specification fictitious of computer devices; the JVM shields the information of a specific operating system platform, platform independence is realized by the JVM and Java, and the Java language does not need to be recompiled when running on different platforms and only needs to be deployed on the platform.
When the JVM is used, the JVM needs to be monitored, so that the use process can be better controlled, and the monitoring of the JVM focuses on the use condition of the memory of the JVM. In the prior art, there are many JVM monitoring methods, for example, Jvisualvm or Java Flight Recorder; jvisualvm is a JVM visualization tool provided by Java, and if a remote JVM on a server needs to be monitored, the JMX port needs to be opened by the server for connection, so that great potential safety hazards are easily caused. In a production environment, tools such as jvisualvm and jstat cannot conveniently acquire garbage recycling information of the JVM.
Disclosure of Invention
The invention aims to provide a method, a system, equipment and a medium for monitoring JVM performance, which aim to monitor the JVM in a production environment so as to carry out risk warning on the operation of the JVM and improve the operation stability of the JVM.
The embodiment of the invention is realized by the following technical scheme:
first aspect
An embodiment of the present application provides a JVM performance monitoring method, where the method includes:
a garbage collection event monitor provided by Java is adopted to periodically acquire garbage collection events generated in the JVM;
analyzing the garbage collection event, and serializing the garbage collection event into a network data packet with a custom format;
acquiring garbage recycling conditions of all application programs in the JVM based on the network data packet;
and early warning the security risk of the JVM based on the garbage recovery condition.
Optionally, the analyzing the garbage collection event and serializing the garbage collection event into a network data packet with a custom format includes:
constructing a JVM performance analyzer;
establishing a network connection between the JVM performance analyzer and the garbage collection event listener;
periodically iterating the garbage recycling events stored in the local cache of the application program, and serializing the garbage recycling events into network data packets with a custom format;
sending the network packet to the JVM performance analyzer based on a network connection between the JVM performance analyzer and the garbage collection event listener.
Optionally, the method further includes emptying the application local cache each time a serialized garbage collection event in the application local cache is completed.
Optionally, the network data packet with the custom format includes a data packet length of 4 bytes, an application number of 2 bytes, a JDK version of 4 bytes, a data length of a garbage collection action name of several bytes, a garbage collection type of 1 byte, a data length of a reason for triggering garbage collection of several bytes, a reason for punishing garbage collection of several bytes, a data length of a remaining space before and after garbage collection of each memory area of several bytes, a garbage collection start time of 8 bytes, and a garbage collection end time of 8 bytes.
Optionally, the method further comprises:
and regularly acquiring the latest TAG from an OpenJDK official warehouse of Github, updating the memory area name of the JVM based on the TAG, and associating the current source code version with the memory area name of the JVM.
Optionally, the obtaining the garbage collection condition of each application in the JVM based on the network data packet includes:
the JVM performance analyzer reads garbage collection conditions from the network data packet, wherein the garbage collection conditions comprise garbage collection action names, garbage collection types, garbage collection reasons, garbage collection starting time and garbage collection ending time;
the JVM performance analyzer acquires residual spaces before and after garbage collection of each region based on the JVM memory region name;
and the JVM performance analyzer stores the garbage collection condition and the residual space before and after the garbage collection of each region into a Redis cache.
Optionally, the method further comprises:
the JVM performance analyzer acquires an application program number in the network data packet;
and the JVM performance analyzer collects garbage collection conditions according to the application program number and sends the garbage collection conditions to a Web page.
Second aspect of the invention
The embodiment of the application provides a JVM performance monitoring system, which comprises a garbage event acquisition module, an analysis module, a recovery condition acquisition module and a risk early warning module;
a garbage event acquiring module, configured to periodically acquire a garbage collection event occurring in the JVM;
the analysis module is used for analyzing the garbage recovery events and serializing the garbage recovery events into network data packets with a custom format;
a recovery condition obtaining module, configured to obtain, based on the network data packet, a garbage recovery condition of each application in the JVM;
and the risk early warning module is used for early warning the security risk of the JVM based on the garbage recycling condition.
Third aspect
An embodiment of the present application provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes a JVM performance monitoring method according to the first aspect of the present disclosure.
Fourth aspect of the invention
An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a JVM performance monitoring method according to the first aspect of the invention.
The technical scheme of the embodiment of the invention at least has the following advantages and beneficial effects: when monitoring garbage collection events in the JVM, because a garbage collection event monitor carried by Java itself is adopted, an external interface is not required to be provided, the safety of a generation environment is not influenced, and the garbage collection event monitor has better safety performance; after the obtained garbage recycling events are serialized into network data packets, by analyzing the network data packets, more complete data can be obtained for users to early warn and alarm the running risk of the JVM, and therefore the effect of improving the running stability of the JVM is achieved.
Drawings
FIG. 1 is a flowchart illustrating steps of a JVM performance monitoring method according to an embodiment of the present invention;
fig. 2 is a block diagram of a JVM performance monitoring system according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Example 1
This embodiment provides a JVM performance monitoring method, and referring to fig. 1, the method includes the following steps:
s101, a garbage collection event monitor provided by Java is adopted to periodically acquire garbage collection events generated in the JVM;
in Java, a memory does not need to be manually released, and a garbage collector in the JVM can automatically collect the memory, so that a garbage collection event can be generated, the use condition of the memory in the JVM can be judged by monitoring the garbage collection event, and the risk of the operation stability of the JVM is alarmed.
The garbage collection event monitor is provided by Java, the garbage collection event monitor can directly monitor the JVM, and the JVM does not need to provide an additional interface during monitoring, so that the JVM has great significance in maintaining the safety performance in a production environment.
S102, analyzing the garbage recycling event, and serializing the garbage recycling event into a network data packet with a custom format. The method comprises the following substeps:
s1021, constructing a JVM performance analyzer; in this embodiment, the JVM performance analyzer is constructed in Java language, and its main role in this embodiment is to analyze the garbage collection event of the JVM.
S1022, establishing network connection between the JVM performance analyzer and the garbage collection event listener; by setting network connection between the JVM performance analyzer and the garbage collection event listener, the garbage collection event of the application program acquired by the garbage collection event listener can be transmitted to the JVM performance analyzer and then analyzed by the JVM performance analyzer.
S1023, periodically iterating the garbage recycling events stored in the local cache of the application program, and serializing the garbage recycling events into a network data packet with a custom format;
the data format of the network data packet with the custom format comprises a data packet length of 4 bytes, an application program number of 2 bytes, a JDK version of 4 bytes, a data length of a garbage collection action name of a plurality of bytes, a garbage collection type of 1 byte, a data length of a reason for triggering garbage collection of a plurality of bytes, a reason for punishing garbage collection of a plurality of bytes, a data length of a residual space before and after garbage collection of each memory area of a plurality of bytes, garbage collection start time of 8 bytes and garbage collection end time of 8 bytes.
During iteration, the application garbage recycling events are stored in the local cache of the application and are not sent to the JVM performance analyzer, and the application garbage recycling events are subjected to iteration and serialization to be normalized into network data packets, so that the analysis and processing of the JVM performance analyzer can be facilitated.
And after the serialized garbage collection event in the local cache of the application program is completed, the local cache of the application program is emptied, so that the phenomenon that the local cache of the application program is occupied too much to cause that the memory cannot be cleaned is avoided.
S1024, based on the network connection between the JVM performance analyzer and the garbage collection event listener, sending the network data packet to the JVM performance analyzer.
S103, acquiring garbage recycling conditions of all application programs in the JVM based on the network data packet;
when monitoring the JVM, the main purpose is to monitor the application garbage collection event to determine the memory usage in the JVM, and the memory usage of the JVM can be determined by the garbage collection of the application in the JVM. It is necessary to obtain the garbage collection condition of JVM through the analysis of network packets.
The JVM performance analyzer reads garbage collection conditions from the network data packet, wherein the garbage collection conditions comprise garbage collection action names, garbage collection types, garbage collection reasons, garbage collection starting time and garbage collection ending time; before uploading, the application garbage collection events occurring in the JVM are serialized into network data packets and uploaded, and the format of the network data packets is relatively complete, so that the JVM performance analyzer can very conveniently acquire the required garbage collection situation from the network data packets.
And regularly acquiring the latest TAG from an OpenJDK official warehouse of Github, updating the memory area name of the JVM based on the TAG, and associating the current source code version with the memory area name of the JVM. Because the source code version of the JVM is updated frequently, when monitoring the JVM, the latest TAG needs to be obtained from the OpenJDK official repository of gitubb periodically, so as to ensure that the source code version of the JVM can be the same as the version published by the official repository, and the situation of inconsistent versions does not occur when monitoring the JVM.
When the latest TAG is obtained, whether the latest TAG is issued or not is detected from a fixed official page, if so, a corresponding source code file is downloaded, and after the source code file is decompressed, a hotspot/src/share/vm/services/memoryManager. hpp file is read; using regular expression/return. + ", obtaining all JVM memory area names; and associating all the acquired JVM memory area names with the JVM memory area names under the current source code version to prevent the problems caused by different versions.
The JVM performance analyzer reads an application program number after receiving a network data packet, the application program number is randomly generated by using a UUID when monitoring is started each time, when the network data packet is analyzed, configuration information corresponding to the application program is firstly read in an Rdeis cache, the configuration information comprises a JDK version, the end time of a last garbage collection event, the garbage collection times and the total garbage collection time consumption, if corresponding buffering is not read, the application program is indicated to enter monitoring for the first time, and the three index values of the end time of the last garbage collection event, the garbage collection times and the total garbage collection time consumption are set to be 0.
Acquiring residual spaces before and after garbage collection of each region based on the JVM memory region name; and corresponding the memory area name of the JVM to an application program contained in a network data packet, and counting the garbage collection times, the total garbage collection time, the garbage collection times of various types, the total garbage collection time of various types, the distribution condition of various types of garbage collection, the garbage collection frequency of six time spans of latest 5 seconds/10 seconds/30 seconds/1 minute/5 minutes/10 minutes and the trend of the occupation condition of the memory area space of the JVM of the application program. And the JVM performance analyzer stores the garbage collection condition and the residual space before and after the garbage collection of each region into a Redis cache.
And S104, early warning the security risk of the JVM based on the garbage collection condition.
The JVM performance analyzer acquires an application program number in the network data packet;
and the JVM performance analyzer collects garbage collection conditions according to the application program number and sends the garbage collection conditions to a Web page. The JVM user can clearly know the memory release condition of the JVM through the Web page, so that the JVM is observed in long-term continuous use, early warning and alarming on JVM operation risks can be realized in an auxiliary mode through deep excavation of acquired data, and the operation stability of a production environment system is improved.
In the implementation, when monitoring garbage collection events occurring in the JVM, since a Java-owned garbage collection event listener is adopted, an external interface is not required, the security of a generation environment is not affected, and the method has better security performance; after the obtained garbage recovery events are serialized into network data packets, the network data packets are analyzed, so that more complete data can be obtained for users to early warn and alarm the operation risk of the JVM, and the effect of improving the operation stability of the JVM is achieved.
Example 2
The present embodiment provides a JVM performance monitoring system, referring to fig. 2, including a garbage event obtaining module, an analyzing module, a recovery condition obtaining module, and a risk early warning module;
a garbage event acquiring module, configured to periodically acquire a garbage collection event occurring in the JVM;
the analysis module is used for analyzing the garbage recovery events and serializing the garbage recovery events into network data packets with custom formats;
a recovery condition obtaining module, configured to obtain, based on the network data packet, a garbage recovery condition of each application in the JVM;
and the risk early warning module is used for early warning the security risk of the JVM based on the garbage recycling condition.
Example 3
An embodiment of the present application provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the JVM performance monitoring method described in embodiment 1.
Example 4
An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a JVM performance monitoring method as described in embodiment 1.
The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes will occur to those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A JVM performance monitoring method, the method comprising:
a garbage collection event monitor provided by Java is adopted to periodically acquire garbage collection events generated in the JVM;
analyzing the garbage collection event, and serializing the garbage collection event into a network data packet with a custom format;
acquiring garbage recycling conditions of all application programs in the JVM based on the network data packet;
and early warning the security risk of the JVM based on the garbage recovery condition.
2. The JVM performance monitoring method of claim 1, wherein the analyzing the garbage collection events and serializing the garbage collection events into custom formatted network packets comprises:
constructing a JVM performance analyzer;
establishing a network connection between the JVM performance analyzer and the garbage collection event listener;
periodically iterating the garbage recycling events stored in the local cache of the application program, and serializing the garbage recycling events into network data packets with a custom format;
sending the network packet to the JVM performance analyzer based on a network connection between the JVM performance analyzer and the garbage collection event listener.
3. The JVM performance monitoring method of claim 2, wherein: the method also includes emptying the application local cache each time a serialized garbage collection event is completed in the application local cache.
4. The JVM performance monitoring method of claim 2, wherein: the network data packet with the user-defined format comprises a data packet length of 4 bytes, an application program number of 2 bytes, a JDK version of 4 bytes, a data length of a garbage collection action name of a plurality of bytes, a garbage collection type of 1 byte, a data length of a reason for triggering garbage collection of a plurality of bytes, a reason for punishing garbage collection of a plurality of bytes, a data length of a residual space before and after garbage collection of each memory area of a plurality of bytes, garbage collection starting time of 8 bytes and garbage collection ending time of 8 bytes.
5. The JVM performance monitoring method of claim 4, wherein: the method further comprises the following steps:
and regularly acquiring the latest TAG from an OpenJDK official warehouse of Github, updating the memory area name of the JVM based on the TAG, and associating the current source code version with the memory area name of the JVM.
6. The JVM performance monitoring method of claim 5, wherein: the obtaining the garbage collection condition of each application program in the JVM based on the network data packet includes:
the JVM performance analyzer reads garbage collection conditions from the network data packet, wherein the garbage collection conditions comprise garbage collection action names, garbage collection types, garbage collection reasons, garbage collection starting time and garbage collection ending time;
the JVM performance analyzer acquires residual spaces before and after garbage collection of each region based on the JVM memory region name;
and the JVM performance analyzer stores the garbage collection condition and the residual space before and after the garbage collection of each region into a Redis cache.
7. The JVM performance monitoring method of claim 5, wherein: the method further comprises the following steps:
the JVM performance analyzer acquires an application program number in the network data packet;
and the JVM performance analyzer collects garbage collection conditions according to the application program number and sends the garbage collection conditions to a Web page.
8. A JVM performance monitoring system, comprising: the system comprises a garbage event acquisition module, an analysis module, a recovery condition acquisition module and a risk early warning module;
a garbage event acquiring module, configured to periodically acquire a garbage collection event occurring in the JVM;
the analysis module is used for analyzing the garbage recovery events and serializing the garbage recovery events into network data packets with a custom format;
a recovery condition obtaining module, configured to obtain, based on the network data packet, a garbage recovery condition of each application in the JVM;
and the risk early warning module is used for early warning the security risk of the JVM based on the garbage recycling condition.
9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements a JVM performance monitoring method as claimed in any of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements a JVM performance monitoring method as claimed in any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211009295.XA CN115080192A (en) | 2022-08-23 | 2022-08-23 | JVM performance monitoring method, system, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211009295.XA CN115080192A (en) | 2022-08-23 | 2022-08-23 | JVM performance monitoring method, system, equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115080192A true CN115080192A (en) | 2022-09-20 |
Family
ID=83245364
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211009295.XA Pending CN115080192A (en) | 2022-08-23 | 2022-08-23 | JVM performance monitoring method, system, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115080192A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070016633A1 (en) * | 2005-07-15 | 2007-01-18 | Bea Systems, Inc. | System and method for deterministic garbage collection in a virtual machine environment |
| CN103870315A (en) * | 2014-03-26 | 2014-06-18 | 中国联合网络通信集团有限公司 | JVM energy consumption control method and device |
| CN108446162A (en) * | 2018-02-13 | 2018-08-24 | 南京途牛科技有限公司 | Monitor the method and system of JVM Full GC events |
| CN110555004A (en) * | 2019-07-30 | 2019-12-10 | 北京奇艺世纪科技有限公司 | Service monitoring method and device, computer equipment and storage medium |
| CN111966464A (en) * | 2020-08-20 | 2020-11-20 | 苏州浪潮智能科技有限公司 | Simple JVM monitoring method and device and computer readable storage medium |
| CN112835765A (en) * | 2021-02-02 | 2021-05-25 | 中国工商银行股份有限公司 | Java program memory use condition monitoring method and device |
| CN113010367A (en) * | 2020-11-02 | 2021-06-22 | 证通股份有限公司 | Monitoring method and monitoring system for JAVA process garbage recovery |
-
2022
- 2022-08-23 CN CN202211009295.XA patent/CN115080192A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070016633A1 (en) * | 2005-07-15 | 2007-01-18 | Bea Systems, Inc. | System and method for deterministic garbage collection in a virtual machine environment |
| CN103870315A (en) * | 2014-03-26 | 2014-06-18 | 中国联合网络通信集团有限公司 | JVM energy consumption control method and device |
| CN108446162A (en) * | 2018-02-13 | 2018-08-24 | 南京途牛科技有限公司 | Monitor the method and system of JVM Full GC events |
| CN110555004A (en) * | 2019-07-30 | 2019-12-10 | 北京奇艺世纪科技有限公司 | Service monitoring method and device, computer equipment and storage medium |
| CN111966464A (en) * | 2020-08-20 | 2020-11-20 | 苏州浪潮智能科技有限公司 | Simple JVM monitoring method and device and computer readable storage medium |
| CN113010367A (en) * | 2020-11-02 | 2021-06-22 | 证通股份有限公司 | Monitoring method and monitoring system for JAVA process garbage recovery |
| CN112835765A (en) * | 2021-02-02 | 2021-05-25 | 中国工商银行股份有限公司 | Java program memory use condition monitoring method and device |
Non-Patent Citations (1)
| Title |
|---|
| 江福松等编著: "《JAVA快速入门》", 30 November 1997, 人民邮电出版社 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109710615B (en) | Database access management method, system, electronic device and storage medium | |
| KR101292979B1 (en) | Method for managing software in terminal using device management server | |
| US7167915B2 (en) | Monitoring storage resources used by computer applications distributed across a network | |
| US20090007146A1 (en) | Method and system to correlate and consolidate a plurality of events | |
| EP2324406B1 (en) | Method and apparatus for monitoring the performance of a power delivery control system | |
| US20060116981A1 (en) | Method and system for automated data collection and analysis of a computer system | |
| US20090271437A1 (en) | Determining computer information from processor properties | |
| CN110309029B (en) | Abnormal data acquisition method and device, computer equipment and storage medium | |
| US8650444B2 (en) | Operation management device and operation management method | |
| CN106407102B (en) | Fuzzy testing method, device and system for application program | |
| US9600523B2 (en) | Efficient data collection mechanism in middleware runtime environment | |
| CN111026621A (en) | Monitoring alarm method, device, equipment and medium for Elasticissearch cluster | |
| CN112306802A (en) | Data acquisition method, device, medium and electronic equipment of system | |
| CN111367760A (en) | Log collection method and device, computer equipment and storage medium | |
| CN114356499A (en) | Kubernetes cluster alarm root cause analysis method and device | |
| CN111597089B (en) | Linux system call event acquisition and caching device and method | |
| EP3789882B1 (en) | Automatic configuration of logging infrastructure for software deployments using source code | |
| CN111061498A (en) | Configuration information management system | |
| US8554908B2 (en) | Device, method, and storage medium for detecting multiplexed relation of applications | |
| CN115080192A (en) | JVM performance monitoring method, system, equipment and medium | |
| JP4256107B2 (en) | Method and program for dealing with unauthorized intrusion to data server | |
| CN116708217A (en) | Data center equipment monitoring method, system, electronic equipment and storage medium | |
| CN107656849B (en) | Method and device for positioning performance problem of software system | |
| CN111198902A (en) | Metadata management method and device, storage medium and electronic equipment | |
| CN112764990B (en) | Target process monitoring method and device and computer equipment |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220920 |
|
| RJ01 | Rejection of invention patent application after publication |