Do you want to use our dedicated database agent or do you want to install the database extension for the machine agent? If you look for the first, you'll find the documentation here: https://docs.appdynamics.com/display/PRO43/Database+Visibility For the extension you need to configure the YAML file to point to your database and the path to the YAML in the monitor.xml.  Since this is an extension it will run with the privileges of the machine agent. So check that the files of the extension are readable by the user running the machine agent. ... View more

One possible root cause might be that you have enabled SSL in your configuration but you are talking to the default non-SSL port. Can you double-check your configuration if SSL is disabled? For mor details, have a look into the documentation: https://docs.appdynamics.com/display/PRO43/Java+Agent+Configuration+Properties#JavaAgentConfigurationProperties-SSLConfigurationProperties ... View more

What I see from your logfiles is that you get an 401 error "Unauthorized". This tells you that you have provided the wrong credentials. Looking at the top of your logfiles I see that you have provided the global account name, but for the app server agent you need the (non-global) account name, so in your case "customer1". ... View more

What I see from your console output, is, that you don't have configured the application, tier and node name: Full Agent Registration Info Resolver using application name [null] Full Agent Registration Info Resolver using tier name [unknown] Full Agent Registration Info Resolver using node name [null] Please check our configuration on the steps to configure the agent: https://docs.appdynamics.com/display/PRO43/Install+the+Java+Agent#InstalltheJavaAgent-ConfiguretheJavaAgent Regards, Severin ... View more