CN112506734A - Service system and management method thereof - Google Patents
Service system and management method thereof Download PDFInfo
- Publication number
- CN112506734A CN112506734A CN202011246450.0A CN202011246450A CN112506734A CN 112506734 A CN112506734 A CN 112506734A CN 202011246450 A CN202011246450 A CN 202011246450A CN 112506734 A CN112506734 A CN 112506734A
- Authority
- CN
- China
- Prior art keywords
- server
- production environment
- abnormal
- service
- environment server
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 14
- 238000004519 manufacturing process Methods 0.000 claims abstract description 114
- 230000002159 abnormal effect Effects 0.000 claims abstract description 82
- 230000008439 repair process Effects 0.000 claims abstract description 29
- 238000012544 monitoring process Methods 0.000 claims abstract description 22
- 230000005856 abnormality Effects 0.000 claims description 34
- 238000000034 method Methods 0.000 claims description 13
- 238000004422 calculation algorithm Methods 0.000 claims description 12
- 238000012545 processing Methods 0.000 claims description 8
- 238000013480 data collection Methods 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000013515 script Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3055—Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3024—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a central processing unit [CPU]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3037—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a memory, e.g. virtual memory, cache
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Mathematical Physics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention relates to a service system and a management method thereof, wherein the service system comprises: the system comprises a production environment server, a monitoring system server and an exception handling server; the production environment server is used for supporting a specific production environment service; the monitoring system server is used for acquiring performance index data of the production environment server; and the exception handling server is used for judging whether the production environment server is abnormal or not according to the performance index data of the production environment server, and determining an abnormal reason and giving a repair suggestion when the abnormal occurs. The service system can provide more accurate monitoring service for the production environment, judge whether the production environment server is abnormal according to the performance index of the production environment server, and give a repair suggestion when the production environment server is abnormal or automatically repair the production environment server.
Description
Technical Field
The invention relates to the technical field of monitoring services, in particular to a service system and a management method thereof.
Background
The traditional monitoring service can only roughly monitor whether the service is abnormal or not, can not monitor different services in different production environments in more detail, can not automatically repair when the service is abnormal, can be used after being maintained by professional maintenance personnel, and seriously influences the use of a server. Therefore, the existing monitoring service has low intelligent degree and is not beneficial to improving the working efficiency and the user experience.
Disclosure of Invention
In view of the above, the present invention provides a service system and a management method thereof to overcome the disadvantages of the prior art.
In order to achieve the purpose, the invention adopts the following technical scheme: a service system, comprising:
the system comprises a production environment server, a monitoring system server and an exception handling server;
the production environment server is used for supporting a specific production environment service;
the monitoring system server is used for acquiring performance index data of the production environment server;
and the exception handling server is used for judging whether the production environment server is abnormal or not according to the performance index data of the production environment server, and determining an abnormal reason and giving a repair suggestion when the abnormal occurs.
Optionally, the monitoring system server includes:
the performance index acquisition module is used for automatically acquiring indexes corresponding to the production environment server; the system is also used for acquiring the specific index of the corresponding production service according to the request sent by the exception handling server;
the crash data collection module is used for immediately collecting the performance indexes within a specific range of a crash time point when the service on the production environment server is abnormally crashed;
and the first sending module is used for sending the index data acquired by the performance index acquisition module and the crash data collection module to the exception handling server.
Optionally, the performance indicator data at least includes one of the following items:
server CPU, memory, network bandwidth, IO and disk space.
Optionally, the method further includes:
an anomaly statistics server;
the exception handling server comprises: the abnormity judgment module and the second sending module;
the abnormity judgment module is used for judging whether the production environment server is abnormal or not according to the performance index data of the production environment server, an abnormity judgment algorithm corresponding to the service and a corresponding threshold value, judging the reason of the abnormity and giving a repair suggestion; and the abnormal data of the production environment server is sent to the abnormal statistical server through the second sending module when the abnormal data occurs, so that the abnormal statistical server records and stores the abnormal data.
Optionally, the terminal device of the user can be connected to the anomaly statistics server to view the service anomaly record and the repair suggestion of the production environment server.
Optionally, the exception handling server further includes:
the historical version module is used for storing the services of the normal historical version and the abnormal threshold values of the services;
and when the number of times of abnormal crash of the service on the production environment server exceeds a service abnormal threshold value, the abnormal processing server replaces the service of the normal historical version stored by the historical version module with the current abnormal production environment service.
The invention also provides a management method of the service system, which comprises the following steps:
acquiring performance index data of a production environment server;
and judging whether the production environment server is abnormal or not according to the performance index data of the production environment server, and determining the reason of the abnormality and giving a repair suggestion when the abnormality occurs.
Optionally, the determining whether the production environment server is abnormal according to the performance index data of the production environment server includes:
determining an abnormal judgment algorithm and a corresponding threshold value corresponding to the service according to the type of the service;
and judging whether the production environment server is abnormal or not according to the performance index data of the production environment server, an abnormal judgment algorithm corresponding to the service and a corresponding threshold value.
Optionally, the method further includes:
and when the number of times of abnormal crash of the service on the production environment server exceeds a service abnormal threshold value, replacing the currently abnormal production environment service with the stored service of the normal historical version.
Optionally, the method further includes:
and storing the performance index data of the production environment server, corresponding abnormal reasons and repair suggestions when the abnormality occurs.
By adopting the technical scheme, the service system comprises: the system comprises a production environment server, a monitoring system server and an exception handling server; the production environment server is used for supporting a specific production environment service; the monitoring system server is used for acquiring performance index data of the production environment server; and the exception handling server is used for judging whether the production environment server is abnormal or not according to the performance index data of the production environment server, and determining an abnormal reason and giving a repair suggestion when the abnormal occurs. The service system can provide more accurate monitoring service for the production environment, judge whether the production environment server is abnormal according to the performance index of the production environment server, and give a repair suggestion when the production environment server is abnormal or automatically repair the production environment server.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a diagram of the overall architecture provided by one embodiment of a service system of the present invention;
FIG. 2 is a schematic structural diagram of an operation principle provided by an embodiment of a service system of the present invention;
fig. 3 is a flowchart illustrating a management method of a service system according to an embodiment of the present invention.
In the figure: 1. a production environment server; 2. a monitoring system server; 21. a performance index acquisition module; 22. a crash data collection module; 23. a first sending module; 3. an exception handling server; 31. an abnormality judgment module; 32. a second sending module; 33. a history version module; 4. and an anomaly counting server.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be described in detail below. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the examples given herein without any inventive step, are within the scope of the present invention.
Fig. 1 is an overall architecture diagram provided by one embodiment of a service system of the present invention.
As shown in fig. 1, a service system according to this embodiment includes:
a production environment server 1, a monitoring system server 2 and an exception handling server 3;
optionally, the service system may further include: an anomaly statistics server 4;
the production environment server 1 is used for supporting a specific production environment service;
the monitoring system server 2 is used for acquiring performance index data of the production environment server 1;
the exception handling server 3 is configured to determine whether the production environment server 1 is abnormal according to the performance index data of the production environment server 1, and when the abnormality occurs, determine an abnormality cause and give a repair suggestion.
Further, as shown in fig. 2, the monitoring system server 2 includes:
a performance index obtaining module 21, configured to automatically obtain an index corresponding to the production environment server 1; the system is also used for acquiring the specific index of the corresponding production service according to the request sent by the exception handling server 3;
a crash data collection module 22, configured to immediately collect performance indexes within a specific range at a crash time point when a service on the production environment server 1 crashes abnormally;
a first sending module 23, configured to send the performance index data obtained by the performance index obtaining module 21 and the crash data collecting module 22 to the exception handling server 3.
Further, the performance indicator data includes at least one of:
server CPU, memory, network bandwidth, IO and disk space.
Further, the exception handling server 3 includes: an abnormality determination module 31 and a second transmission module 32;
the abnormality judgment module 31 is configured to judge whether the production environment server 1 is abnormal, judge a cause of the abnormality, and give a repair suggestion according to the performance index data of the production environment server 1, an abnormality judgment algorithm corresponding to a service, and a corresponding threshold; and is further configured to, when an anomaly occurs, send the anomaly data of the production environment server 1 to the anomaly statistics server 4 through the second sending module 32, so that the anomaly statistics server 4 records and stores the anomaly data.
Further, the user's terminal device can be connected to the anomaly statistics server 4 to view the service anomaly record and repair suggestion of the production environment server 1.
Further, the exception handling server 3 further includes:
a history version module 33, configured to store services of a normal history version and each service exception threshold;
when the number of times of abnormal crashes of the service on the production environment server 1 exceeds a service abnormal threshold, the abnormal processing server 3 replaces the currently abnormal production environment service with the service of the normal history version stored in the history version module 33.
In practical use, the service system described in this embodiment runs a specific service, such as a database service, on the production environment server 1, and the performance index obtaining module 21 of the monitoring system server 2 obtains an index corresponding to the production environment server 1 in 7 × 24 hours through a script file configured in the module, and obtains a necessary index of a corresponding production service according to a request received from the abnormality processing server 3, and sends the necessary index back to the abnormality determining module 31. The indexes include but are not limited to necessary indexes of each production service such as server CPU, memory, network, IO, disk space and the like. Because indexes measured by different production services are different, dynamic adjustment and acquisition are required according to corresponding scripts. When the service on the production environment server 1 is abnormally crashed, each index in the vicinity of the time point of the crash is immediately collected and sent to the abnormality processing server 3. The abnormality judgment module 31 of the abnormality processing server 3 configures different abnormality judgment algorithms and thresholds corresponding to services according to various index data provided by the performance index acquisition module 21 and different production services, and when an abnormality occurs, not only can the abnormal condition of the server be calculated, but also the abnormal problem point of the production service can be calculated.
It should be noted that services corresponding to different services are different, and each service needs a specific algorithm, which is higher in flexibility. Taking database service as an example, when the abnormality determining module 31 determines that the usage of the indexes such as CPU, memory, network, IO, slow query and the like of the server exceeds the threshold, the abnormality determining module actively requests the performance index obtaining module 21 to obtain the indexes such as CPU, memory, network, slow query and the like occupied by the database service, calculates the abnormality reason and the repair suggestion (where the repair suggestion needs to continuously accumulate the abnormal conditions and solutions in the production environment) according to the algorithm corresponding to the service, and pushes the reason and the repair suggestion to the abnormality statistics server 4 for storage.
The history version module 33 stores services of normal history versions and service abnormality thresholds. And when the message of the abnormal collapse and the corresponding index are received, counting and sending the message to the abnormal counting server 4 for storage. However, when the number of times of abnormal crashes of the service on the production environment server 1 exceeds a service abnormal threshold, the abnormal processing server 3 replaces the service of the normal history version stored in the history version module 33 with the production environment service in which the abnormality occurs currently, so as to ensure that the abnormal service is not performed any more.
The service system can provide more accurate monitoring service for the production environment, judge whether the abnormality occurs according to the performance index of the production environment server 1, and give a repair suggestion when the abnormality occurs or automatically repair, and the service system is high in intelligent degree and beneficial to improving the working efficiency and the user experience.
Fig. 3 is a flowchart illustrating a management method of a service system according to an embodiment of the present invention.
As shown in fig. 3, the management method of a service system according to this embodiment includes:
s31: acquiring performance index data of a production environment server;
s32: and judging whether the production environment server is abnormal or not according to the performance index data of the production environment server, and determining the reason of the abnormality and giving a repair suggestion when the abnormality occurs.
Further, the determining whether the production environment server is abnormal according to the performance index data of the production environment server includes:
determining an abnormal judgment algorithm and a corresponding threshold value corresponding to the service according to the type of the service;
and judging whether the production environment server is abnormal or not according to the performance index data of the production environment server, an abnormal judgment algorithm corresponding to the service and a corresponding threshold value.
Further, the management method further comprises:
and when the number of times of abnormal crash of the service on the production environment server exceeds a service abnormal threshold value, replacing the currently abnormal production environment service with the stored service of the normal historical version.
Further, the management method further comprises:
and storing the performance index data of the production environment server, corresponding abnormal reasons and repair suggestions when the abnormality occurs.
Please refer to the above description for the working principle of the management method of the service system in this embodiment, which is not described herein again.
The management method of the service system can provide more accurate monitoring service for the production environment, judge whether an abnormality occurs according to the performance index of the production environment server, and give a repair suggestion when the abnormality occurs or automatically repair the abnormality.
It is understood that the same or similar parts in the above embodiments may be mutually referred to, and the same or similar parts in other embodiments may be referred to for the content which is not described in detail in some embodiments.
It should be noted that the terms "first," "second," and the like in the description of the present invention are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Further, in the description of the present invention, the meaning of "a plurality" means at least two unless otherwise specified.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and alternate implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.
It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present invention may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.
Claims (10)
1. A service system, comprising:
the system comprises a production environment server, a monitoring system server and an exception handling server;
the production environment server is used for supporting a specific production environment service;
the monitoring system server is used for acquiring performance index data of the production environment server;
and the exception handling server is used for judging whether the production environment server is abnormal or not according to the performance index data of the production environment server, and determining an abnormal reason and giving a repair suggestion when the abnormal occurs.
2. The service system of claim 1, wherein the monitoring system server comprises:
the performance index acquisition module is used for automatically acquiring indexes corresponding to the production environment server; the system is also used for acquiring the specific index of the corresponding production service according to the request sent by the exception handling server;
the crash data collection module is used for immediately collecting the performance indexes within a specific range of a crash time point when the service on the production environment server is abnormally crashed;
and the first sending module is used for sending the index data acquired by the performance index acquisition module and the crash data collection module to the exception handling server.
3. The service system according to claim 1, wherein the performance indicator data comprises at least one of:
server CPU, memory, network bandwidth, IO and disk space.
4. The service system according to claim 1, further comprising:
an anomaly statistics server;
the exception handling server comprises: the abnormity judgment module and the second sending module;
the abnormity judgment module is used for judging whether the production environment server is abnormal or not according to the performance index data of the production environment server, an abnormity judgment algorithm corresponding to the service and a corresponding threshold value, judging the reason of the abnormity and giving a repair suggestion; and the abnormal data of the production environment server is sent to the abnormal statistical server through the second sending module when the abnormal data occurs, so that the abnormal statistical server records and stores the abnormal data.
5. The service system of claim 4, wherein a user's terminal device can connect to the anomaly statistics server to view service anomaly records and repair recommendations of the production environment server.
6. The service system according to any one of claims 1 to 5, wherein the exception handling server further includes:
the historical version module is used for storing the services of the normal historical version and the abnormal threshold values of the services;
and when the number of times of abnormal crash of the service on the production environment server exceeds a service abnormal threshold value, the abnormal processing server replaces the service of the normal historical version stored by the historical version module with the current abnormal production environment service.
7. A method for managing a service system, comprising:
acquiring performance index data of a production environment server;
and judging whether the production environment server is abnormal or not according to the performance index data of the production environment server, and determining the reason of the abnormality and giving a repair suggestion when the abnormality occurs.
8. The method according to claim 7, wherein the determining whether the production environment server is abnormal according to the performance index data of the production environment server comprises:
determining an abnormal judgment algorithm and a corresponding threshold value corresponding to the service according to the type of the service;
and judging whether the production environment server is abnormal or not according to the performance index data of the production environment server, an abnormal judgment algorithm corresponding to the service and a corresponding threshold value.
9. The method of managing of claim 7, further comprising:
and when the number of times of abnormal crash of the service on the production environment server exceeds a service abnormal threshold value, replacing the currently abnormal production environment service with the stored service of the normal historical version.
10. The management method according to any one of claims 7 to 9, further comprising:
and storing the performance index data of the production environment server, corresponding abnormal reasons and repair suggestions when the abnormality occurs.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011246450.0A CN112506734A (en) | 2020-11-10 | 2020-11-10 | Service system and management method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011246450.0A CN112506734A (en) | 2020-11-10 | 2020-11-10 | Service system and management method thereof |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112506734A true CN112506734A (en) | 2021-03-16 |
Family
ID=74957435
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011246450.0A Pending CN112506734A (en) | 2020-11-10 | 2020-11-10 | Service system and management method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112506734A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140040174A1 (en) * | 2012-08-01 | 2014-02-06 | Empire Technology Development Llc | Anomaly detection for cloud monitoring |
| CN109522287A (en) * | 2018-09-18 | 2019-03-26 | 平安科技（深圳）有限公司 | Monitoring method, system, equipment and the medium of distributed document storage cluster |
| CN110324179A (en) * | 2019-06-10 | 2019-10-11 | 平安科技（深圳）有限公司 | A kind of load abnormal alarm method and relevant apparatus |
| CN111522706A (en) * | 2020-03-25 | 2020-08-11 | 平安健康保险股份有限公司 | Method and device for monitoring page abnormity of front-end application |
-
2020
- 2020-11-10 CN CN202011246450.0A patent/CN112506734A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140040174A1 (en) * | 2012-08-01 | 2014-02-06 | Empire Technology Development Llc | Anomaly detection for cloud monitoring |
| CN109522287A (en) * | 2018-09-18 | 2019-03-26 | 平安科技（深圳）有限公司 | Monitoring method, system, equipment and the medium of distributed document storage cluster |
| CN110324179A (en) * | 2019-06-10 | 2019-10-11 | 平安科技（深圳）有限公司 | A kind of load abnormal alarm method and relevant apparatus |
| CN111522706A (en) * | 2020-03-25 | 2020-08-11 | 平安健康保险股份有限公司 | Method and device for monitoring page abnormity of front-end application |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107729210B (en) | Distributed service cluster abnormity diagnosis method and device | |
| US7693876B2 (en) | Monitoring usage rate patterns in storage resources | |
| US7246043B2 (en) | Graphical display and correlation of severity scores of system metrics | |
| WO2020119261A1 (en) | Method, device and electronic apparatus for detecting performance status of optical module in engineering application | |
| CN105897501A (en) | Data monitoring method and device | |
| JP5245934B2 (en) | Management device management program, management device, management device management method, and storage system | |
| WO2017215557A1 (en) | Method and device for collecting performance monitor unit (pmu) events | |
| CN111200526A (en) | Monitoring system and method of network equipment | |
| CN114124655A (en) | Network monitoring method, system, device, computer equipment and storage medium | |
| CN110660198A (en) | Alarm information processing method and device and household appliance | |
| CN113590429A (en) | Server fault diagnosis method and device and electronic equipment | |
| CN114154035A (en) | Data processing system for dynamic loop monitoring | |
| CN111049882A (en) | Cache state processing system, method, device and computer readable storage medium | |
| CN114253806A (en) | Access stratum log collection, analysis and early warning system | |
| CN112506734A (en) | Service system and management method thereof | |
| CN106686082B (en) | Storage resource adjusting method and management node | |
| CN112732517B (en) | Disk fault alarm method, device, equipment and readable storage medium | |
| CN115690681A (en) | Processing method of abnormity judgment basis, abnormity judgment method and device | |
| CN115453401A (en) | Battery safety monitoring system | |
| CN115391129A (en) | Data monitoring method, device, equipment and storage medium | |
| CN109587223B (en) | Data aggregation method, device and system | |
| CN111858589A (en) | Method, device and system for acquiring and transmitting time sequence data | |
| CN118012718B (en) | Real-time monitoring method for distributed storage system | |
| CN112416731A (en) | Stability monitoring method and device applied to block chain system | |
| CN109766243A (en) | A kind of multicore host performance monitor method based on power function |
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: 20210316 |
|
| RJ01 | Rejection of invention patent application after publication |