An improper shut down of the Events Service and Elasticsearch processes causes them to leave
elasticsearch.id artifacts in your AppDynamics Event Service home directory. To resolve the issue, terminate the processes and delete the files. You will now be able to restart the Event Service. This issue generally occurs when a machine is crashed or a command, such as
kill -9, is used to forcefully terminate the processes.
If the Analytics Agent Java process is not shut down gracefully, it will leave an
analytics-agent.id artifact in your
analytics-agent directory. Delete this file and restart the Agent. This issue generally occurs when a machine crashes or a command, such as
kill -9, is used to forcefully terminate the process.
Double check the installation instructions to make sure you have set the correct property values, such as Name, Global Account Name and Access Key, and make sure the Analytics Agent can communicate with the necessary destinations (Controller and Events Service) and is not blocked by a firewall.
Make sure the authenticated user has the appropriate analytics permissions.
Make sure the user is appropriately licensed for Analytics.
Make sure you have enabled the selected application for analytics data collection.
Make sure you have selected the right Business Transactions.
Transaction Analytics is by default is enabled for Method Invocation Data Collector. However, make sure if it’s selected.
If you see a similar message to what’s shown in the image below, it is likely that you have installed the Analytics Agent on a downstream tier and not on the starting tier for those Business Transactions.
analytics-agent.logto ensure that no errors exist and the files are being read.