Multi-level transaction flow monitoring

• US 7,698,186 B2
• Filed: 07/26/2005
• Issued: 04/13/2010
• Est. Priority Date: 07/26/2005
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Yatzkar-Haham, Tali, Botzer, David, Oren, David
• Primary Examiner(s): Havan; Thu Thao
• Application Number:
  US11/189,356
• Publication Number:
  US 20070027801A1
• Time in Patent Office: 1,722 Days
• Field of Search: 705 35- 36
• US Class Current: 705/35
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/04 Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Abstract

A computer-implemented method for monitoring transactions in a computer system includes monitoring events reported by components of the computer system responsively to a flow of the transactions through the system. A state machine model and a rule-based model are jointly applied to the monitored events, so as to identify respective transaction-level events and business-level events. A status of the flow of the transactions is assessed responsively to the transaction-level events and the business-level events.

Claims

1. A computer-implemented method for monitoring transactions in a computer system, comprising:

monitoring events reported by components of the computer system responsively to a flow of the transactions through the system;

applying a state machine model to the monitored events so as to identify transaction-level events, and applying a rule-based model to the monitored events so as to identify business-level events;

performing at least one action selected from a group of actions consisting of;

modifying, responsively to at least one of the business-level events identified by the rule-based model, a first criterion applied by the state machine model in identifying one or more of the transaction-level events; and

modifying, responsively to at least one of the transaction-level events identified by the state machine model, a second criterion applied by the rule-based model in identifying one or more of the business-level events; and

assessing a status of the flow of the transactions responsively to the transaction-level events and the business-level events.

2. The method according to claim 1, wherein the transactions comprise financial transactions.

3. The method according to claim 1, wherein monitoring the events comprises exporting the reported events from the components of the computer system to a monitoring system external to the components of the computer system that perform the transactions, wherein the external monitoring system applies the state machine model and the rule-based model and assesses the flow of the transactions.

4. The method according to claim 1, wherein monitoring the events comprises performing at least one action selected from a group of actions consisting of accepting events reported using built-in mechanisms of the components, incorporating one or more monitoring agents into some of the components, and monitoring interfaces between some of the components.

5. The method according to claim 1, wherein applying the state machine model and the rule based model and assessing the status comprise performing at least one action selected from a group of actions consisting of configuring the state machine model, configuring the rule-based model, configuring queries for information and configuring information to be presented to a user, by using a declarative language.

6. The method according to claim 5, wherein the declarative language comprises an extensible markup language (XML).

7. The method according to claim 1, wherein applying the state machine model comprises defining transaction states representing a status of a monitored transaction in the flow, defining state transitions connecting between the transaction states and defining transaction data comprising information relating to the monitored transaction.

8. The method according to claim 7, wherein defining the state transitions comprises, for each state transition, defining a triggering event that triggers the state transition responsively to at least one of the monitored events and the business-level events identified by the rule-based model, and wherein applying the state machine model comprises updating the transaction state of the monitored transaction responsively to an occurrence of the corresponding triggering event.

9. The method according to claim 8, wherein defining the state transitions comprises defining a validity check, and wherein updating the transaction state comprises generating a transaction lifecycle alert responsively to a failure in the validity check of the corresponding state transition.

10. The method according to claim 9, wherein generating the transaction lifecycle alert comprises generating at least one alert type selected from a group of types consisting of a timeout alert, an event inconsistency alert, an event constraint alert and a data constraint alert.

11. The method according to claim 1, wherein applying the rule-based model comprises performing at least one action selected from a group of actions consisting of detecting service level agreement (SLA) violation, anticipating the SLA violation, detecting a deviation from an expected key performance indicator (KPI) value, anticipating the deviation from the expected KPI value, detecting a problem related to the flow external to the computer system, and identifying a system level problem in one or more of the components of the computer system.

12. The method according to claim 1, wherein applying the rule-based model comprises applying a predefined business rule to at least one of the monitored events and the transaction-level events identified by the state machine model, and identifying at least a given business-level event responsively to the evaluated business rule.

13. The method according to claim 1, wherein applying the rule-based model comprises identifying at least a given business-level event responsively to a time-dependent trigger.

14. The method according to claim 1, wherein assessing the status comprises detecting an undesired condition comprising at least one condition type selected from a group of types consisting of a service level agreement (SLA) violation, an anticipated SLA violation, a hardware problem in one or more of the components, an anticipated hardware problem, a capacity bottleneck in the flow, an anticipated capacity bottleneck, a deviation from an expected key performance indicator (KPI) value and an anticipated deviation from the expected KPI value.

15. The method according to claim 14, wherein detecting the undesired condition comprises generating an alert to a user responsively to the detected condition.

16. The method according to claim 1, wherein assessing the status comprises defining a query using a query template and addressing the query to at least one of the state machine model and the rule-based model for information related to the flow.

17. The method according to claim 1, wherein assessing the status comprises performing at least one action selected from a group of actions consisting of calculating and presenting statistical information related to the flow, and calculating and presenting information relating to a key performance indicator (KPI).

19. The method according to claim 1, wherein modifying the first criterion comprises defining in the state machine model a state transition condition that depends on the at least one of the business-level events.

20. The method according to claim 1, wherein modifying the second criterion comprises defining in the rule-based model a rule that depends on the at least one of the transaction-level events.

18. A computer-implemented method for monitoring transactions in a computer system, comprising:

exporting events reported by components of the computer system responsively to a flow of the transactions through the system to a monitoring system external to the components of the computer system that perform the transactions;

at the monitoring system,

applying a state machine model to the exported events so as to identify transaction-level events, applying a rule-based model to the exported events so as to identify business-level events,

performing at least one action selected from a group of actions consisting of;

modifying, responsively to at least one of the business-level events identified by the rule-based model, a first criterion app lied by the state machine model in identifying one or more of the transaction-level events; and

modifying, responsively to at least one of the transaction-level events identified by the state machine model, a second criterion applied by the rule-based model in identifying one or more of the business-level events; and

assessing a status of the flow of the transactions responsively to the transaction-level events and the business-level events.