# US 2015/0106789 A1 · Continuous monitoring and analysis of software events

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

- Number: US 2015/0106789 A1
- Document ID: US20150106789A1
- Status: Published application
- Kind: A1
- Application number: 14/053,409
- Filed: 2013-10-14
- Published: 2015-04-16
- Earliest claimed: 2013-10-14
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: OMAR CARDONA; Michael Paul Vageline
- Web page: https://patentgrep.com/patent/US20150106789A1

## CPC

- G06F 11/3466: {Performance evaluation by tracing or monitoring}
- G06F 2201/86: Event-based monitoring
- G06F 2201/865: Monitoring of software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A set of entry blocks is allocated. An entry block is configured with a set of monitoring attributes to store monitoring data corresponding to a monitoring request. The entry block is updated with an identifier supplied in the monitoring request. The entry block is used to store the monitoring data responsive to the monitoring request. The monitoring data comprises a continuous record of data changes at a requested location in memory from a beginning to an end a of an event corresponding to the monitoring request. A size of the monitoring data is distinct from another size of another monitoring data stored in another entry block in the set of entry blocks responsive to another monitoring request. An operation specified in the monitoring request is performed on a part of the monitoring data accessible from a monitoring attribute in the set of monitoring attributes of the entry block.

## Claims

### Claim 1

A method for continuous monitoring and analysis of software events, the method comprising:
allocating a set of entry blocks, an entry block in the set of entry blocks configured with a set of monitoring attributes to store monitoring data corresponding to a monitoring request;
updating the entry block with an identifier supplied in the monitoring request;
using the entry block to store the monitoring data responsive to the monitoring request, wherein the monitoring data comprises a continuous record of data changes at a requested location in memory from a time of beginning of an event to a time of ending of the event corresponding to the monitoring request, and wherein a size of the monitoring data is distinct from another size of another monitoring data stored in another entry block in the set of entry blocks responsive to another monitoring request; and
performing, using a processor, an operation specified in the monitoring request on a part of the monitoring data accessible from a monitoring attribute in the set of monitoring attributes of the entry block.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
allocating an anchor block, the anchor block storing (i) a reference to the set of entry blocks, (ii) a set of references to a corresponding set of functions, wherein a function in the set of functions performs the operation.

### Claim 3 (depends on 2)

The method of claim 2, the anchor block further including an attribute, where the attribute in the anchor block stores a computation performed using a common monitoring attribute from a subset of the set of entry blocks.

### Claim 4 (depends on 1)

The method of claim 1, wherein a first monitoring attribute in the entry block stores the time of the beginning, wherein a second monitoring attribute in the entry block stores the time of the ending, and wherein the operation is a statistical computation using the time of the beginning and the time of the ending of the event.

### Claim 5 (depends on 1)

The method of claim 1, wherein the event comprises execution of a section of program code in a thread corresponding to the monitoring request.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
using a second entry block to store second monitoring data responsive to the monitoring request, wherein the second monitoring data comprises data changes at the requested location in the memory from a second time of beginning of a second event to a second time of ending of the second event.

### Claim 7 (depends on 6)

The method of claim 6, wherein the second event is the event occurring in a second iteration of executing a section of program code corresponding to the event.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
receiving the monitoring request, wherein the monitoring request specifies a set of parameters of a monitoring activity, wherein a first parameter in the set of parameters includes an address in the memory, and a second parameter in the set of parameters includes a size of data from the address in the memory to be monitored responsive to an event.

### Claim 9 (depends on 8)

The method of claim 8, wherein a third parameter in the set of parameters includes an operation to be performed on the monitoring data collected in the entry block responsive to the monitoring request.

### Claim 10 (depends on 1)

The method of claim 1, wherein the set of entry blocks is configured as a list, further comprising:
allocating a new entry block responsive to a new monitoring request, wherein an entry block in the set of entry blocks is unavailable for use in monitoring responsive to the new monitoring request; and
adding the new entry block to the set of entry blocks forming a new set of entry blocks.

