Transactional boundaries for software system profiling
First Claim
1. A method comprising:
- receiving transaction data from a software-based agent instrumented on a particular software component in a system comprising a plurality of software components, wherein the transaction data identifies characteristics of a particular transaction involving the particular software component and another software component in the plurality of software components as observed by the agent during operation of the system, and the particular transaction is contemporaneous with another transaction involving software components in the system;
using a data processing apparatus to determine, from the transaction data, that the particular transaction falls within a defined transaction boundary for the system, wherein transactions meeting a set of conditions fall within the transaction boundary, and the other transaction falls outside the transaction boundary; and
invoking a profiler to perform software profiling of a portion of a system during the particular transaction based on determining that the particular transaction falls within the transaction boundary, wherein the portion of the system comprises at least the particular software component, software profiling comprises capturing information about execution of threads in the particular transaction, and the other transaction is not profiled by the invoked profiler based on the transaction boundary.
1 Assignment
0 Petitions
Accused Products
Abstract
Transaction data is received from a software-based agent instrumented on a particular software component in a system comprising a plurality of software components. The transaction data can describe characteristics of a particular transaction involving the particular software component and another software component in the plurality of software components as observed by the agent during operation of the system, the particular transaction is contemporaneous with another transaction involving software components in the system. From the transaction data, the particular transaction is determined to fall within a defined transaction boundary for the system. A profiler is automatically invoked to profile the particular transaction based on determining that the particular transaction falls within the transaction boundary.
-
Citations
22 Claims
-
1. A method comprising:
-
receiving transaction data from a software-based agent instrumented on a particular software component in a system comprising a plurality of software components, wherein the transaction data identifies characteristics of a particular transaction involving the particular software component and another software component in the plurality of software components as observed by the agent during operation of the system, and the particular transaction is contemporaneous with another transaction involving software components in the system; using a data processing apparatus to determine, from the transaction data, that the particular transaction falls within a defined transaction boundary for the system, wherein transactions meeting a set of conditions fall within the transaction boundary, and the other transaction falls outside the transaction boundary; and invoking a profiler to perform software profiling of a portion of a system during the particular transaction based on determining that the particular transaction falls within the transaction boundary, wherein the portion of the system comprises at least the particular software component, software profiling comprises capturing information about execution of threads in the particular transaction, and the other transaction is not profiled by the invoked profiler based on the transaction boundary. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18)
-
-
19. A non-transitory computer readable medium having program instructions stored therein, wherein the program instructions are executable by a computer system to perform operations comprising:
-
receiving transaction data from an agent instrumented on a particular software component in a system comprising a plurality of software components, wherein the transaction data identifies characteristics of a particular transaction involving the particular software component and another software component in the plurality of software components as observed by the agent during operation of the system, and the particular transaction is contemporaneous with another transaction involving software components in the system; determining, from the data, that the particular transaction falls within a defined transaction boundary for the system, wherein the transaction boundary defines a subset of all transactions of the system, transactions meeting a set of conditions fall within the transaction boundary, and the other transaction falls outside the transaction boundary; and causing a profiler to perform software profiling of a portion of a system during the particular transaction based on determining that the particular transaction falls within the transaction boundary, wherein the portion of the system comprises at least the particular software component, the software profiling comprises capturing information about execution of threads in the particular transaction, and the other transaction is not profiled by the profiler based on the transaction boundary.
-
-
20. A system comprising:
-
a data processor; a memory; a profiler; and an agent manager to; receive transaction data from an agent instrumented on a particular software component in a system comprising a plurality of software components, wherein the transaction data identifies characteristics of a particular transaction involving the particular software component and another software component in the plurality of software components as observed by the agent during operation of the system, and the particular transaction is contemporaneous with another transaction involving software components in the system; determine, from the data, that the particular transaction falls within a defined transaction boundary for the system, wherein the transaction boundary defines a subset of all transactions of the system, transactions meeting a set of conditions fall within the transaction boundary, and the other transaction falls outside the transaction boundary; and cause a profiler to perform software profiling of a portion of a system during the particular transaction based on determining that the particular transaction falls within the transaction boundary, wherein the portion of the system comprises at least the particular software component, the software profiling comprises capturing information about execution of threads in the particular transaction, and the other transaction is not profiled by the profiler based on the transaction boundary. - View Dependent Claims (21, 22)
-
Specification