# US 2003/0225820 A1 · System and method for collecting and storing event data from distributed transactional applications

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2003/0225820 A1
- Document ID: US20030225820A1
- Status: Published application
- Kind: A1
- Application number: 10/160,844
- Filed: 2002-05-31
- Published: 2003-12-04
- Earliest claimed: 2002-05-31
- Assignees: Microsoft Corporation
- Inventors: Gueorgui B. Chkodrov; Richard Z. Jason
- Web page: https://patentgrep.com/patent/US20030225820A1

## CPC

- G06F 16/2358: {Change logging, detection, and notification (replication G06F16/27)}
- Y10S 707/99938: Concurrency, e.g. lock management in shared database
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- Y10S: TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS

## Abstract

Event data associated with state data corresponding to an instance of a process is collected by an interceptor associated with a server that performs an operation to modify the state data. The server performs a single transaction with the database to store both the modified state data and the associated event data, the transaction either succeeding or failing, whereby if the transaction succeeds, then both the state data and the event data are stored at the database, and if the transaction fails, then both the state data and the event data are not stored at the database. The event data stored at the database is then transmitted to a tracking service for conversion into a query-able format.

## Claims

### Claim 1

A method for collecting tracking data, comprising:
retrieving from a database state data corresponding to an instance of a process;
performing an operation on the instance to modify the state data;
collecting event data associated with the operation; and
performing a single transaction with the database to store both the modified state data and the associated event data at such database, the transaction either succeeding or failing, whereby if the transaction succeeds, then both the state data and the event data are stored at the database, and if the transaction fails, then both the state data and the event data are not stored at the database.

### Claim 2 (depends on 1)

The method of claim 1, wherein retrieving state data from a database comprises retrieving at a server state data from a database.

### Claim 3 (depends on 1)

The method of claim 1, wherein performing an operation on the instance to modify the state data comprises performing at a server an operation on the instance to modify the state data.

### Claim 4 (depends on 3)

The method of claim 3, wherein collecting event data associated with the operation comprises collecting at an interceptor running on the server event data associated with the operation.

### Claim 5 (depends on 1)

The method of claim 1, wherein collecting event data comprises collecting event data corresponding to pre-selected events with regard to the transaction.

### Claim 6 (depends on 5)

The method of claim 5, wherein collecting event data corresponding to pre-selected events with regard to the transaction comprises collecting at least one of service start, service end, and service error data.

### Claim 7 (depends on 5)

The method of claim 5, wherein collecting event data corresponding to pre-selected events with regard to the transaction comprises collecting al least one of message in and message out metadata information.

### Claim 8 (depends on 5)

The method of claim 5, wherein collecting event data corresponding to pre-selected events with regard to the transaction comprises collecting at least one of debugging data, trace data, and message bodies.

### Claim 9 (depends on 1)

The method of claim 1, wherein performing a single transaction with the database comprises performing a single transaction wherein data is transmitted from a server to the database.

### Claim 10 (depends on 1)

The method of claim 1, comprising performing the single transaction only after the operation to modify the state data has been fully performed and the event data has been fully collected.

### Claim 11

A system for collecting tracking data, comprising:
a database for storing state data corresponding to an instance of a process;
a server for retrieving the state data from the database, performing an operation on the instance to modify the state data, and performing a single transaction with the database to store both the modified state data and the associated event data at the database, the transaction either succeeding or failing; and
an interceptor for collecting the event data.

### Claim 12 (depends on 11)

The system of claim 11, wherein said interceptor comprises an interceptor running at said server.

### Claim 13

A method for converting tracking data into query-able data, comprising:
receiving a stream of event data from at least one database, the stream of event data including a plurality of event items, each event item associated with one of a plurality of operations performed on one of a plurality of instances of a process; and
formatting the stream of event data into query-able database by applying a method to each event item to store the event item according to the corresponding instance, whereby a current state of the instance may be obtained from the query-able database and statistics on the plurality of operations may be obtained from the query-able database.

### Claim 14 (depends on 13)

The method of claim 13, comprising receiving streams of event data from a plurality of databases and organizing the received streams of event data into a single stream.

### Claim 15 (depends on 13)

The method of claim 13, comprising formatting the stream of event data into data formatted for online analytical processing.

### Claim 16 (depends on 13)

