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 |
|---|---|---|
| Application | Application name |
application
|
| Business Transaction | Business transaction name |
transactionName
|
| Error | Error details (deprecated) This field is replaced by the more granular fields: Error Code, Error Detail, and Error Type. |
deprecated
|
| 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. |
segments.errorList.errorCode
|
| Error Detail | This is what the "Error" field represented in 4.1. Primarily the error message |
segments.errorList.errorDetail
|
| 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. |
segments.errorList.errorType
|
| Node |
Node name |
segments.node
|
| Tier | Tier name |
segments.tier
|
| requestGUID | GUID for this specific user request as assigned by Splunk AppDynamics |
requestGUID
|
| Response Time (ms) | Business transaction response time for this request in milliseconds |
responseTime
|
| Timestamp | Time the event occurred in the application |
eventTimestamp
|
| User Experience | Indicates if the transaction was marked as Normal, Slow, Very Slow, Stall, or Error |
userExperience
|
| 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 Controller UI. Each UI presents an appropriate level of contextual visibility while preserving low overhead. For example, a snapshot may capture only the exit calls that are most pertinent to transaction performance. | Not Applicable |