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

    Related pages:

    Your Rating:
    Results:
    1 Star2 Star3 Star4 Star5 Star
    31 rates
    Application Analytics can collect data from many sources in your AppDynamics APM Platform, as listed in this topic. 

    Transaction Analytics Data Sources

    Transaction Analytics data is collected by the AppDynamics Java, .NET, PHP and Node.js App Agents. Collecting Transaction Analytics data requires no change to your application code. You enable analytics on the app server agents and Controller you already use. 

    Once you have enabled analytics on your application, you can collect and analyze several kinds of data:

    • Default performance data collected by the app agents about your application's business transactions
    • HTTP-based data collected by HTTP data collectors
    • Custom data collected by method invocation data collectors
    • Business data collected from parameterized SQL calls

    To enable Transaction Analytics for your applications, see Collect Transaction Analytics Data.

    Log Data Sources

    You can collect Log Analytics data from many types of log files, including instrumented and non-instrumented applications as well as infrastructure. Log Analytics can be used as a standalone component. You can search and analyze log data just as you do transaction data. Log Analytics works by default with the syslog (log4j) format and can be configured for other log formats, including GZIP files (log files ending in .gz). You can capture other log formats by setting up regular-expression-based mapping. See Collect Log Analytics Data for details.

    You can view correlated Log and Transaction Analytics Data. By configuring business transaction GUID injection, you can see logs that are related to specific business transaction requests. For details on configuring GUID injection, see Business Transaction and Log Correlation.

    End User Monitoring Data Sources

    Analytics can also use data collected by Browser Real User MonitoringMobile Real User Monitoring and IoT Monitoring. Analytics makes the data available in a more flexible search format. If you have enabled Browser RUM, Mobile RUM or IoT Monitoring and enabled Analytics, you see these event types on the Analytics search page.

    For details on how analytics extends the capability of EUM, see the section "Browser Analyze versus Browser Request Analytics" in Browser RUM Analyze

    Browser Synthetic Data Sources

    Sessions data captured via Browser Synthetic Analytics is available in Analytics.

    Custom Event Sources

    You can add custom events for Analytics using the AppDynamics Analytics Events API.

    Hybrid Deployment Environments

    It is possible to create an environment where EUM data is collected in a SaaS deployment while the Controller on-premises, but it is not supported by Analytics. In this hybrid environment, Analytics metric queries do not work with EUM related data.