Each instance of a business transaction passing through a single tier is an event, so the data associated with a single execution of a distributed business transaction (for example, Checkout) is stored as a series of events in Analytics. The data consists of the default transaction data and additional data from data collectors configured for that transaction. This data is organized and stored per business transaction.
Default Transaction Data
Event Type: transactions
Key (event type identifier): application
The following table lists the data collected by default for each instance of the business transactions that are enabled for Analytics. The table also lists the Events Service internal name. When accessing the data using ADQL queries, you need to use the Events Service internal name in the query.
|UI Field Name||Description||Events Service Internal Name|
|Business Transaction||Business transaction name|
|Error||Error details (deprecated) This field is replaced by the more granular fields: Error Code, Error Detail, and Error Type.|
|Error Code||The value of this field depends on the Error Type. For example, if Error Type is an HTTP_Error_code, then the value is a string representing the corresponding HTTP error code such as 404, 503 and so on.|
|Error Detail||This is what the "Error" field represented in 4.1. Primarily the error message|
|Error Type||Classification of errors into buckets done internally by the Agent. For example, the error type could be HTTP_ERROR_CODE, LOGGER_MESSAGE, THROWABLE and so on.|
|requestGUID||GUID for this specific user request as assigned by AppDynamics|
|Response Time (ms)||Business transaction response time for this request in milliseconds|
|Timestamp||Time the event occurred in the application|
|User Experience||Indicates if the transaction was marked as Normal, Slow, Very Slow, Stall, or Error|
|Exit calls||Details of database and remote service calls. View Details flow map. Note that for partial snapshots, exit call information captured in call graphs can differ between the Analytics and APM UI. Each UI presents an appropriate level of contextual visibility while preserving low overhead. An APM snapshot, for example, may capture only the exit calls that are most pertinent to transaction performance.||Not Applicable|
Custom HTTP Request Data
When HTTP data collectors are configured, the following information can be collected:
|Field||Events Service Database Name|
|URI path segments: segment0-n|
Analytics uses the configured display name as the field name for the HTTP parameters. In Controller versions prior to 4.3, Analytics displayed the data using the actual parameter name.
Custom Method Data
Custom data collected as specified in the method invocation data collector configuration. See Data Collectors for more details.
To specify a custom data field when using the Analytics query APIs, prefix the field name with
segments.userData. For example, if your field is cartTotal, such as shown in the following screenshot, the database name is
AppDynamics deprecated the
Request Experience and
Transaction Time for Analytics Agents 4.2.x and later. Both fields are replaced with new fields as shown:
|Deprecated Field||Description||New Field|
|Request Experience||Indicates if the transaction was marked as Normal, Slow, Very Slow, Stall, or Error||User Experience|
|Transaction Time||Business transaction response time for this request in milliseconds||Response Time|