CN108199927A - Server monitoring diagnosis method - Google Patents
Server monitoring diagnosis method Download PDFInfo
- Publication number
- CN108199927A CN108199927A CN201810100494.9A CN201810100494A CN108199927A CN 108199927 A CN108199927 A CN 108199927A CN 201810100494 A CN201810100494 A CN 201810100494A CN 108199927 A CN108199927 A CN 108199927A
- Authority
- CN
- China
- Prior art keywords
- diagnosis
- monitoring
- destination server
- server
- clouds
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/06—Generation of reports
-
- 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/0654—Management of faults, events, alarms or notifications using network fault recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0677—Localisation of faults
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Debugging And Monitoring (AREA)
- Computer And Data Communications (AREA)
Abstract
An embodiment of the present invention provides a kind of server monitoring diagnosis methods, are realized based on cloud computing, specifically include following steps：Monitoring unit monitoring objective server, and judge whether destination server breaks down；If there is failure, then generate monitoring report and be sent to high in the clouds；High in the clouds analyzing and processing production diagnosis scheme；Diagnosis unit diagnoses destination server according to diagnosis scheme, and generation diagnosis report is sent to high in the clouds again；High in the clouds carries out analyzing and processing production recovery scenario；It repairs unit to repair destination server according to recovery scenario, repairs and send monitoring signal again to monitoring unit after completing.
Description
Technical field
The present invention relates to server diagnostic techniques field, specifically a kind of server monitoring diagnosis method.
Background technology
Server monitoring just refers to record remote server operation data by various modes, and when needed may be used
Monitoring record to be called to be checked at any time.
Server diagnosis just refers to that occurring various problems in server operational process causes server can not work normally, can
To navigate to the process for the reason of server can not work normally using software or manual method.
After server reparation just refers to that server can not work normally, can utilize software or it is artificial the methods of repair ask
Topic, makes server can be with normal operation.
Current server monitoring, diagnosis, repair mostly by software or it is artificial complete, and server is according to update
It constantly regenerates, can not accomplish overall monitor when software is monitored, it may appear that unmatched situation；Artificial Diagnosis can waste
Time, inefficiency.
Invention content
A kind of server monitoring diagnosis method is provided in the embodiment of the present invention, for solving existing server diagnosis
Middle diagnosis can not overall monitor and the problem of inefficiency.
In order to solve the above-mentioned technical problem, the embodiment of the invention discloses following technical solutions：
The present invention provides a kind of server monitoring diagnosis methods, are realized based on cloud computing, specifically include following step
Suddenly：
Monitoring unit monitoring objective server, and judge whether destination server breaks down；If there is failure, then give birth to
High in the clouds is sent into monitoring report；
High in the clouds analyzing and processing production diagnosis scheme；
Diagnosis unit diagnoses destination server according to diagnosis scheme, and generation diagnosis report is sent to high in the clouds again；
High in the clouds carries out analyzing and processing production recovery scenario；
It repairs unit to repair destination server according to recovery scenario, repairs and sent again to monitoring unit after completing
Monitoring signal.
In the first possible implementation, the method for monitoring unit monitoring objective server specifically includes：
Monitor main program timer access destination server；
The timing request of destination server response monitoring main program, and the operating status of monitoring objective server；
The data of its operating status are returned to monitoring main program by destination server.
In second of possible realization method, judge that the method that destination server breaks down is：Each prison monitored
The value of control item is compared with set threshold value, if do not met, then it represents that monitoring item breaks down.
In the third possible realization method, the content of monitoring report includes the IP or number of destination server, monitoring
Indices, value or the threshold value of item.
In the 4th kind of possible realization method, the diagnosis scheme includes the program of calling system, monitoring programme, examines
The implementing result of disconnected scheme；The implementing result includes the set for being likely to occur the result of a variety of situations diagnosis of failure.
In the 5th kind of possible realization method, side that diagnosis unit diagnoses destination server according to diagnosis scheme
Method specifically includes：
Diagnosis report matches：Program and implementing result in diagnosis report go to high in the clouds to match, and judge whether there is class
As implementing result, failure cause is determined according to the diagnosis report being installed to；
Keywords matching：The keyword in procedure match implementing result in diagnosis report, according to matched key
Word determines failure cause；
Synthesis result calculates：The reason of determining a failure may may require that a plurality of script and implementing result to determine, because
This, high in the clouds needs to determine failure cause according to a plurality of script and implementing result.
In the 6th kind of possible realization method, side that diagnosis unit diagnoses destination server according to diagnosis scheme
Method further includes：
Recurrence tune diagnoses：If high in the clouds does not analyze exact failure cause, diagnosis scheme can be called to generate again
Finer diagnostic script is diagnosed, and is carried out the analysis of result again, is determined failure cause.
In the 7th kind of possible realization method, recurrence number is recorded in diagnostic result, is set when diagnosis number is more than
Alarm is sent out during definite value, by artificial treatment, prevents infinite recursion from calling.
In the 8th kind of possible realization method, the side that unit repairs destination server according to recovery scenario is repaired
Method includes：
Restart destination server；
It is modified according to failure cause to configuration file；
Outside automation physical equipment is called.
In the 9th kind of possible realization method, repairing the mark of completion is：
Recovery scenario, which is finished, can return to the label that program performs completion, call the interface of monitoring unit that label is set as
Fault target server normally restarts the label of monitoring.
By above technical scheme as it can be seen that the ability of cloud service of the present invention is dynamic growth, update on monitoring server
Program is with regard to that can increase the ability of monitoring programme process problem.
Realize monitoring, diagnosis, the intelligent automation for repairing whole process, whole process, which is automatically performed, does not need to staff
Operation.
Description of the drawings
In order to illustrate more clearly about the embodiment of the present invention or technical scheme of the prior art, to embodiment or will show below
There is attached drawing needed in technology description to be briefly described, it should be apparent that, for those of ordinary skill in the art
Speech, without creative efforts, can also be obtained according to these attached drawings other attached drawings.
Fig. 1 is a kind of server monitoring diagnosis method flow schematic diagram of the present invention.
Specific embodiment
In order to which those skilled in the art is made to more fully understand the technical solution in the present invention, below in conjunction with of the invention real
The attached drawing in example is applied, the technical solution in the embodiment of the present invention is clearly and completely described, it is clear that described implementation
Example is only part of the embodiment of the present invention, instead of all the embodiments.Based on the embodiments of the present invention, this field is common
Technical staff's all other embodiments obtained without making creative work, should all belong to protection of the present invention
Range.
As shown in Figure 1, server monitoring diagnosis method, is realized based on cloud computing, specifically includes following steps：
S1, monitoring unit monitoring objective server；
S2, judge whether destination server breaks down；If there is failure, then S3 is performed；Otherwise, continue to monitor.
S3, generation monitoring report are sent to high in the clouds；
S4, high in the clouds analyzing and processing production diagnosis scheme are simultaneously sent to diagnosis unit；
S5, diagnosis unit diagnose destination server according to diagnosis scheme, and generation diagnosis report is sent to cloud again
End；
S6, high in the clouds carry out analyzing and processing production recovery scenario and are sent to reparation unit；
S7, reparation unit repair destination server according to recovery scenario, repair and are sent after completing to monitoring unit
Again monitoring signal.
The method of monitoring unit monitoring objective server specifically includes in S1：
Monitor main program timer access destination server；
The timing request of destination server response monitoring main program, and the operating status of monitoring objective server；
The data of its operating status are returned to monitoring main program by destination server.
The method that destination server breaks down is judged in S2 is：The value of each monitored item monitored and set threshold value
It is compared, if do not met, then it represents that monitoring item breaks down.
The content of monitoring report in S3 includes the IP or number of destination server, monitors indices, value or the threshold of item
Value.
Diagnosis scheme in S4 includes program, monitoring programme, the implementing result of diagnosis scheme of calling system；Described holds
Row result includes the set for being likely to occur the result of a variety of situations diagnosis of failure.
Diagnosis unit specifically includes following 3 kinds according to the method that diagnosis scheme diagnoses destination server in S5：
1) diagnosis report matches：Program and implementing result in diagnosis report go to high in the clouds to match, and judge whether there is
Similar implementing result determines failure cause according to the diagnosis report being installed to；
2) Keywords matching：The keyword in procedure match implementing result in diagnosis report, according to matched pass
Keyword determines failure cause；
3) synthesis result calculates：The reason of determining a failure may may require that a plurality of script and implementing result to determine,
Therefore, high in the clouds needs to determine failure cause according to a plurality of script and implementing result.
If above 3 kinds of modes analyze exact failure cause not yet, diagnosed using recurrence tune：It calls and examines again
The disconnected finer diagnostic script of schemes generation is diagnosed, and is carried out the analysis of result again, is determined failure cause.
Recurrence number is recorded in diagnostic result, sends out alarm when diagnosing number and be more than setting value, by artificial treatment,
Prevent infinite recursion from calling.
Unit is repaired in S7 according to the method that recovery scenario repairs destination server to be included：
Restart destination server；
It is modified according to failure cause to configuration file；
Outside automation physical equipment is called.
Repairing the mark completed is：
Recovery scenario, which is finished, can return to the label that program performs completion, call the interface of monitoring unit that label is set as
Fault target server normally restarts the label of monitoring.
The above is only the specific embodiment of the present invention, is made skilled artisans appreciate that or realizing this hair
It is bright.A variety of modifications of these embodiments will be apparent to one skilled in the art, it is as defined herein
General Principle can be realized in other embodiments without departing from the spirit or scope of the present invention.Therefore, it is of the invention
The embodiments shown herein is not intended to be limited to, and is to fit to and the principles and novel features disclosed herein phase one
The most wide range caused.
Claims (10)
1. server monitoring diagnosis method, it is characterized in that, it is realized based on cloud computing, specifically includes following steps：
Monitoring unit monitoring objective server, and judge whether destination server breaks down；If there is failure, then prison is generated
It observes and predicts to accuse and gives high in the clouds；
High in the clouds analyzing and processing production diagnosis scheme；
Diagnosis unit diagnoses destination server according to diagnosis scheme, and generation diagnosis report is sent to high in the clouds again；
High in the clouds carries out analyzing and processing production recovery scenario；
It repairs unit to repair destination server according to recovery scenario, repairs and monitored again to monitoring unit transmission after completing
Signal.
2. according to the method described in claim 1, it is characterized in that, the method for monitoring unit monitoring objective server specifically includes：
Monitor main program timer access destination server；
The timing request of destination server response monitoring main program, and the operating status of monitoring objective server；
The data of its operating status are returned to monitoring main program by destination server.
3. according to the method described in claim 1, it is characterized in that, judge destination server break down method be：It monitors
The value of each monitored item be compared with set threshold value, if do not met, then it represents that monitoring item breaks down.
4. according to the method described in claim 1, it is characterized in that, the content of monitoring report includes the IP or volume of destination server
Number, monitor indices, value or the threshold value of item.
5. according to the method described in claim 1, it is characterized in that, the program of the diagnosis scheme including calling system, monitoring
Program, the implementing result of diagnosis scheme；The implementing result includes the result for being likely to occur a variety of situations diagnosis of failure
Set.
6. according to the method described in claim 1, it is characterized in that, diagnosis unit examines destination server according to diagnosis scheme
Disconnected method specifically includes：
Diagnosis report matches：Program and implementing result in diagnosis report go to high in the clouds to match, and judge whether to whether there is similar
Implementing result determines failure cause according to the diagnosis report being installed to；
Keywords matching：The keyword in procedure match implementing result in diagnosis report, according to matched keyword come
Determine failure cause；
Synthesis result calculates：The reason of determining a failure may may require that a plurality of script and implementing result to determine, therefore, cloud
End needs to determine failure cause according to a plurality of script and implementing result.
7. according to the method described in claim 6, it is characterized in that, diagnosis unit examines destination server according to diagnosis scheme
Disconnected method further includes：
Recurrence tune diagnoses：If high in the clouds does not analyze exact failure cause, diagnosis scheme generation can be called thinner again
The diagnostic script of cause is diagnosed, and is carried out the analysis of result again, is determined failure cause.
8. according to the method described in claim 7, it is characterized in that, recurrence number is recorded in diagnostic result, when diagnosis number
Alarm is sent out during more than setting value, by artificial treatment, prevents infinite recursion from calling.
9. according to the method described in claim 1, it is characterized in that, repair unit destination server is repaiied according to recovery scenario
Multiple method includes：
Restart destination server；
It is modified according to failure cause to configuration file；
Outside automation physical equipment is called.
10. according to the method described in claim 1, it is characterized in that, repairing the mark of completion is：
Recovery scenario, which is finished, can return to the label that program performs completion, call the interface of monitoring unit that label is set as failure
Destination server normally restarts the label of monitoring.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810100494.9A CN108199927A (en) | 2018-02-01 | 2018-02-01 | Server monitoring diagnosis method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810100494.9A CN108199927A (en) | 2018-02-01 | 2018-02-01 | Server monitoring diagnosis method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108199927A true CN108199927A (en) | 2018-06-22 |
Family
ID=62592318
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810100494.9A Pending CN108199927A (en) | 2018-02-01 | 2018-02-01 | Server monitoring diagnosis method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108199927A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120041637A1 (en) * | 2010-08-10 | 2012-02-16 | Detroit Diesel Corporation | Engine diagnostic system and method for capturing diagnostic data in real-time |
| CN105302120A (en) * | 2015-11-19 | 2016-02-03 | 广州云湾信息技术有限公司 | Remote service device, system and method of intelligent equipment |
| CN105323095A (en) * | 2014-07-30 | 2016-02-10 | 中国电信股份有限公司 | Network fault detection method, system and access equipment |
-
2018
- 2018-02-01 CN CN201810100494.9A patent/CN108199927A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120041637A1 (en) * | 2010-08-10 | 2012-02-16 | Detroit Diesel Corporation | Engine diagnostic system and method for capturing diagnostic data in real-time |
| CN105323095A (en) * | 2014-07-30 | 2016-02-10 | 中国电信股份有限公司 | Network fault detection method, system and access equipment |
| CN105302120A (en) * | 2015-11-19 | 2016-02-03 | 广州云湾信息技术有限公司 | Remote service device, system and method of intelligent equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6353902B1 (en) | Network fault prediction and proactive maintenance system | |
| US7680753B2 (en) | System and method for fault identification in an electronic system based on context-based alarm analysis | |
| CN101753382B (en) | Method for establishing adaptive network failure monitoring and positioning security model | |
| JP2004118839A (en) | Method for supporting specification of function unit failed in technical equipment | |
| CN110825768B (en) | Remote television exception handling method and system based on cloud analysis | |
| US20110314331A1 (en) | Automated test and repair method and apparatus applicable to complex, distributed systems | |
| CN109885951A (en) | Equipment fault diagnosis method and device | |
| CN109992440A (en) | A kind of IT root accident analysis recognition methods of knowledge based map and machine learning | |
| CN101783749B (en) | Network fault positioning method and device | |
| CN111913133A (en) | Distributed fault diagnosis and maintenance method, device, equipment and computer readable medium | |
| WO2007147327A1 (en) | Method, system and apparatus of fault location for communicaion apparatus | |
| JPS6014303A (en) | Knowledge-based diagnosis system | |
| CN116820820A (en) | Server fault monitoring method and system | |
| CN117474357A (en) | Power distribution room operation and maintenance management method and system based on deep learning | |
| CN108199927A (en) | Server monitoring diagnosis method | |
| JPH09205429A (en) | Network fault diagnostic device, fault prediction device, and its diagnostic and prediction method | |
| CN110007171A (en) | The screening method and system of transformer online monitoring data false alarm | |
| CN112866839B (en) | Power failure warning device and method for ten-thousand-million passive optical network terminal equipment | |
| KR100506248B1 (en) | How to Diagnose Links in a Private Switching System | |
| CN115544202A (en) | Alarm processing method, device and storage medium | |
| CN104503423A (en) | PROFINET-based industrial Ethernet control system fault diagnosis method | |
| WO2023051097A1 (en) | Network failure diagnosis method and apparatus, storage medium, and electronic apparatus | |
| CN117495357B (en) | Electric power data supervision system and method based on big data | |
| JPH06244935A (en) | Fault diagnostic system for configuration equipment of electronic exchange | |
| KR950005986B1 (en) | Processor-error detecting method |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20180622 |