CN101206610A - System and method for managing computer run case - Google Patents
System and method for managing computer run case Download PDFInfo
- Publication number
- CN101206610A CN101206610A CNA2006101701165A CN200610170116A CN101206610A CN 101206610 A CN101206610 A CN 101206610A CN A2006101701165 A CNA2006101701165 A CN A2006101701165A CN 200610170116 A CN200610170116 A CN 200610170116A CN 101206610 A CN101206610 A CN 101206610A
- Authority
- CN
- China
- Prior art keywords
- level
- event report
- event
- equipment
- report
- 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
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention provides a management system for a computer operating indications and method thereof. The system comprises an indication configuration module, an indication management module and an indication processing module, wherein, the indication configuration module configures and processes a processing program of at least one indication report generated when at least one device is in changed status, and defines the processing grade of each indication report; then, the indication management module receives each indication report, and transmits the program according to the indication processing program and the processing grade; finally, the indication processing module conducts the indication processing program, thereby improving the processing efficiency and the reliability of the computer operating indications.
Description
Technical field
The present invention relates to a kind of management system and method thereof of management system and method thereof, particularly a kind of computer run case of device events.
Background technology
Whether the incident that produces in the computer run process (indication) tends to influence computing machine can continue normal operation, and above-mentioned incident can for example be equipment state change, operation generation etc., computing machine can be collected these event informations and optionally handle, and for example produces warning information and notifies supvr etc. to adopt remedial measures.
At present common event-handling method has two kinds of poll (polling) mode and Interrupt Process modes.Wherein promptly each accepts the equipment of keyholed back plate to polling mode by the event manager module poll, when inquiring certain equipment when having produced pending incident, then event manager module carries out the handling procedure of pending incident, goes back to polling procedure after pending event handling finishes.But the event-handling method of polling mode has following shortcoming: (1) will be aroused every regular hour (polling cycle) event manager module carries out poll, even if produce without any incident, polling procedure is also indispensable, therefore the operation of this poll resident program (daemon) needs the overhead of system resource undoubtedly, can be described as a kind of waste.(2) no matter when equipment produces incident, must wait until that the poll resident program does can be found after the poll, so polling mode is non-real-time to the processing of incident, and polling cycle more major issue just can not get real-time processing more.Just go to handle this incident when (3) the poll resident program is found incident is arranged, after disposing, return main resident program and continue poll, if in the process of processing events, occurred causing program to return unusually, just can make resident program pawn unusually or withdraw from, so reliability is lower.
And compared to the event-handling method of polling mode, though the event-handling method of interrupt mode has improved reliability, and most of incident also can access real-time processing.But when equipment produced more incident simultaneously, the processing of incident often needed to wait in line, and in other words, more important incident (for example, equipment is damaged) can not be handled in real time.
Summary of the invention
In view of above problem, fundamental purpose of the present invention is to provide a kind of management system and method thereof of computer run case, utilization is carried out differentiated control to the event report that equipment produces, and, promote the treatment effeciency and the reliability of computer run case thus according to rank sequential processes computer run case.
The management system of computer run case disclosed according to the present invention includes event configuration module, event manager module and more than one event processing module.
At first, by event configuration block configuration one button.onrelease, and button.onrelease is used to handle at least one event report that at least one equipment produces when Status Change, and defines the processing rank of each event report.Then, utilize event manager module to receive each event report that each equipment produces when Status Change, and carry out a retransmission process with the processing rank according to the button.onrelease of event configuration block configuration.At last, receive the button.onrelease that event manager module is transmitted, go forward side by side and act the part handling procedure by event processing module.
The management method of computer run case disclosed according to the present invention, include the following step: at first, at least one event report that at least one equipment of configuration process produces when Status Change, and define the processing rank of each event report, then, receive each event report that each equipment produces when Status Change, and carry out a retransmission process according to button.onrelease and processing rank, at last, carry out button.onrelease.
Management system and method thereof by this computer run case can reach following beneficial effect at least:
(1) event report that utilizes equipment initiatively to produce when Status Change with the system resource overhead of saving query event, and by a plurality of each incidents of event processing module parallel processing, promotes treatment effeciency thus.
(2) severity level according to the generation incident carries out the processing of different order to incident, to promote the processing real-time of critical event.
(3) utilize monitoring unit to carry out record for each incident, and incident is untreated when finishing in the given time, continues the information of giving notice and give the supvr, continuation is followed the trail of and maintenance so that the supvr carries out the computing machine situation.
Below in conjunction with specific embodiment and shown in accompanying drawing, the present invention is described in further detail.
Description of drawings
Fig. 1 is the system block diagram of the embodiment of the invention;
Fig. 2 is the process flow diagram of the embodiment of the invention.
Wherein, description of reference numerals is as follows:
10 event configuration modules
20 event manager modules
21 monitoring units
30 event processing modules
40 equipment
The button.onrelease of at least one event report that at least one equipment of step 100 configuration process produces when Status Change
The processing rank of each event report of step 101 definition
Step 102 receives each event report that each equipment produces when Status Change
Is step 103 the first rank incident?
Each event report of step 104 record
Does step 105 have from the other incident of second or the third level of same equipment?
Step 106 is removed from the other event report record of second or the third level of same equipment
Step 107 is carried out a retransmission process according to button.onrelease and processing rank
Step 108 is carried out button.onrelease
Is the other event report record of step 109 schedule time interior second or the third level removed?
Embodiment
With reference to Fig. 1, it is the block scheme of the system of the embodiment of the invention.As shown in Figure 1, the management system of the computer run case of the embodiment of the invention includes event configuration module 10, event manager module 20 and more than one event processing module 30, below describes with regard to each module, unit.
First rank: it can for example be actions such as data creation or data deletion corresponding to the Action Events report of each equipment 40.In general, the first rank incident has two kinds of sources: the one, initiate by the supvr, be produce by artificial processing operation and through authentication with confirm that normal operation does not have negative effect to computing machine; The 2nd, equipment state is normal by other state-transition.
Second level: it is corresponding to the report of alarm events of each equipment 40, for example disk health status, disk array lower one's standard or status (Raid Degrade) etc.When the second level incident took place, equipment 40 can also use, but had the possibility that further worsens.When the second level incident produced, if just have in the processed first rank incident from same equipment 40, the processing procedure of the first rank incident will be interrupted so, and in other words, the processing sequence of second level incident has precedence over the first rank incident.
The third level is other: it is corresponding to the damage event report of each equipment 40.This type of incident is big to the influence of computer run, need handle immediately.When the other incident of the third level produced, if just have processed from the first rank incident in the same equipment 40, the processing procedure of second level incident will be interrupted so.Wherein the processing sequence of the other incident of the third level has precedence over the second level incident.
More than one event processing module 30 (for example, first event processing module, second event processing module ... the n event processing module), be used to receive the button.onrelease that event manager module 20 is transmitted, go forward side by side and act the part handling procedure, and the content of button.onrelease includes by user-defined channel (as SNMP, Email etc.) and notifies the user; Can incident by oneself then calling predefined the corresponding interface for computing machine handles.If the incident that some computing machines can't be handled automatically just must wait the user to get involved and take corresponding measure.
With reference to Fig. 2, it is the process flow diagram of the embodiment of the invention.As shown in Figure 2, the management method of the computer run case of the embodiment of the invention includes the following step:
At first, the supvr utilizes the button.onrelease (step 100) of at least one event report that at least one equipment of event configuration module 10 configuration process produces when Status Change, and defines the processing rank (step 101) of each event report.Wherein handle rank and can divide into first rank: be Action Events report corresponding to each equipment; Second level: be Warning Event report corresponding to each equipment; The third level is other: be the damage event report corresponding to each equipment.
Then, event manager module 20 receives each event report (step 102) that each equipment produces when Status Change, does event manager module 20 judge that each event report is the first rank incident? (step 103), judging each event reports when event manager module 20 is second or during other incidents of the third level, the other incident of second or the third level (step 104) that 21 each equipment of record of monitoring unit produce; When event manager module 20 judges that each event report is the first rank incident, then continue to judge have in the monitoring unit 21 from the other incident of second or the third level of same equipment? (step 105), if when second or other incidents of the third level from same equipment arranged in the monitoring unit 21, then remove in the monitoring unit 21 from the other event report record of second or the third level of same equipment (step 106).
Then, event manager module 20 carries out a retransmission process (step 107) according to button.onrelease and processing rank.Wherein retransmission process is according to handling other order of level disposal route in addition to be forwarded to corresponding event processing module 30 after the encapsulation process.
After after the other incident of second or the third level that each equipment of the record of step 104 produces, in the monitoring unit 21 of step 105, not having and in the removing monitoring unit 21 of step 106 from the other incident of second or the third level of same equipment from second or the third level of same equipment behind the other event report record, event processing module 30 carries out button.onrelease (step 108), in the given time second or the other event report of third level record remove yet? (step 109), then get back to step 107, carry out this retransmission process once more.In the given time second or the other event report of third level record when having removed, then get back to step 102 and continue to receive each event report that each equipment produces when Status Change.
Below lifting an example application explains:
At first, computing machine to equipment D1 pre-defined following three incidents: the first rank incident EL1, second level incident EM1 and the other incident EI1 of the third level.
When very first time t1, produced second level incident EM1 on the equipment D1, so equipment D1 informs event manager module 20 with this incident, and event manager module 20 finds that after receiving it is second level incident EM1, so this incident of record in monitoring unit 21, and second level incident EM1 is transmitted to event processing module 30 according to configuration, finish processing by event processing module 30 to this incident.
The second time t2 after very first time t1, the processing of 30 pairs of second level incidents of event processing module EM1 is not finished as yet, and produced the other incident EI1 of the third level on the equipment D1, so equipment D1 informs event manager module 20 with this incident, and event manager module 20 finds that it is the other incident EI1 of the third level after receiving, so it is recorded in the monitoring unit 21, and according to the configuration the other incident EI1 of the third level is transmitted to event processing module 30, because the processing rank of second level incident EM1 is lower and handle and do not finish as yet than the other incident EI1 of the third level, so processing procedure is interrupted, preferentially the other incident EI1 of the third level is handled by event processing module 30, just continue to handle second level incident EM1 after grade in an imperial examination three rank incident EI1 handle.
Then, the 3rd time t3 after the second time t2, monitoring unit 21 finds that the time that the other incident EI1 of the incident third level is recorded has surpassed schedule time Δ t (for example the other incident EI1 of the third level handles failure automatically or the other incident EI1 of the third level needs the supvr to get involved), so to these situations of event manager module 20 report, and event manager module 20 is transmitted to event processing module 30 with the other incident EI1 of the third level once more after receiving and handles.
The 4th time t4 after the 3rd time t3, produced the first rank incident EL1 on the equipment D1, so equipment D1 informs event manager module 20 with this incident, and event manager module 20 finds that it is the first rank incident EL1 after receiving, so query monitor unit 21, discovery has from the second level incident EM1 of same equipment (D1) and the other incident EI1 of the third level, so second level incident EM1 and the other incident EI1 of the third level are removed from monitoring unit 21, simultaneous events administration module 20 is transmitted to event processing module 30 according to configuration with the first rank incident EL1, finishes processing to the first rank incident EL1 by event processing module 30.At last, the logout tabulation from equipment D1 in the monitoring unit 21 is sky, and the equipment D1 of representative has returned to normal condition.
Comprehensive the above, the management system of computer run case of the present invention and method thereof, be to utilize equipment when Status Change, initiatively to produce event report, to save the system resource overhead of query event, and incident is carried out the processing of different order according to the severity level of generation incident, to promote the processing real-time of critical event.In addition, utilize monitoring unit to carry out record for each incident, and incident is untreated when finishing in the given time, continues the information of giving notice and give the supvr, continuation is followed the trail of and maintenance so that the supvr carries out the computing machine situation.
Claims (12)
1. the management system of a computer run case is characterized in that, includes:
One event configuration module is used to dispose a button.onrelease, and this button.onrelease is used to handle at least one event report that at least one equipment produces when Status Change, and defines the processing rank of described event report;
One event manager module is used to receive the described event report that described equipment produces when Status Change, and carries out a retransmission process according to this button.onrelease and this processing rank of this event configuration block configuration; And
More than one event processing module is used to receive this button.onrelease that this event manager module is transmitted, and carries out this button.onrelease.
2. the management system of computer run case as claimed in claim 1 is characterized in that, this processing level region is divided into:
One first rank, it is corresponding to the Action Events report of described equipment;
One second level, it is corresponding to the Warning Event report of described equipment; And
One third level is other, and it is corresponding to the damage event report of described equipment.
3. the management system of computer run case as claimed in claim 2 is characterized in that, this event manager module also includes a monitoring unit, is used for record or removes described event report.
4. the management system of computer run case as claimed in claim 3 is characterized in that, when this event manager module received this second level or other described event report of this third level, this monitoring unit write down described event report.
5. the management system of computer run case as claimed in claim 3, it is characterized in that, when this event manager module received other described event report of this first order of same equipment, this monitoring unit was removed this second level or other described event report of this third level of same equipment.
6. the management system of computer run case as claimed in claim 3, it is characterized in that, in a schedule time, when other described event report of this second level in this monitoring unit or this third level was not removed, then this event manager module carried out this retransmission process once more.
7. the management method of a computer run case is characterized in that, includes the following step:
At least one event report that at least one equipment of configuration process produces when Status Change;
Define the processing rank of described event report;
Receive the described event report that described equipment produces when Status Change;
Carry out a retransmission process according to this button.onrelease and this processing rank; And
Carry out this button.onrelease.
8. the management method of computer run case as claimed in claim 7 is characterized in that, this processing rank system divides into:
One first rank, it is corresponding to the Action Events report of described equipment;
One second level, it is corresponding to the Warning Event report of described equipment; And
One third level is other, and it is corresponding to the damage event report of described equipment.
9. the management method of computer run case as claimed in claim 8 is characterized in that, after the step of the described event report that produces when receiving described equipment in Status Change, also includes the step that writes down or remove described event report.
10. the management method of computer run case as claimed in claim 9 is characterized in that, when receiving this second level or other described event report of this third level, then writes down described event report.
11. the management method of computer run case as claimed in claim 9 is characterized in that, when receiving other described event report of this first order of same equipment, then removes this second level or other described event report of this third level of same equipment.
12. the management method of computer run case as claimed in claim 9 is characterized in that, in a schedule time, when other described event report of this second level or this third level is not removed, then carries out this retransmission process once more.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006101701165A CN101206610A (en) | 2006-12-22 | 2006-12-22 | System and method for managing computer run case |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006101701165A CN101206610A (en) | 2006-12-22 | 2006-12-22 | System and method for managing computer run case |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101206610A true CN101206610A (en) | 2008-06-25 |
Family
ID=39566837
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2006101701165A Pending CN101206610A (en) | 2006-12-22 | 2006-12-22 | System and method for managing computer run case |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101206610A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103530173A (en) * | 2012-07-06 | 2014-01-22 | 上海宝信软件股份有限公司 | Dynamic weighted event processing system and method |
| CN108199980A (en) * | 2017-12-29 | 2018-06-22 | 天津芯海创科技有限公司 | The action listener method and monitoring system of exchange chip |
| CN108234476A (en) * | 2017-12-29 | 2018-06-29 | 天津芯海创科技有限公司 | The action listener method and monitoring system of exchange chip |
-
2006
- 2006-12-22 CN CNA2006101701165A patent/CN101206610A/en active Pending
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103530173A (en) * | 2012-07-06 | 2014-01-22 | 上海宝信软件股份有限公司 | Dynamic weighted event processing system and method |
| CN103530173B (en) * | 2012-07-06 | 2018-07-17 | 上海宝信软件股份有限公司 | Changeable weight event handling system and method |
| CN108199980A (en) * | 2017-12-29 | 2018-06-22 | 天津芯海创科技有限公司 | The action listener method and monitoring system of exchange chip |
| CN108234476A (en) * | 2017-12-29 | 2018-06-29 | 天津芯海创科技有限公司 | The action listener method and monitoring system of exchange chip |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110581773A (en) | automatic service monitoring and alarm management system | |
| CN101222361B (en) | Alarm frequency monitor and alarm processing method | |
| CN111339175B (en) | Data processing method, device, electronic equipment and readable storage medium | |
| CN106487574A (en) | Automatic operating safeguards monitoring system | |
| CN101997925A (en) | Server monitoring method with early warning function and system thereof | |
| US8341637B2 (en) | Utilization management | |
| CN110659307A (en) | Event stream correlation analysis method and system | |
| CN111143167B (en) | Alarm merging method, device, equipment and storage medium for multiple platforms | |
| CN104407959A (en) | Application based monitoring method and monitoring device | |
| CN104408654A (en) | Financial monitoring management system | |
| CN103763127A (en) | Device state alarm monitoring method and system | |
| CN108304293A (en) | A kind of software systems monitoring method based on big data technology | |
| CN103823743B (en) | The monitoring method of software system and equipment | |
| CN101206610A (en) | System and method for managing computer run case | |
| CN112256548B (en) | Abnormal data monitoring method and device, server and storage medium | |
| CN113672452A (en) | Method and system for monitoring operation of data acquisition task | |
| CN101677278A (en) | Method and system for monitoring availability of network information system | |
| CN103995759A (en) | High-availability computer system failure handling method and device based on core internal-external synergy | |
| CN114090382B (en) | Health inspection method and device for super-converged cluster | |
| CN115766768A (en) | Method and device for designing sensing center in computational power network operating system | |
| CN110851316A (en) | Abnormity early warning method, abnormity early warning device, abnormity early warning system, electronic equipment and storage medium | |
| CN113868094A (en) | Big data abnormal information monitoring system | |
| CN109766238B (en) | Session number-based operation and maintenance platform performance monitoring method and device and related equipment | |
| CN115222181A (en) | Robot operation state monitoring system and method | |
| CN101741654B (en) | Monitoring device and method of operating system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |