The instructions in this document are specific to AppDynamics versions 4.2.x and 4.3.x App Agent, Controller. and Analytics Agent. The instructions assume that Transaction Analytics has been enabled, like so:
If the analytic plugin (
analytics-dynamic-service-enabled) in the App Agent fails to connect to the Analytics Agent due to connectivity issues, or if the Analytics Agent is not running, then the plugin will keep attempting to connect to the Analytics Agent a number of times.
Until that time, the plugin will try to hold Transaction BT details in buffer. If the plugin cannot connect to the Analytics Agent, and the buffer holding the BT events is full, the buffer will drop the BT event details.
The following error message will be displayed in the logs:
ERROR Analytics - Transaction [/app/Health:92477754-7573-469c-8a4e-a37c7554db30] could not be saved. Internal buffers appear to be full
This means that when the Analytic Agent is not available, the App Agent will show error messages and the analytic plugin will assume that there is an issue with the Analytics Agent and shut off the component responsible for pushing the BT events data.
[appdynamics-analytics-writer1] WARN HttpSink - Error occurred while attempting to send data to [http://localhost:9090/v2/sinks/bt]. Retry attempts remaining  org.apache.http.conn.HttpHostConnectException: Connect to localhost:9090 [localhost/127.0.0.1] failed: Connection refused [appdynamics-analytics-writer0] 09 Oct 2017 22:19:18,480 FATAL SinkWriterTask - Stopping abruptly due to error org.apache.http.conn.HttpHostConnectException: Connect to localhost:9090 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused (Connection refused)
Note: In version 4.2.x, there is another option to reset the plugin. It is possible to toggle off & on the plugin property (
analytics-dynamic-service-enabled) from the UI. This option is not available in version 4.3.x.
[Thread-0] 04 Oct 2017 08:48:55,383 INFO AnnotationPropertyListenerManager - Propagating analytics-dynamic-service-enabled value true
analytics-dynamic-service-enablednode property to enable Transaction Analytics. Using the node property directly allowed for disabling and enabling the Analytics Dynamic Service at the application, tier, and node levels. The Analytics Configuration UI allows for setting this property only at the Application level. Therefore, Java Agents 4.3 and higher are not able to disable or enable the Analytics Dynamic Service at the tier and node levels.
analytics-dynamic-service-enabledproperty. Therefore, if you use one of these import mechanisms to enable or disable the Analytics Dynamic Service and you have a mixture of old (pre 4.3) and new (4.3 and higher) agents, you must manually set the associated property to match the Analytics Dynamic Service configuration value.
analytics-dynamic-service-enablednode property can also be set as part of the application import and has its own import REST API (accessed at
POST /setAgentProperty). See Import Application Analytics Dynamic Service Configuration at Configuration Import and Export API for more information.