Transaction stitching definitions

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, from a plurality of agents instrumented on a plurality of software components, transaction data describing a plurality of transaction portions of a plurality of transactions involving the plurality of software components as observed by the plurality of agents, wherein the transaction data comprises a plurality of transaction data frames, and each of the transaction data frames describes attributes of a respective portion of a corresponding one of the plurality of transactions;
• determining a particular characteristic of a particular one of the plurality of transactions, wherein the particular transaction comprises a first one of the transaction portions and a second one of the transaction portions, and the particular characteristic is determined from the transaction data describing the particular transaction;
• determining that a user-defined stitching definition is to be used in lieu of a default stitching definition in determining a transaction path including the particular transaction, wherein the user-defined stitching definition is to be used to determine the transaction path for the particular transaction based on the particular characteristic, transaction paths of one or more other transactions in the plurality of transactions are to be determined based on the default stitching definition;
• determining a particular correlation between the first transaction portion and the second transaction portion based on the user-defined stitching definition;
• determining another correlation between another pair of transaction portions of the particular transaction based on the default stitching definition;
• determining a transaction path of the particular transaction based at least in part on the determined particular correlation and the other correlation, and at least one of the transaction portions in the transaction path comprises a transaction portion hidden from a user;
• and
• generating a test case based on the transaction path to test correct operation of a subset of the plurality of software components participating in a test instance of the particular transaction.

A system comprising:

• a data processor;
• a memory;
• a transaction path engine, executable to:
• access transaction data describing a plurality of transaction portions in a plurality of transactions involving a plurality of software components, wherein the transaction data comprises a plurality of transaction data frames, and each of the transaction data frames describes attributes of a respective portion of a corresponding one of the plurality of transactions;
• determine a particular characteristic of a particular one of the plurality of transactions, wherein the particular transaction comprises a first one of the transaction portions and a second one of the transaction portions, and the particular characteristic is determined from the transaction data describing the particular transaction;
• determine that a user-defined stitching definition is to be used in lieu of a default stitching definition in determining a transaction path for the particular transaction, wherein the user-defined stitching definition is to be used to determine the transaction path for the particular transaction based on the particular characteristic and transaction paths of one or more other transactions in the plurality of transactions are to be determined based on the default stitching definition;
• determine a particular correlation between the first transaction portion and the second transaction portion based on the user-defined stitching definition;
• and
• determine a transaction path of the particular transaction based at least in part on the determined particular correlation, and at least one of the transaction portions in the transaction path comprises a transaction portion hidden from a user;
• and
• a test case generator to generate a test case based on the transaction path to test correct operation of a subset of the plurality of software components participating in a test instance of the particular transaction.