CN101546396A - Method and system for performing non-intrusive monitoring on end-to-end service processes - Google Patents
Method and system for performing non-intrusive monitoring on end-to-end service processes Download PDFInfo
- Publication number
- CN101546396A CN101546396A CN200810087924A CN200810087924A CN101546396A CN 101546396 A CN101546396 A CN 101546396A CN 200810087924 A CN200810087924 A CN 200810087924A CN 200810087924 A CN200810087924 A CN 200810087924A CN 101546396 A CN101546396 A CN 101546396A
- Authority
- CN
- China
- Prior art keywords
- event
- incident
- business
- rule
- operation flow
- 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
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a method and a system for performing non-intrusive monitoring on end-to-end service processes, wherein an event editor is used for defining event metadata related to to-be-monitored service processes and generating event-promoting rules; a data event sensor is used for generating database events on the basis of service data changes; and a monitoring server is used for monitoring the end-to-end service processes on the basis of the database events, the event metadata and the event-promoting rules.
Description
Technical field
The present invention relates to the field of monitoring business flowpath in the computer utility infosystem, relate in particular to the method and system that is used for end-to-end operation flow is carried out the non-intrusion type monitoring.
Background technology
In recent years, enterprise is more and more for the demand of the monitoring of the operation flow in the computer utility infosystem, so that realize professional visual.Some method and systems that are used for monitoring business flowpath also occur thereupon.Traditional operation flow policer operation all needs business process management system (BPMS) usually, and the processing engine that is positioned among this business process management system is driving automatically performing of operation flow.Operation flow now has and much is implemented as the teleservice flow process, but a teleservice flow process has comprised many execution units, such as BPEL, and EJB, POJO, JSP or the like, even also may more integrated application or system.In this case, operation flow is not only driven by processing engine, is also driven by other application.Just do not monitor processing engine so monitor end-to-end operation flow.
The method for supervising that has some data handling systems in the prior art.For example title discloses a kind of method for supervising and device in the U.S. Pat 7003781 of " Method and apparatus for correlation of events in a distributedmulti-system computing environment ", wherein concrete disclosed be monitoring at distributed data processing system, rather than at the monitoring of operation flow, its method is not suitable for the end-to-end operation flow of monitoring yet.Title is the U.S. Patent application US 20020116362 of " Real time business process analysis method andapparatus " for another example, and it is disclosed to be that a kind of mechanism of Event Service of utilizing is improved the efficiency of being brought when the traditional database inquiry mode is used in the flow process inquiry.It does not carry out tracing and monitoring at the state of orchestration instance yet, neither carry out the monitoring that event definition is proceeded operation flow according to the state about orchestration instance.And we in the operation of the end-to-end operation flow of this said monitoring based on " case mechanism ", so-called case mechanism is achieved in that follows the tracks of logout determining the executing state of orchestration instance, thereby realizes monitoring.The WebSphere traffic monitor is a kind of monitoring product of known end-to-end flow processing device.The WebSphere traffic monitor needs the developer to incite somebody to action clearly, and service call is inserted in the flow implementation source code, perhaps can provide software package to be convenient to implement predefined standard Event, but need on original procedural model, be configured equally to determine to send wherein incident and event type that will send and event content.Therefore, need provide a kind of and can under the situation that does not change existing business flow logic and enforcement, can obtain monitored operation flow state and define the incident that is associated, thus the method and system of the non-intrusion type monitoring of realization teleservice flow process.
Summary of the invention
The purpose of this invention is to provide a kind of method and system that is used for end-to-end operation flow is carried out the non-intrusion type monitoring.
Provide a kind of being used for that end-to-end operation flow is carried out the system that non-intrusion type is monitored according to an aspect of the present invention, having comprised: event editor, relevant event metadata and the generation incident of operation flow that is used to define and want monitored advances rule; The data event sensor is used for changing based on business datum producing Database Events; And monitoring server, be used for advancing rule to monitor end-to-end operation flow based on Database Events and event metadata and incident.
Provide a kind of being used for that end-to-end operation flow is carried out the method that non-intrusion type is monitored according to a further aspect in the invention, comprised the steps: to define and wanted the monitored relevant event metadata of operation flow; The incident that the operation flow that generates and will be monitored is relevant advances rule; Change based on business datum and to produce Database Events; And advance rule to monitor end-to-end operation flow based on Database Events and event metadata and incident.
Preferably, monitoring server according to the present invention also comprises: supervisor engine is used for advancing rule to generate business event based on described Database Events and described event metadata and described incident; The business event watch-dog is used for coming monitoring business flowpath based on described business event.
Preferably, at the system and method that is used for end-to-end operation flow is carried out the non-intrusion type monitoring according to the present invention, described incident advances rule to generate automatically or manually generates by the user.
Preferably, at the system and method that is used for end-to-end operation flow is carried out the non-intrusion type monitoring according to the present invention, described event metadata and described incident advance rule to be associated with described business datum.
Description of drawings
By below in conjunction with the description of the drawings, and along with understanding more comprehensively to of the present invention, other purpose of the present invention and effect will become clear more and easy to understand, wherein:
Fig. 1 is the non-intrusion type supervisory system that is used for the teleservice flow process that illustrates according to the embodiment of the invention;
Fig. 2 is the process flow diagram that is used for end-to-end operation flow is carried out the non-intrusion type monitoring that illustrates according to the embodiment of the invention;
Fig. 3 is the non-intrusion type supervisory system that is used for the teleservice flow process that further is shown specifically according to the embodiment of the invention;
Fig. 4 is the process flow diagram that is used for end-to-end operation flow is carried out the non-intrusion type monitoring that further is shown specifically according to the embodiment of the invention;
Fig. 5 schematically shows the example that is used to monitor an operation flow according to the embodiment of the invention;
Fig. 6 schematically shows the defined event metadata of example that is used for monitoring an operation flow according to the embodiment of the invention;
Fig. 7 schematically shows the automatic incident propelling rule that generates of example that is used for monitoring an operation flow according to the embodiment of the invention;
Fig. 8 schematically shows the example that is used for monitoring an operation flow according to the embodiment of the invention and changes the incident that generates by the user and advance regular.
Embodiment
Fig. 1 and Fig. 2 are respectively supervisory system 100 and the process flow diagrams that illustrates according to the end-to-end non-intrusion type that is used for operation flow of the embodiment of the invention.As shown in Figure 1, this supervisory system 100 comprises: event editor 101, and be used to define and want the monitored relevant event metadata E1 of operation flow, E2...En and generation incident advance regular; Data event sensor 102 is used for changing based on business datum producing Database Events; And monitoring server 103, be used for advancing rule to monitor end-to-end operation flow based on Database Events and event metadata and incident.In the supervisory system shown in Fig. 1 100, data event sensor 102 can realize in many ways that for example, it can be realized by database trigger and UDF (user-defined function).Data event sensor 102 for example by communicating by letter with Service Database, obtains the variation of business datum thus, thereby changes the generation Database Events based on business datum.Supervisory system 100 as shown in Figure 1 can also comprise other assembly, Cache or the like for example, and for fuzzy the present invention, the description of other this class component is omitted.The process flow diagram of non-intrusion type method for supervising of the present invention as shown in Figure 2.At step 201 place, define the event metadata that is associated at each operation flow state in the monitored operation flow of needs, and generate the incident propelling rule that to stipulate the progress direction between each operation flow state.At step 202 place, during certain operation flow state in wanting monitoring business flowpath, based in the data event sensor, producing Database Events with changing at the relevant business datum of the defined event metadata of this operation flow state.At step 203 place, monitoring server advances rule and Database Events to produce monitored business event and be presented to the user based on event metadata, incident, realizes the monitoring to this operation flow state.For each the operation flow state that needs in the operation flow to monitor, the user can define various monitored incident E1, E2 ..., En.Each event metadata E1 wherein, E2 ..., En comprises trigger condition and content, and comprise with Service Database in business datum related.For instance, an exemplary event metadata (E5) is defined as follows:
createInstance:No
Trigger:AFTER INSERTON No tification(T5)
Correlation Condition:notification.msgID＝$poACKID
Correlation set:
Data Retrieving:Select*From Notification
Data: title:notification.title
user:notification.userName
date:notificaiton.sendTime
This shows, event metadata is definition and the description to the Database Events of representing the operation flow state in the monitored operation flow, it includes various field, for example createInstance field (establishment example), trigger field (triggering), CorrelationCondition field (related condition), Correlation set field (correlativity setting), Data Retrieving field (data retrieval) and Data field (data).Being described below of each field of described event metadata: createInstance: the value of this field is Yes/No.Yes shows that when monitoring this incident this incident is considered to the first generation incident of monitored flow process, monitors flow instance accordingly and can create on monitoring server.Trigger: in example of the present invention, corresponding is the trigger that is defined on the Service Database.CorrelationCondition: be conditional expression, be used to judge whether this monitor event is to be associated with certain monitoring flow instance.When createInstance is Yes, can not define this field.Correlation Set: global variable (global variable) assignment to the monitoring flow process, can in the expression formula of Correlation Condition, be occurred by the variable of assignment, whether be used for decision event related with flow instance.Data Retrieving:SQL statement, how definition obtains the business datum that needs from Service Database.Data: the business datum that the definition monitor event needs, for example title (title), user (user) and date (date) or the like.And they are mapped to the field in the SQL statement among the Data Retrieving.In addition, for the whole service flow process, can the generation incident advance rule.Described incident advances rule to be used to describe the order of occurrence of the monitor event of operation flow.Wherein advance rule for described incident, it is used for defining the follow-up one or more incidents of subsequently all of an incident.The incident that is noted that advances rule also can be generated automatically according to event metadata on the monitoring process base that the user describes by user's manual definition.For example, a kind of mode by user's manual definition time propelling rule is: 1) the global variable of the needs of user definition operation flow; 2) event metadata of the needs of user definition operation flow; 3) user is according to the logic of monitoring flow process, and the definition incident advances rule.In addition, a kind of mode according to the automatic rise time propelling of event metadata rule is: the logical view of user definition monitoring flow process; The user defines event metadata on some nodes of operation flow; If defined a plurality of monitor events on the described node, then indicate the precedence relationship of these incidents; According to the definition of monitoring flow process, generation incident automatically advances rule.It is exemplary that the event metadata of above-mentioned definition and incident advance rule, and the present invention is not limited thereto, but can also carry out other suitable definition according to practical application.
Fig. 3 and Fig. 4 are respectively the non-intrusion type supervisory system 300 and the process flow diagrams that are used for the teleservice flow process that further is shown specifically according to the embodiment of the invention.As shown in Figure 3, preferably, this supervisory system 300 comprises: event editor 301, and be used to define and want the monitored relevant event metadata E1 of operation flow, E2...En and generation incident advance regular; Data event sensor 302 is used for changing based on business datum producing Database Events; And monitoring server 303, be used for advancing rule to monitor end-to-end operation flow based on Database Events and event metadata and incident.Wherein monitoring server 303 preferably also comprises: event metadata database 305, be used for storing described event metadata E1 from event editor 301, and E2...En and described incident advance rule; Supervisor engine 306 is used for advancing rule to generate business event based on described Database Events and described event metadata and described incident; Business event watch-dog 320 is used for coming monitoring business flowpath based on described business event.Wherein business event watch-dog 320 preferably includes: monitor database 307, be used to store from the described business event of supervisor engine 306 and with business event and offer visualization model 308, and visualization model 308 is used for business event is visual and offer the user so that monitoring business flowpath.The monitoring process flow diagram of this supervisory system 300 as shown in Figure 4, at step 401 place, event editor 301 definition event metadata and incident advance rule, and wherein event metadata is corresponding to the monitored operation flow state in the operation flow, and incident advances the working direction of rule expression operation flow.Advance rale store in event metadata database 305 defined event metadata and incident at step 402 place.And in step 403, the variation based on business datum in data event sensor 302 generates Database Events.Then, the supervisor engine 306 in the monitoring server 303 advances rule to generate business event in step 404 based on described Database Events and described event metadata and described incident.In step 405, then be stored in the monitor database 307 and will be provided for visualization model 308 then from the business event of supervisor engine 306.At last in step 406, visualization model 308 is visual and offer the user so that monitoring business flowpath with business event.In supervisory system 300 as shown in Figure 3, supervisor engine 306 wherein also comprises incident distributor 310, is used to receive from the Database Events of data event sensor 302 triggerings and with Database Events be distributed to the flow monitoring instance and thread.When the Database Events that receives from incident distributor 310 distribution, the flow monitoring instance and thread is checked the condition of a business event.If this business event condition satisfies, then send monitored business event with data.Then, advance rule for the next event application affairs.When user login and utilize the title of monitored operation flow and example ID when inquiring about monitored flow process, the operation flow supervisor engine will be inquired about the monitored business event that is sent by the processing monitoring thread, and extract the data of business event and present visual model from monitor database and give the user.Wherein, the described Database Events corresponding to the change of operation flow data will reflect the operation flow logic.Supervisory system 300 as shown in Figure 3 can also comprise other assembly, Cache or the like for example, and for fuzzy the present invention, the description of other this class component is omitted.
With a concrete example Database Events and monitored business event and regular generation and the operation flow monitoring end to end of incident propelling in the operation flow method for supervising of the present invention are described to Fig. 7 below with reference to Fig. 5.Should be appreciated that this example is just used a specific example of the present invention, be not limited to this and can use operation flow monitoring of the present invention.In this example, on the one hand, buyer's logging in network server is done shopping, and the buyer submits the order of purchase to.On the other hand, supplier confirms order or revises, if confirm refusal order message, then will refuse order message informing buyer; If confirm to accept order message, then ensuingly be divided into two kinds of situations, if do not need the buyer to confirm that then order directly comes into force; The buyer further confirms if desired, if the order that buyer's acceptance is identified, then order comes into force; If the buyer does not accept the order that is identified, then notify supplier with buyer's refuse information.After order comes into force, will send to factory to order.Factory's delivery afterwards, logistics distribution, examination is received.In order to monitor such operation flow, at first understand the business datum relevant, and the definition trigger is as shown in table 1 below with this operation flow.
| Business Name | Key (key) | Reference key | Remarks | The trigger of creating for monitoring |
| POReq | POR_ID | T1:After INSERT ON POReq | ||
| POAck | POACK_ID | POR_ID | Accept/refuse/accept with changing.The buyer checks state | T2:After INSERTON POACK T3:After UPDATE ON POACK |
| PO | PO_ID | POR_ID | ||
| POChange | POChange_ID | POR_ID | ||
| POCancel | POCancel_ID | POR_ID | ||
| ASN | ASN_ID | POR_ID | T4:After INSERT ON ASN | |
| ShipmentRecipt | CRA_ID | ASN_ID |
| Notification | Notice_ID | T5：After INSERT ON Notification |
Table 1
For example, in this operation flow, can define some incidents, for example, when the buyer submits order to, definition incident E1, it is as follows to comprise some fields among the incident E1.Because incident E1 is first incident, so this flow monitoring example is created at this, so the createInstance field is for being.And trigger fields is to trigger according to request, so the Trigger field is: AFTER INSERT ON POReq (T1).Correlativity setting represents this operation flow relevant with concrete order request, and Correlation Set field is poID=POReq.POR_ID.Because E1 is first incident, do not have any correlativity, so Corralation Condition field is empty.Data retrieving field is Select*From POReq, and the Data field is: POID:POReq.POR_ID; Date:POReq.receive Time.After order was submitted to, supplier confirmed order, at this definition incident E2, comprises following these fields among the incident E2.Because incident E2 is the intermediate event of this operation flow, so the createInstance field is for denying.The Trigger field is AFTER INSERT ON POACK (T2).Because E2 is an intermediate event, it and incident E1 before have correlativity, so Corralation Condition field is not empty, but POACK.POR_ID=$poID.$ represents to quote the variable among the gloabal variable.Correlation Set field is poACKID=POACK.POACK_ID.The Dataretrieving field is Select*From POACK.The Data field is: POACKID:POACK.POACK_ID; Date:POACK.receiveTime; Status:POACK.status.After supplier does not accept order, then will negate to determine the message informing buyer, at this definition incident E3, incident E3 comprises following these fields.Because incident E3 also is the intermediate event of this operation flow, so the createInstance field is for denying.The Trigger field is AFTER INSERTON Notification (T3).Because E3 is intermediate event, it has correlativity with before incident E1 and E2, so Corralation Condition field be a sky, but can with incident E1 or E2 carry out relevant, notification.msg=$poACKID for example.The CorrelationSet field is empty.Data retrieving field is Select*From Notification.The Data field is: title:notification.title; User:notification.userName; Date:notification.sendTime.If after incident E2, supplier accepts order, and when needing the user that the order of confirming is confirmed, at this definition incident E4, incident E4 comprises following these fields.Because incident E4 also is the intermediate event of this operation flow, so createInstance is for denying.The Trigger field is AFTER UPDATE ON POACK (T3).Because E4 is an intermediate event, it and before incident E1, E2 and E3 have correlativity, so Corralation Condition field is not empty, but can with incident E1, E2 or E3 carry out relevant, Correlation Condition:POACK.POACKID=$poACKID for example.Correlation set field is empty.The Dataretrieveing field is Select*from POACK.The Data field is poACKid:$poACKID; Status:POACK.BuyerReviewStatus; Date:POACK.BuyerReviewTime.In like manner, can define the incident E5 that buyer's firm order is notified supplier after correct, and order is notified the incident E6 of factory after coming into force.Each field contents of incident E5 is as follows: createInstance:No; Trigger:AFTER INSERT ONNotification (T5); Correlation Condition:notification.msgID=$poACKID; Correlation set:; Data Retrieving:Select*From Notification; Data:title:notification.title; User:notification.userName; Date:notificaiton.sendTime.Each field contents of incident E6 is as follows: createInstance:No; Trigger:AFTERINSERT ON ASN (T4); Correlation Condition ASN.POR_ID=$poId; Correlation set:ASNID=ASN.ASN_ID; Data retrieving:Select*from ASN; Data:title:ASN ASN_ID; Date:ASN.sendTime.
After the event definition of operation flow, can advance rule according to some pattern generation incident simultaneously.Incident advances rule to generate automatically according to operation flow, also can be generated or be adjusted or upgraded by the user by the user.For example, based on operation flow, incident advances rule can generate as follows automatically: begin to advance to incident E1, incident E1 advances to incident E2, and incident E2 advances to incident E3 or incident E4 or incident E6, and incident E3 advances to end, incident E4 advances to incident E5 or incident E6, incident E5 advances to end, and incident E6 advances to incident E7, and incident E7 advances to end.Replacedly, as shown in Figure 8, incident advances rule can be changed as follows by the user: begin to advance to incident E1, incident E1 advances to incident E2, incident E2 advances to incident E3, incident E5 or incident E6, and incident E3 advances to end, and incident E5 advances to end, incident E6 advances to incident E7, and incident E7 advances to end.This amended incident advances rule to represent to be different from before, and incident advances regular operation flow logic.Embodied the dirigibility of supervisory system of the present invention and method thereof thus.
Should be appreciated that it is exemplary that the incident E1-E7 of above-mentioned definition and incident advance rule, the present invention is not limited thereto, but can also carry out other suitable definition according to practical application.
Therefore, at this exemplary operation flow, the method for teleservice flow monitoring of the present invention is to realize like this.When the buyer submits order to, then current operation flow state is corresponding to (generation) incident E1, incident E1 corresponding service data (promptly, each field that is comprised among the Data of E1) is stored in the business datum database of lower floor, the renewal of business datum has produced Database Events, this Database Events is pushed in the incident distributor of supervisor engine, and the incident distributor is distributed to Database Events flow monitoring thread (not creating the flow monitoring of example) and the flow monitoring instance and thread that may be correlated with accordingly.The supervisor engine monitoring advances rule definition based on incident and incident then, mate this Database Events to E1, visioning procedure monitoring example, flow monitoring example " begin to advance to incident E1 " and according to the definition tissue of E1 with send a business event in monitor database.Final business event converts visual model to and is and passs the user, so that the executing state that the user can tracking of service flow.When order is sent to supplier, then this operation flow state is corresponding to (generation) incident E2, incident E2 corresponding service data (promptly, each field that E2 comprised) is stored in the business datum database of lower floor, therefore be updated to business datum in the business datum database corresponding to incident E2, therefore the renewal of business datum has produced another Database Events, this Database Events is pushed in the incident distributor of supervisor engine, and the incident distributor is distributed to corresponding possible flow monitoring instance and thread with Database Events.The supervisor engine monitoring advances rule definition to mate this Database Events to E2 based on incident E2 and incident then, and the flow monitoring example " advances to incident E2 by incident E1 " and sends a business event in monitor database.This business event converts visual model to and is and passs the user, so that the user can follow the tracks of this operation flow state.In like manner, the user can define incident E3-E6 and events corresponding advances rule, thereby the variation of the corresponding business datum by being mapped to the business datum database generates the corresponding business incident and converts the executing state of visual monitor view for the user monitoring operation flow to thereby produce Database Events.
This shows, utilization is according to the method and system that is used for end-to-end operation flow is carried out the non-intrusion type monitoring of the present invention, make the user can define the incident relevant and incident and advance rule with interested operation flow state in the monitored operation flow, thereby thereby by advancing the variation of the bottom business datum that rule is associated to reflect that operation flow state in the monitored operation flow realizes the non-intrusion type monitoring of operation flow with described incident and incident.
Certainly, it will be understood by those of skill in the art that method of the present invention can be encoded to the program that is stored on the computer-readable recording medium, computing machine is carried out this program to realize method of the present invention.Therefore, the present invention also covers the method according to this invention calculation of coding machine program product, and the computer-readable recording medium of storing this computer program.
Should be noted that for the present invention is more readily understood top description has been omitted to be known for a person skilled in the art and may to be essential some ins and outs more specifically for realization of the present invention.
The purpose that instructions of the present invention is provided is in order to illustrate and to describe, rather than is used for exhaustive or limits the invention to disclosed form.For those of ordinary skill in the art, many modifications and changes all are conspicuous.
Therefore; selecting and describing embodiment is in order to explain principle of the present invention and practical application thereof better; and those of ordinary skills are understood, under the prerequisite that does not break away from essence of the present invention, all modifications and change all fall within protection scope of the present invention defined by the claims.
Claims (18)
1. one kind is used for end-to-end operation flow is carried out the system that non-intrusion type is monitored, and comprising:
Event editor is used to define and wants monitored operation flow relevant event metadata and generation incident to advance regular;
The data event sensor is used for changing based on business datum producing Database Events; And
Monitoring server is used for advancing rule to monitor end-to-end operation flow based on Database Events and event metadata and incident.
2. system according to claim 1, wherein, described monitoring server also comprises:
Supervisor engine is used for advancing rule to generate business event based on described Database Events and described event metadata and described incident;
The business event watch-dog is used for coming monitoring business flowpath based on described business event.
3. system according to claim 1 also comprises: the event metadata database, the described event metadata and the described incident that are used for storing from event editor advance rule.
4. according to any described system of claim 1-3, wherein: event editor also is used for generating automatically described incident propelling rule or manually generates described incident propelling rule by the user.
5. system according to claim 1, wherein: described monitoring server also comprises the incident distributor, is used to accept Database Events and Database Events is distributed to the flow monitoring instance and thread.
6. system according to claim 1, wherein, described business event watch-dog also comprises the transaction event database that is used for the storage service incident.
7. system according to claim 1, wherein: described event metadata and described incident advance described business datum variation regular and in the data event sensor to be associated.
8. system according to claim 1, wherein said monitoring server also is used for advancing rule to determine next event metadata based on current event metadata and incident.
9. system according to claim 2, wherein said monitoring server also comprises visualization model, is used to receive from the business event of business event watch-dog and converts business event to user visual data pass the user to be.
10. a method that is used for end-to-end operation flow is carried out the non-intrusion type monitoring comprises the steps:
Definition with will the monitored relevant event metadata of operation flow;
The incident that the operation flow that generates and will be monitored is relevant advances rule;
Change based on business datum and to produce Database Events; And
Advance rule to monitor end-to-end operation flow based on Database Events and event metadata and incident.
11. method according to claim 10, wherein, the step that advances rule to monitor end-to-end operation flow based on Database Events and event metadata and incident further comprises: advance rule to generate business event based on described Database Events and described event metadata and described incident; Come monitoring business flowpath based on described business event then.
12. method according to claim 10 also comprises advancing rale store in the event metadata database described event metadata and described incident.
13. according to any described method of claim 10-12, wherein: described incident advances rule to generate automatically or manually generates by the user.
14. method according to claim 10 also comprises: Database Events is received and is distributed to the flow monitoring instance and thread, and flow process control examples thread advances rule and Database Events to send a business event based on event metadata and incident.
15. method according to claim 11 also comprises business event is stored in the transaction event database.
16. method according to claim 10, wherein: described event metadata and described incident advance rule to change with described business datum and are associated.
17. method according to claim 10 also comprises: advance rule to determine next event metadata based on current event metadata and incident.
18. system according to claim 11 comprises that also reception is from the business event of business event watch-dog and convert business event to user visual data and pass the user to be.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810087924A CN101546396A (en) | 2008-03-25 | 2008-03-25 | Method and system for performing non-intrusive monitoring on end-to-end service processes |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810087924A CN101546396A (en) | 2008-03-25 | 2008-03-25 | Method and system for performing non-intrusive monitoring on end-to-end service processes |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101546396A true CN101546396A (en) | 2009-09-30 |
Family
ID=41193522
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200810087924A Pending CN101546396A (en) | 2008-03-25 | 2008-03-25 | Method and system for performing non-intrusive monitoring on end-to-end service processes |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101546396A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106096920A (en) * | 2016-08-19 | 2016-11-09 | 江苏电力信息技术有限公司 | A kind of power grid operation based on end-to-end flow process management on-line monitoring method |
| CN106803152A (en) * | 2017-01-23 | 2017-06-06 | 北京外企德科人力资源服务上海有限公司 | A kind of operation flow Visualized Monitoring System |
-
2008
- 2008-03-25 CN CN200810087924A patent/CN101546396A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106096920A (en) * | 2016-08-19 | 2016-11-09 | 江苏电力信息技术有限公司 | A kind of power grid operation based on end-to-end flow process management on-line monitoring method |
| CN106803152A (en) * | 2017-01-23 | 2017-06-06 | 北京外企德科人力资源服务上海有限公司 | A kind of operation flow Visualized Monitoring System |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7730022B2 (en) | Data processing system and method for supply chain management | |
| CN101963799B (en) | Process control system with integrated external data sources | |
| US8799031B2 (en) | System and method to screen insurance claims to identify subrogation potential | |
| CN106447284B (en) | Nuclear power station DCS configuration change informatization platform management system and method | |
| WO2002071171A3 (en) | Automatic work order/parts order generation and tracking | |
| CN108764610A (en) | Standard technology construction management of project method based on big data, storage medium | |
| KR101552216B1 (en) | Integrated system for research productivity and operation managment based on big date technology, and method thereof | |
| CN110991886A (en) | Community task processing method, device, equipment and medium | |
| CN113448693A (en) | SAAS cloud platform of digital factory | |
| CN107846322A (en) | A kind of monitoring system of self-service device | |
| CN101546396A (en) | Method and system for performing non-intrusive monitoring on end-to-end service processes | |
| CN104346669A (en) | Business logic modeling system based on 6W | |
| CN111046068B (en) | Method and device for displaying alarm generation process | |
| CN116757484B (en) | Enterprise safety hidden danger monitoring and tracing method, device, equipment and storage medium | |
| CN109389328A (en) | A kind of card Product development process management method and system | |
| CN101527012A (en) | Flow template generation method, flow mission executor determining method and devices thereof | |
| CN117455358A (en) | Tool priority ex-warehouse control method based on radio frequency reading technology | |
| JP5028129B2 (en) | Facility business integrated management method and system and program thereof | |
| CN105099939A (en) | Method and device for implementing flow control among different data centers | |
| US20100169387A1 (en) | Analytics enablement objects | |
| CN114157705A (en) | Information pushing method and device and storage medium | |
| CN110069765B (en) | Method and device for monitoring compilation process of merged report | |
| JP2011048459A (en) | System and method for supporting project planning | |
| CN115239216B (en) | Method, device, equipment and storage medium for preventive planned maintenance of production resources | |
| CN105827418B (en) | A kind of communication network warning correlating method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| AD01 | Patent right deemed abandoned |
Effective date of abandoning: 20090930 |
|
| C20 | Patent right or utility model deemed to be abandoned or is abandoned |