AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.

    Skip to end of metadata
    Go to start of metadata

    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 NameDescriptionEvents Service Internal Name
    ApplicationApplication nameapplication
    Business TransactionBusiness transaction nametransactionName
    ErrorError details (deprecated) This field is replaced by the more granular fields: Error Code, Error Detail, and Error Type.deprecated
    Error CodeThe 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 DetailThis is what the "Error" field represented in 4.1. Primarily the error messagesegments.errorList.errorDetail
    Error TypeClassification 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 name

    TierTier namesegments.tier
    requestGUIDGUID for this specific user request as assigned by AppDynamicsrequestGUID
    Response Time (ms)Business transaction response time for this request in millisecondsresponseTime
    TimestampTime the event occurred in the applicationeventTimestamp
    User ExperienceIndicates if the transaction was marked as Normal, Slow, Very Slow, Stall, or ErroruserExperience
    Exit callsDetails 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:

    FieldEvents Service Database Name
    session IDsegments.httpData.sessionId
    session Objectssegments.httpData.sessionObjects
    URI path segments: segment0-nsegments.httpData.uriPathSegments

    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 segments.userData.cartTotal. 

    Deprecated Fields

    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 FieldDescriptionNew Field
    Request ExperienceIndicates if the transaction was marked as Normal, Slow, Very Slow, Stall, or ErrorUser Experience
    Transaction TimeBusiness transaction response time for this request in millisecondsResponse Time