### Claim 11 (depends on 1)

The method of claim 1, wherein the set of entry blocks is configured as a ring buffer, further comprising:
selecting an old entry block from the set of entry blocks responsive to a new monitoring request, wherein a monitoring stop time of the old entry block is the oldest in the set of entry blocks; and
storing monitoring data responsive to the new monitoring request in the old entry block.

### Claim 12

A computer usable program product comprising a computer usable storage device including computer usable code for continuous monitoring and analysis of software events, the computer usable code comprising:
computer usable code for allocating a set of entry blocks, an entry block in the set of entry blocks configured with a set of monitoring attributes to store monitoring data corresponding to a monitoring request;
computer usable code for updating the entry block with an identifier supplied in the monitoring request;
computer usable code for using the entry block to store the monitoring data responsive to the monitoring request, wherein the monitoring data comprises a continuous record of data changes at a requested location in memory from a time of beginning of an event to a time of ending of the event corresponding to the monitoring request, and wherein a size of the monitoring data is distinct from another size of another monitoring data stored in another entry block in the set of entry blocks responsive to another monitoring request; and
computer usable code for performing, using a processor, an operation specified in the monitoring request on a part of the monitoring data accessible from a monitoring attribute in the set of monitoring attributes of the entry block.

### Claim 13 (depends on 12)

The computer usable program product of claim 12, further comprising:
computer usable code for allocating an anchor block, the anchor block storing (i) a reference to the set of entry blocks, (ii) a set of references to a corresponding set of functions, wherein a function in the set of functions performs the operation.

### Claim 14 (depends on 13)

The computer usable program product of claim 13, the anchor block further including an attribute, where the attribute in the anchor block stores a computation performed using a common monitoring attribute from a subset of the set of entry blocks.

### Claim 15 (depends on 12)

The computer usable program product of claim 12, wherein a first monitoring attribute in the entry block stores the time of the beginning, wherein a second monitoring attribute in the entry block stores the time of the ending, and wherein the operation is a statistical computation using the time of the beginning and the time of the ending of the event.

### Claim 16 (depends on 12)

The computer usable program product of claim 12, wherein the event comprises execution of a section of program code in a thread corresponding to the monitoring request.

### Claim 17 (depends on 12)

The computer usable program product of claim 12, further comprising:
computer usable code for using a second entry block to store second monitoring data responsive to the monitoring request, wherein the second monitoring data comprises data changes at the requested location in the memory from a second time of beginning of a second event to a second time of ending of the second event.

### Claim 18 (depends on 12)

The computer usable program product of claim 12, wherein the computer usable code is stored in a computer readable storage medium in a data processing system, and wherein the computer usable code is transferred over a network from a remote data processing system.

### Claim 19 (depends on 12)

The computer usable program product of claim 12, wherein the computer usable code is stored in a computer readable storage medium in a server data processing system, and wherein the computer usable code is downloaded over a network to a remote data processing system for use in a computer readable storage medium associated with the remote data processing system.

### Claim 20

A data processing system for continuous monitoring and analysis of software events, the data processing system comprising:
a storage device including a storage medium, wherein the storage device stores computer usable program code; and
a processor, wherein the processor executes the computer usable program code, and wherein the computer usable program code comprises:
computer usable code for allocating a set of entry blocks, an entry block in the set of entry blocks configured with a set of monitoring attributes to store monitoring data corresponding to a monitoring request;
computer usable code for updating the entry block with an identifier supplied in the monitoring request;
computer usable code for using the entry block to store the monitoring data responsive to the monitoring request, wherein the monitoring data comprises a continuous record of data changes at a requested location in memory from a time of beginning of an event to a time of ending of the event corresponding to the monitoring request, and wherein a size of the monitoring data is distinct from another size of another monitoring data stored in another entry block in the set of entry blocks responsive to another monitoring request; and
computer usable code for performing, using a processor, an operation specified in the monitoring request on a part of the monitoring data accessible from a monitoring attribute in the set of monitoring attributes of the entry block.