The method of claim 13, comprising formatting the stream of event data into data organized according to a plurality of dimensions, whereby each dimension represents an attribute of the data.

### Claim 17 (depends on 16)

The method of claim 16, comprising formatting the stream of event data into data that may be organized according to a plurality of dimensions wherein one dimension in the plurality of dimensions represents a identifier identifying each event.

### Claim 18 (depends on 16)

The method of claim 16, comprising formatting the stream of event data into data that may be organized according to a plurality of dimensions wherein one dimension in the plurality of dimensions represents an event type.

### Claim 19 (depends on 16)

The method of claim 16, comprising formatting the stream of event data into data that may be organized according to a plurality of dimensions wherein one dimension in the plurality of dimensions represents an event time.

### Claim 20

A computer readable medium having stored thereon computer executable instructions implementing a method for collecting tracking data, the method comprising:
retrieving from a database state data corresponding to an instance of a process;
performing an operation on the instance to modify the state data;
collecting event data associated with the operation; and
performing a single transaction with the database to store both the modified state data and the associated event data at such database, the transaction either succeeding or failing, whereby if the transaction succeeds, then both the state data and the event data are stored at the database, and if the transaction fails, then both the state data and the event data are not stored at the database.

### Claim 21 (depends on 20)

The medium of claim 20, wherein retrieving state data from a database comprises retrieving at a server state data from a database.

### Claim 22 (depends on 20)

The medium of claim 20, wherein performing an operation on the instance to modify the state data comprises performing at a server an operation on the instance to modify the state data.

### Claim 23 (depends on 22)

The medium of claim 22, wherein collecting event data associated with the operation comprises collecting at an interceptor running on the server event data associated with the operation.

### Claim 24 (depends on 20)

The medium of claim 20, wherein collecting event data comprises collecting event data corresponding to pre-selected events with regard to the transaction.

### Claim 25 (depends on 24)

The medium of claim 24, wherein collecting event data corresponding to pre-selected events with regard to the transaction comprises collecting at least one of service start, service end, and service error data.

### Claim 26 (depends on 24)

The medium of claim 24, wherein collecting event data corresponding to pre-selected events with regard to the transaction comprises collecting al least one of message in and message out metadata information.

### Claim 27 (depends on 24)

The medium of claim 24, wherein collecting event data corresponding to pre-selected events with regard to the transaction comprises collecting at least one of debugging data, trace data, and message bodies.

### Claim 28 (depends on 20)

The medium of claim 20, wherein performing a single transaction with the database comprises performing a single transaction wherein data is transmitted from a server to the database.

### Claim 29 (depends on 20)

The medium of claim 20, wherein the method comprises performing the single transaction only after the operation to modify the state data has been fully performed and the event data has been fully collected.

### Claim 30

A computer readable medium having stored thereon computer executable instructions implementing a method for collecting tracking data, the method comprising:
receiving a stream of event data from at least one database, the stream of event data including a plurality of event items, each event item associated with one of a plurality of operations performed on one of a plurality of instances of a process; and
formatting the stream of event data into query-able database by applying a method to each event item to store the event item according to the corresponding instance, whereby a current state of the instance may be obtained from the query-able database and statistics on the plurality of operations may be obtained from the query-able database.

### Claim 31 (depends on 30)

The medium of claim 30, wherein the method comprises receiving streams of event data from a plurality of databases and organizing the received streams of event data into a single stream.

### Claim 32 (depends on 30)

The medium of claim 30, wherein the method comprises formatting the stream of event data into data formatted for online analytical processing.

### Claim 33 (depends on 30)

The medium of claim 30, wherein the method comprises formatting the stream of event data into data organized according to a plurality of dimensions, whereby each dimension represents an attribute of the data.

### Claim 34 (depends on 33)

The method of claim 33, comprising formatting the stream of event data into data that may be organized according to a plurality of dimensions wherein one dimension in the plurality of dimensions represents a identifier identifying each event.

### Claim 35 (depends on 33)

The medium of claim 33, wherein the method comprises formatting the stream of event data into data that may be organized according to a plurality of dimensions wherein one dimension in the plurality of dimensions represents an event type.

### Claim 36 (depends on 33)

The medium of claim 33, wherein the method comprises sing formatting the stream of event data into data that may be organized according to a plurality of dimensions wherein one dimension in the plurality of dimensions represents an event time.
